Lines Matching +full:full +full:- +full:duplex

5 SPI devices have a limited userspace API, supporting basic half-duplex
7 full duplex transfers and device I/O configuration are also available.
19  * Prototyping in an environment that's not crash-prone; stray pointers
73 Since this is a standard Linux device driver -- even though it just happens
74 to expose a low level API to userspace -- it can be associated with any number
84 Standard read() and write() operations are obviously only half-duplex, and
85 the chipselect is deactivated between those operations.  Full-duplex access,
86 and composite operation without chipselect de-activation, is available using
103 	which will return (RD) or assign (WR) the full SPI transfer mode,
109 	transfer SPI words.  Zero indicates MSB-first; other values indicate
110 	the less common LSB-first encoding.  In both cases the specified value
111 	is right-justified in each word, so that unused (TX) or undefined (RX)
127     - At this time there is no async I/O support; everything is purely
130     - There's currently no way to report the actual bit rate used to
133     - From userspace, you can't currently change the chip select polarity;
138     - There's a limit on the number of bytes each I/O request can transfer
142     - Because SPI has no low-level transfer acknowledgement, you usually
143       won't see any I/O errors when talking to a non-existent device.
146 FULL DUPLEX CHARACTER DEVICE API
150 full duplex programming interface.  (Although it doesn't perform a full duplex
155 The example shows one half-duplex RPC-style request and response message.
162 To make a full duplex request, provide both rx_buf and tx_buf for the