From: Nicola Mazzucato <nicola.mazzucato@arm.com>
To: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org, sudeep.holla@arm.com,
rjw@rjwysocki.net, vireshk@kernel.org, robh+dt@kernel.org,
sboyd@kernel.org, nm@ti.com
Cc: daniel.lezcano@linaro.org, morten.rasmussen@arm.com,
chris.redpath@arm.com, nicola.mazzucato@arm.com
Subject: [PATCH v4 0/4] CPUFreq: Add support for opp-sharing cpus
Date: Wed, 2 Dec 2020 17:23:52 +0000 [thread overview]
Message-ID: <20201202172356.10508-1-nicola.mazzucato@arm.com> (raw)
Hi All,
In this V4 posting I have fixed suggestions on opp/of and have added the
implementation for scmi-cpufreq driver.
This is to support systems where exposed cpu performance controls are more
fine-grained that the platform's ability to scale cpus independently.
[v4]
* Remove unconditional set of opp_table->shared_opp to exclusive
* Add implementation for scmi-cpufreq
* Change subject
These patches are on top of:
next-20201201 + Lukasz Luba's patches (waiting for Rafael) [1]
[v3]
* Remove proposal for new 'cpu-performance-dependencies' as we instead
can reuse the opp table.
* Update documentation for devicetree/bindings/opp
* Minor changes within opp to support empty opp table
* Rework the RFC by adding a second proposal
[v2]
* Fix errors when running make dt_binding_check
* Improve commit message description for the dt-binding
* Add RFC for implementation in cpufreq-core and one of its
drivers.
Nicola Mazzucato (3):
dt-bindings/opp: Update documentation for opp-shared
opp/of: Allow empty opp-table with opp-shared
scmi-cpufreq: get opp_shared_cpus from opp-v2 for EM
Sudeep Holla (1):
cpufreq: blacklist Arm Vexpress platforms in cpufreq-dt-platdev
Documentation/devicetree/bindings/opp/opp.txt | 53 +++++++++++++++++++
drivers/cpufreq/cpufreq-dt-platdev.c | 2 +
drivers/cpufreq/scmi-cpufreq.c | 51 ++++++++++++------
drivers/opp/of.c | 7 ++-
4 files changed, 95 insertions(+), 18 deletions(-)
[1] https://lore.kernel.org/linux-pm/20201124104346.27167-1-lukasz.luba@arm.com/
--
2.27.0
next reply other threads:[~2020-12-02 17:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 17:23 Nicola Mazzucato [this message]
2020-12-02 17:23 ` [PATCH v4 1/4] dt-bindings/opp: Update documentation for opp-shared Nicola Mazzucato
2020-12-08 4:29 ` Viresh Kumar
2020-12-08 7:15 ` Nicola Mazzucato
2020-12-02 17:23 ` [PATCH v4 2/4] opp/of: Allow empty opp-table with opp-shared Nicola Mazzucato
2020-12-02 17:23 ` [PATCH v4 3/4] scmi-cpufreq: get opp_shared_cpus from opp-v2 for EM Nicola Mazzucato
2020-12-08 5:50 ` Viresh Kumar
2020-12-08 7:22 ` Nicola Mazzucato
2020-12-08 7:26 ` Viresh Kumar
2020-12-08 10:58 ` Nicola Mazzucato
2020-12-08 11:01 ` Viresh Kumar
2020-12-08 11:21 ` Sudeep Holla
2020-12-08 11:20 ` Sudeep Holla
2020-12-08 11:34 ` Lukasz Luba
2020-12-08 12:22 ` Sudeep Holla
2020-12-08 13:17 ` Nicola Mazzucato
2020-12-09 5:45 ` Viresh Kumar
2020-12-09 9:20 ` Nicola Mazzucato
2020-12-09 9:41 ` Sudeep Holla
2020-12-02 17:23 ` [PATCH v4 4/4] cpufreq: blacklist Arm Vexpress platforms in cpufreq-dt-platdev Nicola Mazzucato
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=20201202172356.10508-1-nicola.mazzucato@arm.com \
--to=nicola.mazzucato@arm.com \
--cc=chris.redpath@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=morten.rasmussen@arm.com \
--cc=nm@ti.com \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=vireshk@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