Hello,
Felipe, sorry but I don't understand your questions,m maybe I'm
missing something.
All IGEP v2 boards uses USB1HS EHCI port. My mistake was suppose that
port_mode[1] --> EHCI USB1HS but this is not correct, the EHCI USB1HS
is port_mode[0]. This patch only fixes this.
Best regards,
Enric
>> 2010/3/15 Felipe Balbi <me@xxxxxxxxxxxxxxx>
>>>
>>> Hi,
>>>
>>> On Mon, Mar 01, 2010 at 04:02:36PM +0100, Enric Balletbo i Serra wrote:
>>> > @@ -458,13 +458,13 @@ static struct omap_musb_board_data musb_board_data = {
>>> > };
>>> >
>>> > static const struct ehci_hcd_omap_platform_data ehci_pdata __initconst = {
>>> > - .port_mode[0] = EHCI_HCD_OMAP_MODE_UNKNOWN,
>>> > - .port_mode[1] = EHCI_HCD_OMAP_MODE_PHY,
>>> > + .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,
>>> > - .reset_gpio_port[0] = -EINVAL,
>>> > - .reset_gpio_port[1] = IGEP2_GPIO_USBH_NRESET,
>>> > + .reset_gpio_port[0] = IGEP2_GPIO_USBH_NRESET,
>>> > + .reset_gpio_port[1] = -EINVAL,
>>>
>>> no way to be backwards compatible ? Is it worth to be backwards
>>> compatible ?
>>>
>>> --
>>> balbi
>>>
>>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
