From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: MSM: Implement read_current_timer for msm timers
Date: Tue, 28 Aug 2012 00:59:32 +0100 [thread overview]
Message-ID: <20120827235932.GA8468@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <1346102319-24497-1-git-send-email-sboyd@codeaurora.org>
On Mon, Aug 27, 2012 at 10:18:39PM +0100, Stephen Boyd wrote:
> Setup the same timer used as the clocksource to be used as the
> read_current_timer implementation. This allows us to support a
> stable udelay implementation on MSMs where it's possible for the
> CPUs to scale speeds independently of one another.
>
> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
> ---
>
> I have some patches to send that add DT support to the MSM timer that
> this conflicts with slightly. I'm not too concerned though, but we may
> want to decide what tree this goes through when I send out those patches.
Cheers Stephen, this looks good to me. After looking at this code some more
I think I'll change the read_current_timer function pointer type to be:
unsigned long (*read_current_timer)(void);
since it doesn't make sense to return an error code from the platform
implementation (in fact, it will cause havoc in the delay loop).
I'll post a new patch -- rebasing your code should be trivial.
Cheers,
Will
prev parent reply other threads:[~2012-08-27 23:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 14:13 [PATCH 1/2] ARM: delay: set loops_per_jiffy when moving to timer-based loop Will Deacon
2012-08-24 14:13 ` [PATCH 2/2] ARM: delay: add registration mechanism for delay timer sources Will Deacon
2012-08-27 21:18 ` [PATCH] ARM: MSM: Implement read_current_timer for msm timers Stephen Boyd
2012-08-27 23:59 ` Will Deacon [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=20120827235932.GA8468@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).