From: Tony Lindgren <tony@atomide.com>
To: Stefan Roese <sr@denx.de>
Cc: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
Lukas Stockmann <lukas.stockmann@siemens.com>,
Benoit Cousson <bcousson@baylibre.com>
Subject: Re: [PATCH 1/3] arm: dts: am33xx.dtsi: Add node name to rtc device node
Date: Fri, 28 Feb 2014 14:45:05 -0800 [thread overview]
Message-ID: <20140228224504.GQ13624@atomide.com> (raw)
In-Reply-To: <1391602361-2666-1-git-send-email-sr@denx.de>
* Stefan Roese <sr@denx.de> [140205 04:14]:
> Making it possible to reference and therefor change (disable) this
> device node from other dts file which import this dtsi file.
>
> Signed-off-by: Stefan Roese <sr@denx.de>
> Cc: Lukas Stockmann <lukas.stockmann@siemens.com>
> Cc: Benoit Cousson <bcousson@baylibre.com>
> Cc: Tony Lindgren <tony@atomide.com>
Thanks applying into omap-for-v3.15/dt.
Tony
> ---
> arch/arm/boot/dts/am33xx.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
> index 6d95d3d..b8daf8c 100644
> --- a/arch/arm/boot/dts/am33xx.dtsi
> +++ b/arch/arm/boot/dts/am33xx.dtsi
> @@ -399,7 +399,7 @@
> ti,timer-pwm;
> };
>
> - rtc@44e3e000 {
> + rtc: rtc@44e3e000 {
> compatible = "ti,da830-rtc";
> reg = <0x44e3e000 0x1000>;
> interrupts = <75
> --
> 1.8.5.3
>
prev parent reply other threads:[~2014-02-28 22:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 12:12 [PATCH 1/3] arm: dts: am33xx.dtsi: Add node name to rtc device node Stefan Roese
2014-02-05 12:12 ` [PATCH 2/3] arm: dts: Add Siemens Draco SOM dtsi Stefan Roese
2014-02-05 12:12 ` [PATCH 3/3] arm: dts: Add Siemens am335x-dxr2-e.dts Stefan Roese
2014-02-05 18:29 ` [PATCH 1/3] arm: dts: am33xx.dtsi: Add node name to rtc device node Sergei Shtylyov
2014-02-28 22:45 ` Tony Lindgren [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=20140228224504.GQ13624@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=lukas.stockmann@siemens.com \
--cc=sr@denx.de \
/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).