[PATCH 22/22] usb: document that URB transfer_buffer should be aligned
Mauro Carvalho Chehab
mchehab at s-opensource.com
Thu Mar 30 05:37:16 PDT 2017
Em Thu, 30 Mar 2017 15:05:30 +0300
Laurent Pinchart <laurent.pinchart at ideasonboard.com> escreveu:
> Hi Mauro,
> On Thursday 30 Mar 2017 07:28:00 Mauro Carvalho Chehab wrote:
> > Em Thu, 30 Mar 2017 12:34:32 +0300 Laurent Pinchart escreveu:
> > > On Thursday 30 Mar 2017 10:11:31 Oliver Neukum wrote:
> > >> Am Donnerstag, den 30.03.2017, 01:15 +0300 schrieb Laurent Pinchart:
> > >>>> + may also override PAD bytes at the end of the
> > >>>> ``transfer_buffer``, up to the
> > >>>> + size of the CPU word.
> > >>>
> > >>> "May" is quite weak here. If some host controller drivers require
> > >>> buffers to be aligned, then it's an API requirement, and all buffers
> > >>> must be aligned. I'm not even sure I would mention that some host
> > >>> drivers require it, I think we should just state that the API requires
> > >>> buffers to be aligned.
> > >>
> > >> That effectively changes the API. Many network drivers are written with
> > >> the assumption that any contiguous buffer is valid. In fact you could
> > >> argue that those drivers are buggy and must use bounce buffers in those
> > >> cases.
> > Blaming the dwc2 driver was my first approach, but such patch got nacked ;)
> > Btw, the dwc2 driver has a routine that creates a temporary buffer if the
> > buffer pointer is not DWORD aligned. My first approach were to add
> > a logic there to also use the temporary buffer if the buffer size is
> > not DWORD aligned:
> > https://patchwork.linuxtv.org/patch/40093/
> > While debugging this issue, I saw *a lot* of network-generated URB
> > traffic from RPi3 Ethernet port drivers that were using non-aligned
> > buffers and were subject to the temporary buffer conversion.
> > My understanding here is that having a temporary bounce buffer sucks,
> > as the performance and latency are affected. So, I see the value of
> > adding this constraint to the API, pushing the task of getting
> > aligned buffers to the USB drivers,
> This could however degrade performances when the HCD can handle unaligned
No, it won't degrade performance out there, except if the driver
would need to do double buffering due to such constraint.
It will just waste memory.
> > but you're right: that means a lot of work, as all USB drivers should be
> > reviewed.
> If we decide in the end to push the constraint on the USB device driver side,
> then the dwc2 HCD driver should return an error when the buffer isn't
> correctly aligned.
Yeah, with such constraint, either the HCD drivers or the USB core
There is another option: to add a field, filled by te USB driver,
telling the core that the buffer is aligned, e. g. drivers would
be doing something like:
urb->transfer_buffer_align = 4;
Something similar could be filled by the HCD driver:
hc_driver->transfer_buffer_align = 4;
The core will then check if the alignment required by the HCD driver
is compatible with the buffer alignment ensured by the USB driver.
If it doesn't, then the core would create a temporary buffer for the
No idea about how easy/hard would be to implement something like
In such case, it could make sense to generate a warning that
the driver should be fixed, or that the performance would
decrease due to double-buffering.
More information about the linux-rpi-kernel