Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-13.5 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_CR_TRAILER,INCLUDES_PATCH, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 17E4BC433DB for ; Fri, 26 Feb 2021 10:35:09 +0000 (UTC) Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 9B87464F03 for ; Fri, 26 Feb 2021 10:35:08 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 9B87464F03 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=linuxfoundation.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=dri-devel-bounces@lists.freedesktop.org Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id BE8966EDBD; Fri, 26 Feb 2021 10:35:07 +0000 (UTC) Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by gabe.freedesktop.org (Postfix) with ESMTPS id 85C616EDBD for ; Fri, 26 Feb 2021 10:35:06 +0000 (UTC) Received: by mail.kernel.org (Postfix) with ESMTPSA id 969EA64EFA; Fri, 26 Feb 2021 10:35:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1614335706; bh=z+qgGB7+6MVl+isAgLsv90QpIbve0M/3vwf8t2X3a4s=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=t9NLzqZPvHxyD+pfnYRKni0KrXLpHoPfh6YJ14o4YA7IyjQAiPvjQkdKjHGyxsBti k/3qMZ2CcV32zlY7LraeM73UY+lTK2HEmieA0+3yuvWlxdFkbue/3UEboDXK4c9Ct4 mVjUTeKCEf0/MFkN9Bp3I8LvXzINHSIWIWj8GlP0= Date: Fri, 26 Feb 2021 11:35:03 +0100 From: Greg KH To: Thomas Zimmermann Subject: Re: [PATCH v5] drm: Use USB controller's DMA mask when importing dmabufs Message-ID: References: <20210226092648.4584-1-tzimmermann@suse.de> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-BeenThere: dri-devel@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Direct Rendering Infrastructure - Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: airlied@linux.ie, Daniel Vetter , dri-devel@lists.freedesktop.org, christian.koenig@amd.com, hdegoede@redhat.com, stern@rowland.harvard.edu, stable@vger.kernel.org, Pavel Machek , sean@poorly.run, Christoph Hellwig Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" On Fri, Feb 26, 2021 at 11:29:05AM +0100, Thomas Zimmermann wrote: > Hi > = > Am 26.02.21 um 11:19 schrieb Greg KH: > > On Fri, Feb 26, 2021 at 10:26:47AM +0100, Thomas Zimmermann wrote: > > > USB devices cannot perform DMA and hence have no dma_mask set in their > > > device structure. Therefore importing dmabuf into a USB-based driver > > > fails, which breaks joining and mirroring of display in X11. > > > = > > > For USB devices, pick the associated USB controller as attachment dev= ice. > > > This allows the DRM import helpers to perform the DMA setup. If the D= MA > > > controller does not support DMA transfers, we're out of luck and cann= ot > > > import. Our current USB-based DRM drivers don't use DMA, so the actual > > > DMA device is not important. > > > = > > > Drivers should use DRM_GEM_SHMEM_DROVER_OPS_USB to initialize their > > > instance of struct drm_driver. > > > = > > > Tested by joining/mirroring displays of udl and radeon un der Gnome/X= 11. > > > = > > > v5: > > > * provide a helper for USB interfaces (Alan) > > > * add FIXME item to documentation and TODO list (Daniel) > > > v4: > > > * implement workaround with USB helper functions (Greg) > > > * use struct usb_device->bus->sysdev as DMA device (Takashi) > > > v3: > > > * drop gem_create_object > > > * use DMA mask of USB controller, if any (Daniel, Christian, Noralf) > > > v2: > > > * move fix to importer side (Christian, Daniel) > > > * update SHMEM and CMA helpers for new PRIME callbacks > > > = > > > Signed-off-by: Thomas Zimmermann > > > Fixes: 6eb0233ec2d0 ("usb: don't inherity DMA properties for USB devi= ces") > > > Tested-by: Pavel Machek > > > Acked-by: Christian K=F6nig > > > Acked-by: Daniel Vetter > > > Cc: Christoph Hellwig > > > Cc: Greg Kroah-Hartman > > > Cc: # v5.10+ > > > --- > > > Documentation/gpu/todo.rst | 15 ++++++++++ > > > drivers/gpu/drm/drm_prime.c | 45 +++++++++++++++++++++++++++= +++ > > > drivers/gpu/drm/tiny/gm12u320.c | 2 +- > > > drivers/gpu/drm/udl/udl_drv.c | 2 +- > > > drivers/usb/core/usb.c | 31 ++++++++++++++++++++ > > > include/drm/drm_gem_shmem_helper.h | 16 +++++++++++ > > > include/drm/drm_prime.h | 5 ++++ > > > include/linux/usb.h | 24 ++++++++++++++++ > > > 8 files changed, 138 insertions(+), 2 deletions(-) > > > = > > > diff --git a/Documentation/gpu/todo.rst b/Documentation/gpu/todo.rst > > > index f872d3d33218..c185e0a2951e 100644 > > > --- a/Documentation/gpu/todo.rst > > > +++ b/Documentation/gpu/todo.rst > > > @@ -617,6 +617,21 @@ Contact: Daniel Vetter > > > Level: Intermediate > > > +Remove automatic page mapping from dma-buf importing > > > +---------------------------------------------------- > > > + > > > +When importing dma-bufs, the dma-buf and PRIME frameworks automatica= lly map > > > +imported pages into the importer's DMA area. This is a problem for U= SB devices, > > > +which do not support DMA operations. By default, importing fails for= USB > > > +devices. USB-based drivers work around this problem by employing > > > +drm_gem_prime_import_usb(). To fix the issue, automatic page mapping= s should > > > +be removed from the buffer-sharing code. > > > + > > > +Contact: Thomas Zimmermann , Daniel Vetter > > > + > > > +Level: Advanced > > > + > > > + > > > Better Testing > > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > diff --git a/drivers/gpu/drm/drm_prime.c b/drivers/gpu/drm/drm_prime.c > > > index 2a54f86856af..59013bb1cd4b 100644 > > > --- a/drivers/gpu/drm/drm_prime.c > > > +++ b/drivers/gpu/drm/drm_prime.c > > > @@ -29,6 +29,7 @@ > > > #include > > > #include > > > #include > > > +#include > > > #include > > > #include > > > @@ -1055,3 +1056,47 @@ void drm_prime_gem_destroy(struct drm_gem_obje= ct *obj, struct sg_table *sg) > > > dma_buf_put(dma_buf); > > > } > > > EXPORT_SYMBOL(drm_prime_gem_destroy); > > > + > > > +/** > > > + * drm_gem_prime_import_usb - helper library implementation of the i= mport callback for USB devices > > > + * @dev: drm_device to import into > > > + * @dma_buf: dma-buf object to import > > > + * > > > + * This is an implementation of drm_gem_prime_import() for USB-based= devices. > > > + * USB devices cannot perform DMA directly. This function selects th= e USB host > > > + * controller as DMA device instead. Drivers can use this as their > > > + * &drm_driver.gem_prime_import implementation. > > > + * > > > + * See also drm_gem_prime_import(). > > > + * > > > + * FIXME: The dma-buf framework expects to map the exported pages in= to > > > + * the importer's DMA area. USB devices don't support DMA, and > > > + * importing would fail. Foir the time being, this function p= rovides > > > + * a workaround by using the USB controller's DMA area. The r= eal > > > + * solution is to remove page-mapping operations from the dma= -buf > > > + * framework. > > > + * > > > + * Returns: A GEM object on success, or a pointer-encoder errno valu= e otherwise. > > > + */ > > > +#ifdef CONFIG_USB > > > +struct drm_gem_object *drm_gem_prime_import_usb(struct drm_device *d= ev, > > > + struct dma_buf *dma_buf) > > > +{ > > > + struct device *dmadev; > > > + struct drm_gem_object *obj; > > > + > > > + if (!dev_is_usb(dev->dev)) > > > + return ERR_PTR(-ENODEV); > > = > > I have resisted the "dev_is_*()" type of function for USB for a long > > time now, and I really don't want to add it now. > > = > > The driver core explicitly was not created with RTI (run type > > identification), but over time it has been slowly added on a per-bus > > basis for various reasons, some good and others not good. > > = > > In this function, why would a drm device that was NOT a usb device ever > > call it? Because of that, I don't think dev_is_usb() is needed at all, > > just don't call this function unless it really is a USB device. > = > It was simply a safety measure. There's really no reason a non-USB device > would ever call this function. So not using dev_is_usb() is fine. It'll be > gone in v6. Great, thanks! Other than that, and the documentation comment I made, looks semi-sane to me. greg k-h _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel