doc/driver-model/pci-info.txt

1 PCI with Driver Model
8 uclass_get_device_by_seq() to get the PCI bus for a particular bus number.
14 		pci0 = &pci;
17 	pci: pci-controller {
18 		compatible = "sandbox,pci";
26 The call to uclass_get_device() will cause the PCI bus to be probed.
29 they are bound to a generic PCI driver which does nothing.
35 touched on PCI (eg: a call to pci_find_devices()) it will not be probed.
37 PCI devices can appear in the flattened device tree. If they do this serves to
39 first. Each PCI device node must have a compatible string list as well as a
40 <reg> property, as defined by the IEEE Std 1275-1994 PCI bus binding document
41 v2.1. Note we must describe PCI devices with the same bus hierarchy as the
43 relationship during PCI bus enumeration thus PCI devices won't be bound to
46 	pci {
49 		compatible = "pci-x86";
58 			compatible = "pci-bridge";
65 				compatible = "pci-bridge";
88 In this example, the root PCI bus node is the "/pci" which matches "pci-x86"
89 driver. It has a subnode "pcie@17,0" with driver "pci-bridge". "pcie@17,0"
90 also has subnode "topcliff@0,0" which is a "pci-bridge" too. Under that bridge,
91 a PCI UART device "uart@a,1" is described. This exactly reflects the hardware
92 bus hierarchy: on the root PCI bus, there is a PCIe root port which connects
94 PCIe-to-PCI bridge and all the chipset integrated devices like the PCI UART
95 device are on the PCI bus. Like other devices in the device tree, if we want
96 to bind PCI devices before relocation, "u-boot,dm-pre-reloc" must be declared
99 If PCI devices are not listed in the device tree, U_BOOT_PCI_DEVICE can be used
111 is no real PCI bus. This works by looking in the device tree node for a
115 	pci@1f,0 {
116 		compatible = "pci-generic";
126 PCI bus binding document, v2.1)
130 `- * pci-controller @ 05c660c8, 0
131  `-   pci@1f,0 @ 05c661c8, 63488
134 When accesses go to the pci@1f,0 device they are forwarded to its child, the