From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Carlos Alberto Lopez Perez <clopez@igalia.com>
Cc: Martin Bark <martin@barkynet.com>,
Julien Grossholtz <julien.grossholtz@openest.io>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] configs/raspberrypi*: stop setting powersave as the default CPU governor
Date: Sat, 21 Oct 2023 23:38:00 +0200 [thread overview]
Message-ID: <20231021213800.GG2607@scaer> (raw)
In-Reply-To: <20231020142041.25503-1-clopez@igalia.com>
Carlos, All,
On 2023-10-20 15:20 +0100, Carlos Alberto Lopez Perez spake thusly:
> * The defconfigs from the RPi Kernel set `powersave` as the default
> CPU governor, which is a bad idea as that reduces performance by
> setting the CPU frequency to the minimum one.
>
> * In case of a buildroot build user-space is not configured by default
> to change the CPU governor, so `powersave` will remain the CPU
> governor and it will slow down everything.
>
> * I submitted a fix for those defconfigs to upstream here:
> https://github.com/raspberrypi/linux/pull/5666
> However, we shouldn't wait until that is accepted and backported
> to all the stable branches (if ever is).
Unfortunately, the rpi folks have rejected this change:
https://github.com/raspberrypi/linux/pull/5666#issuecomment-1772531097
We're not changing it.
So, as much as I understand the situation, we're are not going to go
counter the upstream decision.
Besides, it is not proper kconfig syntax, see below.
[--SNIP--]
> diff --git a/board/raspberrypi/default-cpu-governor.fragment b/board/raspberrypi/default-cpu-governor.fragment
> new file mode 100644
> index 0000000000..e2e201d71d
> --- /dev/null
> +++ b/board/raspberrypi/default-cpu-governor.fragment
> @@ -0,0 +1,9 @@
> +# The defconfigs from the RPi Kernel set "powersave" as the default CPU governor.
> +# That is a bad idea as it reduces performance, so we unset that default option here.
> +# The option to build the powersave governor (but not as the default) is also enabled.
> +# A fix for this was sent to upstream: https://github.com/raspberrypi/linux/pull/5666
> +# However, we need to carry this option override until those defconfigs are fixed on
> +# *all* the kernel branches that we support. So that can be a long time depending
> +# on wheter the above PR gets accepted and/or backported to the stable branches.
> +CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE=n
In kconfig, a symbol is never set to 'n'; rather it is not set as a
comment, e.g."
# CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-10-21 21:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 14:20 [Buildroot] [PATCH 1/1] configs/raspberrypi*: stop setting powersave as the default CPU governor Carlos Alberto Lopez Perez
2023-10-21 21:38 ` Yann E. MORIN [this message]
2023-10-23 12:40 ` Marcus Hoffmann via buildroot
2023-10-23 16:25 ` Yann E. MORIN
2023-10-23 20:23 ` Carlos Alberto Lopez Perez
2023-10-24 14:01 ` [Buildroot] [External] - " Vincent Fazio
2023-10-24 14:28 ` Carlos Alberto Lopez Perez
2023-10-24 14:52 ` Vincent Fazio
2023-10-24 15:00 ` Carlos Alberto Lopez Perez
2023-10-24 15:17 ` Vincent Fazio
2023-10-24 15:28 ` Carlos Alberto Lopez Perez
2023-10-24 19:07 ` Yann E. MORIN
2023-10-24 20:53 ` Carlos Alberto Lopez Perez
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=20231021213800.GG2607@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=clopez@igalia.com \
--cc=julien.grossholtz@openest.io \
--cc=martin@barkynet.com \
/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