Skip to content

Commit 9aea644

Browse files
fancerbroonie
authored andcommitted
spi: dw: Fix native CS being unset
Commit 6e0a32d ("spi: dw: Fix default polarity of native chipselect") attempted to fix the problem when GPIO active-high chip-select is utilized to communicate with some SPI slave. It fixed the problem, but broke the normal native CS support. At the same time the reversion commit ada9e3f ("spi: dw: Correct handling of native chipselect") didn't solve the problem either, since it just inverted the set_cs() polarity perception without taking into account that CS-high might be applicable. Here is what is done to finally fix the problem. DW SPI controller demands any native CS being set in order to proceed with data transfer. So in order to activate the SPI communications we must set any bit in the Slave Select DW SPI controller register no matter whether the platform requests the GPIO- or native CS. Preferably it should be the bit corresponding to the SPI slave CS number. But currently the dw_spi_set_cs() method activates the chip-select only if the second argument is false. Since the second argument of the set_cs callback is expected to be a boolean with "is-high" semantics (actual chip-select pin state value), the bit in the DW SPI Slave Select register will be set only if SPI core requests the driver to set the CS in the low state. So this will work for active-low GPIO-based CS case, and won't work for active-high CS setting the bit when SPI core actually needs to deactivate the CS. This commit fixes the problem for all described cases. So no matter whether an SPI slave needs GPIO- or native-based CS with active-high or low signal the corresponding bit will be set in SER. Signed-off-by: Serge Semin <[email protected]> Fixes: ada9e3f ("spi: dw: Correct handling of native chipselect") Fixes: 6e0a32d ("spi: dw: Fix default polarity of native chipselect") Reviewed-by: Charles Keepax <[email protected]> Reviewed-by: Andy Shevchenko <[email protected]> Acked-by: Linus Walleij <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Mark Brown <[email protected]>
1 parent afb7f56 commit 9aea644

File tree

1 file changed

+9
-1
lines changed

1 file changed

+9
-1
lines changed

drivers/spi/spi-dw.c

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -124,8 +124,16 @@ static inline void dw_spi_debugfs_remove(struct dw_spi *dws)
124124
void dw_spi_set_cs(struct spi_device *spi, bool enable)
125125
{
126126
struct dw_spi *dws = spi_controller_get_devdata(spi->controller);
127+
bool cs_high = !!(spi->mode & SPI_CS_HIGH);
127128

128-
if (!enable)
129+
/*
130+
* DW SPI controller demands any native CS being set in order to
131+
* proceed with data transfer. So in order to activate the SPI
132+
* communications we must set a corresponding bit in the Slave
133+
* Enable register no matter whether the SPI core is configured to
134+
* support active-high or active-low CS level.
135+
*/
136+
if (cs_high == enable)
129137
dw_writel(dws, DW_SPI_SER, BIT(spi->chip_select));
130138
else if (dws->cs_override)
131139
dw_writel(dws, DW_SPI_SER, 0);

0 commit comments

Comments
 (0)