From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/3] ARM sched_clock selection enhancements
Date: Mon, 1 Apr 2013 15:58:31 -0500 [thread overview]
Message-ID: <1364849914-26420-1-git-send-email-robherring2@gmail.com> (raw)
From: Rob Herring <rob.herring@calxeda.com>
In preparation to move more timer initialization to use CLKSRC_OF and
out of the platforms, a way to select the timer used for sched_clock is
needed. This series makes the ARM sched_clock function override-able and
makes the sched_clock setup code prefer higher frequency counters. This
is sufficient at least on ARM Ltd boards to use the 24MHz counter rather
than sp804 and to always use the 64-bit architected timer when present.
This mechanism can be extended to DT properties if needed for any
non-discoverable h/w feature.
Patch 1 is unchanged from the prior version. Patch 2 is completely
rewritten and more simple than the prior version. It simply converts
sched_clock to a function pointer which can be overridden by the
architected timer init. It seems unlikely we will have other 64-bit
timers or not want to use the architected timer.
Rob
Rob Herring (3):
ARM: sched_clock: allow changing to higher frequency counter
ARM: make sched_clock just call a function pointer
ARM: arch_timer: use full 64-bit counter for sched_clock
arch/arm/include/asm/sched_clock.h | 2 ++
arch/arm/kernel/arch_timer.c | 15 ++++++++++-----
arch/arm/kernel/sched_clock.c | 15 +++++++++++++--
3 files changed, 25 insertions(+), 7 deletions(-)
--
1.7.10.4
next reply other threads:[~2013-04-01 20:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-01 20:58 Rob Herring [this message]
2013-04-01 20:58 ` [PATCH v2 1/3] ARM: sched_clock: allow changing to higher frequency counter Rob Herring
2013-04-01 20:58 ` [PATCH v2 2/3] ARM: make sched_clock just call a function pointer Rob Herring
2013-04-01 20:58 ` [PATCH v2 3/3] ARM: arch_timer: use full 64-bit counter for sched_clock Rob Herring
2013-04-19 16:27 ` 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=1364849914-26420-1-git-send-email-robherring2@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).