Browse Source

spi: spi-fsl-dspi: Fix cs_change handling in message transfer

There are use cases when chip select should be triggered between transfers
in single SPI message. Current implementation does this only on last
transfer in message ignoring cs_change value provided in current transfer.

Signed-off-by: Andrey Vostrikov <andrey.vostrikov@cogentembedded.com>
Signed-off-by: Mark Brown <broonie@kernel.org>
Andrey Vostrikov 9 years ago
parent
commit
92dc20d83a
1 changed files with 2 additions and 2 deletions
  1. 2 2
      drivers/spi/spi-fsl-dspi.c

+ 2 - 2
drivers/spi/spi-fsl-dspi.c

@@ -385,8 +385,8 @@ static int dspi_transfer_one_message(struct spi_master *master,
 		dspi->cur_chip = spi_get_ctldata(spi);
 		dspi->cur_chip = spi_get_ctldata(spi);
 		dspi->cs = spi->chip_select;
 		dspi->cs = spi->chip_select;
 		dspi->cs_change = 0;
 		dspi->cs_change = 0;
-		if (dspi->cur_transfer->transfer_list.next
-				== &dspi->cur_msg->transfers)
+		if (list_is_last(&dspi->cur_transfer->transfer_list,
+				 &dspi->cur_msg->transfers) || transfer->cs_change)
 			dspi->cs_change = 1;
 			dspi->cs_change = 1;
 		dspi->void_write_data = dspi->cur_chip->void_write_data;
 		dspi->void_write_data = dspi->cur_chip->void_write_data;