From: tixy@linaro.org (Jon Medhurst (Tixy))
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: multi_v7_defconfig: major refresh
Date: Fri, 01 Aug 2014 16:53:19 +0100 [thread overview]
Message-ID: <1406908399.22757.12.camel@linaro1.home> (raw)
In-Reply-To: <53DBAAEA.2010908@arm.com>
On Fri, 2014-08-01 at 15:57 +0100, Sudeep Holla wrote:
>
> On 01/08/14 12:28, Jon Medhurst (Tixy) wrote:
> > On Fri, 2014-08-01 at 12:12 +0100, Sudeep Holla wrote:
> >>
> >> On 01/08/14 12:03, Olof Johansson wrote:
> >>> On Fri, Aug 1, 2014 at 4:01 AM, Jon Medhurst (Tixy) <tixy@linaro.org> wrote:
> >>>> On Fri, 2014-08-01 at 11:26 +0100, Sudeep Holla wrote:
>
> [...]
>
> >>>>
> >>>>> One way to achieve this:
> >>>>> (There's sysfs to re-enable it runtime)
> >>>>
> >>>> The opposite is also true, if you don't want the switcher enabled you
> >>>> can disable it by the same method after boot ;-)
> >>>>
> >>>>> -->8
> >>>>> diff --git a/arch/arm/common/bL_switcher.c b/arch/arm/common/bL_switcher.c
> >>>>> index 490f3dced749..f4c36e70166a 100644
> >>>>> --- a/arch/arm/common/bL_switcher.c
> >>>>> +++ b/arch/arm/common/bL_switcher.c
> >>>>> @@ -794,7 +794,7 @@ static int bL_switcher_hotplug_callback(struct
> >>>>> notifier_block *nfb,
> >>>>> return NOTIFY_DONE;
> >>>>> }
> >>>>>
> >>>>> -static bool no_bL_switcher;
> >>>>> +static bool no_bL_switcher = true;
> >>>>
> >>>> This changes the default for everyone, which I guess is fair enough if
> >>>> there is a good reason, but I'm not sure there is.
> >>>
> >>> No, I don't think there is.
> >>>
> >>
> >> It's just that people using TC2 will suddenly see 3 of the 5 CPUs missing.
> >
> > Yes, if they we're previously using multi_v7_defconfig (do people
> > working specifically with TC2's use that?)
> >
>
> I don't, but assumed many might use it.
>
> > Conversely, with the change in default proposed above, anyone with their
> > own configs enabling the switcher will suddenly see the number of CPUs
> > go from 2 to 5. We also have the situation where we have a config
> > option, which when enabled, doesn't actually do anything unless the user
> > also changes boot arguments or takes measures to enable it after boot.
> > Which seems the wrong way for things to work to me.
> >
>
> OK, makes sense. Just curious how many big.LITTLE platforms have CPUFreq
> support and integrated with bL switcher. Otherwise we end up switching
> clusters/cpus using dummy i/f anyways
Hmm, that is a point, there are 3 other big.LITTLE SoC's I can spot in
mainline [1], and I wouldn't want to speculate how they would be
affected by having the big.LITTLE switcher enabled.
[1] exynos5420, exynos5260, r8a7790
--
Tixy
next prev parent reply other threads:[~2014-08-01 15:53 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 18:01 [PATCH] ARM: multi_v7_defconfig: major refresh Olof Johansson
2014-07-22 18:36 ` Arnd Bergmann
2014-07-22 20:28 ` Olof Johansson
2014-07-31 6:07 ` Tushar Behera
2014-07-31 6:26 ` Sachin Kamat
2014-08-01 6:44 ` Sachin Kamat
2014-08-01 12:53 ` Bartlomiej Zolnierkiewicz
2014-08-03 3:17 ` Olof Johansson
2014-08-05 11:39 ` Sachin Kamat
2014-08-11 3:05 ` Olof Johansson
2014-08-27 7:59 ` Bartlomiej Zolnierkiewicz
2014-11-14 11:07 ` Bartlomiej Zolnierkiewicz
2014-07-23 14:24 ` Pawel Moll
2014-08-01 10:26 ` Sudeep Holla
2014-08-01 11:01 ` Jon Medhurst (Tixy)
2014-08-01 11:03 ` Olof Johansson
2014-08-01 11:12 ` Sudeep Holla
2014-08-01 11:28 ` Jon Medhurst (Tixy)
2014-08-01 14:57 ` Sudeep Holla
2014-08-01 15:53 ` Jon Medhurst (Tixy) [this message]
2014-08-03 3:20 ` Olof Johansson
2014-08-08 18:12 ` Kevin Hilman
2014-08-08 18:26 ` Nicolas Pitre
2014-08-08 18:44 ` Kevin Hilman
2014-08-08 18:37 ` Amit Kucheria
2014-08-08 18:04 ` Kevin Hilman
2014-08-08 18:17 ` Nicolas Pitre
2014-08-01 11:06 ` Pawel Moll
2014-08-03 3:23 ` Olof Johansson
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=1406908399.22757.12.camel@linaro1.home \
--to=tixy@linaro.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).