From: Doug Anderson Date: Fri, 13 Jun 2014 18:13:32 +0000 (-0700) Subject: mfd: cros_ec: spi: Fix end of transfer on devices with no spi-msg-delay X-Git-Tag: omap-for-v3.17/fixes-against-rc2~129^2~92 X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=967580598f46997ce5eeeea812686f5220bb49de;p=pandora-kernel.git 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 Signed-off-by: Lee Jones --- Reading git-diff-tree failed