driver-api/rapidio/rapidio.rst

17 into the kernel similarly to other buses by defining RapidIO-specific device and
21 architecture-specific interfaces that provide support for common RapidIO
38 by a rio_mport data structure. This structure contains master port specific
43 RapidIO master ports are serviced by subsystem specific mport device drivers
46 includes rio_ops data structure which contains pointers to hardware specific
64 data structure, which contains switch specific information such as copy of the
65 routing table and pointers to switch specific functions.
68 specific switch drivers that are designed to provide hardware-specific
83 RapidIO device-specific drivers follow Linux Kernel Driver Model and are
84 intended to support specific RapidIO devices attached to the RapidIO network.
91 common services may act separately from device-specific drivers or be used by
92 device-specific drivers. Example of such service provider is the RIONET driver
96 the same device without blocking attachment of a device-specific driver.
190 If the host device ID for a specific master port is set to -1, the discovery
196 NOTE: If RapidIO switch-specific device drivers are built as loadable modules
199 vendor-specific callbacks on early stages.
230 an enumeration or discovery process on specific mport device, a user needs to
265 structure to store switch specific information. Then the switch's vendor ID and
267 table entry contains a pointer to a switch-specific initialization routine that
268 initializes pointers to the rest of switch specific operations, and performs
326 RapidIO-specific modprobe configuration file as shown in the example below.