From: Dmitry Osipenko <digetx@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Peter Geis <pgwipeout@gmail.com>,
Nicolas Chauvet <kwizart@gmail.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Kevin Hilman <khilman@kernel.org>,
Peter De Schrijver <pdeschrijver@nvidia.com>,
Viresh Kumar <vireshk@kernel.org>,
Stephen Boyd <sboyd@kernel.org>, Nishanth Menon <nm@ti.com>,
Yangtao Li <tiny.windzz@gmail.com>,
Matt Merhar <mattmerhar@protonmail.com>
Cc: linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-pm@vger.kernel.org
Subject: [PATCH v4 0/4] OPP API fixes and improvements
Date: Thu, 21 Jan 2021 01:26:45 +0300 [thread overview]
Message-ID: <20210120222649.28149-1-digetx@gmail.com> (raw)
Hi,
This series fixes problems and adds features to OPP API that are required
for implementation of a power domain driver for NVIDIA Tegra SoCs.
It is a continuation of [1], where Viresh Kumar asked to factor OPP
patches into a separate series. I factored out the patches into this
series, addressed the previous review comments and re-based patches
on top of [2], which replaced some of my patches that added resource-managed
helpers.
[1] https://patchwork.ozlabs.org/project/linux-tegra/list/?series=221130
[2] https://lore.kernel.org/linux-pm/20210101165507.19486-1-tiny.windzz@gmail.com/
Changelog:
v4: - Fixed missing export of devm_pm_opp_attach_genpd(). Thanks to
Nicolas Chauvet for catching this problem.
- Removed a bit questionable locking from dev_pm_opp_sync_regulators()
and dev_pm_opp_set_voltage(). We may come back to the OPP locking
sometime later, it's not an essential problem right now. I moved
the lock from OPP core to the PD driver for now.
- Added "Make _set_opp_custom() work without regulators" patch,
which is made on top of "Prepare for ->set_opp() helper to work without
regulators" patch from Viresh Kumar. The set_opp() helper now works
without regulators.
v3: - Reordered patches by importance.
- Added locking to dev_pm_opp_set_voltage().
- Reworked "Fix adding OPP entries in a wrong order if rate is unavailable"
patch, like it was suggested by Viresh Kumar.
- Reworked "Support set_opp() customization without requiring to use
regulators" patch, like it was suggested by Viresh Kumar.
The opp_table->set_opp_data is now allocated by dev_pm_opp_register_set_opp_helper().
The set_opp_data is refcounted now and can be allocated by any other
OPP functions if this will become needed in the future for other OPP API
changes.
Dmitry Osipenko (4):
opp: Export devm_pm_opp_attach_genpd()
opp: Add dev_pm_opp_sync_regulators()
opp: Add dev_pm_opp_set_voltage()
opp: Make _set_opp_custom() work without regulators
drivers/opp/core.c | 119 +++++++++++++++++++++++++++++++++++++----
include/linux/pm_opp.h | 12 +++++
2 files changed, 122 insertions(+), 9 deletions(-)
--
2.29.2
next reply other threads:[~2021-01-20 22:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 22:26 Dmitry Osipenko [this message]
2021-01-20 22:26 ` [PATCH v4 1/4] opp: Export devm_pm_opp_attach_genpd() Dmitry Osipenko
2021-01-20 22:26 ` [PATCH v4 2/4] opp: Add dev_pm_opp_sync_regulators() Dmitry Osipenko
2021-01-25 22:30 ` Dmitry Osipenko
2021-01-27 4:30 ` Viresh Kumar
2021-01-20 22:26 ` [PATCH v4 3/4] opp: Add dev_pm_opp_set_voltage() Dmitry Osipenko
2021-01-20 22:26 ` [PATCH v4 4/4] opp: Make _set_opp_custom() work without regulators Dmitry Osipenko
2021-01-22 7:26 ` Viresh Kumar
2021-01-22 14:44 ` Dmitry Osipenko
2021-01-22 14:43 ` Dmitry Osipenko
2021-01-22 7:34 ` [PATCH v4 0/4] OPP API fixes and improvements Viresh Kumar
2021-01-27 6:54 ` 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=20210120222649.28149-1-digetx@gmail.com \
--to=digetx@gmail.com \
--cc=broonie@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=khilman@kernel.org \
--cc=kwizart@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mattmerhar@protonmail.com \
--cc=nm@ti.com \
--cc=pdeschrijver@nvidia.com \
--cc=pgwipeout@gmail.com \
--cc=rjw@rjwysocki.net \
--cc=sboyd@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=tiny.windzz@gmail.com \
--cc=ulf.hansson@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.