I'am using dvsdk4.2.6.
We've designed a customed board based on Mistral EVM. And for some reason, we connected USB3320 to DM3730 through HSUSB1, while the EVM adopted HSUSB2.
Now, I cannot make the new board find the usb disk.
The result of "lsusb" is:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
------------------------------------------------------------------------------------------
I've test my kernel on mistral EVM before I ported it on my new board .
What I have done is to modify the file arch/arm/mach-omap2/board-omap3evm.c:
1.
static struct ehci_hcd_omap_platform_data ehci_pdata __initconst = {
.port_mode[0] = EHCI_HCD_OMAP_MODE_PHY,
.port_mode[1] = EHCI_HCD_OMAP_MODE_UNKNOWN,
.port_mode[2] = EHCI_HCD_OMAP_MODE_UNKNOWN,
.phy_reset = true,
/* PHY reset GPIO will be runtime programmed based on EVM version */
.reset_gpio_port[0] = -EINVAL,
.reset_gpio_port[1] = -EINVAL,
.reset_gpio_port[2] = -EINVAL,
.aux[0] = 0,
.aux[1] = 0,
.aux[2] = 0,
};
2. In the function omap3_evm_init(), modified the reset pin as our design.
omap_mux_init_gpio(29, OMAP_PIN_INPUT_PULLUP);
gpio_request(29, "usb3320 host reset");
gpio_direction_output(29, 0);
mdelay(20);
gpio_set_value(29, 1);
ehci_pdata.reset_gpio_port[0] = 29;
----------------------------------------------------------------------------------------------------------
At present, I am sure that pin-mux is ok, since I've checked througth debugfs.
Some hint, Please!