From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Push selects for TWD/SCU into machine entries
Date: Thu, 04 Oct 2012 12:22:28 -0700 [thread overview]
Message-ID: <506DE1F4.9090309@codeaurora.org> (raw)
In-Reply-To: <506D899C.6010705@gmail.com>
On 10/04/12 06:05, Rob Herring wrote:
> On 10/04/2012 03:50 AM, Stephen Boyd wrote:
>> The TWD and SCU configs are selected by default as long as
>> 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 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.
>>
>> Push the select out to the machine entries so that we can compile
>> these machines together and still select the appropriate configs.
> I think this is the wrong direction as I'd like to see the platform
> selects shrink. I believe the local timers are run-time enabled now, so
> can't we just drop the condition and always select TWD and SCU for
> multi-platform?
That sounds fine for multi-platform but it penalizes the "optimized"
images made for a particular device that doesn't want any extra code
than is necessary. Isn't this why we have the Kconfig language?
>
> Or perhaps we need a CortexA9 config symbol that selects V7, GIC, TWD,
> SCU, SMP, PL310, errata, etc. rather than duplicating those for every
> platform.
>
>
This sounds like a good consolidation of lines that can be done in
parallel to this patch. Care to send a patch on top?
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd@codeaurora.org>
To: Rob Herring <robherring2@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org,
Kukjin Kim <kgene.kim@samsung.com>,
Russell King <linux@arm.linux.org.uk>,
Pawel Moll <pawel.moll@arm.com>,
Srinidhi Kasagar <srinidhi.kasagar@stericsson.com>,
Tony Lindgren <tony@atomide.com>,
Linus Walleij <linus.walleij@linaro.org>,
Stephen Warren <swarren@wwwdotorg.org>,
linux-kernel@vger.kernel.org,
Shiraz Hashim <shiraz.hashim@st.com>,
Simon Horman <horms@verge.net.au>,
Viresh Kumar <viresh.linux@gmail.com>,
Sascha Hauer <kernel@pengutronix.de>,
David Brown <davidb@codeaurora.org>,
Marc Zyngier <marc.zyngier@arm.com>
Subject: Re: [PATCH] ARM: Push selects for TWD/SCU into machine entries
Date: Thu, 04 Oct 2012 12:22:28 -0700 [thread overview]
Message-ID: <506DE1F4.9090309@codeaurora.org> (raw)
In-Reply-To: <506D899C.6010705@gmail.com>
On 10/04/12 06:05, Rob Herring wrote:
> On 10/04/2012 03:50 AM, Stephen Boyd wrote:
>> The TWD and SCU configs are selected by default as long as
>> 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 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.
>>
>> Push the select out to the machine entries so that we can compile
>> these machines together and still select the appropriate configs.
> I think this is the wrong direction as I'd like to see the platform
> selects shrink. I believe the local timers are run-time enabled now, so
> can't we just drop the condition and always select TWD and SCU for
> multi-platform?
That sounds fine for multi-platform but it penalizes the "optimized"
images made for a particular device that doesn't want any extra code
than is necessary. Isn't this why we have the Kconfig language?
>
> Or perhaps we need a CortexA9 config symbol that selects V7, GIC, TWD,
> SCU, SMP, PL310, errata, etc. rather than duplicating those for every
> platform.
>
>
This sounds like a good consolidation of lines that can be done in
parallel to this patch. Care to send a patch on top?
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2012-10-04 19:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-04 8:50 [PATCH] ARM: Push selects for TWD/SCU into machine entries Stephen Boyd
2012-10-04 8:50 ` Stephen Boyd
2012-10-04 8:52 ` viresh kumar
2012-10-04 8:52 ` viresh kumar
2012-10-04 9:11 ` Santosh Shilimkar
2012-10-04 9:11 ` Santosh Shilimkar
2012-10-04 19:01 ` Stephen Boyd
2012-10-04 19:01 ` Stephen Boyd
2012-10-05 1:12 ` Simon Horman
2012-10-05 1:12 ` Simon Horman
2012-10-05 6:42 ` Santosh Shilimkar
2012-10-05 6:42 ` Santosh Shilimkar
2012-10-04 13:05 ` Rob Herring
2012-10-04 13:05 ` Rob Herring
2012-10-04 19:22 ` Stephen Boyd [this message]
2012-10-04 19:22 ` Stephen Boyd
2012-10-08 12:56 ` Rob Herring
2012-10-08 12:56 ` Rob Herring
2012-10-05 1:13 ` Simon Horman
2012-10-05 1:13 ` Simon Horman
2012-10-08 12:15 ` Pawel Moll
2012-10-08 12:15 ` Pawel Moll
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=506DE1F4.9090309@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 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.