From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 1/5] arm:omap1/2/3/4:Convert 32k-Sync clocksource driver to platform_driver
Date: Thu, 19 Jan 2012 05:09:26 -0800 [thread overview]
Message-ID: <20120119130926.GF22818@atomide.com> (raw)
In-Reply-To: <20120118145032.GO16726@n2100.arm.linux.org.uk>
* Russell King - ARM Linux <linux@arm.linux.org.uk> [120118 06:18]:
> On Wed, Jan 18, 2012 at 02:45:36PM +0000, Marc Zyngier wrote:
> > Can't you instead use the ARM sched_clock framework?
>
> OMAP does, and has done for quite some time. The problem is these
> patches are against an old kernel.
Additionally we're already handling the 32k timer or not case already
on omap1 as it does not exist on 1510, so there should only minimal
patching needed AFAIK.
Tony
next prev parent reply other threads:[~2012-01-19 13:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 11:28 [RFC PATCH 0/5] arm:omap1/2/3/4: 32k sync timer cleanup Vaibhav Hiremath
2012-01-18 11:28 ` [RFC PATCH 1/5] arm:omap1/2/3/4:Convert 32k-Sync clocksource driver to platform_driver Vaibhav Hiremath
2012-01-18 11:59 ` Russell King - ARM Linux
2012-01-18 13:34 ` Hiremath, Vaibhav
2012-01-18 14:11 ` Russell King - ARM Linux
2012-01-18 14:19 ` Hiremath, Vaibhav
2012-01-18 14:25 ` Marc Zyngier
2012-01-18 14:38 ` Hiremath, Vaibhav
2012-01-18 14:45 ` Marc Zyngier
2012-01-18 14:50 ` Russell King - ARM Linux
2012-01-19 13:09 ` Tony Lindgren [this message]
2012-01-19 13:30 ` Hiremath, Vaibhav
2012-01-25 23:53 ` john stultz
2012-01-30 8:49 ` Hiremath, Vaibhav
2012-01-18 11:28 ` [RFC PATCH 2/5] arm:omap2/3: Add idle_st bits for ST_32KSYNC timer Vaibhav Hiremath
2012-01-18 11:28 ` [RFC PATCH 3/5] arm:omap1/2/3/4: Add 32k counter data to hwmod database Vaibhav Hiremath
2012-01-18 11:28 ` [RFC PATCH 4/5] arm:omap1/2/3/4: Add platform hookup code for counter-32k driver Vaibhav Hiremath
2012-01-18 11:28 ` [RFC PATCH 5/5] arm:omap1/2/3: Change dev name for sync_32k_ick clk to omap-counter-32k Vaibhav Hiremath
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=20120119130926.GF22818@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.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).