diff options
| author | Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com> | 2026-07-30 16:05:13 +0300 |
|---|---|---|
| committer | Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com> | 2026-09-14 00:11:24 +0300 |
| commit | ea9dadeac79cef509a4b8b4a3e3b39a741e63313 (patch) | |
| tree | f61111b7e530d5e05dcc551fa386a2f10c7f9826 /tools/perf/scripts/python/bin/stackcollapse-report | |
| parent | ba970587a0e1203b6a0934b5b9174886b4c4d24c (diff) | |
| download | linux-next-ea9dadeac79cef509a4b8b4a3e3b39a741e63313.tar.gz linux-next-ea9dadeac79cef509a4b8b4a3e3b39a741e63313.zip | |
drm/msm: mark the fbdev framebuffer as system memory
msm_fbdev_driver_fbdev_probe() points screen_buffer at a kernel virtual
mapping of the GEM object and uses the deferred sysmem fb ops, but never
sets FBINFO_VIRTFB. The framebuffer core then assumes the memory is not
in the virtual address space and warns on the first console draw:
fb0: sys_fillrect: framebuffer is not in virtual address space.
The drm_fbdev_dma, drm_fbdev_shmem and drm_fbdev_ttm helpers all set the
flag for system memory. Do the same here.
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Assisted-by: Claude:claude-opus-5
Patchwork: https://patchwork.freedesktop.org/patch/743293/
Link: https://lore.kernel.org/r/20260730-drm-msm-fbinfo-virt-v1-1-a27099a6dc58@oss.qualcomm.com
Acked-by: Rob Clark <robin.clark@oss.qualcomm.com> # on IRC
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-report')
0 files changed, 0 insertions, 0 deletions