diff options
| author | Randall Spangler <rspangler@chromium.org> | 2012-11-20 18:31:54 -0800 |
|---|---|---|
| committer | Gerrit <chrome-bot@google.com> | 2012-11-26 14:49:49 -0800 |
| commit | e2f84669979f63df4a11d78caee9abf3e9b1724a (patch) | |
| tree | 421b42c02cd9b30eb69db6feb9070dfae21e6e29 /core/cortex-m | |
| parent | 3c575ccb02ff58eaae3e7c3dd8e2e86ad25ac106 (diff) | |
| download | chrome-ec-e2f84669979f63df4a11d78caee9abf3e9b1724a.tar.gz | |
Handle bus errors on thermal I2C bus
1) Properly report I2C errors on TMP006 as error, not device-not-powered.
2) Treat clock timeout and bus-busy I2C status as error (previously ignored).
3) If clock timeout or bus-busy, reset I2C master for that bus to clear the
error.
These should help with systems where the thermal I2C bus gets into a
weird state on suspend/resume.
BUG=chrome-os-partner:16262
BRANCH=link
TEST=boot system; 'battery' and 'temps' should give good info
Then run snanda's suspend_stress_test for a while and repeat.
Change-Id: I534be8236a4d6de82575fe6d33a68502ce0a3a95
Original-Change-Id: Iec5d6bbd357d2e5eb3dc3d361c829f353e996ab6
Signed-off-by: Randall Spangler <rspangler@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/38444
Reviewed-on: https://gerrit.chromium.org/gerrit/38659
Reviewed-by: Yung-Chieh Lo <yjlou@chromium.org>
Diffstat (limited to 'core/cortex-m')
0 files changed, 0 insertions, 0 deletions