From: Sekhar Nori <nsekhar@ti.com>
To: Afzal Mohammed <afzal@ti.com>, <a.zummo@towertech.it>
Cc: <grant.likely@secretlab.ca>, <rob.herring@calxeda.com>,
<rob@landley.net>, <linux@arm.linux.org.uk>, <khilman@ti.com>,
<tony@atomide.com>, <devicetree-discuss@lists.ozlabs.org>,
<linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<davinci-linux-open-source@linux.davincidsp.com>,
<rtc-linux@googlegroups.com>
Subject: Re: [PATCH v3 0/6] omap-am33xx rtc dt support
Date: Sat, 11 Aug 2012 01:27:11 +0530 [thread overview]
Message-ID: <50256797.3020505@ti.com> (raw)
In-Reply-To: <cover.1343383616.git.afzal@ti.com>
On 7/27/2012 5:53 PM, Afzal Mohammed wrote:
> Hi,
>
> This series makes rtc-omap driver DT capable, adds AM33xx
> RTC DT support along with a few enchancments to the driver.
>
> rtc-omap driver is made intelligent enough to handle kicker
> mechanism. This helps in removing kicker mechanism support
> done for DaVinci at platform level.
>
> This has been tested on Beaglebone (AM33xx platform) and on
> DaVinci DA850 EVM.
>
> This series is based over linux-omap master and can be
> directly applied over linux-next, except for
> [PATCH 6/6] arm/dts: am33xx rtc node.
>
> PATCH 6/6 should go through linux-omap tree and needs
> http://www.mail-archive.com/linux-omap@vger.kernel.org/msg71644.html
> (arm/dts: am33xx wdt node) to get applied cleanly
I tested patches 1-5 on AM18x EVM using rtcwake and hwclock commands.
Also tested on DT enabled AM18x EVM using hwclock.
For patched 1-5:
Acked-by: Sekhar Nori <nsekhar@ti.com>
Alessandro,
I assume you would want me to queue 2/6 through DaVinci tree. That patch
depends on 1/6 being accepted and merged by you. Let me know how you
want to move forward here.
Thanks,
Sekhar
next parent reply other threads:[~2012-08-10 19:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1343383616.git.afzal@ti.com>
2012-08-10 19:57 ` Sekhar Nori [this message]
2012-08-27 7:35 ` [PATCH v3 0/6] omap-am33xx rtc dt support Mohammed, Afzal
2012-10-09 12:26 ` 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=50256797.3020505@ti.com \
--to=nsekhar@ti.com \
--cc=a.zummo@towertech.it \
--cc=afzal@ti.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=rtc-linux@googlegroups.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).