From: Dmitry Osipenko <digetx@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Peter De Schrijver <pdeschrijver@nvidia.com>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/5] regulator: core: Expose some of core functions needed by couplers
Date: Tue, 25 Jun 2019 17:40:01 +0300 [thread overview]
Message-ID: <a0626c9d-c68b-9043-8b2f-870f594938b8@gmail.com> (raw)
In-Reply-To: <20190625111946.GP5316@sirena.org.uk>
25.06.2019 14:19, Mark Brown пишет:
> On Mon, Jun 24, 2019 at 12:08:32AM +0300, Dmitry Osipenko wrote:
>> Expose some of internal functions that are required for implementation of
>> customized regulator couplers.
>
> The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:
>
> Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)
>
> are available in the Git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git tags/regulator-couple-api
>
> for you to fetch changes up to d22b85a1b97d12a4940ef9d778f6122546736f78:
>
> regulator: core: Expose some of core functions needed by couplers (2019-06-25 12:15:35 +0100)
>
> ----------------------------------------------------------------
> regulator: Coupling API
>
> This series introduces a way of specifying a customized regulators coupler
> which is necessary for cases like a non-trivial DVFS implementation.
>
> ----------------------------------------------------------------
> Dmitry Osipenko (2):
> regulator: core: Introduce API for regulators coupling customization
> regulator: core: Expose some of core functions needed by couplers
>
> drivers/regulator/core.c | 194 ++++++++++++++++++++++++++++----------
> drivers/regulator/of_regulator.c | 63 +++++++++----
> include/linux/regulator/coupler.h | 97 +++++++++++++++++++
> include/linux/regulator/driver.h | 6 +-
> include/linux/regulator/machine.h | 2 +-
> 5 files changed, 287 insertions(+), 75 deletions(-)
> create mode 100644 include/linux/regulator/coupler.h
>
Thank you very much! Very nice to see some more progress!
next prev parent reply other threads:[~2019-06-25 14:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-23 21:08 [PATCH v3 0/5] Introduce customized regulators coupling Dmitry Osipenko
2019-06-23 21:08 ` [PATCH v3 1/5] regulator: core: Introduce API for regulators coupling customization Dmitry Osipenko
2019-06-23 21:08 ` [PATCH v3 2/5] regulator: core: Expose some of core functions needed by couplers Dmitry Osipenko
2019-06-25 11:19 ` Mark Brown
2019-06-25 14:40 ` Dmitry Osipenko [this message]
2019-06-23 21:08 ` [PATCH v3 3/5] dt-bindings: regulator: Document regulators coupling of NVIDIA Tegra20/30 SoCs Dmitry Osipenko
2019-06-23 21:08 ` [PATCH v3 4/5] soc/tegra: regulators: Add regulators coupler for Tegra20 Dmitry Osipenko
2019-06-23 21:08 ` [PATCH v3 5/5] soc/tegra: regulators: Add regulators coupler for Tegra30 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=a0626c9d-c68b-9043-8b2f-870f594938b8@gmail.com \
--to=digetx@gmail.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--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 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).