Re: [PATCH v3 1/3] drm/shmem-helper: Import dmabuf without mapping its sg_table

Hi Am 07.05.25 um 11:47 schrieb oushixiong1...@163.com: From: Shixiong Ou [WHY] 1. Drivers using DRM_GEM_SHADOW_PLANE_HELPER_FUNCS and DRM_GEM_SHMEM_DRIVER_OPS (e.g., udl, ast) do not require sg_table import. They only need dma_buf_vmap() to access the shared buffer's kernel vi

Re: [PATCH v3 1/3] drm/shmem-helper: Import dmabuf without mapping its sg_table

On 5/7/25 11:47, oushixiong1...@163.com wrote: > From: Shixiong Ou > > [WHY] > 1. Drivers using DRM_GEM_SHADOW_PLANE_HELPER_FUNCS and >DRM_GEM_SHMEM_DRIVER_OPS (e.g., udl, ast) do not require >sg_table import. >They only need dma_buf_vmap() to access the shared buffer's >kernel vi

[PATCH v3 1/3] drm/shmem-helper: Import dmabuf without mapping its sg_table

From: Shixiong Ou [WHY] 1. Drivers using DRM_GEM_SHADOW_PLANE_HELPER_FUNCS and DRM_GEM_SHMEM_DRIVER_OPS (e.g., udl, ast) do not require sg_table import. They only need dma_buf_vmap() to access the shared buffer's kernel virtual address. 2. On certain Aspeed-based boards, a dma_mask o