Lines Matching refs:SPI

1 SPI devices have a limited userspace API, supporting basic half-duplex
2 read() and write() access to SPI slave devices.  Using ioctl() requests,
17    as SPI slaves, which you may need to change quite often.
29 Set up the other device characteristics (bits per word, SPI clocking,
36 When you do that, the sysfs node for the SPI device will include a child
39 busybox; it's less featureful, but often enough.)  For a SPI device with
46     /sys/devices/.../spiB.C ... as usual, the SPI device node will
47 	be a child of its SPI master controller.
61 by having kernel code remove the SPI device, probably by removing the driver
62 for its SPI controller (so its spi_master vanishes).
67 SPI device, and you'll get a /dev device node for each device.
84 	return (RD) or assign (WR) the SPI transfer mode.  Use the constants
88 	Note that this request is limited to SPI mode flags that fit in a
92 	which will return (RD) or assign (WR) the full SPI transfer mode,
97 	transfer SPI words.  Zero indicates MSB-first; other values indicate
104 	each SPI transfer word.  The value zero signifies eight bits.
107 	u32 which will return (RD) or assign (WR) the maximum SPI transfer
120       that could corrupt transfers to other devices sharing the SPI bus.
121       Each SPI device is deselected when it's not in active use, allowing
125       to the SPI device.  It defaults to one page, but that can be changed
128     - Because SPI has no low-level transfer acknowledgement, you usually