summaryrefslogtreecommitdiffstats
path: root/drivers/regulator/gpio-regulator.c
diff options
context:
space:
mode:
authorJavier Martinez Canillas <javier.martinez@collabora.co.uk>2014-11-10 14:43:51 +0100
committerMark Brown <broonie@kernel.org>2014-11-26 18:58:14 +0000
commit218094c975e03b3b202663901a3bbf91041fdd20 (patch)
treec3bfc8cbf3f182f6f19bd0c15ebfba98a3e761da /drivers/regulator/gpio-regulator.c
parent8cbcaea89cfc4603c954f50aaddc3172446961d1 (diff)
downloadlinux-stable-218094c975e03b3b202663901a3bbf91041fdd20.tar.gz
linux-stable-218094c975e03b3b202663901a3bbf91041fdd20.tar.bz2
linux-stable-218094c975e03b3b202663901a3bbf91041fdd20.zip
regulator: Document binding for initial and suspend modes
Some regulators can run on different operating modes (opmodes). This allows systems to choose the most efficient opmode for each regulator. This patch builds on top of (291d761 regulator: Document binding for regulator suspend state for PM state) adding a regulator-initial-mode DT property to configure at startup the operating mode for regulators that support changing its mode during normal operation and a property regulator-mode to be used in the regulator-state-[mem/disk] nodes for regulators that supports changing its operating mode when the system enters in a suspend state. The set of possible modes that a regulator can operate depends on the hardware capabilities so a list of generic operating modes can't be provided. Instead, each hardware binding should define the list of valid operating modes for the regulators found on that device. Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk> Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'drivers/regulator/gpio-regulator.c')
0 files changed, 0 insertions, 0 deletions