aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation
diff options
context:
space:
mode:
authorDoug Anderson <dianders@chromium.org>2016-08-29 14:22:36 -0700
committerWolfram Sang <wsa@the-dreams.de>2016-09-08 22:50:33 +0200
commitcbfff439c54f37fc363b1d365183fa61af43585c (patch)
treebce37b2dd8c72755fd23bcd7a14c4106c9dbf8ff /Documentation
parenti2c: Spelling s/acknowedge/acknowledge/ (diff)
downloadlinux-dev-cbfff439c54f37fc363b1d365183fa61af43585c.tar.xz
linux-dev-cbfff439c54f37fc363b1d365183fa61af43585c.zip
i2c: rk3x: Restore clock settings at resume time
Depending on a number of factors including: - Which exact Rockchip SoC we're working with - How deep we suspend - Which i2c port we're on We might lose the state of the i2c registers at suspend time. Specifically we've found that on rk3399 the i2c ports that are not in the PMU power domain lose their state with the current suspend depth configured by ARM Tursted Firmware. Note that there are very few actual i2c registers that aren't configured per transfer anyway so all we actually need to re-configure are the clock config registers. We'll just add a call to rk3x_i2c_adapt_div() at resume time and be done with it. NOTE: On rk3399 on ports whose power was lost, I put printouts in at resume time. I saw things like: before: con=0x00010300, div=0x00060006 after: con=0x00010200, div=0x00180025 Signed-off-by: Douglas Anderson <dianders@chromium.org> Reviewed-by: David Wu <david.wu@rock-chips.com> Tested-by: David Wu <david.wu@rock-chips.com> [wsa: removed duplicate const] Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
Diffstat (limited to 'Documentation')
0 files changed, 0 insertions, 0 deletions