From: Viresh Kumar <viresh.kumar@linaro.org>
To: k.konieczny@samsung.com, peron.clem@gmail.com,
m.szyprowski@samsung.com, Nishanth Menon <nm@ti.com>,
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>,
Rafael Wysocki <rjw@rjwysocki.net>,
broonie@kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] opp: core: add regulators enable and disable
Date: Fri, 15 May 2020 13:27:19 +0530 [thread overview]
Message-ID: <cover.1589528491.git.viresh.kumar@linaro.org> (raw)
Hi,
This series reintroduces the usage of regulator_enable/disable() to the
OPP core after the previous attempt was reverted [1] shortly after getting
applied. This time the regulator is enabled only after it is configured
by the OPP core.
Marek, Kamil and Clément: Can you guys please test this out and report
if this doesn't work as expected ?
--
viresh
[1] https://lore.kernel.org/lkml/20191017102758.8104-1-m.szyprowski@samsung.com/
Kamil Konieczny (1):
opp: core: add regulators enable and disable
Viresh Kumar (1):
opp: Reorder the code for !target_freq case
drivers/opp/core.c | 39 ++++++++++++++++++++++++++++++++++-----
drivers/opp/opp.h | 2 ++
2 files changed, 36 insertions(+), 5 deletions(-)
--
2.25.0.rc1.19.g042ed3e048af
next reply other threads:[~2020-05-15 7:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200515075745eucas1p2f14c7fcec7c3d190704ddc6f608b6ce9@eucas1p2.samsung.com>
2020-05-15 7:57 ` Viresh Kumar [this message]
2020-05-15 7:57 ` [PATCH 1/2] opp: Reorder the code for !target_freq case Viresh Kumar
2020-05-15 7:57 ` [PATCH 2/2] opp: core: add regulators enable and disable Viresh Kumar
2020-05-15 9:16 ` [PATCH 0/2] " Marek Szyprowski
2020-05-15 12:00 ` Clément Péron
2020-05-21 12:23 ` Clément Péron
2022-09-03 20:35 ` Clément Péron
2022-09-05 4:35 ` Viresh Kumar
2022-09-05 8:28 ` Clément Péron
2022-09-05 10:24 ` 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.1589528491.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=broonie@kernel.org \
--cc=k.konieczny@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=nm@ti.com \
--cc=peron.clem@gmail.com \
--cc=rjw@rjwysocki.net \
--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 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).