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,
Ulf Hansson <ulf.hansson@linaro.org>,
Chunyan Zhang <zhang.lyra@gmail.com>
Subject: Re: [PATCH V2 1/5] bindings: regulator: added support for suspend states
Date: Tue, 9 Jan 2018 16:40:52 +0000 [thread overview]
Message-ID: <20180109164052.GD11471@sirena.org.uk> (raw)
In-Reply-To: <CAG2=9p9D1QHErF22A+aA9OwvnBiuxAOV27iYYCzC_5ZpZzF9eQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 258 bytes --]
On Tue, Jan 09, 2018 at 02:08:45PM +0800, Chunyan Zhang wrote:
> Then, do we need a flag as well to give permission to change
> 'suspend_state->enabled'?
Yes, that's a separate thing which people might want to control even if
the voltage can't be changed.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-01-09 16:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 7:22 [PATCH V2 0/5] Add regulator suspend and resume support Chunyan Zhang
2018-01-04 7:22 ` [PATCH V2 1/5] bindings: regulator: added support for suspend states Chunyan Zhang
2018-01-05 18:53 ` Rob Herring
2018-01-05 19:18 ` Mark Brown
2018-01-08 6:36 ` Chunyan Zhang
2018-01-08 12:35 ` Mark Brown
2018-01-09 6:08 ` Chunyan Zhang
2018-01-09 16:40 ` Mark Brown [this message]
2018-01-04 7:22 ` [PATCH V2 2/5] regulator: make regulator voltage be an array to support more states Chunyan Zhang
2018-01-04 7:22 ` [PATCH V2 3/5] drivers: regulator: leave one item to record whether regulator is enabled Chunyan Zhang
2018-01-04 7:22 ` [PATCH V2 4/5] drivers: regulator: empty the old suspend functions Chunyan Zhang
2018-01-04 7:22 ` [PATCH V2 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=20180109164052.GD11471@sirena.org.uk \
--to=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=ulf.hansson@linaro.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
all inboxes | Powered by JetHome®