On Mon, Jul 29, 2019 at 7:30 AM Marek Vasut marex@denx.de wrote:
On 7/29/19 2:16 PM, Adam Ford wrote:
On Sun, Jun 30, 2019 at 5:21 PM Adam Ford aford173@gmail.com wrote:
The omap3.dtsi file shows the usbhshost node with two sub-nodes for ohci and ehci. This patch file creates the usbhshost, and pulls the portX-mode information. It then locates the EHCI sub-node, and initializes the EHCI controller with the info pulled from the usbhshost node.
There is still more to do since there isn't an actual link between the 'phys' reference and the corresponding phy driver, and there is no nop-xceiv driver yet.
In the meantime, the older style reference to CONFIG_OMAP_EHCI_PHYx_RESET_GPIO is still needed to pull the phy out of reset until the phy driver is completed and the phandle reference is made.
Signed-off-by: Adam Ford aford173@gmail.com
Marek,
Some subsequent patches that were depending on this have been applied already, but they cannot be really useful until this patch is applied. Is there any chance it can be applied? It will give some of the OMAP3 boards the USB EHCI functionality which has been lost for a little while.
Sure, I am kinda busy and don't have enough free time to cope with this. Moreover, u-boot-usb/master fails to build: https://travis-ci.org/marex/u-boot-usb/builds/563567738
Can you take a look whether it's this patchset that causes it ?
Marek,
I looked at the Travis logs, and it looks like the da850evm_nand and da850evm_direct_nor were failing, so I tried to clone git clone --depth=50 --branch=master https://github.com/marex/u-boot-usb.git marex/u-boot-usb based on line 846 of the Travis log.
When I built da850evm_nand and da850evm_direct_nor, I could not replicate either the build error.
The EHCI patch referenced above should not impact the da850 board because that driver isn't loaded and the IP isn't present on the da850evm. They are a different OMAP family.
If you have some suggestions I how I can replicate this build error or what I might be doing wrong, please let me know.
adam