From: shawn.guo@freescale.com (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 3/3] ARM: vf610: Add ARM Global Timer clocksource option
Date: Mon, 29 Sep 2014 19:51:41 +0800 [thread overview]
Message-ID: <20140929115122.GA14087@tiger> (raw)
In-Reply-To: <1411575610-20895-4-git-send-email-stefan@agner.ch>
On Wed, Sep 24, 2014 at 06:20:10PM +0200, Stefan Agner wrote:
> Add the ARM Global Timer as clocksource/scheduler clock option and
> use it as default scheduler clock. This leaves the PIT timer for
> other users e.g. the secondary Cortex-M4 core. Also, the Global Timer
> has double the precission (running at pheripheral clock compared to
> IPG clock) and a 64-bit incrementing counter register. We still keep
> the PIT timer as an secondary option in case the ARM Global Timer is
> not available.
>
> Signed-off-by: Stefan Agner <stefan@agner.ch>
> ---
> arch/arm/mach-imx/Kconfig | 19 ++++++++++++++++++-
> 1 file changed, 18 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm/mach-imx/Kconfig b/arch/arm/mach-imx/Kconfig
> index 11b2957..9482f58 100644
> --- a/arch/arm/mach-imx/Kconfig
> +++ b/arch/arm/mach-imx/Kconfig
> @@ -633,12 +633,29 @@ config SOC_VF610
> bool "Vybrid Family VF610 support"
> select ARM_GIC
> select PINCTRL_VF610
> - select VF_PIT_TIMER
> select PL310_ERRATA_769419 if CACHE_L2X0
>
> help
> This enable support for Freescale Vybrid VF610 processor.
>
> +choice
> + prompt "Clocksource for scheduler clock"
> + depends on SOC_VF610
> + default ARM_GLOBAL_TIMER
> +
> + config ARM_GLOBAL_TIMER
> + bool "Use ARM Global Timer"
> + select CLKSRC_ARM_GLOBAL_TIMER_SCHED_CLOCK
> + help
> + Use the ARM Global Timer as clocksource
> +
> + config VF_PIT_TIMER
> + bool "Use PIT timer"
> + help
> + Use SoC Periodic Interrupt Timer (PIT) as clocksource
> +
> +endchoice
> +
As per the report from 0-DAY kernel build test (thanks), the change
causes the following warning on a particular config.
warning: (ARCH_ROCKCHIP && ARCH_BCM_5301X) selects CLKSRC_ARM_GLOBAL_TIMER_SCHED_CLOCK which has unmet direct dependencies (ARM_GLOBAL_TIMER)
It looks the redefinition of ARM_GLOBAL_TIMER is the cause for that
warning. I think it's more safer to use new config symbols for choosing
the clocksource device for VF610. I propose the following change to fix
the warning. If there is no objection, I will squash it into the
original commit soon.
diff --git a/arch/arm/mach-imx/Kconfig b/arch/arm/mach-imx/Kconfig
index 9482f5837b7e..e26b0fdd72db 100644
--- a/arch/arm/mach-imx/Kconfig
+++ b/arch/arm/mach-imx/Kconfig
@@ -641,16 +641,18 @@ config SOC_VF610
choice
prompt "Clocksource for scheduler clock"
depends on SOC_VF610
- default ARM_GLOBAL_TIMER
+ default VF_USE_ARM_GLOBAL_TIMER
- config ARM_GLOBAL_TIMER
+ config VF_USE_ARM_GLOBAL_TIMER
bool "Use ARM Global Timer"
+ select ARM_GLOBAL_TIMER
select CLKSRC_ARM_GLOBAL_TIMER_SCHED_CLOCK
help
Use the ARM Global Timer as clocksource
- config VF_PIT_TIMER
+ config VF_USE_PIT_TIMER
bool "Use PIT timer"
+ select VF_PIT_TIMER
help
Use SoC Periodic Interrupt Timer (PIT) as clocksource
next prev parent reply other threads:[~2014-09-29 11:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 16:20 [PATCH v2 0/3] ARM: vf610: Fix/add clocksource Stefan Agner
2014-09-24 16:20 ` [PATCH v2 1/3] clocksource: vf_pit_timer: Support shutdown mode Stefan Agner
2014-09-25 12:19 ` Sergei Shtylyov
2014-09-24 16:20 ` [PATCH v2 2/3] ARM: dts: vf610: Add ARM Global Timer Stefan Agner
2014-09-26 1:41 ` Shawn Guo
2014-09-24 16:20 ` [PATCH v2 3/3] ARM: vf610: Add ARM Global Timer clocksource option Stefan Agner
2014-09-26 1:45 ` Shawn Guo
2014-09-29 11:51 ` Shawn Guo [this message]
2014-09-29 12:18 ` Stefan Agner
2014-09-24 17:06 ` [PATCH v2 0/3] ARM: vf610: Fix/add clocksource Bill Pringlemeir
2014-09-26 7:01 ` Daniel Lezcano
2014-09-26 7:24 ` Stefan Agner
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=20140929115122.GA14087@tiger \
--to=shawn.guo@freescale.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).