From: Thomas Zimmermann <tzimmermann@suse.de>
To: Christoph Hellwig <hch@lst.de>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Daniel Vetter <daniel@ffwll.ch>,
David Airlie <airlied@redhat.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
USB list <linux-usb@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Regression: 6eb0233ec2d0 ("usb: don't inherity DMA properties for USB devices")
Date: Thu, 18 Feb 2021 16:21:26 +0100 [thread overview]
Message-ID: <ef51698a-cd93-47b3-b79f-8c86a4c215fc@suse.de> (raw)
In-Reply-To: <20210218150746.GA18220@lst.de>
[-- Attachment #1.1: Type: text/plain, Size: 916 bytes --]
Hi
Am 18.02.21 um 16:07 schrieb Christoph Hellwig:
> On Thu, Feb 18, 2021 at 03:56:00PM +0100, Thomas Zimmermann wrote:
>> I only have udl devices, but I expect that other DRM USB adapters are also
>> affected.
>
> Find where the driver calls dma_map_* itself instead of using the USB
> wrappers and fix that..
>
Sure, it's at [1]. For udl, the dmabuf would need to be in system
memory. The driver creates urbs from the framebuffer content and sends
them to the device for displaying.
My question is more: what's the best interface to do this? Is there
example code somewhere?
Best regards
Thomas
[1]
https://elixir.bootlin.com/linux/v5.11/source/drivers/gpu/drm/drm_prime.c#L630
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Felix Imendörffer
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2021-02-18 18:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-18 14:56 Thomas Zimmermann
2021-02-18 15:07 ` Christoph Hellwig
2021-02-18 15:21 ` Thomas Zimmermann [this message]
2021-02-18 15:24 ` Christoph Hellwig
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=ef51698a-cd93-47b3-b79f-8c86a4c215fc@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@redhat.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®