Lines Matching refs:device
60 * Target device number sent in the ID in the
218 * Build a PCIe config space request address for a device
257 * @pcie_port: PCIe port the device is on
279 * @pcie_port: PCIe port the device is on
301 * @pcie_port: PCIe port the device is on
323 * @pcie_port: PCIe port the device is on
342 * @pcie_port: PCIe port the device is on
361 * @pcie_port: PCIe port the device is on
950 * device addresses, so make sure the peer to peer forwarding
1380 * device addresses, so make sure the peer to peer forwarding
1455 * Map a PCI device to the appropriate interrupt line
1457 * @dev: The Linux PCI device structure for the device to map
1458 * @slot: The slot number for this device on __BUS 0__. Linux
1460 * slot on Bus 0 where this device eventually hooks to.
1461 * @pin: The PCI interrupt pin read from the device, then swizzled
1463 * Returns Interrupt number for the device
1469 * wires the first slot for both device id 2 and interrupt
1470 * A. According to the PCI spec, device id 2 should be C. The
1476 * Iterate all the way up the device chain and find
1487 (dev->vendor == 0x10b5) && (dev->device == 0x8114)) {
1574 * PCIe only has a single device connected to Octeon. It is
1575 * always device ID 0. Don't bother doing reads for other
1576 * device IDs on the first segment.
1593 * bridge only respondes to device ID 0, function
1599 * The PCI-X slots are device ID 2,3. Choose one of
1940 * device addresses at the same place as PCI
2007 * To calculate the address for accessing the 2nd PCIe device,
2022 * To keep things similar to PCI, we start device