Re: [RESEND][PATCH 3/3] usb.c: Add a retry in the usb_prepare_device()

2020-08-18 Thread Marek Vasut
On 8/18/20 8:01 PM, Jason Wessel wrote: >>From the Raspberry Pi3 - With the patch removed: > > U-Boot> setenv usb_pgood_delay 2000 > U-Boot> usb reset > resetting USB... > Bus usb@7e98: USB DWC2 > scanning bus usb@7e98 for devices... unable to get device descriptor > (error=-22) > 6 USB D

Re: [RESEND][PATCH 3/3] usb.c: Add a retry in the usb_prepare_device()

2020-08-18 Thread Jason Wessel
>From the Raspberry Pi3 - With the patch removed: U-Boot> setenv usb_pgood_delay 2000 U-Boot> usb reset resetting USB... Bus usb@7e98: USB DWC2 scanning bus usb@7e98 for devices... unable to get device descriptor (error=-22) 6 USB Device(s) found scanning usb for storage devices...

Re: [RESEND][PATCH 3/3] usb.c: Add a retry in the usb_prepare_device()

2020-08-18 Thread Marek Vasut
On 8/18/20 4:34 PM, Jason Wessel wrote: > I have found through testing some USB 2 composite mouse/keyboard > devices do not response to the usb_set_address call immediately > following the port reset. It can take anywhere from 2ms to 20ms. Does it work if you do => setenv usb_pgood_delay 2000 b

[RESEND][PATCH 3/3] usb.c: Add a retry in the usb_prepare_device()

2020-08-18 Thread Jason Wessel
I have found through testing some USB 2 composite mouse/keyboard devices do not response to the usb_set_address call immediately following the port reset. It can take anywhere from 2ms to 20ms. This patch adds a retry and delay for usb_prepare_device() and allows all the USB keyboards I tried to