diff options
author | Vic (Chun-Ju) Yang <victoryang@chromium.org> | 2013-12-09 15:51:26 +0800 |
---|---|---|
committer | chrome-internal-fetch <chrome-internal-fetch@google.com> | 2013-12-10 04:40:39 +0000 |
commit | 6f348ecf083a3182b7eed83cdd9a9bc19751a0ba (patch) | |
tree | cf26cf7ccbfe525abb4074b6743b2c0fcad73b98 /include | |
parent | 1d24f4d661473223fd5eaf60a62ec0f1068d58f2 (diff) | |
download | chrome-ec-6f348ecf083a3182b7eed83cdd9a9bc19751a0ba.tar.gz |
Remove unneeded TODO comment
When we are detecting Apple charger type, we disable TSU6721 interrupt.
This, however, doesn't create a race condition, because any pending
interrupt fires immediately after we re-enable TSU6721 interrupt, and in
turns schedules charger task. As a result, charger task gets waken right
after it finishes its current iteration.
As for overcurrent detection, the current algorithm seems to do a good
enough job.
BUG=chrome-os-partner:23743, chrome-os-partner:23744
TEST=None
BRANCH=None
Change-Id: Ib3a6d562a305020ef5413e2a493e4163a6e70954
Signed-off-by: Vic (Chun-Ju) Yang <victoryang@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/179303
Reviewed-by: Randall Spangler <rspangler@chromium.org>
Reviewed-by: Vincent Palatin <vpalatin@chromium.org>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions