From: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Chanwoo Choi <cw00.choi-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
Cc: lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
kyungmin.park-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org,
k.kozlowski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCHv3 2/2] dt-bindings: regulator: Add regulator suspend state for PM state
Date: Fri, 15 Aug 2014 11:56:15 +0100 [thread overview]
Message-ID: <20140815105615.GI17528@sirena.org.uk> (raw)
In-Reply-To: <1407976814-21882-3-git-send-email-cw00.choi-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 2119 bytes --]
On Thu, Aug 14, 2014 at 09:40:14AM +0900, Chanwoo Choi wrote:
> +- regulator-initial-state: initial state for suspend state, cnd set initial
> + state among following defined suspend states:
> + <2>: PM_SUSPEND_STANDBY - Setup regulator according to regulator-state-standby
> + <3>: PM_SUSPEND_MEM - Setup regulator according to regulator-state-mem
> + <4>: PM_SUSPEND_MAX - Setup regulator according to regulator-state-disk
> +- regulator-state-standby sub-root node for Standby mode
> + : the device is in a power-saving state, but can also receive certain events,
> + specific behavior depends on the specific device.
These are all Linux internal descriptions of the states but the device
tree is supposed to be OS neutral. For suspend to memory and suspend to
disk that's probably adequately clear but _STANDBY is really unclear.
I would suggest just dropping this without a clearer defintion, it's
something that I'd expect to emerge organically from low power modes
rather than having a specific definition anyway.
> +- regulator-state-[standby/mem/disk] node has following common properties:
> + - regulator-volt: voltage consumers may set in suspend state.
> + - regulator-mode: voltage mode in suspend state, can set mode among
> + following defined regulator modes:
> + 0x1: REGULATOR_MODE_FAST, Regulator can handle fast changes.
> + 0x2: REGULATOR_MODE_NORMAL, Normal regulator power supply mode.
> + 0x4: REGULATOR_MODE_IDLE, Regulator runs in a more efficient mode.
> + 0x8: REGULATOR_MODE_STANDBY, Regulator runs in the most efficient mode.
> + - regulator-on-in-suspend: regulator should be on in suspend state.
> + - regulator-off-in-suspend: regulator should be off in suspend state.
> + If node don't include regulator-[on/off]-in-suspend, can't change
> + regulator state in suspend mode and only should sustain the regulator
> + state of normal state.
Modes are a similarly problematic thing - their definition is really
unclear even within Linux and we don't support them at all at present.
I'd just drop them initially and then add them in as a part of adding
mode support in general.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-08-15 10:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-14 0:40 [PATCHv3 0/2] regulator: of: Add support for pasing regulator suspend state Chanwoo Choi
2014-08-14 0:40 ` [PATCHv3 1/2] regulator: of: Add support for parsing regulator_state for " Chanwoo Choi
[not found] ` <1407976814-21882-1-git-send-email-cw00.choi-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2014-08-14 0:40 ` [PATCHv3 2/2] dt-bindings: regulator: Add regulator suspend state for PM state Chanwoo Choi
[not found] ` <1407976814-21882-3-git-send-email-cw00.choi-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2014-08-15 10:56 ` Mark Brown [this message]
[not found] ` <20140815105615.GI17528-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-08-15 12:15 ` Chanwoo Choi
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=20140815105615.GI17528@sirena.org.uk \
--to=broonie-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=cw00.choi-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=k.kozlowski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
--cc=kyungmin.park-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
--cc=lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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