centos man page for spi_write_then_read

Query: spi_write_then_read

OS: centos

Section: 9

Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar

SPI_WRITE_THEN_READ(9)					  Serial Peripheral Interface (S				    SPI_WRITE_THEN_READ(9)

NAME
spi_write_then_read - SPI synchronous write followed by read
SYNOPSIS
int spi_write_then_read(struct spi_device * spi, const void * txbuf, unsigned n_tx, void * rxbuf, unsigned n_rx);
ARGUMENTS
spi device with which data will be exchanged txbuf data to be written (need not be dma-safe) n_tx size of txbuf, in bytes rxbuf buffer into which data will be read (need not be dma-safe) n_rx size of rxbuf, in bytes
CONTEXT
can sleep
DESCRIPTION
This performs a half duplex MicroWire style transaction with the device, sending txbuf and then reading rxbuf. The return value is zero for success, else a negative errno status code. This call may only be used from a context that may sleep. Parameters to this routine are always copied using a small buffer; portable code should never use this for more than 32 bytes. Performance-sensitive or bulk transfer code should instead use spi_{async,sync}() calls with dma-safe buffers.
COPYRIGHT
Kernel Hackers Manual 3.10 June 2014 SPI_WRITE_THEN_READ(9)
Related Man Pages
spi_async_locked(9) - centos
struct_spi_master(9) - centos
struct_spi_message(9) - centos
struct_usb_request(9) - centos
struct_usb_request(9) - suse
Similar Topics in the Unix Linux Community
Set hard block limit for user using quota
Best performance UNIX just for HOST Virtualization?
Unsure why access time on a directory change isn't changing
CentOS 6 ran out of space, need to reclaim it
Controlling user input