summaryrefslogtreecommitdiff
path: root/board/hoho
diff options
context:
space:
mode:
authorNicolas Boichat <drinkcat@chromium.org>2016-05-23 15:23:38 +0800
committerchrome-bot <chrome-bot@chromium.org>2016-06-02 14:06:52 -0700
commit4f600b32bbcdd1f870f8389b8666101d3a8513ed (patch)
treed60ca034718fd19e0a13411825b1eaef25901072 /board/hoho
parentf6a53e9917b474e95afb42e2522fb88c61998c9a (diff)
downloadchrome-ec-4f600b32bbcdd1f870f8389b8666101d3a8513ed.tar.gz
stm32: i2c: Busy loop for a while waiting for interrupt
I2C is not necessarily _that_ slow, especially when using 1Mhz clock speed, and, looking at traces from userspace, there are large gaps (150us) between bytes (while the bytes themselves only take ~10us). At 400kHz and higher bus speed, busy-loop for the duration of 2 bytes, before sleeping (and yielding to other tasks) for 100us between each attempt. BRANCH=None BUG=chrome-os-partner:50381 TEST=i2cget, look at Logic 16 traces: no gaps between address and bytes Change-Id: If47f0f8e55be37002361800d35f71c945863d42d Signed-off-by: Nicolas Boichat <drinkcat@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/346670 Reviewed-by: Vincent Palatin <vpalatin@chromium.org>
Diffstat (limited to 'board/hoho')
0 files changed, 0 insertions, 0 deletions