From: Roger Quadros <rogerq@ti.com>
To: Nishanth Menon <nm@ti.com>,
linux-omap <linux-omap@vger.kernel.org>,
linux-usb@vger.kernel.org, "Balbi, Felipe" <balbi@ti.com>
Cc: linux-next@vger.kernel.org,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"tony@atomide.com" <tony@atomide.com>
Subject: Re: regression(ti platforms): next-20140210 (ehci?)
Date: Mon, 10 Feb 2014 20:16:53 +0200 [thread overview]
Message-ID: <52F91795.9080500@ti.com> (raw)
In-Reply-To: <52F91451.8050802@ti.com>
On 02/10/2014 08:02 PM, Nishanth Menon wrote:
> 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?
>
>
I'm not sure either. Let's get rid of it.
Patch to fix the reported issue.
http://article.gmane.org/gmane.linux.drivers.devicetree/61204
cheers,
-roger
next prev parent reply other threads:[~2014-02-10 18:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52F8F77B.70605@ti.com>
[not found] ` <52F8F77B.70605-l0cyMroinI0@public.gmane.org>
2014-02-10 17:50 ` regression(ti platforms): next-20140210 (ehci?) Roger Quadros
2014-02-10 18:02 ` Nishanth Menon
2014-02-10 18:16 ` Roger Quadros [this message]
2014-02-10 18:28 ` Kevin Hilman
2014-02-10 19:33 ` Nishanth Menon
2014-02-11 1:07 ` Kevin Hilman
2014-02-11 13:27 ` Nishanth Menon
[not found] ` <7h38jq8nk9.fsf-4poPxKt068f/PtFMR13I2A@public.gmane.org>
2014-02-11 15:21 ` Alan Stern
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52F91795.9080500@ti.com \
--to=rogerq@ti.com \
--cc=balbi@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=nm@ti.com \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).