summaryrefslogtreecommitdiffstats
path: root/drivers/lightnvm
diff options
context:
space:
mode:
authorTero Kristo <t-kristo@ti.com>2016-06-24 13:58:08 +0530
committerMark Brown <broonie@kernel.org>2016-06-27 17:56:43 +0100
commitb9a0d359413d7f4e078d81cd59f9d851a6febb7a (patch)
treee18abc30b2338f1d22e4d8a27129dc407ba47e61 /drivers/lightnvm
parent3de56099591a4042556a2d05d4703387ad950c6f (diff)
downloadlinux-b9a0d359413d7f4e078d81cd59f9d851a6febb7a.tar.bz2
regulator: tps65218: Enable suspend configuration
TPS65218 has a pre-defined power-up / power-down sequence which in a typical application does not need to be changed. However, it is possible to define custom sequences under I2C control. The power-up sequence is defined by strobes and delay times. Each output rail is assigned to a strobe to determine the order in which the rails are enabled. Every regulator has sequence registers and every regulator has a default strobe value and gets disabled when a particular power down sequence occurs. To keep a regulator on during suspend we write value 0 to strobe so that the regulator is out of all sequencers and is not impacted by any power down sequence. Hence saving the default strobe value during probe so that when we want to regulator to be enabled during suspend we write 0 to strobe and when we want it to get disabled during suspend we write the default saved strobe value. This allows platform data to specify which power rails should be on or off during RTC only suspend. This is necessary to keep DDR state while in RTC only suspend. Signed-off-by: Tero Kristo <t-kristo@ti.com> Signed-off-by: Keerthy <j-keerthy@ti.com> Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'drivers/lightnvm')
0 files changed, 0 insertions, 0 deletions