summaryrefslogtreecommitdiff
path: root/drivers/mfd/asic3.c
diff options
context:
space:
mode:
authorDoug Anderson <dianders@chromium.org>2014-06-13 22:13:32 +0400
committerLee Jones <lee.jones@linaro.org>2014-07-09 17:58:00 +0400
commit967580598f46997ce5eeeea812686f5220bb49de (patch)
treedd21d96eacae8420d255b1360cead990b47a5e95 /drivers/mfd/asic3.c
parentc03842d89b769db44be5cb0b1ebb384ccfa25f7f (diff)
downloadlinux-967580598f46997ce5eeeea812686f5220bb49de.tar.xz
mfd: cros_ec: spi: Fix end of transfer on devices with no spi-msg-delay
cros_ec_spi makes the assumption that a 0-length message will put the spi chip select back to normal (non cs_toggle mode). This used to be the case back on kernel-3.8 on the spi-s3c64xx driver but doesn't appear to be true anymore. It seems like it was a pretty questionable assumption to begin with, so let's fix the code to be more robust. We know that a message with a single 0-length segment _will_ put things back in order. Change cros_ec_spi to handle this. This wasn't a problem on the main user of cros_ec_spi upstream (tegra) because it specified 'google,cros-ec-spi-msg-delay'. Signed-off-by: Doug Anderson <dianders@chromium.org> Signed-off-by: Lee Jones <lee.jones@linaro.org>
Diffstat (limited to 'drivers/mfd/asic3.c')
0 files changed, 0 insertions, 0 deletions