Re: [U-Boot] [RFC PATCH] usb: ehci: do not invalidate a NULL buffer

2017-11-21 Thread Marek Vasut
On 11/21/2017 07:30 AM, Dirk Behme wrote: > On 17.11.2017 16:04, Marek Vasut wrote: >> On 11/17/2017 03:28 PM, Dirk Behme wrote: >>> Its a valid use case to call ehci_submit_async() with a NULL buffer >>> with length 0. E.g. from usb_set_configuration(). >>> >>> As invalidate_dcache_range() isn't a

Re: [U-Boot] [RFC PATCH] usb: ehci: do not invalidate a NULL buffer

2017-11-21 Thread Dirk Behme
On 17.11.2017 16:04, Marek Vasut wrote: On 11/17/2017 03:28 PM, Dirk Behme wrote: Its a valid use case to call ehci_submit_async() with a NULL buffer with length 0. E.g. from usb_set_configuration(). As invalidate_dcache_range() isn't able to judge if the address NULL is valid or not (depending

Re: [U-Boot] [RFC PATCH] usb: ehci: do not invalidate a NULL buffer

2017-11-17 Thread Marek Vasut
On 11/17/2017 03:28 PM, Dirk Behme wrote: > Its a valid use case to call ehci_submit_async() with a NULL buffer > with length 0. E.g. from usb_set_configuration(). > > As invalidate_dcache_range() isn't able to judge if the address > NULL is valid or not (depending on the SoC hardware configuratio

[U-Boot] [RFC PATCH] usb: ehci: do not invalidate a NULL buffer

2017-11-17 Thread Dirk Behme
Its a valid use case to call ehci_submit_async() with a NULL buffer with length 0. E.g. from usb_set_configuration(). As invalidate_dcache_range() isn't able to judge if the address NULL is valid or not (depending on the SoC hardware configuration it might be valid) do the check in ehci_submit_asy