From: Greg KH <gregkh@linuxfoundation.org>
To: Hans de Goede <hansg@kernel.org>
Cc: Xu Yang <xu.yang_2@nxp.com>,
ezequiel@vanguardiasur.com.ar, mchehab@kernel.org,
laurent.pinchart@ideasonboard.com, hdegoede@redhat.com,
mingo@kernel.org, tglx@linutronix.de,
andriy.shevchenko@linux.intel.com, viro@zeniv.linux.org.uk,
thomas.weissschuh@linutronix.de, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
imx@lists.linux.dev, jun.li@nxp.com
Subject: Re: [PATCH v5 0/3] add dma noncoherent API
Date: Wed, 9 Jul 2025 12:12:45 +0200 [thread overview]
Message-ID: <2025070932-stifle-squabble-6042@gregkh> (raw)
In-Reply-To: <78b86f34-6477-436a-b59c-b0ae5371f581@kernel.org>
On Mon, Jul 07, 2025 at 12:02:41PM +0200, Hans de Goede wrote:
> Hi all,
>
> On 4-Jul-25 11:57, Xu Yang wrote:
> > On architectures where there is no coherent caching such as ARM it's
> > proved that using dma_alloc_noncontiguous API and handling manually
> > the cache flushing will significantly improve performance.
> >
> > Refer to:
> > commit 20e1dbf2bbe2 ("media: uvcvideo: Use dma_alloc_noncontiguous API")
> > commit 68d0c3311ec1 ("media: stk1160: use dma_alloc_noncontiguous API")
> >
> > However, it's obvious that there is significant code duplication between
> > these two commits. Besides, a potential user USB Monitor may read outdated
> > data before the driver do DMA sync for CPU which will make the data
> > unreliable.
> >
> > To reduce code duplication and avoid USB Monitor result unreliable, this
> > series will introduce DMA noncoherent API to USB core. And the USB core
> > layer will manage synchronization itself.
> >
> > Then the last 2 patches have used the API.
> >
> > I have tested uvcvideo driver. But I haven't tested stk1160 driver as I
> > don't have such boards. @Ezequiel Garcia, @Dafna Hirschfeld do you have
> > time to test it? Your support on this would be greatly appreciated.
>
> It seems that patches 1 + 2 are ready for merging now
> (for patch 3 we should probably wait for testing).
>
> I think that it would be best for both patches 1 + 2 to
> be merged through the USB tree. The changed code in the UVC
> driver is not touched that often so I do not expect any
> conflicts.
Ok, thanks, I'll take them through the USB tree now.
greg k-h
prev parent reply other threads:[~2025-07-09 10:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-04 9:57 [PATCH v5 0/3] add dma noncoherent API Xu Yang
2025-07-04 9:57 ` [PATCH v5 1/3] usb: core: add dma-noncoherent buffer alloc and free API Xu Yang
2025-07-04 13:51 ` Alan Stern
2025-07-04 9:57 ` [PATCH v5 2/3] media: uvcvideo: use usb_alloc_noncoherent/usb_free_noncoherent() Xu Yang
2025-07-07 9:50 ` Hans de Goede
2025-07-04 9:57 ` [PATCH v5 3/3] media: stk1160: " Xu Yang
2025-07-07 10:00 ` Hans de Goede
2025-07-07 10:02 ` [PATCH v5 0/3] add dma noncoherent API Hans de Goede
2025-07-09 10:12 ` Greg KH [this message]
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=2025070932-stifle-squabble-6042@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=hansg@kernel.org \
--cc=hdegoede@redhat.com \
--cc=imx@lists.linux.dev \
--cc=jun.li@nxp.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=thomas.weissschuh@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
--cc=xu.yang_2@nxp.com \
/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