Some systems need to set regulators to specific states when they enter low power modes, especially around CPUs. Currently the regulator driver, for suspend and resume features, provides two functions which are exported for being called directly by any modules or subsystems when they thought the regulator should be entering into suspend states. This patchset adds hooks to PM suspend core and provides suspend/resume callback functions to regulator device, for those who can be switched off or set low voltage in suspend states only need to implement the callback functions in the driver, and set the right configurations for suspend states via device tree and the APIs which regulator core driver provides. Those drivers who use the old interfaces - i.e. regulator_suspend_prepare() and regulator_suspend_finish() should stop using that, since we leave these two functions empty and plan to remove them one day in the future. Any comments would be greatly appreciated. Thanks, Chunyan Changes from V1: (https://lkml.org/lkml/2017/12/21/9) * Rephrased the commit message of patch 0001; * Declared the property 'regulator-suspend-microvolt' deperated and documented the way recommended; * Revised of_regulator.c, use suspend_state::min_uV as default suspend voltage if the property 'regulator-suspend-microvolt' is not used. Chunyan Zhang (5): bindings: regulator: added support for suspend states regulator: make regulator voltage be an array to support more states drivers: regulator: leave one item to record whether regulator is enabled drivers: regulator: empty the old suspend functions regulator: add PM suspend and resume hooks .../devicetree/bindings/regulator/regulator.txt | 15 +- drivers/regulator/core.c | 342 ++++++++++++++------- drivers/regulator/internal.h | 18 +- drivers/regulator/of_regulator.c | 20 +- include/linux/regulator/driver.h | 2 + include/linux/regulator/machine.h | 31 +- 6 files changed, 305 insertions(+), 123 deletions(-) -- 2.7.4 -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
