Searched refs:SPI_MOSI_IDLE_HIGH (Results 1 – 8 of 8) sorted by relevance
70 word = spi->mode & SPI_MOSI_IDLE_HIGH ? 0xFF : 0; in bitbang_txrx_8()101 word = spi->mode & SPI_MOSI_IDLE_HIGH ? 0xFFFF : 0; in bitbang_txrx_16()132 word = spi->mode & SPI_MOSI_IDLE_HIGH ? 0xFFFFFFFF : 0; in bitbang_txrx_32()
220 if (spi->mode & SPI_MOSI_IDLE_HIGH) in spi_engine_get_config()1232 host->mode_bits |= SPI_MOSI_IDLE_LOW | SPI_MOSI_IDLE_HIGH; in spi_engine_probe()
4039 if ((spi->mode & SPI_MOSI_IDLE_LOW) && (spi->mode & SPI_MOSI_IDLE_HIGH)) { in spi_setup()
32 #define SPI_MOSI_IDLE_HIGH _BITUL(18) /* leave MOSI line high when idle */ macro
60 it requires the SPI controller to support the ``SPI_MOSI_IDLE_HIGH`` feature.85 controller is not required to support ``SPI_MOSI_IDLE_HIGH`` but register access157 turbo mode, and the SPI controller is ``SPI_MOSI_IDLE_HIGH`` capable. If those
1649 if (spi->controller->mode_bits & SPI_MOSI_IDLE_HIGH) { in ad7768_probe()1650 spi->mode |= SPI_MOSI_IDLE_HIGH; in ad7768_probe()
1079 spi->mode |= SPI_MOSI_IDLE_HIGH; in ad4000_probe()
661 controller is not clocking out data (``SPI_MOSI_IDLE_HIGH``), then a transfer in693 ``SPI_MOSI_IDLE_HIGH`` bit into the mode attribute of their ``struct695 should indicate it by setting ``SPI_MOSI_IDLE_HIGH`` in the mode_bits attribute