You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Even with a recent devicetree fix, the OTG port does not seem to function in the desired host mode. Obviously because of the hardware design, it is intended to always operate in "host" mode, and this is confirmed by the devicetree. Plugging in a USB 2.0 device into this OTG port and then running lsusb shows notink!
dmesg shows notink.
If you look at the devicetree compatibility string for the "otg" node, and then grep the kernel source code for it, it takes you to a driver which is enabled by this line in the drivers/usb/musb/Makefile:
obj-$(CONFIG_USB_MUSB_SUNXI) += sunxi.o
There is no evidence that this "MUSB" party is happening in the kernel config file fragments. And since this kernel does not enable /proc/config.gz, there is a remnant of doubt about where one actually finds a complete kernel config file for this 4.14 kernel build, but I leave that for another day.
The text was updated successfully, but these errors were encountered:
dickelbeck:
Even with a recent devicetree fix, the OTG port does not seem to function in the desired host mode. Obviously because of the hardware design, it is intended to always operate in "host" mode, and this is confirmed by the devicetree. Plugging in a USB 2.0 device into this OTG port and then running lsusb shows notink!
dmesg shows notink.
If you look at the devicetree compatibility string for the "otg" node, and then grep the kernel source code for it, it takes you to a driver which is enabled by this line in the drivers/usb/musb/Makefile:
obj-$(CONFIG_USB_MUSB_SUNXI) += sunxi.o
There is no evidence that this "MUSB" party is happening in the kernel config file fragments. And since this kernel does not enable /proc/config.gz, there is a remnant of doubt about where one actually finds a complete kernel config file for this 4.14 kernel build, but I leave that for another day.
The text was updated successfully, but these errors were encountered: