devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: balbi@ti.com
Cc: devicetree@vger.kernel.org, linux@arm.linux.org.uk,
	Tony Lindgren <tony@atomide.com>, Rajendra Nayak <rnayak@ti.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	r.sricharan@ti.com, robh+dt@kernel.org,
	Benoit Cousson <bcousson@baylibre.com>,
	galak@codeaurora.org,
	Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
	Linux ARM Kernel Mailing List
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 1/2] arm: dts: am4372: let boards enable RTC and Watchdog
Date: Wed, 18 Jun 2014 16:55:33 -0500	[thread overview]
Message-ID: <53A20AD5.7080207@ti.com> (raw)
In-Reply-To: <20140618215143.GA8181@saruman.home>

On 06/18/2014 04:51 PM, Felipe Balbi wrote:
> Hi,
>
> On Wed, Jun 18, 2014 at 04:43:28PM -0500, Nishanth Menon wrote:
>> On 06/18/2014 02:25 PM, Felipe Balbi wrote:
>>> Hi,
>>>
>>> On Wed, Jun 18, 2014 at 10:55:35AM -0500, Nishanth Menon wrote:
>>>> $subject - ARM: dts:
>>>>
>>>> On 06/18/2014 10:43 AM, Felipe Balbi wrote:
>>>>> by providing phandles to rtc and wdt nodes, we can
>>>>> let boards enable rtc and wdt as necessary.
>>>>>
>>>>> Signed-off-by: Felipe Balbi <balbi@ti.com>
>>>>> ---
>>>>>   arch/arm/boot/dts/am4372.dtsi | 4 ++--
>>>>>   1 file changed, 2 insertions(+), 2 deletions(-)
>>>>>
>>>>> diff --git a/arch/arm/boot/dts/am4372.dtsi b/arch/arm/boot/dts/am4372.dtsi
>>>>> index 49fa596..e3830d4 100644
>>>>> --- a/arch/arm/boot/dts/am4372.dtsi
>>>>> +++ b/arch/arm/boot/dts/am4372.dtsi
>>>>> @@ -270,7 +270,7 @@
>>>>>   			ti,hwmods = "counter_32k";
>>>>>   		};
>>>>>
>>>>> -		rtc@44e3e000 {
>>>>> +		rtc: rtc@44e3e000 {
>>>>>   			compatible = "ti,am4372-rtc","ti,da830-rtc";
>>>>>   			reg = <0x44e3e000 0x1000>;
>>>>>   			interrupts = <GIC_SPI 75 IRQ_TYPE_LEVEL_HIGH
>>>>> @@ -279,7 +279,7 @@
>>>>>   			status = "disabled";
>>>>>   		};
>>>>>
>>>>> -		wdt@44e35000 {
>>>>> +		wdt: wdt@44e35000 {
>>>>>   			compatible = "ti,am4372-wdt","ti,omap3-wdt";
>>>>>   			reg = <0x44e35000 0x1000>;
>>>>>   			interrupts = <GIC_SPI 91 IRQ_TYPE_LEVEL_HIGH>;
>>>>>
>>>> we might want to fix up any other similar nodes in dtsi as well, no?
>>>>
>>>> examples:
>>>> cpu@0
>>>
>>> and why would you want boards to mess with the cpu node ?
>>>
>> cpu-supply = <&regulator>;
>>
>> for cpufreq.
>
> good point, but does thqt even work with AM437x devices in mainline?

it will once we are done adding a node. context here being - if you are 
fixing phandles, please fix them all up.. that is a little nice to do.

I wont argue more on this. I will leave it to maintainers.

--
Regards,
Nishanth Menon


  reply	other threads:[~2014-06-18 21:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-18 15:43 [PATCH v2 0/2] arm: dts: add support for am437x sk Felipe Balbi
2014-06-18 15:43 ` [PATCH v2 1/2] arm: dts: am4372: let boards enable RTC and Watchdog Felipe Balbi
2014-06-18 15:55   ` Nishanth Menon
2014-06-18 19:25     ` Felipe Balbi
2014-06-18 21:43       ` Nishanth Menon
2014-06-18 21:51         ` Felipe Balbi
2014-06-18 21:55           ` Nishanth Menon [this message]
2014-06-18 15:43 ` [PATCH v2 2/2] arm: dts: add support for AM437x StarterKit Felipe Balbi
2014-06-18 16:14   ` Nishanth Menon
2014-06-18 19:31     ` Felipe Balbi
     [not found]       ` <20140618193113.GC4570-HgARHv6XitL9zxVx7UNMDg@public.gmane.org>
2014-06-18 21:54         ` Nishanth Menon
2014-06-18 23:19           ` Felipe Balbi
     [not found]             ` <20140618231923.GA9855-HgARHv6XitL9zxVx7UNMDg@public.gmane.org>
2014-06-18 23:23               ` Felipe Balbi
2014-06-19  2:26             ` Nishanth Menon
     [not found]               ` <53A24A39.4080100-l0cyMroinI0@public.gmane.org>
2014-06-19  3:05                 ` Felipe Balbi
     [not found]                   ` <20140619030520.GA13805-HgARHv6XitL9zxVx7UNMDg@public.gmane.org>
2014-06-19  3:17                     ` Nishanth Menon
2014-06-19  4:02                       ` Felipe Balbi

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=53A20AD5.7080207@ti.com \
    --to=nm@ti.com \
    --cc=balbi@ti.com \
    --cc=bcousson@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=r.sricharan@ti.com \
    --cc=rnayak@ti.com \
    --cc=robh+dt@kernel.org \
    --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).