From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/2] ARM: delay: allow timer-based delay implementation to be selected
Date: Thu, 5 Jul 2012 15:15:43 +0100 [thread overview]
Message-ID: <20120705141542.GH3399@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <4FF59145.2020009@renesas.com>
On Thu, Jul 05, 2012 at 02:06:13PM +0100, Shinya Kuribayashi wrote:
> On 6/30/2012 2:33 AM, Will Deacon wrote:
> > +extern void init_current_timer_delay(unsigned long freq);
> > +
>
> This is needed for all users of the new timer-baed delay routine.
> How about moving this extern declaration to more generic place, in
> <asm/timex.h>?
I mentioned this before in the original posting. Currently, only the
architected timers are using this interface and I have some reservations
about using memory-mapped timers instead (although there may be specific
instances where they're suitable).
In this case, I'd rather see a registration mechanism for the current_timer
where we take a pointer to read_current_timer and register the delay at the
same time. That can be added when somebody else decides they want to make
use of the new delay routines.
> Tested-off-by: Shinya Kuribayashi <shinya.kuribayashi.px@renesas.com>
Thanks!
Will
next prev parent reply other threads:[~2012-07-05 14:15 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 17:33 [PATCH v2 0/2] Use architected timers for delay loop Will Deacon
2012-06-29 17:33 ` [PATCH v2 1/2] ARM: arch timer: implement read_current_timer and get_cycles Will Deacon
2012-07-02 19:14 ` Stephen Boyd
2012-07-05 12:35 ` Shinya Kuribayashi
2012-07-05 12:59 ` Will Deacon
2012-06-29 17:33 ` [PATCH v2 2/2] ARM: delay: allow timer-based delay implementation to be selected Will Deacon
2012-07-02 19:14 ` Stephen Boyd
2012-07-02 21:53 ` Will Deacon
2012-07-03 12:09 ` Shinya Kuribayashi
2012-07-04 15:36 ` Will Deacon
2012-07-05 12:12 ` Shinya Kuribayashi
2012-07-05 12:56 ` Will Deacon
2012-07-05 16:51 ` Stephen Boyd
2012-07-05 13:06 ` Shinya Kuribayashi
2012-07-05 14:15 ` Will Deacon [this message]
2012-07-12 7:33 ` Shinya Kuribayashi
2012-07-12 8:44 ` Will Deacon
2012-07-12 9:35 ` Shinya Kuribayashi
2012-07-12 16:40 ` Stephen Boyd
2012-07-13 2:16 ` Shinya Kuribayashi
2012-07-13 8:57 ` Will Deacon
2012-07-13 10:48 ` Shilimkar, Santosh
2012-07-13 11:13 ` Will Deacon
2012-07-13 12:04 ` Shilimkar, Santosh
2012-07-13 12:08 ` Will Deacon
2012-07-13 12:14 ` Shilimkar, Santosh
2012-07-13 12:23 ` Will Deacon
2012-07-13 12:28 ` Shilimkar, Santosh
2012-07-17 3:10 ` Shinya Kuribayashi
2012-07-17 6:11 ` Shilimkar, Santosh
2012-07-17 7:42 ` Shinya Kuribayashi
2012-07-17 9:05 ` Will Deacon
2012-07-19 12:43 ` Shinya Kuribayashi
2012-07-18 17:52 ` Will Deacon
2012-07-19 15:19 ` Jonathan Austin
2012-07-20 10:17 ` Will Deacon
2012-07-24 9:06 ` Shinya Kuribayashi
2012-07-24 9:15 ` Will Deacon
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=20120705141542.GH3399@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).