summaryrefslogtreecommitdiffstats
path: root/arch/microblaze
diff options
context:
space:
mode:
authorDoug Anderson <dianders@chromium.org>2017-03-01 12:58:32 +0100
committerLee Jones <lee.jones@linaro.org>2017-04-27 10:25:04 +0200
commitca691f7118087a652e4d6c83a30f5ed6d5acbf14 (patch)
tree59599bc8510486259975f08336f0737eecae5e83 /arch/microblaze
parentmfd: Add TI LMU driver (diff)
downloadlinux-ca691f7118087a652e4d6c83a30f5ed6d5acbf14.tar.xz
linux-ca691f7118087a652e4d6c83a30f5ed6d5acbf14.zip
mfd: cros ec: spi: Increase wait time to 200ms
This is a sucky change to bump up the time we'll wait for the EC. Why is it sucky? If 200ms for a transfer is a common thing it will have a massively bad impact on keyboard responsiveness. It still seems like a good idea to do this, though, because we have a gas gauge that claims that in an extreme case it could stretch the i2c clock for 144ms. It's not a common case so it shouldn't affect responsiveness, but it can happen. It's much better to have a single slow keyboard response than to start returning errors when we don't have to. In newer EC designs we should probably implement a virtual battery to respond to the kernel to insulate the kernel from these types of issues. Signed-off-by: Doug Anderson <dianders@chromium.org> Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com> Signed-off-by: Lee Jones <lee.jones@linaro.org>
Diffstat (limited to 'arch/microblaze')
0 files changed, 0 insertions, 0 deletions