Lines Matching refs:ID

39 host device ID that is valid when a master port is configured as an enumerating
157 assigning a host destination ID greater than or equal to zero. The host
158 destination ID can be assigned to a master port using various methods depending
162   "rapidio.hdid=" with a list of destination ID assignments in order of mport
165   the host destination ID=7 to the second RapidIO controller, while the first
166   one will be assigned destination ID=-1.
169   to the method shown above, the host destination ID(s) can be specified using
178   destination ID = -1;
180   destination ID assignments omitted from the end of list (default = -1).
182 If the host device ID for a specific master port is set to -1, the discovery
223 write mport_ID (not RapidIO destination ID) into that file. The mport_ID is a
248 device by writing into the Host Device ID Lock CSR. It does this to ensure that
253 If the device is an endpoint, a unique device ID is assigned to it and its value
254 is written into the device's Base Device ID CSR.
257 structure to store switch specific information. Then the switch's vendor ID and
258 device ID are queried against a table of known RapidIO switches. Each switch
262 device ID; it relies on hopcount and routing for device ID of an attached
265 it, a fake device ID will be assigned to configure a route to that switch.
266 In the case of a chain of switches without endpoint, one fake device ID is used
276 port of that switch. For each active link, a route to a default device ID
279 and the default device ID in order to access the device on the active port.
282 devices by clearing device ID locks (calls rio_clear_locks()). For each endpoint
325   # Set enumerator host destination ID (overrides kernel command line option)