From: Jon Hunter <jon-hunter@ti.com>
To: Jon Hunter <jon-hunter@ti.com>
Cc: Tarun Kanti DebBarma <tarun.kanti@ti.com>,
Tony Lindgren <tony@atomide.com>,
Rob Herring <rob.herring@calxeda.com>,
Grant Likely <grant.likely@secretlab.ca>,
Paul Walmsley <paul@pwsan.com>, Benoit Cousson <b-cousson@ti.com>,
linux-omap <linux-omap@vger.kernel.org>,
linux-arm <linux-arm-kernel@lists.infradead.org>,
device-tree <devicetree-discuss@lists.ozlabs.org>
Subject: Re: [RFC 0/4] ARM: OMAP3+: Add device-tree support for timers
Date: Fri, 13 Jul 2012 17:28:54 -0500 [thread overview]
Message-ID: <5000A126.7090707@ti.com> (raw)
In-Reply-To: <1342217976-29802-1-git-send-email-jon-hunter@ti.com>
Sorry for all the noise. I was having network problems in the midst of
sending and then I royally screwed it up by deciding to make some last
minute edits. So ignore this version of the series.
Jon
On 07/13/2012 05:19 PM, Jon Hunter wrote:
> This series adds device-tree support for the timers on OMAP3/4 devices. Once
> everyone is happy with the implementation I can add support for OMAP2/5 devices
> too.
>
> Testing:
> - I have tested the all the timers (not used by the kernel as sys-timers) on
> both OMAP3430 Beagle and OMAP4460 Panda with/without device-tree with this
> series.
> - The testing includes
> - Configuring, starting a timer and checking the counter value is
> incrementing.
> - Testing timer overflow interrupt when timer expires.
> - Using different clock sources to operate the timer with.
> - Using DT to provide resource information for IRQ and memory by
> removing Benoit's intention "HACK" in commit a4f6cdb0 (ARM: OMAP:
> omap_device: Add omap_device_[alloc|delete] for DT integration)
>
> Jon Hunter (4):
> arm/dts: OMAP: Add timer nodes
> ARM: OMAP3: Dynamically disable secure timer nodes for secure devices
> ARM: OMAP4: Add timer clock aliases for device-tree
> ARM: OMAP: Add DT support for timer driver
>
> .../devicetree/bindings/arm/omap/timer.txt | 34 +++++++
> arch/arm/boot/dts/omap3.dtsi | 104 ++++++++++++++++++++
> arch/arm/boot/dts/omap4.dtsi | 93 +++++++++++++++++
> arch/arm/mach-omap2/board-generic.c | 1 +
> arch/arm/mach-omap2/clock44xx_data.c | 12 +++
> arch/arm/mach-omap2/common.h | 1 +
> arch/arm/mach-omap2/timer.c | 40 ++++++++
> arch/arm/plat-omap/dmtimer.c | 32 ++++--
> 8 files changed, 311 insertions(+), 6 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/arm/omap/timer.txt
>
prev parent reply other threads:[~2012-07-13 22:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-13 22:19 [RFC 0/4] ARM: OMAP3+: Add device-tree support for timers Jon Hunter
2012-07-13 22:19 ` [RFC 3/4] ARM: OMAP4: Add timer clock aliases for device-tree Jon Hunter
[not found] ` <1342217976-29802-1-git-send-email-jon-hunter-l0cyMroinI0@public.gmane.org>
2012-07-13 22:19 ` [RFC 1/4] arm/dts: OMAP: Add genernal purpose timer nodes Jon Hunter
2012-07-13 22:19 ` [RFC 1/4] arm/dts: OMAP: Add " Jon Hunter
2012-07-13 22:19 ` [RFC 2/4] ARM: OMAP3: Dynamically disable secure timer nodes for secure devices Jon Hunter
2012-07-13 22:19 ` [RFC 4/4] ARM: OMAP: Add DT support for dmtimer driver Jon Hunter
2012-07-13 22:19 ` [RFC 4/4] ARM: OMAP: Add DT support for timer driver Jon Hunter
2012-07-13 22:28 ` Jon Hunter [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=5000A126.7090707@ti.com \
--to=jon-hunter@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=paul@pwsan.com \
--cc=rob.herring@calxeda.com \
--cc=tarun.kanti@ti.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).