Hi,
On 24-02-16 14:59, Andre Przywara wrote:
Hi,
(dropping some lists and people)
On 24/02/16 11:15, Hans de Goede wrote:
From: Reinder de Haan <patchesrdh@xxxxxxxxx>
At least the EHCI/OHCI found on the Allwinnner H3 SoC needs multiple
reset lines, the controller will not initialize while the reset for
its companion is still asserted, which means we need to de-assert
2 resets for the controller to work.
Interesting, is that documented somewhere or has this been found out by
try-and-error?
Found out by try-and-error.
I was experimenting with USB on the Pine64 yesterday and stumbled upon
the failing OHCI reset (because it now needs bits 16 _and_ 17 to be set
for the OHCI PHY to reset), but couldn't get the EHCI controller to work
properly also.
Then it likely is something different, the problem on the H3 causes
the ohci / ehci driver to not load at all, since the registers read
all 00 (or was it FF ?), which causes the reset-control and wait for
ack code in the generic bits of the drivers to fail (IIRC).
How would this behaviour manifest? I don't see failure messages with my
new DT (the driver seems to happily initialize), but it doesn't show
anything other than the root hub even when plugging in devices.
This may be a phy init problem (specifically missing something similar to
sun4i_usb_phy_passby() in drivers/phy/phy-sun4i-usb.c for the A64), or
maybe you've not enabled the 5V power to the host USB ports ?
My first step would be to check the 5v plug something with a powerled
or some such into the usb port and if the led does not light up
you need to drive some gpio high (typically) or enable some regulator
somewhere.
Regards,
Hans
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
