From: Jon Hunter <jon-hunter@ti.com>
To: Jon Hunter <jon-hunter@ti.com>
Cc: Benoit Cousson <b-cousson@ti.com>,
Tony Lindgren <tony@atomide.com>, Paul Walmsley <paul@pwsan.com>,
Rob Herring <rob.herring@calxeda.com>,
Grant Likely <grant.likely@secretlab.ca>,
device-tree <devicetree-discuss@lists.ozlabs.org>,
linux-omap <linux-omap@vger.kernel.org>,
linux-arm <linux-arm-kernel@lists.infradead.org>,
Vaibhav Hiremath <hvaibhav@ti.com>
Subject: Re: [PATCH V3 0/5] ARM: OMAP2+: Add device-tree support for timers
Date: Wed, 17 Oct 2012 13:03:16 -0500 [thread overview]
Message-ID: <507EF2E4.3050509@ti.com> (raw)
In-Reply-To: <1350496873-21337-1-git-send-email-jon-hunter@ti.com>
On 10/17/2012 01:01 PM, Jon Hunter wrote:
> This series adds device-tree support for the timers on OMAP2+ devices
> including AM33xx.
>
> Testing:
> 1. I have booted tested this series on OMAP2420 H4, OMAP3430 Beagle, OMAP4430
> Panda and AM335x Beagle Bone with/without ...
> a). device-tree present
> b). CONFIG_OMAP_32K_TIMER set
> c). kernel boot parameter "clocksource=gp_timer" present
> 2. I have tested the all the timers (not used by the kernel as sys-timers) on
> OMAP2420 H4, OMAP3430 Beagle and OMAP4430 Panda with/without device-tree with
> this series. The testing includes ...
> a. Configuring, starting a timer and checking the counter value is
> incrementing.
> b. Testing timer overflow interrupt when timer expires.
> c. Using different clock sources to operate the timer with.
>
> V3 changes:
> - Removed definition "TIMER_PROP_ALWON" per Rob Herring's feedback
> - Updated OMAP system timer (clock-events and clock-source) code so that
> HWMOD is NOT used for getting resource (memory and interrupt) information
> when device-tree is present.
>
> V2 changes:
> - Remove use of device-tree alias property
> - Migrate OMAP timers to request timers by property instead of device ID
> - Include OMAP2 support
Forgot to mention that this is based on top of v3.7-rc1.
Cheers
Jon
prev parent reply other threads:[~2012-10-17 18:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-17 18:01 [PATCH V3 0/5] ARM: OMAP2+: Add device-tree support for timers Jon Hunter
2012-10-17 18:01 ` [PATCH V3 1/5] ARM: dts: OMAP: Add timer nodes Jon Hunter
2012-10-24 18:17 ` Hiremath, Vaibhav
[not found] ` <79CD15C6BA57404B839C016229A409A83EB49C1B-Er742YJ7I/eIQmiDNMet8wC/G2K4zDHf@public.gmane.org>
2012-10-24 23:00 ` Jon Hunter
2012-10-25 12:12 ` Hiremath, Vaibhav
2012-10-25 12:18 ` Jon Hunter
2012-10-25 12:33 ` Jon Hunter
2012-10-25 15:51 ` Hiremath, Vaibhav
2012-10-25 15:27 ` Hiremath, Vaibhav
2012-10-25 18:38 ` Jon Hunter
2012-10-17 18:01 ` [PATCH V3 2/5] ARM: OMAP3: Dynamically disable secure timer nodes for secure devices Jon Hunter
2012-10-17 18:01 ` [PATCH V3 3/5] ARM: OMAP: Add function to request a timer by capability Jon Hunter
2012-10-17 18:01 ` [PATCH V3 4/5] ARM: OMAP3: Add generic machine descriptor for boards with OMAP3 GP devices Jon Hunter
2012-10-17 18:01 ` [PATCH V3 5/5] ARM: OMAP: Add DT support for timer driver Jon Hunter
2012-10-17 18:03 ` 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=507EF2E4.3050509@ti.com \
--to=jon-hunter@ti.com \
--cc=b-cousson@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-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--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).