From: rnayak@ti•com (Rajendra Nayak)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v2 4/4] arm/dts: OMAP3: Add mmc controller nodes and board data
Date: Fri, 24 Feb 2012 09:30:49 +0530 [thread overview]
Message-ID: <4F470B71.1020308@ti.com> (raw)
In-Reply-To: <20120223185718.GZ18185@atomide.com>
On Friday 24 February 2012 12:27 AM, Tony Lindgren wrote:
>> --- a/arch/arm/boot/dts/omap3.dtsi
>> +++ b/arch/arm/boot/dts/omap3.dtsi
>> @@ -113,5 +113,31 @@
>> #size-cells =<0>;
>> ti,hwmods = "i2c3";
>> };
>> +
>> + mmc1: mmc at 1 {
>> + compatible = "ti,omap2-hsmmc";
>> + ti,hwmods = "mmc1";
>> + ti,dual-volt;
>> + };
>> +
>> + mmc2: mmc at 2 {
>> + compatible = "ti,omap2-hsmmc";
>> + ti,hwmods = "mmc2";
>> + };
>> +
>> + mmc3: mmc at 3 {
>> + compatible = "ti,omap2-hsmmc";
>> + ti,hwmods = "mmc3";
>> + };
>> +
>> + mmc4: mmc at 4 {
>> + compatible = "ti,omap2-hsmmc";
>> + ti,hwmods = "mmc4";
>> + };
>> +
>> + mmc5: mmc at 5 {
>> + compatible = "ti,omap2-hsmmc";
>> + ti,hwmods = "mmc5";
>> + };
>> };
>> };
>
> These all should all be "ti,omap3-hsmmc" I guess?
Well, I defined the binding such that both omap2 and omap3
can use the same compatible "ti,omap2-hsmmc" since there is
no difference in the way they are defined or handled. If thats
confusing, I can have separate compatibles.
Btw, I guess we do the same with a few other re-used IPs as well,
I just checked and mcpsi does the same.
>
> Tony
next prev parent reply other threads:[~2012-02-24 4:00 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 12:01 [PATCH v2 0/4] omap hsmmc device tree support Rajendra Nayak
2012-02-23 12:01 ` [PATCH v2 1/4] mmc: omap_hsmmc: Convert hsmmc driver to use device tree Rajendra Nayak
2012-02-24 11:32 ` T Krishnamoorthy, Balaji
2012-02-24 11:35 ` Rajendra Nayak
2012-02-24 12:51 ` Cousson, Benoit
2012-02-24 12:58 ` Rajendra Nayak
2012-02-24 13:02 ` Cousson, Benoit
2012-02-24 13:04 ` Rajendra Nayak
2012-03-08 3:46 ` Rajendra Nayak
2012-03-08 15:58 ` Rob Herring
2012-03-09 5:42 ` Grant Likely
2012-03-09 9:21 ` Rajendra Nayak
2012-02-23 12:01 ` [PATCH v2 2/4] mmc: omap_hsmmc: Avoid a regulator voltage change with dt Rajendra Nayak
2012-02-23 12:01 ` [PATCH v2 3/4] arm/dts: OMAP4: Add mmc controller nodes and board data Rajendra Nayak
2012-02-24 10:16 ` T Krishnamoorthy, Balaji
2012-02-24 10:26 ` Rajendra Nayak
2012-02-24 10:37 ` Russell King - ARM Linux
2012-02-24 10:59 ` T Krishnamoorthy, Balaji
2012-03-09 15:49 ` Grant Likely
2012-02-23 12:01 ` [PATCH v2 4/4] arm/dts: OMAP3: " Rajendra Nayak
2012-02-23 18:57 ` Tony Lindgren
2012-02-24 4:00 ` Rajendra Nayak [this message]
2012-02-24 11:23 ` Cousson, Benoit
2012-02-24 18:49 ` Tony Lindgren
2012-03-09 5:46 ` Grant Likely
2012-03-09 6:51 ` Paul Walmsley
2012-03-09 9:36 ` Rajendra Nayak
2012-03-09 9:26 ` Rajendra Nayak
2012-02-23 12:13 ` [PATCH v2 0/4] omap hsmmc device tree support Rajendra Nayak
-- strict thread matches above, loose matches on Subject: below --
2012-03-12 15:02 Rajendra Nayak
2012-03-12 15:02 ` [PATCH v2 4/4] arm/dts: OMAP3: Add mmc controller nodes and board data Rajendra Nayak
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=4F470B71.1020308@ti.com \
--to=rnayak@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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