Hi Geert-san,
> From: Geert Uytterhoeven
> Sent: Monday, April 25, 2016 11:57 PM
>
> Hi Shimoda-san,
>
> On Thu, Apr 21, 2016 at 2:57 PM, Geert Uytterhoeven
> <geert@xxxxxxxxxxxxxx> wrote:
> > On Thu, Apr 21, 2016 at 12:27 PM, Yoshihiro Shimoda
> > <yoshihiro.shimoda.uh@xxxxxxxxxxx> wrote:
> >>> > [ 1.565605] xhci-hcd ee000000.usb: xHCI Host Controller
> >>> > [ 1.570636] xhci-hcd ee000000.usb: new USB bus registered, assigned bus number 5
> >>> > [ 22.270160] xhci-hcd ee000000.usb: can't setup: -110
> >>> > [ 22.274931] xhci-hcd ee000000.usb: USB bus 5 deregistered
> >>> > [ 22.280158] xhci-hcd: probe of ee000000.usb failed with error -110
> >>> >
> >>> > The timestamp is strange to me. But, logs of R-Car H3 (ES1.0) and
> >>> > R-Car H2 were the same.
> >>>
> >>> yeah, seems like your system timer is counting twice for each tick.
> >>
> >> Yes, I will investigate this later.
> >
> > The main clock crystal on Salvator-X is half of the expected value. But
> > despite the correct value being in the DTS, there's some timer code that
> > doesn't take this into account.
>
> It's fixed by upgrading to bootloader v270:
>
> -Architected cp15 timer(s) running at 16.66MHz (virt).
> +Architected cp15 timer(s) running at 8.33MHz (virt).
Thank you for the comment!
Yes, the timer works correct on my environment.
echo do > /dev/kmsg; sleep 60; echo done > /dev/kmsg
[ 169.784474] do
[ 229.791962] done
However, the xhci timeout is still about 20 seconds.
So, I investigated this issue more. Then, it seemed that readl() in xhci_handshake() is
large delay (about 10 seconds) when the xhci driver didn't do firmware downloading.
Best regards,
Yoshihiro Shimoda
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
