From: Viresh Kumar <viresh.kumar@linaro.org>
To: Nicola Mazzucato <nicola.mazzucato@arm.com>
Cc: 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, daniel.lezcano@linaro.org,
morten.rasmussen@arm.com, chris.redpath@arm.com
Subject: Re: [PATCH v5 0/4] CPUFreq: Add support for opp-sharing cpus
Date: Wed, 9 Dec 2020 11:25:30 +0530 [thread overview]
Message-ID: <20201209055530.gadaie5lttpdprc6@vireshk-i7> (raw)
In-Reply-To: <20201208174229.24323-1-nicola.mazzucato@arm.com>
On 08-12-20, 17:42, Nicola Mazzucato wrote:
> Hi All,
>
> In this V5 posting I have addressed suggestions on opp/of and 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.
>
> Nicola Mazzucato (3):
> dt-bindings: opp: Allow empty OPP tables
> opp/of: Allow empty opp-table with opp-shared
Applied these two for now. Please rework the other patches based on
the feedback given on the other thread. Thanks.
--
viresh
prev parent reply other threads:[~2020-12-09 5:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 17:42 [PATCH v5 0/4] CPUFreq: Add support for opp-sharing cpus Nicola Mazzucato
2020-12-08 17:42 ` [PATCH v5 1/4] dt-bindings: opp: Allow empty OPP tables Nicola Mazzucato
2020-12-08 17:42 ` [PATCH v5 2/4] opp/of: Allow empty opp-table with opp-shared Nicola Mazzucato
2020-12-08 17:42 ` [PATCH v5 3/4] scmi-cpufreq: get opp_shared_cpus from opp-v2 for EM Nicola Mazzucato
2020-12-08 17:42 ` [PATCH v5 4/4] cpufreq: blacklist Arm Vexpress platforms in cpufreq-dt-platdev Nicola Mazzucato
2020-12-09 5:55 ` Viresh Kumar [this message]
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=20201209055530.gadaie5lttpdprc6@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--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=nicola.mazzucato@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;
as well as URLs for NNTP newsgroup(s).