struct_rio_mport(9) [centos man page]
STRUCT
RIO_MPORT(9) Internals STRUCT RIO_MPORT(9) NAME
struct_rio_mport - RIO master port info SYNOPSIS
struct rio_mport { struct list_head dbells; struct list_head node; struct list_head nnode; struct resource iores; struct resource riores[RIO_MAX_MPORT_RESOURCES]; struct rio_msg inb_msg[RIO_MAX_MBOX]; struct rio_msg outb_msg[RIO_MAX_MBOX]; int host_deviceid; struct rio_ops * ops; unsigned char id; unsigned char index; unsigned int sys_size; enum rio_phy_type phy_type; u32 phys_efptr; unsigned char name[RIO_MAX_MPORT_NAME]; void * priv; #ifdef CONFIG_RAPIDIO_DMA_ENGINE struct dma_device dma; #endif struct rio_scan * nscan; }; MEMBERS
dbells List of doorbell events node Node in global list of master ports nnode Node in network list of master ports iores I/O mem resource that this master port interface owns riores[RIO_MAX_MPORT_RESOURCES] RIO resources that this master port interfaces owns inb_msg[RIO_MAX_MBOX] RIO inbound message event descriptors outb_msg[RIO_MAX_MBOX] RIO outbound message event descriptors host_deviceid Host device ID associated with this master port ops configuration space functions id Port ID, unique among all ports index Port index, unique among all port interfaces of the same type sys_size RapidIO common transport system size phy_type RapidIO phy type phys_efptr RIO port extended features pointer name[RIO_MAX_MPORT_NAME] Port name string priv Master port private data dma DMA device associated with mport nscan RapidIO network enumeration/discovery operations AUTHOR
Matt Porter <mporter@kernel.crashing.org>, <mporter@mvista.com> Author. COPYRIGHT
Kernel Hackers Manual 3.10 June 2014 STRUCT RIO_MPORT(9)
Check Out this Related Man Page
STRUCT
SPI_MESSAGE(9) Serial Peripheral Interface (S STRUCT SPI_MESSAGE(9) NAME
struct_spi_message - one multi-segment SPI transaction SYNOPSIS
struct spi_message { struct list_head transfers; struct spi_device * spi; unsigned is_dma_mapped:1; void (* complete) (void *context); void * context; unsigned actual_length; int status; struct list_head queue; void * state; }; MEMBERS
transfers list of transfer segments in this transaction spi SPI device to which the transaction is queued is_dma_mapped if true, the caller provided both dma and cpu virtual addresses for each transfer buffer complete called to report transaction completions context the argument to complete when it's called actual_length the total number of bytes that were transferred in all successful segments status zero for success, else negative errno queue for use by whichever driver currently owns the message state for use by whichever driver currently owns the message DESCRIPTION
A spi_message is used to execute an atomic sequence of data transfers, each represented by a struct spi_transfer. The sequence is "atomic" in the sense that no other spi_message may use that SPI bus until that sequence completes. On some systems, many such sequences can execute as as single programmed DMA transfer. On all systems, these messages are queued, and might complete after transactions to other devices. Messages sent to a given spi_device are alway executed in FIFO order. The code that submits an spi_message (and its spi_transfers) to the lower layers is responsible for managing its memory. Zero-initialize every field you don't set up explicitly, to insulate against future API updates. After you submit a message and its transfers, ignore them until its completion callback. COPYRIGHT
Kernel Hackers Manual 3.10 June 2014 STRUCT SPI_MESSAGE(9)