This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TUSB1210 and AM3715 for OTG and EHCI

Other Parts Discussed in Thread: AM3715, TUSB1210

Hi All,

I am working with AM3715 and TUSB1210 with the following application:

PC <---- TUSB1210 <----- AM3715 -----> TUSB1210 -----> WiFi

I am using kernel 3.3.0 and I am having problems to configure the PHY USB, thus not recognizing the HW attached to the USB

From my board configuration files I have the following:

/* Two GPIOS controlling the reset of the TUSB1210*/

static struct omap_board_mux board_mux[] __initdata ={

OMAP3_MUX(UART1_RTS, OMAP_MUX_MODE4 | OMAP_PIN_OUTPUT), //149
OMAP3_MUX(UART1_RX, OMAP_MUX_MODE4 | OMAP_PIN_OUTPUT), //151

{ .reg_offset = OMAP_MUX_TERMINATOR },
};

/* USB hub port is configured as follows: */

static const struct usbhs_omap_board_data usbhs_bdata __initconst = {

.port_mode[0] = OMAP_EHCI_PORT_MODE_PHY,
.port_mode[1] = OMAP_EHCI_PORT_MODE_PHY,
.port_mode[2] = OMAP_USBHS_PORT_MODE_UNUSED,

.phy_reset = true,
.reset_gpio_port[0] = -EINVAL,
.reset_gpio_port[1] = 149,
.reset_gpio_port[2] = -EINVAL
};

I found this link regarding a patch made couple of months ago. Is EHCI driver broken?

http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap.git;a=commit;h=1fcb57d0f6e1150003d222051aaaf4bc4a9ccc94

If someone has any idea what the problem is, please advise. If need more information please let me know.

Thanks!

Federico