Re: [PATCH 0/2] USB fixes: (Re)implement timeouts

2023-10-29 Thread Marek Vasut
On 10/29/23 08:36, Hector Martin wrote: A long time ago, the USB code was interrupt-driven and used top-level timeout handling. This has long been obsolete, and that code is just broken dead cruft. HC drivers instead hardcode timeouts today. We need to be able to specify timeouts explicitly to

Re: [PATCH 0/2] USB fixes: (Re)implement timeouts

2023-10-29 Thread Neal Gompa
On Sun, Oct 29, 2023 at 3:36 AM Hector Martin wrote: > > A long time ago, the USB code was interrupt-driven and used top-level > timeout handling. This has long been obsolete, and that code is just > broken dead cruft. HC drivers instead hardcode timeouts today. > > We need to be able to specify

[PATCH 0/2] USB fixes: (Re)implement timeouts

2023-10-29 Thread Hector Martin
A long time ago, the USB code was interrupt-driven and used top-level timeout handling. This has long been obsolete, and that code is just broken dead cruft. HC drivers instead hardcode timeouts today. We need to be able to specify timeouts explicitly to handle cases like USB hard disks spinning