diff options
| author | Leon Romanovsky <leonro@nvidia.com> | 2026-01-24 21:14:15 +0200 |
|---|---|---|
| committer | Christian König <christian.koenig@amd.com> | 2026-01-27 10:45:11 +0100 |
| commit | 609fc8766d68da10697e1df0514d079d54bf48df (patch) | |
| tree | 6dbd89934d9357f5f80d0adffa01b66daa719e95 /drivers/gpu/drm/xe/xe_dma_buf.c | |
| parent | 95308225e5baeaae1e313816059c59a0036ab6b2 (diff) | |
| download | linux-next-609fc8766d68da10697e1df0514d079d54bf48df.tar.gz linux-next-609fc8766d68da10697e1df0514d079d54bf48df.zip | |
dma-buf: Always build with DMABUF_MOVE_NOTIFY
DMABUF_MOVE_NOTIFY was introduced in 2018 and has been marked as
experimental and disabled by default ever since. Six years later,
all new importers implement this callback.
It is therefore reasonable to drop CONFIG_DMABUF_MOVE_NOTIFY and
always build DMABUF with support for it enabled.
Suggested-by: Christian König <christian.koenig@amd.com>
Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
Reviewed-by: Christian König <christian.koenig@amd.com>
Link: https://lore.kernel.org/r/20260124-dmabuf-revoke-v5-3-f98fca917e96@nvidia.com
Signed-off-by: Christian König <christian.koenig@amd.com>
Diffstat (limited to 'drivers/gpu/drm/xe/xe_dma_buf.c')
| -rw-r--r-- | drivers/gpu/drm/xe/xe_dma_buf.c | 12 |
1 files changed, 4 insertions, 8 deletions
diff --git a/drivers/gpu/drm/xe/xe_dma_buf.c b/drivers/gpu/drm/xe/xe_dma_buf.c index 2e167b29d0c9..4e3a968bc6a0 100644 --- a/drivers/gpu/drm/xe/xe_dma_buf.c +++ b/drivers/gpu/drm/xe/xe_dma_buf.c @@ -56,14 +56,10 @@ static int xe_dma_buf_pin(struct dma_buf_attachment *attach) bool allow_vram = true; int ret; - if (!IS_ENABLED(CONFIG_DMABUF_MOVE_NOTIFY)) { - allow_vram = false; - } else { - list_for_each_entry(attach, &dmabuf->attachments, node) { - if (!attach->peer2peer) { - allow_vram = false; - break; - } + list_for_each_entry(attach, &dmabuf->attachments, node) { + if (!attach->peer2peer) { + allow_vram = false; + break; } } |