Lines Matching refs:ID
40 host device ID that is valid when a master port is configured as an enumerating
163 assigning a host destination ID greater than or equal to zero. The host
164 destination ID can be assigned to a master port using various methods depending
168 "rapidio.hdid=" with a list of destination ID assignments in order of mport
171 the host destination ID=7 to the second RapidIO controller, while the first
172 one will be assigned destination ID=-1.
175 to the method shown above, the host destination ID(s) can be specified using
185 destination ID = -1;
188 destination ID assignments omitted from the end of list (default = -1).
190 If the host device ID for a specific master port is set to -1, the discovery
231 write mport_ID (not RapidIO destination ID) into that file. The mport_ID is a
256 device by writing into the Host Device ID Lock CSR. It does this to ensure that
261 If the device is an endpoint, a unique device ID is assigned to it and its value
262 is written into the device's Base Device ID CSR.
265 structure to store switch specific information. Then the switch's vendor ID and
266 device ID are queried against a table of known RapidIO switches. Each switch
270 device ID; it relies on hopcount and routing for device ID of an attached
273 it, a fake device ID will be assigned to configure a route to that switch.
274 In the case of a chain of switches without endpoint, one fake device ID is used
284 port of that switch. For each active link, a route to a default device ID
287 and the default device ID in order to access the device on the active port.
290 devices by clearing device ID locks (calls rio_clear_locks()). For each endpoint
332 # Set enumerator host destination ID (overrides kernel command line option)