driver-api/rapidio/mport_cdev.rst

17 for user-space applications. Most of RapidIO operations are supported through
24 Using available set of ioctl commands user-space applications can perform
27 - Reads and writes from/to configuration registers of mport devices
29 - Reads and writes from/to configuration registers of remote RapidIO devices.
32 - Set RapidIO Destination ID for mport devices (RIO_MPORT_MAINT_HDID_SET)
33 - Set RapidIO Component Tag for mport devices (RIO_MPORT_MAINT_COMPTAG_SET)
34 - Query logical index of mport devices (RIO_MPORT_MAINT_PORT_IDX_GET)
35 - Query capabilities and RapidIO link configuration of mport devices
37 - Enable/Disable reporting of RapidIO doorbell events to user-space applications
39 - Enable/Disable reporting of RIO port-write events to user-space applications
41 - Query/Control type of events reported through this driver: doorbells,
42   port-writes or both (RIO_SET_EVENT_MASK/RIO_GET_EVENT_MASK)
43 - Configure/Map mport's outbound requests window(s) for specific size,
46 - Configure/Map mport's inbound requests window(s) for specific size,
49 - Allocate/Free contiguous DMA coherent memory buffer for DMA data transfers
51 - Initiate DMA data transfers to/from remote RapidIO devices (RIO_TRANSFER).
52   Supports blocking, asynchronous and posted (a.k.a 'fire-and-forget') data
54 - Check/Wait for completion of asynchronous DMA data transfer
56 - Manage device objects supported by RapidIO subsystem (RIO_DEV_ADD/RIO_DEV_DEL).
58   as user-space applications while using remaining functionality provided by
68 At this moment the most common limitation is availability of RapidIO-specific
69 DMA engine framework for specific mport device. Users should verify available
72 - IDT Tsi721 PCIe-to-RapidIO bridge device and its mport device driver are fully
74 - Freescale SoCs 'fsl_rio' mport driver does not have implementation for RapidIO
75   specific DMA engine support and therefore DMA data transfers mport_cdev driver
81 - 'dma_timeout'
82       - DMA transfer completion timeout (in msec, default value 3000).
83         This parameter set a maximum completion wait time for SYNC mode DMA
84         transfer requests and for RIO_WAIT_FOR_ASYNC ioctl requests.
86 - 'dbg_level'
87       - This parameter allows to control amount of debug information
99 5. User-space Applications and API
108 - Add support for sending/receiving "raw" RapidIO messaging packets.
109 - Add memory mapped DMA data transfers as an option when RapidIO-specific DMA