From: pawel.moll@arm.com (Pawel Moll)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] arm: vexpress: select HAVE_ARM_ARCH_TIMER
Date: Mon, 17 Jun 2013 14:48:05 +0100 [thread overview]
Message-ID: <1371476885.3483.36.camel@hornet> (raw)
In-Reply-To: <1371462316-9201-2-git-send-email-mark.rutland@arm.com>
On Mon, 2013-06-17 at 10:45 +0100, Mark Rutland wrote:
> When building a ARCH_MULTI_V7 kernel, support for the architected timers
> won't be enabled out-of-the-box even when ARCH_VEXPRESS is selected,
> which is unexpected and disappointing when using a coretile with
> architected timers.
>
> Fix this up by having ARCH_VEXPRESS select HAVE_ARM_ARCH_TIMER.
>
> Signed-off-by: Mark Rutland <mark.rutland@arm.com>
> Cc: Pawel Moll <pawel.moll@arm.com>
> ---
> arch/arm/mach-vexpress/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm/mach-vexpress/Kconfig b/arch/arm/mach-vexpress/Kconfig
> index 5907e10..e0f4974 100644
> --- a/arch/arm/mach-vexpress/Kconfig
> +++ b/arch/arm/mach-vexpress/Kconfig
> @@ -9,6 +9,7 @@ config ARCH_VEXPRESS
> select COMMON_CLK_VERSATILE
> select CPU_V7
> select GENERIC_CLOCKEVENTS
> + select HAVE_ARM_ARCH_TIMER
> select HAVE_ARM_SCU if SMP
> select HAVE_ARM_TWD if LOCAL_TIMERS
> select HAVE_CLK
Acked-by: Pawel Moll <pawel.moll@arm.com>
Do you want me to queue it for 3.12?
Pawe?
next prev parent reply other threads:[~2013-06-17 13:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 9:45 [PATCH 0/2] arm: move HAVE_ARM_ARCH_TIMER selects into multi_v7 platforms Mark Rutland
2013-06-17 9:45 ` [PATCH 1/2] arm: vexpress: select HAVE_ARM_ARCH_TIMER Mark Rutland
2013-06-17 13:48 ` Pawel Moll [this message]
2013-06-17 14:02 ` Mark Rutland
2013-06-17 9:45 ` [PATCH 2/2] arm: highbank: " Mark Rutland
2013-06-17 13:45 ` 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=1371476885.3483.36.camel@hornet \
--to=pawel.moll@arm.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