From: Mark Brown <broonie@kernel.org>
To: Chunyan Zhang <zhang.chunyan@linaro.org>
Cc: Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Chunyan Zhang <zhang.lyra@gmail.com>
Subject: Re: [PATCH 1/5] bindings: regulator: added support for suspend states
Date: Fri, 22 Dec 2017 15:49:04 +0000 [thread overview]
Message-ID: <20171222154904.GK1827@finisterre> (raw)
In-Reply-To: <CAG2=9p9ahGgnz1Gos-o-o5PB9UH--2t3Lv54PaK5_f2jpNQnDQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1442 bytes --]
On Fri, Dec 22, 2017 at 02:05:21PM +0800, Chunyan Zhang wrote:
> On 22 December 2017 at 07:26, Rob Herring <robh@kernel.org> wrote:
> > On Thu, Dec 21, 2017 at 02:25:02PM +0800, Chunyan Zhang wrote:
> >> + - regulator-suspend-microvolt: the default voltage which regulator
> >> + should be set in suspend, this can be adjusted among
> >> + <regulator-suspend-min-microvolt, regulator-suspend-max-microvolt>
> > Perhaps this should stay a single property with: <target> <min> <max>
> Do you mean that change the property name from "regulator-suspend-microvolt" to
> "regulator-suspend-target-microvolt"?
> "regulator-suspend-microvolt" is the one that some SoC is using. My
> intention was just to keep that configuration still working.
Yeah, the regulator-suspend-microvolt is an existing property. Thinking
about it we should probably say that it's equivalent to setting both
-min and -max to the same value and possibly mark it as deprecated too.
It is documented in regulator.txt already.
> > Though why would you ever not try to set to the minimum voltage within
> > the range of <min> to <max>?
> IIUC, you mean just removing "regulator-suspend-microvolt", and use
> "regulator-suspend-min-microvolt" as the default value for suspend
> voltage?
> I think that can work, but would it be better to not remove that right
> now, since some one is using that?
Indeed. I think my suggestion above would cover things.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-12-22 15:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-21 6:25 [PATCH 0/5] Add regulator suspend and resume support Chunyan Zhang
2017-12-21 6:25 ` [PATCH 3/5] drivers: regulator: leave one item to record whether regulator is enabled Chunyan Zhang
[not found] ` <1513837506-26543-1-git-send-email-zhang.chunyan-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2017-12-21 6:25 ` [PATCH 1/5] bindings: regulator: added support for suspend states Chunyan Zhang
[not found] ` <1513837506-26543-2-git-send-email-zhang.chunyan-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2017-12-21 23:26 ` Rob Herring
2017-12-22 6:05 ` Chunyan Zhang
2017-12-22 15:49 ` Mark Brown [this message]
2017-12-21 6:25 ` [PATCH 2/5] regulator: make regulator voltage be an array to support more states Chunyan Zhang
2017-12-21 6:25 ` [PATCH 4/5] drivers: regulator: empty the old suspend functions Chunyan Zhang
[not found] ` <1513837506-26543-5-git-send-email-zhang.chunyan-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2018-01-25 12:15 ` Applied "regulator: empty the old suspend functions" to the regulator tree Mark Brown
2018-01-26 15:26 ` Mark Brown
2017-12-21 6:25 ` [PATCH 5/5] regulator: add PM suspend and resume hooks Chunyan Zhang
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=20171222154904.GK1827@finisterre \
--to=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=zhang.chunyan@linaro.org \
--cc=zhang.lyra@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).