From: Dmitry Osipenko <digetx@gmail.com>
To: Mark Brown <broonie@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Maciej Purski <m.purski@samsung.com>
Cc: Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Peter De Schrijver <pdeschrijver@nvidia.com>,
Lucas Stach <l.stach@pengutronix.de>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-omap@vger.kernel.org
Subject: [PATCH v1 00/11] Continuing the work on coupled regulators
Date: Fri, 5 Oct 2018 18:36:27 +0300 [thread overview]
Message-ID: <20181005153638.1886-1-digetx@gmail.com> (raw)
Hello,
Maciej moved on to work on something else and kindly allowed me to
take over the coupled regulators patches [0] which I'll try to finalize.
I recently started to work on adding DVFS support to the CPUFreq driver
of NVIDIA Tegra20/30 which require the coupled regulators functionality.
Both Tegra20 and Tegra30 have the voltage "max-spread" constraint.
Tegra30 has an additional constraint, the "max-step" voltage.
What is done in this series:
1. Re-worked the original "Add voltage balancing mechanism" patch from
Maciej by:
1) Fixing infinite loop within regulator_balance_voltage().
2) Handling suspend_state_t properly.
3) Fixing broken compilation of the patch.
2. Added pair of patches to clean up regulator-couple resolving.
3. Changed device tree binding of the regulator-coupled-max-spread property
to make it more flexible.
4. Added new device tree property, the regulator-max-step-microvolt.
5. Implemented wait/wound mutex which was suggested by Lucas Stach in the
review comment to [0]. I've tested w/w locking extensively (including
CONFIG_DEBUG_WW_MUTEX_SLOWPATH) and quite confident that everything is
okay.
6. Patches were tested with KASAN on Tegra20 / Tegra30, I tried to cover
various cases and verified that voltage constraints not violated under
different circumstances.
Please review, thanks.
[0] https://lkml.org/lkml/2018/4/23/619
Dmitry Osipenko (9):
regulator: core: Mutually resolve regulators coupling
regulator: core: Don't allow to get regulator until all couples
resolved
dt-bindings: regulator: Change regulator-coupled-max-spread property
regulator: core: Limit regulators coupling to a single couple
dt-bindings: regulator: Document new regulator-max-step-microvolt
property
regulator: core: Add new max_uV_step constraint
regulator: core: Decouple regulators on regulator_unregister()
regulator: core: Use ww_mutex for regulators locking
regulator: core: Properly handle case where supply is the couple
Maciej Purski (2):
regulator: core: Add voltage balancing mechanism
regulator: core: Change voltage setting path
.../bindings/regulator/regulator.txt | 7 +-
drivers/regulator/core.c | 821 +++++++++++++++---
drivers/regulator/of_regulator.c | 4 +
include/linux/regulator/driver.h | 5 +-
include/linux/regulator/machine.h | 3 +
5 files changed, 713 insertions(+), 127 deletions(-)
--
2.19.0
next reply other threads:[~2018-10-05 15:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-05 15:36 Dmitry Osipenko [this message]
2018-10-05 15:36 ` [PATCH v1 01/11] regulator: core: Add voltage balancing mechanism Dmitry Osipenko
2018-10-05 15:36 ` [PATCH v1 02/11] regulator: core: Change voltage setting path Dmitry Osipenko
2018-10-05 15:36 ` [PATCH v1 03/11] regulator: core: Mutually resolve regulators coupling Dmitry Osipenko
2018-10-05 15:36 ` [PATCH v1 04/11] regulator: core: Don't allow to get regulator until all couples resolved Dmitry Osipenko
2018-10-05 15:36 ` [PATCH v1 05/11] dt-bindings: regulator: Change regulator-coupled-max-spread property Dmitry Osipenko
2018-10-17 13:25 ` Rob Herring
2018-10-17 13:32 ` Dmitry Osipenko
2018-10-17 13:33 ` Rob Herring
2018-10-17 13:36 ` Dmitry Osipenko
2018-10-17 13:27 ` Rob Herring
2018-10-17 13:31 ` Rob Herring
2018-10-05 15:36 ` [PATCH v1 06/11] regulator: core: Limit regulators coupling to a single couple Dmitry Osipenko
2018-10-05 15:36 ` [PATCH v1 07/11] dt-bindings: regulator: Document new regulator-max-step-microvolt property Dmitry Osipenko
2018-10-17 13:33 ` Rob Herring
2018-10-05 15:36 ` [PATCH v1 08/11] regulator: core: Add new max_uV_step constraint Dmitry Osipenko
2018-10-05 15:36 ` [PATCH v1 09/11] regulator: core: Decouple regulators on regulator_unregister() Dmitry Osipenko
2018-10-05 15:36 ` [PATCH v1 10/11] regulator: core: Use ww_mutex for regulators locking Dmitry Osipenko
2018-11-08 13:07 ` Mark Brown
2018-11-08 16:53 ` Dmitry Osipenko
2018-10-05 15:36 ` [PATCH v1 11/11] regulator: core: Properly handle case where supply is the couple Dmitry Osipenko
2018-10-08 17:58 ` [PATCH v1 00/11] Continuing the work on coupled regulators Tony Lindgren
2018-10-09 8:52 ` Dmitry Osipenko
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=20181005153638.1886-1-digetx@gmail.com \
--to=digetx@gmail.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=l.stach@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=m.purski@samsung.com \
--cc=pdeschrijver@nvidia.com \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
/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.