From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/6] ARM: local timers: Add A15 architected timer support
Date: Mon, 16 Apr 2012 10:45:00 -0700 [thread overview]
Message-ID: <4F8C5A9C.9000506@codeaurora.org> (raw)
In-Reply-To: <1334592810-4382-3-git-send-email-marc.zyngier@arm.com>
On 04/16/12 09:13, Marc Zyngier wrote:
> diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
> index cf006d4..68c382d 100644
> --- a/arch/arm/Kconfig
> +++ b/arch/arm/Kconfig
> @@ -1543,6 +1543,13 @@ config HAVE_ARM_SCU
> help
> This option enables support for the ARM system coherency unit
>
> +config ARM_ARCH_TIMER
> + bool "Architected timer support"
> + depends on CPU_V7
> + select TICK_ONESHOT
I believe TICK_ONESHOT is a "hidden" option that should not be selected
outside the generic clockevents layer. It seems Russell and Thomas have
talked about this too, see 3872c48 (tick: Document TICK_ONESHOT config
option, 2012-03-31).
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2012-04-16 17:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 16:13 [PATCH v3 0/6] A7/A15 architected timer support Marc Zyngier
2012-04-16 16:13 ` [PATCH v3 1/6] ARM: local timers: reserve local_timer_register() to SMP Marc Zyngier
2012-04-16 16:13 ` [PATCH v3 2/6] ARM: local timers: Add A15 architected timer support Marc Zyngier
2012-04-16 17:45 ` Stephen Boyd [this message]
2012-04-17 9:21 ` Marc Zyngier
2012-04-16 16:13 ` [PATCH v3 3/6] ARM: architected timers: Add A15 specific sched_clock implementation Marc Zyngier
2012-04-16 16:13 ` [PATCH v3 4/6] ARM: architected timers: add DT support Marc Zyngier
2012-04-19 12:55 ` Arnd Bergmann
2012-04-19 13:07 ` Marc Zyngier
2012-04-16 16:13 ` [PATCH v3 5/6] ARM: architected timers: add support for UP timer Marc Zyngier
2012-04-16 16:13 ` [PATCH v3 6/6] ARM: vexpress: plug local timers into the DT code Marc Zyngier
2012-04-17 9:22 ` Pawel Moll
2012-04-17 9:41 ` Marc Zyngier
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=4F8C5A9C.9000506@codeaurora.org \
--to=sboyd@codeaurora.org \
--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).