From: Andrzej Pietrasiewicz <andrzej.p@collabora.com>
To: "Paul Cercueil" <paul@crapouillou.net>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Christian König" <christian.koenig@amd.com>
Cc: michael.hennerich@analog.com, nuno.sa@analog.com,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org,
linaro-mm-sig@lists.linaro.org
Subject: Re: [PATCH v2 0/3] usb: gadget: functionfs: DMABUF import interface
Date: Fri, 31 Mar 2023 11:40:58 +0200 [thread overview]
Message-ID: <c6ce737d-25cc-7f22-7c0f-c0ba1420e57d@collabora.com> (raw)
In-Reply-To: <20230322092118.9213-1-paul@crapouillou.net>
Hi Paul,
W dniu 22.03.2023 o 10:21, Paul Cercueil pisze:
> Hi,
>
> This small patchset adds three new IOCTLs that can be used to attach,
> detach, or transfer from/to a DMABUF object.
>
> Changes since v1:
> - patch [2/3] is new. I had to reuse a piece of code that was already
> duplicated in the driver, so I factorized the code.
> - Make ffs_dma_resv_lock() static
> - Add MODULE_IMPORT_NS(DMA_BUF);
> - The attach/detach functions are now performed without locking the
> eps_lock spinlock. The transfer function starts with the spinlock
> unlocked, then locks it before allocating and queueing the USB
> transfer.
>
Can you share an example use case for these new features?
Is there a userspace that excercises the new ioctls?
Regards,
Andrzej
next prev parent reply other threads:[~2023-03-31 9:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 9:21 Paul Cercueil
2023-03-22 9:21 ` [PATCH v2 1/3] usb: gadget: Support already-mapped DMA SGs Paul Cercueil
2023-03-22 9:21 ` [PATCH v2 2/3] usb: gadget: functionfs: Factorize wait-for-endpoint code Paul Cercueil
2023-03-22 9:21 ` [PATCH v2 3/3] usb: gadget: functionfs: Add DMABUF import interface Paul Cercueil
2023-03-31 9:40 ` Andrzej Pietrasiewicz [this message]
2023-04-01 14:31 ` [PATCH v2 0/3] usb: gadget: functionfs: " Paul Cercueil
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=c6ce737d-25cc-7f22-7c0f-c0ba1420e57d@collabora.com \
--to=andrzej.p@collabora.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=michael.hennerich@analog.com \
--cc=nuno.sa@analog.com \
--cc=paul@crapouillou.net \
--cc=sumit.semwal@linaro.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®