Re: regression(ti platforms): next-20140210 (ehci?)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 02/10/2014 11:50 AM, Roger Quadros wrote:
> +devicetree
> 
[...]
> In the DT node we have compatible ids for both. e.g. for omap4.dtsi
> 
>                         usbhsehci: ehci@4a064c00 {
>                                 compatible = "ti,ehci-omap", "usb-ehci";
>                                 reg = <0x4a064c00 0x400>;
>                                 interrupt-parent = <&gic>;
>                                 interrupts = <GIC_SPI 77 IRQ_TYPE_LEVEL_HIGH>;
>                         };
> 
> Shouldn't ehci-omap driver be getting a higher priority than usb-ehci?
> 
> A quick fix would be to eliminate "usb-ehci" from the DT node of all failing platforms.

If the driver is not compatible with "usb-ehci", not sure why do we
even state that in dts node?


-- 
Regards,
Nishanth Menon
--
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




[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux