Lines Matching +full:spi +full:- +full:slave
2 PXA2xx SPI on SSP driver HOWTO
6 synchronous serial port into an SPI master controller
7 (see Documentation/spi/spi-summary.rst). The driver has the following features
9 - Support for any PXA2xx and compatible SSP.
10 - SSP PIO and SSP DMA data transfers.
11 - External and Internal (SSPFRM) chip selects.
12 - Per slave device (chip) configuration.
13 - Full suspend, freeze, resume support.
17 is responsible for queuing SPI transactions and setting up and launching
21 -----------------------------------
22 Typically, for a legacy platform, an SPI master is defined in the
23 arch/.../mach-*/board-*.c as a "platform device". The master configuration
24 is passed to the driver via a table found in include/linux/spi/pxa2xx_spi.h::
33 slave device (chips) attached to this SPI master.
44 ------------------
66 .name = "pxa2xx-spi", /* MUST BE THIS VALUE, so device match driver */
84 Declaring Slave Devices
85 -----------------------
86 Typically, for a legacy platform, each SPI slave (chip) is defined in the
87 arch/.../mach-*/board-*.c using the "spi_board_info" structure found in
88 "linux/spi/spi.h". See "Documentation/spi/spi-summary.rst" for additional
91 Each slave device attached to the PXA must provide slave specific configuration
93 "include/linux/spi/pxa2xx_spi.h". The pxa2xx_spi master controller driver
94 will uses the configuration whenever the driver communicates with the slave
119 to determine the correct value. An SSP configured for byte-wide transfers would
125 dependent on the SPI bus speed ("spi_board_info.max_speed_hz") and the specific
126 slave device. Please note that the PXA2xx SSP 1 does not support trailing byte
127 timeouts and must busy-wait any trailing bytes.
129 NOTE: the SPI driver cannot control the chip select if SSPFRM is used, so the
135 NSSP SLAVE SAMPLE
136 -----------------
165 .irq = STREETRACER_APCI_IRQ, /* Slave device interrupt */
173 .irq = STREETRACER_APCI_IRQ, /* Slave device interrupt */
185 -----------------------
213 ---------