summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorKevin Cernekee <cernekee@chromium.org>2015-05-05 15:14:14 -0700
committerNitin Garg <nitin.garg@nxp.com>2016-01-14 11:00:04 -0600
commit3986758c3c12d3eb044a5fe4514bc7a23040bddd (patch)
tree81d37d20552807476c6fb4122e654172eab54213 /Documentation
parentd177846b66164e380780704705dac4137d5d68ad (diff)
regmap: Use regcache_mark_dirty() to indicate power loss or reset
Existing regmap users call regcache_mark_dirty() as part of the suspend/resume sequence, to tell regcache that non-default values need to be resynced post-resume. Add an internal "no_sync_defaults" regmap flag to remember this state, so that regcache_sync() can differentiate between these two cases: 1) HW was reset, so any cache values that match map->reg_defaults can be safely skipped. On some chips there are a lot of registers in the reg_defaults list, so this optimization speeds things up quite a bit. 2) HW was not reset (maybe it was just clock-gated), so if we cached any writes, they should be sent to the hardware regardless of whether they match the HW default. Currently this will write out all values in the regcache, since we don't maintain per-register dirty bits. Suggested-by: Mark Brown <broonie@kernel.org> Signed-off-by: Kevin Cernekee <cernekee@chromium.org> Signed-off-by: Mark Brown <broonie@kernel.org> (cherry picked from commit 1c79771a7270278e6ff486edf4dfeb8c4fc01ee0)
Diffstat (limited to 'Documentation')
0 files changed, 0 insertions, 0 deletions