From: Ionela Voinescu <ionela.voinescu@arm.com>
To: rjw@rjwysocki.net, viresh.kumar@linaro.org,
dietmar.eggemann@arm.com, catalin.marinas@arm.com,
sudeep.holla@arm.com, will@kernel.org,
valentin.schneider@arm.com
Cc: ionela.voinescu@arm.com, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org
Subject: [PATCH v5 0/5] cpufreq: improve frequency invariance support
Date: Tue, 1 Sep 2020 21:55:44 +0100 [thread overview]
Message-ID: <20200901205549.30096-1-ionela.voinescu@arm.com> (raw)
Hi,
v4->v5
- I've applied Viresh's remaining suggestion and Acked-by/s
- v4 can be found at [4]
- v5 is based on linux-next 20200828
Thank you,
Ionela.
---
v3->v4:
- addressing Viresh's comments on patches 1/5 and 3/5, and
- with his Acked-by applied for the rest of the patches;
- v3 can be found at [3], and
- this is based on linux-next 20200827.
v2->v3
- v2 can be found at [2]
- 1/5 was introduced to check input frequencies to
arch_set_freq_scale() as recommended by Rafael
- The previous 2/7 was squashed into 1/7 - now 2/5, with additions to
the changelog as suggested by Rafael.
- The previous 3/7 (BL_SWITCHER handling) was dropped to be handled
in a separate patch. This does not change the current functionality.
- The previous 4/7 - now 3/5 is simplified as suggested by Viresh.
- 3/5 - cpufreq_supports_freq_invariance() replaces
cpufreq_sets_freq_scale(). The meaning chosen for
cpufreq_supports_freq_invariance() is whether it can set the frequency
scale factor, not whether arch_set_freq_scale() actually does.
- 4/5 - Change after Catalin's Ack: The changes to
arch_set_thermal_pressure() were dropped as they were done in a separate
patch. Therefore this patch now has a subset of the previous changes
at 5/7
- 5/5 - Change after Catalin's Ack:
s/cpufreq_sets_freq_scale/cpufreq_supports_freq_invariance
- v3 is based on linux-next 20200814
v1 -> v2:
- v1 can be found at [1]
- No cpufreq flags are introduced
- Previous patches 2/8 and 3/8 were squashed in this series under 1/7,
to ensure bisection.
- 2/7 was introduced as a proposal for Viresh's suggestion to use
policy->cur in the call to arch_set_freq_scale() and is extended to
support drivers that implement the target() callback as well
- Additional commit message changes are added to 1/7 and 2/7, to
clarify that the definition of arch_set_freq_scale() will filter
settings of the scale factor, if unwanted
- 3/7 disables setting of the scale factor for
CONFIG_BL_SWITCHER, as Dietmar suggested
- Small change introduced in 4/7 to disable cpufreq-based frequency
invariance for the users of the default arch_set_freq_scale() call
which will not actually set a scale factor
- build issue solved (reported by 0day test)
- v2 is based on linux-next 20200716
- all functional tests in v1 were repeated for v2
[1] https://lore.kernel.org/lkml/20200701090751.7543-1-ionela.voinescu@arm.com/
[2] https://lore.kernel.org/lkml/20200722093732.14297-1-ionela.voinescu@arm.com/
[3] https://lore.kernel.org/lkml/20200824210252.27486-1-ionela.voinescu@arm.com/
[4] https://lore.kernel.org/lkml/20200828173303.11939-1-ionela.voinescu@arm.com/
Ionela Voinescu (3):
arch_topology: validate input frequencies to arch_set_freq_scale()
cpufreq: move invariance setter calls in cpufreq core
cpufreq: report whether cpufreq supports Frequency Invariance (FI)
Valentin Schneider (2):
arch_topology, cpufreq: constify arch_* cpumasks
arch_topology, arm, arm64: define arch_scale_freq_invariant()
arch/arm/include/asm/topology.h | 1 +
arch/arm64/include/asm/topology.h | 1 +
arch/arm64/kernel/topology.c | 9 ++++++-
drivers/base/arch_topology.c | 13 ++++++++--
drivers/cpufreq/cpufreq-dt.c | 10 +-------
drivers/cpufreq/cpufreq.c | 33 +++++++++++++++++++++++---
drivers/cpufreq/qcom-cpufreq-hw.c | 9 +------
drivers/cpufreq/scmi-cpufreq.c | 12 ++--------
drivers/cpufreq/scpi-cpufreq.c | 6 +----
drivers/cpufreq/vexpress-spc-cpufreq.c | 12 ++--------
include/linux/arch_topology.h | 4 +++-
include/linux/cpufreq.h | 8 ++++++-
12 files changed, 68 insertions(+), 50 deletions(-)
base-commit: b36c969764ab12faebb74711c942fa3e6eaf1e96
--
2.17.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-09-01 20:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 20:55 Ionela Voinescu [this message]
2020-09-01 20:55 ` [PATCH v5 1/5] arch_topology: validate input frequencies to arch_set_freq_scale() Ionela Voinescu
2020-09-02 13:32 ` Sudeep Holla
2020-09-01 20:55 ` [PATCH v5 2/5] cpufreq: move invariance setter calls in cpufreq core Ionela Voinescu
2020-09-02 13:30 ` Sudeep Holla
2020-09-01 20:55 ` [PATCH v5 3/5] cpufreq: report whether cpufreq supports Frequency Invariance (FI) Ionela Voinescu
2020-09-02 13:28 ` Sudeep Holla
2020-09-03 13:45 ` Ionela Voinescu
2020-09-03 14:19 ` Sudeep Holla
2020-09-01 20:55 ` [PATCH v5 4/5] arch_topology, cpufreq: constify arch_* cpumasks Ionela Voinescu
2020-09-02 13:25 ` Sudeep Holla
2020-09-01 20:55 ` [PATCH v5 5/5] arch_topology, arm, arm64: define arch_scale_freq_invariant() Ionela Voinescu
2020-09-02 13:24 ` Sudeep Holla
2020-09-03 13:32 ` [PATCH v5 0/5] cpufreq: improve frequency invariance support Ionela Voinescu
2020-09-04 4:38 ` Viresh Kumar
2020-09-18 17:12 ` Rafael J. Wysocki
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=20200901205549.30096-1-ionela.voinescu@arm.com \
--to=ionela.voinescu@arm.com \
--cc=catalin.marinas@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=sudeep.holla@arm.com \
--cc=valentin.schneider@arm.com \
--cc=viresh.kumar@linaro.org \
--cc=will@kernel.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).