lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-id: <1407976814-21882-3-git-send-email-cw00.choi@samsung.com> Date: Thu, 14 Aug 2014 09:40:14 +0900 From: Chanwoo Choi <cw00.choi@...sung.com> To: broonie@...nel.org Cc: lgirdwood@...il.com, grant.likely@...aro.org, robh+dt@...nel.org, kyungmin.park@...sung.com, k.kozlowski@...sung.com, linux-kernel@...r.kernel.org, devicetree@...r.kernel.org, Chanwoo Choi <cw00.choi@...sung.com> Subject: [PATCHv3 2/2] dt-bindings: regulator: Add regulator suspend state for PM state This patch add regulator suspend state to constraint in dt file. The regulation_ constraints structure already has regulator suspend state field as following. The regulator suspend state control the state of regulator according to PM (Power Management) state. - struct regulator_state state_disk - struct regulator_state state_mem - struct regulator_state state_standby Signed-off-by: Chanwoo Choi <cw00.choi@...sung.com> Acked-by: Kyungmin Park <kyungmin.park@...sung.com> --- .../devicetree/bindings/regulator/regulator.txt | 32 ++++++++++++++++++++++ 1 file changed, 32 insertions(+) diff --git a/Documentation/devicetree/bindings/regulator/regulator.txt b/Documentation/devicetree/bindings/regulator/regulator.txt index 8607433..c4f566a 100644 --- a/Documentation/devicetree/bindings/regulator/regulator.txt +++ b/Documentation/devicetree/bindings/regulator/regulator.txt @@ -19,6 +19,33 @@ Optional properties: design requires. This property describes the total system ramp time required due to the combination of internal ramping of the regulator itself, and board design issues such as trace capacitance and load on the supply. +- 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. +- regulator-state-mem sub-root node for Suspend-to-RAM mode + : suspend to memory, the device goes to sleep, but all data stored in memory, + only some external interrupt can wake the device. +- regulator-state-disk sub-root node for Suspend-to-disk mode + : suspend to disk, this state operates similarly to Suspend-to-RAM, + but includes a final step of writing memory contents to disk. +- 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. Deprecated properties: - regulator-compatible: If a regulator chip contains multiple @@ -34,6 +61,11 @@ Example: regulator-max-microvolt = <2500000>; regulator-always-on; vin-supply = <&vin>; + + regulator-state-mem { + regulator-volt = <1000000>; + regulator-off-in-suspend; + }; }; Regulator Consumers: -- 1.8.0 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists