From: Mark Brown <broonie@kernel.org>
To: Doug Anderson <dianders@chromium.org>
Cc: David Collins <collinsd@codeaurora.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-msm@vger.kernel.org,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
devicetree@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Rajendra Nayak <rnayak@codeaurora.org>,
Stephen Boyd <sboyd@kernel.org>
Subject: Re: [PATCH v3 1/2] regulator: dt-bindings: add QCOM RPMh regulator bindings
Date: Wed, 30 May 2018 16:48:49 +0100 [thread overview]
Message-ID: <20180530154849.GQ6920@sirena.org.uk> (raw)
In-Reply-To: <CAD=FV=XJd-udEE6az0xP7i6x0oGsnd=BSCyZ0Og_+RjNCMXnCQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1037 bytes --]
On Wed, May 30, 2018 at 08:34:50AM -0700, Doug Anderson wrote:
> On Wed, May 30, 2018 at 8:02 AM, Mark Brown <broonie@kernel.org> wrote:
> > What you're describing sounds like what we should be doing normally, if
> > we're not doing that we should probably be fixing the core.
> I'm not convinced that this behavior makes sense to move to the core.
> On most regulators I'd expect that when the regulator driver says to
> turn them off that they will output no voltage. The reason RPMh is
Oh, you mean while the regulator is off... TBH I don't see a huge
problem doing that anyway and just reverting to the bottom of the
constraints when everything gets turned off since we have to see if we
need to adjust the voltage every time we enabled anyway.
> In any other system when Linux disabled the regulator it wouldn't
> matter that you left it set at 1.4V. Thus RPMh is special and IMO the
> workaround belongs there.
Without the core doing something the regulator isn't going to get told
that anything updated voltages anyway...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-05-30 15:48 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-12 2:28 [PATCH v3 0/2] regulator: add QCOM RPMh regulator driver David Collins
2018-05-12 2:28 ` [PATCH v3 1/2] regulator: dt-bindings: add QCOM RPMh regulator bindings David Collins
2018-05-17 21:22 ` Doug Anderson
2018-05-18 0:16 ` David Collins
2018-05-18 1:01 ` Doug Anderson
2018-05-19 0:46 ` David Collins
2018-05-21 18:01 ` Doug Anderson
2018-05-22 0:00 ` David Collins
2018-05-22 16:43 ` Doug Anderson
2018-05-22 16:55 ` Mark Brown
2018-05-22 22:46 ` David Collins
2018-05-23 0:08 ` Doug Anderson
2018-05-23 1:19 ` David Collins
2018-05-23 5:10 ` Doug Anderson
2018-05-23 8:29 ` Mark Brown
2018-05-23 15:23 ` Doug Anderson
2018-05-23 15:40 ` Mark Brown
2018-05-23 15:50 ` Doug Anderson
2018-05-23 15:56 ` Mark Brown
2018-05-30 5:30 ` Doug Anderson
2018-05-30 9:37 ` Mark Brown
2018-05-30 14:46 ` Doug Anderson
2018-05-30 15:02 ` Mark Brown
2018-05-30 15:34 ` Doug Anderson
2018-05-30 15:48 ` Mark Brown [this message]
2018-05-30 16:06 ` Doug Anderson
2018-05-30 16:07 ` Mark Brown
2018-05-30 16:09 ` Doug Anderson
2018-05-30 16:13 ` Mark Brown
2018-05-30 16:31 ` Doug Anderson
2018-05-30 16:36 ` Mark Brown
2018-05-30 16:41 ` Doug Anderson
2018-05-30 16:59 ` Mark Brown
2018-05-18 22:24 ` Rob Herring
2018-05-12 2:28 ` [PATCH v3 2/2] regulator: add QCOM RPMh regulator driver David Collins
2018-05-17 21:23 ` Doug Anderson
2018-05-18 0:16 ` David Collins
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=20180530154849.GQ6920@sirena.org.uk \
--to=broonie@kernel.org \
--cc=collinsd@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=rnayak@codeaurora.org \
--cc=robh+dt@kernel.org \
--cc=sboyd@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).