From: Arnd Bergmann <arnd@arndb.de>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
arm-soc <arm@kernel.org>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
SoC Team <soc@kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ARM: config: multi_v7 Use schedutil cpufreq
Date: Wed, 25 Mar 2020 17:27:57 +0100 [thread overview]
Message-ID: <CAK8P3a3CkAfozaMMNsGk5VDib53veMhm7ExWZT+A2gc+J_GqWA@mail.gmail.com> (raw)
In-Reply-To: <20200302042205.tonnru7ysr46fht4@vireshk-i7>
On Mon, Mar 2, 2020 at 5:22 AM Viresh Kumar <viresh.kumar@linaro.org> wrote:
>
> On 29-02-20, 22:02, Linus Walleij wrote:
> > The multi v7 config is using the ondemand governor by default,
> > but the schedutil is mature and enabled by default in other
> > defconfigs, let's encourage schedutil as governor but keep
> > ondemand as compiled-in instead of the other way around.
> >
> > Cc: Rafael J. Wysocki <rjw@rjwysocki.net>
> > Cc: Viresh Kumar <viresh.kumar@linaro.org>
> > Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> > ---
> > ARM SoC folks: if you agree please apply this directly. I think
> > putting this in the multi v7 as default is a good way to
> > actively encourage this governor, unless Viresh or Rafael
> > objects.
> > ---
>
> FWIW, I have tried something similar for arm64 earlier.
>
> https://lore.kernel.org/lkml/af12e002bc165844101830c0eb00e283b536a879.1510813288.git.viresh.kumar@linaro.org/
I've dropped this one and not applied it for now after rereading the old thread.
If there is a broader agreement on what the default should be, please
collect more Acks and we can apply whatever you come up with.
Arnd
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-03-25 16:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-29 21:02 [PATCH] ARM: config: multi_v7 Use schedutil cpufreq Linus Walleij
2020-03-02 4:22 ` Viresh Kumar
2020-03-25 16:27 ` Arnd Bergmann [this message]
2020-03-26 22:08 ` Linus Walleij
2020-03-27 5:07 ` Viresh Kumar
2020-03-27 8:06 ` Vincent Guittot
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=CAK8P3a3CkAfozaMMNsGk5VDib53veMhm7ExWZT+A2gc+J_GqWA@mail.gmail.com \
--to=arnd@arndb.de \
--cc=arm@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=rjw@rjwysocki.net \
--cc=soc@kernel.org \
--cc=viresh.kumar@linaro.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).