Lines Matching refs:SPI

2 SPI userspace API
5 SPI devices have a limited userspace API, supporting basic half-duplex
6 read() and write() access to SPI slave devices.  Using ioctl() requests,
23    as SPI slaves, which you may need to change quite often.
33 The spidev driver contains lists of SPI devices that are supported for
36 The following are the SPI device tables supported by the spidev driver:
50 You are encouraged to add an entry for your SPI device name to relevant
54 It used to be supported to define an SPI device using the "spidev" name.
56 is no longer supported by the Linux kernel and instead a real SPI device
59 Not having a real SPI device name will lead to an error being printed and
69 When the spidev driver is bound to a SPI device, the sysfs node for the
74 For a SPI device with chipselect C on bus B, you should see:
82 	as usual, the SPI device node will
83 	be a child of its SPI master controller.
98 by having kernel code remove the SPI device, probably by removing the driver
99 for its SPI controller (so its spi_master vanishes).
104 SPI device, and you'll get a /dev device node for each device.
122 	return (RD) or assign (WR) the SPI transfer mode.  Use the constants
126 	Note that this request is limited to SPI mode flags that fit in a
131 	which will return (RD) or assign (WR) the full SPI transfer mode,
137 	transfer SPI words.  Zero indicates MSB-first; other values indicate
145 	each SPI transfer word.  The value zero signifies eight bits.
149 	u32 which will return (RD) or assign (WR) the maximum SPI transfer
162       that could corrupt transfers to other devices sharing the SPI bus.
163       Each SPI device is deselected when it's not in active use, allowing
167       to the SPI device.  It defaults to one page, but that can be changed
170     - Because SPI has no low-level transfer acknowledgement, you usually