From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] ARM sched_clock selection enhancements
Date: Mon, 11 Mar 2013 21:26:34 -0500 [thread overview]
Message-ID: <1363055197-17296-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 support code prefer 64-bit
counters or 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.
Rob
Rob Herring (3):
ARM: sched_clock: allow changing to higher frequency counter
ARM: sched_clock: support 64-bit counters
ARM: arch_timer: use the 64-bit sched_clock setup
arch/arm/include/asm/sched_clock.h | 1 +
arch/arm/kernel/arch_timer.c | 8 +-------
arch/arm/kernel/sched_clock.c | 35 ++++++++++++++++++++++++++++++++---
3 files changed, 34 insertions(+), 10 deletions(-)
--
1.7.10.4
next reply other threads:[~2013-03-12 2:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 2:26 Rob Herring [this message]
2013-03-12 2:26 ` [PATCH 1/3] ARM: sched_clock: allow changing to higher frequency counter Rob Herring
2013-03-12 2:26 ` [PATCH 2/3] ARM: sched_clock: support 64-bit counters Rob Herring
2013-03-21 14:02 ` Christopher Covington
2013-03-21 22:15 ` Rob Herring
2013-03-22 12:03 ` Christopher Covington
2013-03-22 12:58 ` Rob Herring
2013-03-22 15:20 ` Russell King - ARM Linux
2013-03-22 11:09 ` Russell King - ARM Linux
2013-03-12 2:26 ` [PATCH 3/3] ARM: arch_timer: use the 64-bit sched_clock setup Rob Herring
2013-03-12 9:23 ` [PATCH 0/3] ARM sched_clock selection enhancements Russell King - ARM Linux
2013-03-12 12:43 ` Rob Herring
2013-03-20 23:03 ` 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=1363055197-17296-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.