Lines Matching refs:that

13  * Prototyping in an environment that's not crash-prone; stray pointers
19 Of course there are drivers that can never be written in userspace, because
21 of the driver stack) that are not accessible to userspace.
36 When you do that, the sysfs node for the SPI device will include a child
37 device node with a "dev" attribute that will be understood by udev or mdev.
44 	that userspace programs will open, created by "udev" or "mdev".
50 	binds to that device.  (Directory or symlink, based on whether
57 If you unbind the "spidev" driver from that device, those two "spidev" nodes
88 	Note that this request is limited to SPI mode flags that fit in a
93 	not limited to the bits that fit in one byte.
99 	is right-justified in each word, so that unused (TX) or undefined (RX)
108 	speed, in Hz.  The controller can't necessarily assign that specific
120       that could corrupt transfers to other devices sharing the SPI bus.
125       to the SPI device.  It defaults to one page, but that can be changed
137 transfer.)  The model is the same as that used in the kernel spi_sync()
139 available to kernel drivers (except that it's not asynchronous).
142 These requests commonly require that the chip not be deselected between