From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2] ARM: Push selects for TWD/SCU into machine entries
Date: Wed, 24 Oct 2012 11:54:54 -0600 [thread overview]
Message-ID: <50882B6E.5020103@wwwdotorg.org> (raw)
In-Reply-To: <1351099475-29349-1-git-send-email-sboyd@codeaurora.org>
On 10/24/2012 11:24 AM, Stephen Boyd wrote:
> The TWD and SCU configs are selected by default as long as
> MSM_SCORPIONMP is false and/or MCT is false. Implementing the
> logic this way certainly saves lines in the Kconfig but it
> precludes those machines which select MSM_SCORPIONMP or MCT from
> participating in the single zImage effort because when those
> machines are combined with other SMP capable machines the TWD and
> SCU are no longer selected by default.
>
> Push the select out to the machine entries so that we can compile
> these machines together and still select the appropriate configs.
Acked-by: Stephen Warren <swarren@nvidia.com>
> diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
> @@ -633,6 +633,8 @@ config ARCH_TEGRA
> select GENERIC_GPIO
> select HAVE_CLK
> select HAVE_SMP
> + select HAVE_ARM_SCU if SMP
> + select HAVE_ARM_TWD if LOCAL_TIMERS
> select MIGHT_HAVE_CACHE_L2X0
> select SPARSE_IRQ
> select USE_OF
Where will this patch be merged?
It probably won't happen for 3.8, but that config fragment will move to
arch/arm/mach-tegra/Kconfig when Tegra enables single zImage support, I
believe. So, it'd be good to make sure this patch gets merged somewhere
that could be used as a baseline for other arm-soc branches if needed,
to avoid merge conflicts.
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Warren <swarren@wwwdotorg.org>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, David Brown <davidb@codeaurora.org>,
Kukjin Kim <kgene.kim@samsung.com>,
Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <rob.herring@calxeda.com>,
Russell King <linux@arm.linux.org.uk>,
Sascha Hauer <kernel@pengutronix.de>,
Shiraz Hashim <shiraz.hashim@st.com>,
Srinidhi Kasagar <srinidhi.kasagar@stericsson.com>,
Tony Lindgren <tony@atomide.com>
Subject: Re: [PATCHv2] ARM: Push selects for TWD/SCU into machine entries
Date: Wed, 24 Oct 2012 11:54:54 -0600 [thread overview]
Message-ID: <50882B6E.5020103@wwwdotorg.org> (raw)
In-Reply-To: <1351099475-29349-1-git-send-email-sboyd@codeaurora.org>
On 10/24/2012 11:24 AM, Stephen Boyd wrote:
> The TWD and SCU configs are selected by default as long as
> MSM_SCORPIONMP is false and/or MCT is false. Implementing the
> logic this way certainly saves lines in the Kconfig but it
> precludes those machines which select MSM_SCORPIONMP or MCT from
> participating in the single zImage effort because when those
> machines are combined with other SMP capable machines the TWD and
> SCU are no longer selected by default.
>
> Push the select out to the machine entries so that we can compile
> these machines together and still select the appropriate configs.
Acked-by: Stephen Warren <swarren@nvidia.com>
> diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
> @@ -633,6 +633,8 @@ config ARCH_TEGRA
> select GENERIC_GPIO
> select HAVE_CLK
> select HAVE_SMP
> + select HAVE_ARM_SCU if SMP
> + select HAVE_ARM_TWD if LOCAL_TIMERS
> select MIGHT_HAVE_CACHE_L2X0
> select SPARSE_IRQ
> select USE_OF
Where will this patch be merged?
It probably won't happen for 3.8, but that config fragment will move to
arch/arm/mach-tegra/Kconfig when Tegra enables single zImage support, I
believe. So, it'd be good to make sure this patch gets merged somewhere
that could be used as a baseline for other arm-soc branches if needed,
to avoid merge conflicts.
next prev parent reply other threads:[~2012-10-24 17:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 17:24 [PATCHv2] ARM: Push selects for TWD/SCU into machine entries Stephen Boyd
2012-10-24 17:24 ` Stephen Boyd
2012-10-24 17:54 ` Stephen Warren [this message]
2012-10-24 17:54 ` Stephen Warren
2012-10-25 18:04 ` Stephen Boyd
2012-10-25 18:04 ` Stephen Boyd
2012-10-25 20:34 ` David Brown
2012-10-25 20:34 ` David Brown
-- strict thread matches above, loose matches on Subject: below --
2013-02-27 23:28 Stephen Boyd
2013-02-27 23:28 ` Stephen Boyd
2013-02-27 23:43 ` Stephen Warren
2013-02-27 23:43 ` Stephen Warren
2013-03-05 1:45 ` Stephen Boyd
2013-03-05 1:45 ` Stephen Boyd
2013-03-05 22:34 ` Arnd Bergmann
2013-03-05 22:34 ` Arnd Bergmann
2013-03-16 19:32 ` Stephen Boyd
2013-03-16 19:32 ` Stephen Boyd
2013-03-26 17:34 ` Stephen Boyd
2013-03-26 17:34 ` Stephen Boyd
2013-04-09 16:47 ` Stephen Boyd
2013-04-09 16:47 ` Stephen Boyd
2013-04-09 18:32 ` Arnd Bergmann
2013-04-09 18:32 ` Arnd Bergmann
2013-04-09 19:35 ` Arnd Bergmann
2013-04-09 19:35 ` Arnd Bergmann
2013-04-09 19:35 ` Arnd Bergmann
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=50882B6E.5020103@wwwdotorg.org \
--to=swarren@wwwdotorg.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 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.