From: Rob Herring <robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Viresh Kumar <viresh.kumar-qxv4g6HH51o@public.gmane.org>
Cc: Stefan Roese <sr-ynQEQJNshbs@public.gmane.org>,
"linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
spear-devel <spear-devel-nkJGhpqTU55BDgjK7y7TUQ@public.gmane.org>,
"devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org"
<devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org>,
Deepak SIKRI <deepak.sikri-qxv4g6HH51o@public.gmane.org>
Subject: Re: [PATCH] USB: Add DT probing support to ehci-spear and ohci-spear
Date: Fri, 23 Mar 2012 09:17:16 -0500 [thread overview]
Message-ID: <4F6C85EC.4070309@gmail.com> (raw)
In-Reply-To: <4F6C2F25.8030402-qxv4g6HH51o@public.gmane.org>
On 03/23/2012 03:07 AM, Viresh Kumar wrote:
> On 3/23/2012 1:30 PM, Stefan Roese wrote:
>> There could be differences between the IP cores integrated into the SoCs. I
>> only tested on spear600, so thats what I integrated into the drivers. While
>> supporting more SoCs (SPEAr300 etc) to those drivers, you should add the
>> specific compatible properties to the lists.
>
> Ya. That's what i was expecting.
>
>> If the IP core doesn't differ between those SoCs, then it might make sense to
>> change this property to something more general, like "st,spear-ohci" (etc).
>> Not 100% sure though. Other DT experts might have more insight here.
>
> Ok. FSMC version is same for 3xx and 6xx. Is different for 13xx.
> But driver is capable of detecting the version itself and so we might
> go ahead with "st,spear-fsmc there"
>
> SMI, EHCI and OHCI have exactly the same version for all three families of SoC's.
> So, we must better name them "st,spear-***"
No, it's better to be safe and be more specific. You have to think of it
as if you created the DT entries as the h/w came out. Define the
compatible string in terms of the 1st version. Then if the 2nd SOC
happens to have the same version, you can re-use the compatible string
and not change the driver.
Rob
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-03-23 14:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 15:50 [PATCH] USB: Add DT probing support to ehci-spear and ohci-spear Stefan Roese
[not found] ` <1332431402-20606-1-git-send-email-sr-ynQEQJNshbs@public.gmane.org>
2012-03-23 3:48 ` Viresh Kumar
[not found] ` <4F6BF275.9040007-qxv4g6HH51o@public.gmane.org>
2012-03-23 8:00 ` Stefan Roese
[not found] ` <201203230900.02280.sr-ynQEQJNshbs@public.gmane.org>
2012-03-23 8:07 ` Viresh Kumar
[not found] ` <4F6C2F25.8030402-qxv4g6HH51o@public.gmane.org>
2012-03-23 14:17 ` Rob Herring [this message]
2012-04-13 3:59 ` Viresh Kumar
[not found] ` <4F87A48E.3090300-qxv4g6HH51o@public.gmane.org>
2012-04-13 18:26 ` Greg KH
[not found] ` <20120413182655.GA5444-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2012-04-16 3:44 ` Viresh Kumar
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=4F6C85EC.4070309@gmail.com \
--to=robherring2-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=deepak.sikri-qxv4g6HH51o@public.gmane.org \
--cc=devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=spear-devel-nkJGhpqTU55BDgjK7y7TUQ@public.gmane.org \
--cc=sr-ynQEQJNshbs@public.gmane.org \
--cc=viresh.kumar-qxv4g6HH51o@public.gmane.org \
/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).