From: Viresh Kumar <viresh.kumar@linaro.org>
To: Jun Nie <jun.nie@linaro.org>, Nishanth Menon <nm@ti.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Stephen Boyd <sboyd@kernel.org>,
Viresh Kumar <vireshk@kernel.org>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
linux-pm@vger.kernel.org,
Vincent Guittot <vincent.guittot@linaro.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] OPP: Simplify set_required_opp handling
Date: Wed, 22 Feb 2023 16:36:36 +0530 [thread overview]
Message-ID: <cover.1677063656.git.viresh.kumar@linaro.org> (raw)
Hello,
The required-opps configuration is closely tied to genpd and performance
states at the moment and it is not very obvious that required-opps can
live without genpds. Though we don't support configuring required-opps
for non-genpd cases currently.
This patchset aims at cleaning up this a bit, just like what's done for clk and
regulators. This also makes it possible for platforms to provide their own
version of set_required_opps() helper, which can be used to configure the
devfreq device propertly.
Jun,
I haven't found time to test this through yet, though there isn't much anyway I
guess. Can you see if these can solve your problem properly ?
Viresh Kumar (3):
OPP: Handle all genpd cases together in _set_required_opps()
OPP: Move required opps configuration to specialized callback
OPP: Allow platforms to add a set_required_opps() callback
drivers/opp/core.c | 113 ++++++++++++++++++++++++++++-------------
drivers/opp/of.c | 3 ++
drivers/opp/opp.h | 4 ++
include/linux/pm_opp.h | 5 ++
4 files changed, 91 insertions(+), 34 deletions(-)
--
2.31.1.272.g89b43f80a514
next reply other threads:[~2023-02-22 11:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 11:06 Viresh Kumar [this message]
2023-02-22 11:06 ` [PATCH 1/3] OPP: Handle all genpd cases together in _set_required_opps() Viresh Kumar
2023-03-01 13:03 ` Ulf Hansson
2023-02-22 11:06 ` [PATCH 2/3] OPP: Move required opps configuration to specialized callback Viresh Kumar
2023-03-01 13:06 ` Ulf Hansson
2023-04-03 4:29 ` Viresh Kumar
2023-02-22 11:06 ` [PATCH 3/3] OPP: Allow platforms to add a set_required_opps() callback Viresh Kumar
2023-02-23 9:56 ` [PATCH 0/3] OPP: Simplify set_required_opp handling Jun Nie
2023-02-24 2:17 ` Viresh Kumar
2023-02-24 8:17 ` Jun Nie
2023-02-27 4:23 ` Viresh Kumar
2023-02-27 9:21 ` Jun Nie
2023-02-27 9:29 ` Viresh Kumar
2023-03-06 10:48 ` Jun Nie
2023-04-03 4:30 ` Viresh Kumar
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=cover.1677063656.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=jun.nie@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=nm@ti.com \
--cc=rafael@kernel.org \
--cc=sboyd@kernel.org \
--cc=vincent.guittot@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.