From: Tony Lindgren <tony@atomide.com>
To: "Mohammed, Afzal" <afzal@ti.com>
Cc: "Cousson, Benoit" <b-cousson@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>,
"grant.likely@secretlab.ca" <grant.likely@secretlab.ca>
Subject: Re: [PATCH] arm/dts: am33xx wdt node
Date: Mon, 9 Jul 2012 01:59:44 -0700 [thread overview]
Message-ID: <20120709085944.GC1122@atomide.com> (raw)
In-Reply-To: <C8443D0743D26F4388EA172BF4E2A7A93E9A2FE9@DBDE01.ent.ti.com>
* Mohammed, Afzal <afzal@ti.com> [120704 06:44]:
> + Grant and device tree, watchdog lists
>
> On Wed, Jul 04, 2012 at 18:00:37, Mohammed, Afzal wrote:
> > Add am33xx wdt node.
> >
> > Signed-off-by: Afzal Mohammed <afzal@ti.com>
> > ---
> >
> > Hi,
> >
> > This was tested on AM335X EVM. This depends on,
> > http://www.mail-archive.com/linux-omap@vger.kernel.org/msg69424.html
Thanks I'll apply this into omap devel-dt branch now that we have
an ack from Wim on the wdt changes.
Tony
> > Regards
> > Afzal
> >
> >
> > arch/arm/boot/dts/am33xx.dtsi | 5 +++++
> > 1 file changed, 5 insertions(+)
> >
> > diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
> > index f46e353..08b2a5b 100644
> > --- a/arch/arm/boot/dts/am33xx.dtsi
> > +++ b/arch/arm/boot/dts/am33xx.dtsi
> > @@ -185,5 +185,10 @@
> > compatible = "ti,omap3-hsmmc";
> > ti,hwmods = "mmc3";
> > };
> > +
> > + wdt2: wdt@44e35000 {
> > + compatible = "ti,omap3-wdt";
> > + ti,hwmods = "wd_timer2";
> > + };
> > };
> > };
> > --
> > 1.7.11.1
> >
> >
>
prev parent reply other threads:[~2012-07-09 8:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1341405037-16391-1-git-send-email-afzal@ti.com>
2012-07-04 13:40 ` [PATCH] arm/dts: am33xx wdt node Mohammed, Afzal
2012-07-09 8:59 ` 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=20120709085944.GC1122@atomide.com \
--to=tony@atomide.com \
--cc=afzal@ti.com \
--cc=b-cousson@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
/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).