summaryrefslogtreecommitdiff
path: root/chip/stm32/uart.c
diff options
context:
space:
mode:
authorDoug Anderson <dianders@chromium.org>2012-08-08 09:33:33 -0700
committerGerrit <chrome-bot@google.com>2012-08-08 15:35:29 -0700
commit3a6a369d39512d8cc394936ec2ccea81c651816b (patch)
tree9114f26ce40f8aef14f6a24102553b325f4a38fc /chip/stm32/uart.c
parenta7d7297577d5450610ddc1a76544fe3300873042 (diff)
downloadchrome-ec-3a6a369d39512d8cc394936ec2ccea81c651816b.tar.gz
i2c: stm32: Increase tx timeout in slave mode from 10ms to 100ms
We have seen instances where the AP has interrupts disabled for a long period of time (specifically when doing a lot of printk messages to the console). When this happens the host can't service i2c in < 10ms (it needs an interrupt per byte) and we were getting a timeout. We'll increase the timeout to 100ms to avoid these problems. Better to be safe than sorry. This timeout runs from the host command task so having the delay shouldn't be a terrible thing (we're not running from an IRQ handler or anything). Only affected the timeout for slave mode specifically so as not to affect any untested behavior. BUG=chrome-os-partner:12123 TEST=With serial console enabled, run this in two different ssh sessions: a) while true; do flashrom -p internal:bus=i2c -r /tmp/ec.bin; done b) while true; do /usr/local/lib/flimflam/test/connect-wifi GoogleGuest; done ...if flashrom reports success over and over again then this is good. Change-Id: I7f32d5f1e4134896c857ee26f449a1fdd579d589 Signed-off-by: Doug Anderson <dianders@chromium.org> Reviewed-on: https://gerrit.chromium.org/gerrit/29621
Diffstat (limited to 'chip/stm32/uart.c')
0 files changed, 0 insertions, 0 deletions