From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/2] ARM: delay: add registration mechanism for delay timer sources
Date: Fri, 7 Sep 2012 18:07:32 +0100 [thread overview]
Message-ID: <20120907170729.GJ15916@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <1346275524-13817-2-git-send-email-will.deacon@arm.com>
On Wed, Aug 29, 2012 at 10:25:24PM +0100, Will Deacon wrote:
> From: Jonathan Austin <Jonathan.Austin@arm.com>
>
> The current timer-based delay loop relies on the architected timer to
> initiate the switch away from the polling-based implementation. This is
> unfortunate for platforms without the architected timers but with a
> suitable delay source (that is, constant frequency, always powered-up
> and ticking as long as the CPUs are online).
>
> This patch introduces a registration mechanism for the delay timer
> (which provides an unconditional read_current_timer implementation) and
> updates the architected timer code to use the new interface.
[...]
> +int read_current_timer(unsigned long *timer_val)
> +{
> + return delay_timer ? delay_timer->read_current_timer() : -ENXIO;
> +}
So this is clearly wrong with the new function prototype -- I've fixed it on
my delay branch (when the mirrors sync).
Will
next prev parent reply other threads:[~2012-09-07 17:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-29 21:25 [PATCH v2 1/2] ARM: delay: set loops_per_jiffy when moving to timer-based loop Will Deacon
2012-08-29 21:25 ` [PATCH v2 2/2] ARM: delay: add registration mechanism for delay timer sources Will Deacon
2012-08-30 23:51 ` Stephen Boyd
2012-09-04 10:07 ` Will Deacon
2012-09-04 10:44 ` Will Deacon
2012-09-04 17:11 ` Stephen Boyd
2012-09-04 17:38 ` Will Deacon
2012-09-07 17:07 ` Will Deacon [this message]
2012-08-30 23:51 ` [PATCH v2 1/2] ARM: delay: set loops_per_jiffy when moving to timer-based loop Stephen Boyd
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=20120907170729.GJ15916@mudshark.cambridge.arm.com \
--to=will.deacon@arm.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).