Lines Matching refs:transfer

389         buffer for each transfer direction, supporting full duplex
397       + whether the chipselect becomes inactive after a transfer and
402 	transfer in that atomic group, and potentially saving costs
433 transfer mode, wordsize, or clock rate.  This is done with spi_setup(),
531 	driver to prepare the transfer hardware by issuing this call.
541 	The subsystem calls the driver to transfer a single message while
548 			 struct spi_transfer *transfer)
549 	The subsystem calls the driver to transfer a single transfer while
551 	finished with this transfer, it must call
553 	transfer. This may sleep. Note: transfer_one and transfer_one_message
559 	0: transfer is finished
560 	1: transfer is still in progress
564     master->transfer(struct spi_device *spi, struct spi_message *message)
566 	transfer happens and its complete() callback is issued. The two
584 function transfer().
593 Such a transfer() method would normally just add the message to a
594 queue, and then start some asynchronous transfer engine (unless it's