From: "Maxime Ripard" <mripard@kernel.org>
To: "Thomas Zimmermann" <tzimmermann@suse.de>
Cc: admin@kodeit.net, airlied@gmail.com, airlied@redhat.com,
christian.koenig@amd.com, dri-devel@lists.freedesktop.org,
gargaditya08@live.com, hdegoede@redhat.com,
jani.nikula@intel.com, javierm@redhat.com,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
sean@poorly.run, simona@ffwll.ch, sumit.semwal@linaro.org,
"Maxime Ripard" <mripard@kernel.org>
Subject: Re: [PATCH v2 1/5] drm/prime: Support dedicated DMA device for dma-buf imports
Date: Fri, 07 Mar 2025 13:03:04 +0000 [thread overview]
Message-ID: <27c8aaa39d53c4af0328442662f966be@kernel.org> (raw)
In-Reply-To: <20250307080836.42848-2-tzimmermann@suse.de>
On Fri, 7 Mar 2025 09:03:59 +0100, Thomas Zimmermann wrote:
> Importing dma-bufs via PRIME requires a DMA-capable device. Devices on
> peripheral busses, such as USB, often cannot perform DMA by themselves.
> Without DMA-capable device PRIME import fails. DRM drivers for USB
> devices already use a separate DMA device for dma-buf imports. Make the
> mechanism generally available.
>
> [ ... ]
Reviewed-by: Maxime Ripard <mripard@kernel.org>
Thanks!
Maxime
next prev parent reply other threads:[~2025-03-07 13:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 8:03 [PATCH v2 0/5] drm: Provide a dedicated DMA device for PRIME import Thomas Zimmermann
2025-03-07 8:03 ` [PATCH v2 1/5] drm/prime: Support dedicated DMA device for dma-buf imports Thomas Zimmermann
2025-03-07 12:45 ` Jani Nikula
2025-03-07 13:03 ` Maxime Ripard [this message]
2025-03-07 8:04 ` [PATCH v2 2/5] drm/appletbdrm: Set struct drm_device.dma_dev Thomas Zimmermann
2025-03-07 11:14 ` Aditya Garg
2025-03-07 8:04 ` [PATCH v2 3/5] drm/gm12u320: " Thomas Zimmermann
2025-03-07 8:04 ` [PATCH v2 4/5] drm/gud: " Thomas Zimmermann
2025-03-07 8:04 ` [PATCH v2 5/5] drm/udl: " Thomas Zimmermann
2025-03-07 12:50 ` [PATCH v2 0/5] drm: Provide a dedicated DMA device for PRIME import Jani Nikula
2025-03-07 13:32 ` Simona Vetter
2025-03-10 9:50 ` Thomas Zimmermann
2025-03-10 10:04 ` Thomas Zimmermann
2025-03-10 13:56 ` Christian König
2025-03-10 14:30 ` Thomas Zimmermann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=27c8aaa39d53c4af0328442662f966be@kernel.org \
--to=mripard@kernel.org \
--cc=admin@kodeit.net \
--cc=airlied@gmail.com \
--cc=airlied@redhat.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gargaditya08@live.com \
--cc=hdegoede@redhat.com \
--cc=jani.nikula@intel.com \
--cc=javierm@redhat.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=sean@poorly.run \
--cc=simona@ffwll.ch \
--cc=sumit.semwal@linaro.org \
--cc=tzimmermann@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.