Lines Matching +full:slave +full:- +full:kernel

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.
15 The driver is built around a &struct spi_message FIFO serviced by kernel
16 thread. The kernel thread, spi_pump_messages(), drives message FIFO and
21 -----------------------------------
23 arch/.../mach-*/board-*.c as a "platform device". The master configuration
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
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
126 slave device.  Please note that the PXA2xx SSP 1 does not support trailing byte
127 timeouts and must busy-wait any trailing bytes.
135 NSSP SLAVE SAMPLE
136 -----------------
165 		.irq = STREETRACER_APCI_IRQ, /* Slave device interrupt */
173 		.irq = STREETRACER_APCI_IRQ, /* Slave device interrupt */
185 -----------------------
213 ---------