From: Mike Frysinger Date: Sat, 23 Jul 2011 03:10:11 +0000 (-0400) Subject: Blackfin: spi-docs: further clarify GPIO CS behavior with various modes X-Git-Tag: MMI-PSA29.97-13-9~18881^2 X-Git-Url: https://git.stricted.de/?a=commitdiff_plain;h=10617340ce1491da7654d408d0d635ba98ef8350;p=GitHub%2FMotorolaMobilityLLC%2Fkernel-slsi.git Blackfin: spi-docs: further clarify GPIO CS behavior with various modes Signed-off-by: Mike Frysinger --- diff --git a/Documentation/blackfin/bfin-spi-notes.txt b/Documentation/blackfin/bfin-spi-notes.txt index 556fa877f2e8..eae6eaf2a09d 100644 --- a/Documentation/blackfin/bfin-spi-notes.txt +++ b/Documentation/blackfin/bfin-spi-notes.txt @@ -9,6 +9,8 @@ the entire SPI transfer. - And not just bits_per_word duration. In most cases you can utilize SPI MODE_3 instead of MODE_0 to work-around this behavior. If your SPI slave device in question requires SPI MODE_0 or MODE_2 timing, you can utilize the GPIO controlled SPI Slave Select option instead. +In this case, you should use GPIO based CS for all of your slaves and not just +the ones using mode 0 or 2 in order to guarantee correct CS toggling behavior. You can even use the same pin whose peripheral role is a SSEL, but use it as a GPIO instead.