From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/3] ARM: timer-sp: support timer clock freq other than 1MHz
Date: Tue, 21 Dec 2010 13:44:43 +0000 [thread overview]
Message-ID: <20101221134443.GA1556@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1286030086-25556-3-git-send-email-robherring2@gmail.com>
On Sat, Oct 02, 2010 at 09:34:45AM -0500, Rob Herring wrote:
> From: Rob Herring <rob.herring@smooth-stone.com>
>
> The timer-sp code is fixed to 1MHz timer clock. Add clock api
> calls to get the timer clock frequency and support for independent
> clock frequencies.
>
> Rename timer names for clocksource and clockevent to timer-sp or
> the clock connection ID string if provided.
>
> Signed-off-by: Rob Herring <rob.herring@smooth-stone.com>
As mentioned in the previous few days on the mailing list, rather than
having this code half-heartedly use the clk API, I'd much rather we did
a proper conversion. That means having the clk API up and running
earlier than we currently do on the ARM platforms.
In order to allow this to happen, I've queued an addition to the mdesc
record which provides an early hook which can be used for this kind of
early platform initialization.
So, after the next merge window, could you have another look at this
please?
next prev parent reply other threads:[~2010-12-21 13:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-02 14:34 [PATCH v2 0/3] ARM: add clock api to sp804 and smp_twd timers Rob Herring
2010-10-02 14:34 ` [PATCH v2 1/3] ARM: move timer-sp.c from versatile to common Rob Herring
2010-10-02 14:34 ` [PATCH v2 2/3] ARM: timer-sp: support timer clock freq other than 1MHz Rob Herring
2010-12-21 13:44 ` Russell King - ARM Linux [this message]
2010-12-21 14:14 ` Rob Herring
2010-10-02 14:34 ` [PATCH v2 3/3] ARM: twd_smp: add clock api support Rob Herring
2010-12-21 13:45 ` Russell King - ARM Linux
2011-01-12 21:28 ` Rob Herring
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=20101221134443.GA1556@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).