devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sekhar Nori <nsekhar@ti.com>
To: Sourav Poddar <sourav.poddar@ti.com>
Cc: bcousson@baylibre.com, tony@atomide.com,
	linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
	balbi@ti.com
Subject: Re: [PATCH] arm: dts: omap5-uevm: Add status parameter for i2c/spi/uart.
Date: Tue, 24 Sep 2013 11:57:49 +0530	[thread overview]
Message-ID: <524130E5.8050704@ti.com> (raw)
In-Reply-To: <52412792.1050105@ti.com>

On Tuesday 24 September 2013 11:18 AM, Sourav Poddar wrote:
> On Tuesday 24 September 2013 11:14 AM, Sekhar Nori wrote:
>> On Tuesday 24 September 2013 11:09 AM, Sourav Poddar wrote:
>>> omap5 has all devices enable by default.
>>> Disable thosw not required in omap5 uevm board.
>> s/thosw/those
>>
>>> Fix the following:
>>> Added status parameter
>>> Simulataneously, fix some tab formatting.
>> s/Simulataneously/Simultaneously
>>
>>> Signed-off-by: Sourav Poddar<sourav.poddar@ti.com>
>>> ---
>>>   arch/arm/boot/dts/omap5-uevm.dts |   38
>>> +++++++++++++++++++++++++++++++-------
>>>   1 files changed, 31 insertions(+), 7 deletions(-)
>>>
>>> diff --git a/arch/arm/boot/dts/omap5-uevm.dts
>>> b/arch/arm/boot/dts/omap5-uevm.dts
>>> index 65d7b60..78cf0f2 100644
>>> --- a/arch/arm/boot/dts/omap5-uevm.dts
>>> +++ b/arch/arm/boot/dts/omap5-uevm.dts
>>> @@ -450,6 +450,18 @@
>>>       };
>>>   };
>>>
>>> +&i2c2 {
>>> +    status = "disabled";
>>> +};
>>> +
>>> +&i2c3 {
>>> +    status = "disabled";
>>> +};
>>> +
>>> +&i2c4 {
>>> +    status = "disabled";
>>> +};
>> The right thing to do would be to mark these as disabled in omap5.dtsi
>> so boards can enable only what they need instead of disable what they
>> don't need (which is potentially a very long list)
> Yes, initially I thought so. But saw these varies from soc to soc.
> On DRA, it is done the way you suggested. For omap5, I saw mmc
> getting disabled in board dts.
> 
> I can change these though. Then, other modules like keypad/mmc should
> also be disable in
> dtsi file to have some uniformity. ?

Yes, that would be nice. This is usually the norm. One exception that is
made is that internal modules like RTC, cryptos can be left enabled in
the <soc>.dtsi so each board doesn't have to enable it. Just make sure
that the module is such that it can really function on *all* boards.
Typically that would mean IOs are not present or optional without loss
of complete functionality.

Thanks,
Sekhar

      reply	other threads:[~2013-09-24  6:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-24  5:39 [PATCH] arm: dts: omap5-uevm: Add status parameter for i2c/spi/uart Sourav Poddar
     [not found] ` <1380001165-19078-1-git-send-email-sourav.poddar-l0cyMroinI0@public.gmane.org>
2013-09-24  5:44   ` Sekhar Nori
     [not found]     ` <524126CC.3020300-l0cyMroinI0@public.gmane.org>
2013-09-24  5:48       ` Sourav Poddar
2013-09-24  6:27         ` Sekhar Nori [this message]

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=524130E5.8050704@ti.com \
    --to=nsekhar@ti.com \
    --cc=balbi@ti.com \
    --cc=bcousson@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=sourav.poddar@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).