Quoting Jonas Smedegaard (2019-04-18 20:22:28)
Quoting Jagan Teki (2019-04-18 18:57:59)
On Thu, Apr 18, 2019 at 9:02 PM Jonas Smedegaard dr@jones.dk wrote:
Known broken:
- USB
what is broken? any information?
Below is the console output - neither builtin USB1 keyboard nor an external USB USB2 hub with a USB1 keyboard attached are detected:
U-Boot 2019.04-00502-g3a85a96182-dirty (Apr 18 2019 - 17:12:25 +0200) Allwinner Technology
CPU: Allwinner A64 (SUN50I) Model: Olimex A64 Teres-I DRAM: 2 GiB MMC: Device 'mmc@1c11000': seq 1 is in use by 'mmc@1c10000' mmc@1c0f000: 0, mmc@1c10000: 2, mmc@1c11000: 1 Loading Environment from FAT... OK In: serial Out: vidconsole Err: vidconsole Net: No ethernet found. starting USB... Bus usb@1c1b000: USB EHCI 1.00 scanning bus usb@1c1b000 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 => usb tree USB device tree: 1 Hub (480 Mb/s, 0mA) u-boot EHCI Host Controller
...and "dm tree" contains this:
[...] regulator 0 [ ] fixed regulator |-- usb1-vbus regulator 1 [ + ] fixed regulator |-- regulator@0 [...]
Also, if I enable CONFIG_USB_OHCI_HCD (noticing that was done generally for a64 boards recently in commit 29d280c88a), then u-boot hangs just after the "Bus usb@1c1b000: USB EHCI 1.00".
General question: Is it appropriate to cc this many individuals (resolved by the patman script), or if not which are appropriate?
- Jonas