linux/spi/spi.h

62  *                 transfer bytes histogram
136  *	The spi_transfer.speed_hz can override this for each transfer.
143  *	each word in a transfer (by specifying SPI_LSB_FIRST).
149  *	The spi_transfer.bits_per_word can override this for each transfer.
166  *	words of a transfer
405  *	supported. If set, the SPI core will reject any transfer with an
408  * @min_speed_hz: Lowest supported transfer speed
409  * @max_speed_hz: Highest supported transfer speed
414  * @max_transfer_size: function that returns the max transfer size for
431  * @transfer: adds a message to the controller's transfer queue.
451  * @fallback: fallback to PIO if DMA transfer return failure with
464  * @max_dma_len: Maximum length of a DMA transfer for the device.
466  *	so the subsystem requests the driver to prepare the transfer hardware
468  * @transfer_one_message: the subsystem calls the driver to transfer a single
481  * @prepare_message: set up the controller to transfer a single message,
484  * @transfer_one: transfer a single spi_transfer.
486  *                  - return 0 if the transfer is finished,
487  *                  - return 1 if the transfer is still in progress. When
488  *                    the driver is finished with this transfer it must
490  *                    can issue the next transfer. If the transfer fails, the
504  * @slave_abort: abort the ongoing transfer request on an SPI slave controller
505  * @target_abort: abort the ongoing transfer request on an SPI target controller
584 	/* Limits on transfer speed */
614 	 * On some hardware transfer / message size may be constrained
615 	 * the limit may depend on device transfer settings.
655 	 * + The transfer() method may not sleep; its main role is
672 	int			(*transfer)(struct spi_device *spi,
680 	 * exists and returns true then the transfer will be mapped
694 	 * controller transfer queueing mechanism. If these are used, the
695 	 * transfer() function above must NOT be specified by the driver.
740 			    struct spi_transfer *transfer);
824 /* Helper calls for driver to timestamp transfer */
944  * The spi_messages themselves consist of a series of read+write transfer
967  *      transfer. If 0 the default (from @spi_device) is used.
969  *      for this transfer. If 0 the default (from @spi_device) is used.
970  * @dummy_data: indicates transfer is dummy bytes transfer.
971  * @cs_off: performs the transfer with chipselect off.
972  * @cs_change: affects chipselect after this transfer completes
975  * @delay: delay to be introduced after this transfer before
977  *	the next transfer or completing this @spi_message.
981  *      transfer this transfer. Set to 0 if the SPI bus driver does
988  *	snapshot for this transfer begins. Upon completing the SPI transfer,
990  *	on the available snapshotting resolution (DMA transfer,
996  *	@ptp_sts_word_post to the length of the transfer. This is done
998  *	that a transfer-level snapshot taken from within the driver may still
1002  *	hardware has some sort of assist for retrieving exact transfer timing,
1009  * @timestamped: true if the transfer has been timestamped
1030  * When the word size of the SPI transfer is not a power-of-two multiple
1036  * it stays selected until after the last transfer in a message.  Drivers
1039  * (i) If the transfer isn't the last one in the message, this flag is
1045  * (ii) When the transfer is the last one in the message, the chip may
1046  * stay selected until the next transfer.  On multi-device SPI busses
1055  * When SPI can transfer in 1x,2x or 4x. It can get this transfer information
1057  * two should both be set. User can set transfer mode with SPI_NBITS_SINGLE(1x)
1058  * SPI_NBITS_DUAL(2x) and SPI_NBITS_QUAD(4x) to support these three transfer.
1091 #define	SPI_NBITS_SINGLE	0x01 /* 1-bit transfer */
1092 #define	SPI_NBITS_DUAL		0x02 /* 2-bit transfer */
1093 #define	SPI_NBITS_QUAD		0x04 /* 4-bit transfer */
1112  * @transfers: list of transfer segments in this transaction
1132  * a single programmed DMA transfer.  On all systems, these messages are
1157 	 * last transfer ... allowing things like "read 16 bit length L"
1326  * Compute a relevant timeout value for the given transfer. We derive the time
1340 /* SPI transfer replacement methods which make use of spi_res */
1355  * @replaced_after:     the transfer after which the @replaced_transfers
1376 /* SPI transfer transformation methods */
1388  * All these synchronous SPI transfer routines are utilities layered
1389  * over the core async transfer primitive.  Here, "synchronous" means
1390  * they will sleep uninterruptibly until the async transfer completes.
1399  * spi_sync_transfer - synchronous SPI data transfer
1405  * Does a synchronous SPI data transfer of the given spi_transfer array.
1585  * as the default transfer wordsize) is not included here.