From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] ARM: move timer-sp.c from versatile to common
Date: Thu, 30 Sep 2010 22:23:06 -0500 [thread overview]
Message-ID: <4CA5541A.9070108@gmail.com> (raw)
In-Reply-To: <20101001023921.GB25320@game.jcrosoft.org>
On 09/30/2010 09:39 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 17:49 Thu 30 Sep , Rob Herring wrote:
>> From: Rob Herring<rob.herring@smooth-stone.com>
>>
>> The timer-sp h/w used on versatile platforms can also be used for other
>> platforms, so move it to a common location.
>>
>> Rename timer names for clocksource and clockevent to generic name.
>> Which timer instance is which is platform dependent.
>>
> How about move it to drivers/clocksource ?
>
> Best Regards,
> J.
I'll defer to Russell. It's not exactly common practice to put timer
code there. The ones that are there don't appear to be the primary
system timers as they are initialized by initcalls which is not early
enough.
Rob
next prev parent reply other threads:[~2010-10-01 3:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 22:49 [PATCH 1/3] ARM: move timer-sp.c from versatile to common Rob Herring
2010-09-30 22:49 ` [PATCH 3/3] ARM: twd_smp: add clock api support Rob Herring
2010-10-01 0:49 ` Colin Cross
2010-10-01 2:03 ` Rob Herring
2010-10-01 2:30 ` Colin Cross
2010-10-01 3:14 ` Rob Herring
2010-10-01 3:27 ` Colin Cross
2010-10-01 17:04 ` Rob Herring
2010-10-01 18:22 ` Colin Cross
2010-10-01 18:34 ` Russell King - ARM Linux
2010-10-01 18:47 ` Rob Herring
2010-10-01 2:39 ` [PATCH 1/3] ARM: move timer-sp.c from versatile to common Jean-Christophe PLAGNIOL-VILLARD
2010-10-01 3:23 ` Rob Herring [this message]
2010-10-01 8:24 ` Russell King - ARM Linux
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=4CA5541A.9070108@gmail.com \
--to=robherring2@gmail.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).