devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benoit Cousson <b-cousson@ti.com>
To: Afzal Mohammed <afzal@ti.com>
Cc: Grant Likely <grant.likely@secretlab.ca>,
	devicetree-discuss@lists.ozlabs.org,
	Russell King <linux@arm.linux.org.uk>,
	Tony Lindgren <tony@atomide.com>, AnilKumar Ch <anilkumar@ti.com>,
	Rob Herring <rob.herring@calxeda.com>,
	Vaibhav Hiremath <hvaibhav@ti.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ARM: dts: am33xx: rtc node
Date: Wed, 31 Oct 2012 12:07:16 +0100	[thread overview]
Message-ID: <50910664.1010304@ti.com> (raw)
In-Reply-To: <1351589646-27082-1-git-send-email-afzal@ti.com>

Hi Afzal,

On 10/30/2012 10:34 AM, Afzal Mohammed wrote:
> Add am33xx rtc node.
> 
> Signed-off-by: Afzal Mohammed <afzal@ti.com>
> ---
> Hi Benoit,
> 
> This is based on your for_3.8/dts branch.

I've just applied it in the branch with a slight change in the subject.

Thanks,
Benoit

> 
> This has been tested on Beagle Bone.
> 
> Bindings along with driver changes for DT has been picked by Andrew
> Morton and is now present in linux-next.
> 
> Regards
> Afzal
> 
> v2
>  1. Remove interrupt parent in rtc node.
>  2. Modify subject as per new convention.
> 
> 
>  arch/arm/boot/dts/am33xx.dtsi | 8 ++++++++
>  1 file changed, 8 insertions(+)
> 
> diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
> index 70d24b8..97a7bd3 100644
> --- a/arch/arm/boot/dts/am33xx.dtsi
> +++ b/arch/arm/boot/dts/am33xx.dtsi
> @@ -291,5 +291,13 @@
>  			ti,hwmods = "timer7";
>  			ti,timer-pwm;
>  		};
> +
> +		rtc@44e3e000 {
> +			compatible = "ti,da830-rtc";
> +			reg = <0x44e3e000 0x1000>;
> +			interrupts = <75
> +				      76>;
> +			ti,hwmods = "rtc";
> +		};
>  	};
>  };
> 

  reply	other threads:[~2012-10-31 11:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-30  9:34 [PATCH v2] ARM: dts: am33xx: rtc node Afzal Mohammed
2012-10-31 11:07 ` Benoit Cousson [this message]
2012-10-31 11:37   ` Afzal Mohammed

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=50910664.1010304@ti.com \
    --to=b-cousson@ti.com \
    --cc=afzal@ti.com \
    --cc=anilkumar@ti.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=hvaibhav@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=rob.herring@calxeda.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).