[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-id: <1407976814-21882-1-git-send-email-cw00.choi@samsung.com>
Date: Thu, 14 Aug 2014 09:40:12 +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 0/2] regulator: of: Add support for pasing regulator suspend
state
The regulators would set different state/mode according to the kind of suspend
state. So regulation_constraints structure has already regulator suspend state filed.
This patch parse regulator suspend state from devicetree file.
For example:
ldoX_reg: LDOx {
regulator-name = "VAP_XXX_1.2V";
regulator-min-microvolt = <1200000>;
regulator-max-microvolt = <1200000>;
regulator-always-on;
regulator-initial-state = <3>; /* PM_SUSPEND_MEM */
regulator-state-standby {
regulator-volt = <1200000>;
};
regulator-state-mem {
regulator-volt = <1200000>;
regulator-off-in-suspend;
};
regulator-state-disk {
regulator-volt = <1200000>;
regulator-on-in-suspend;
};
};
Changes from v2:
- Fix over 80 lines by using checkpatch script
- Rebase this patchset on latest for-next branch of regulator.git
Changes from v1:
- Check whether regulator-initial-state and regulator-mode is correct or not
- Add more detailed description about regulator-initial-state, regulator-mode
and regulator-state-[standby/mem/disk] for devicetree bindings
- Modify example of regulator suspend state in bindings documentation
Chanwoo Choi (2):
regulator: of: Add support for parsing regulator_state for suspend state
dt-bindings: regulator: Add regulator suspend state for PM state
.../devicetree/bindings/regulator/regulator.txt | 32 +++++++++
drivers/regulator/of_regulator.c | 79 +++++++++++++++++++++-
2 files changed, 109 insertions(+), 2 deletions(-)
--
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