summaryrefslogtreecommitdiffstats
path: root/fs
diff options
context:
space:
mode:
authorGabor Juhos <juhosg@openwrt.org>2014-03-02 20:54:42 +0100
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2014-03-23 21:38:16 -0700
commitcb67b44a0ddb8c1387ad2df82508b17b9b3f546d (patch)
treea96d78756bab1273b6acc64652244f7b673c85f3 /fs
parent2e44c866bfcea9dcd77dda2c77f03f6d042aade7 (diff)
downloadlinux-stable-cb67b44a0ddb8c1387ad2df82508b17b9b3f546d.tar.gz
linux-stable-cb67b44a0ddb8c1387ad2df82508b17b9b3f546d.tar.bz2
linux-stable-cb67b44a0ddb8c1387ad2df82508b17b9b3f546d.zip
spi: spi-ath79: fix initial GPIO CS line setup
commit 61d1cf163c8653934cc8cd5d0b2a562d0990c265 upstream. The 'ath79_spi_setup_cs' function initializes the chip select line of a given SPI device in order to make sure that the device is inactive. If the SPI_CS_HIGH bit is set for a given device, it means that the CS line of that device is active HIGH so it must be set to LOW initially. In case of GPIO CS lines, the 'ath79_spi_setup_cs' function does the opposite of that due to the wrong GPIO flags. Fix the code to use the correct GPIO flags. Reported-by: Ronald Wahl <ronald.wahl@raritan.com> Signed-off-by: Gabor Juhos <juhosg@openwrt.org> Signed-off-by: Mark Brown <broonie@linaro.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'fs')
0 files changed, 0 insertions, 0 deletions