1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
4 $id: http://devicetree.org/schemas/pci/brcm,stb-pcie.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Brcmstb PCIe Host Controller
10 - Jim Quinlan <james.quinlan@broadcom.com>
16 - brcm,bcm2711-pcie # The Raspberry Pi 4
18 - brcm,bcm7211-pcie # Broadcom STB version of RPi4
19 - brcm,bcm7216-pcie # Broadcom 7216 Arm
20 - brcm,bcm7278-pcie # Broadcom 7278 Arm
21 - brcm,bcm7425-pcie # Broadcom 7425 MIPs
22 - brcm,bcm7435-pcie # Broadcom 7435 MIPs
23 - brcm,bcm7445-pcie # Broadcom 7445 Arm
24 - brcm,bcm7712-pcie # Broadcom STB sibling of Rpi 5
32 - description: PCIe host controller
33 - description: builtin MSI controller
57 description: Identifies the node as an MSI controller.
60 description: MSI controller the device is capable of using.
63 description: Indicates usage of spread-spectrum clocking.
69 description: A string that determines the operating
70 clkreq mode of the PCIe RC HW with respect to controlling the refclk
71 signal. There are three different modes -- "safe", which drives the
72 refclk signal unconditionally and will work for all devices but does
73 not provide any power savings; "no-l1ss" -- which provides Clock
74 Power Management, L0s, and L1, but cannot provide L1 substate (L1SS)
75 power savings. If the downstream device connected to the RC is L1SS
76 capable AND the OS enables L1SS, all PCIe traffic may abruptly halt,
77 potentially hanging the system; "default" -- which provides L0s, L1,
78 and L1SS, but not compliant to provide Clock Power Management;
79 specifically, may not be able to meet the T_CLRon max timing of 400ns
80 as specified in "Dynamic Clock Control", section 3.2.5.2.2 PCI
81 Express Mini CEM 2.1 specification. This situation is atypical and
82 should happen only with older devices.
83 $ref: /schemas/types.yaml#/definitions/string
84 enum: [ safe, no-l1ss, default ]
87 description: u64 giving the 64bit PCIe memory
88 viewport size of a memory controller. There may be up to
89 three controllers, and each size must be a power of two
90 with a size greater or equal to the amount of memory the
91 controller supports. Note that each memory controller
92 may have two component regions -- base and extended -- so
93 this information cannot be deduced from the dma-ranges.
94 $ref: /schemas/types.yaml#/definitions/uint64-array
120 - $ref: /schemas/pci/pci-host-bridge.yaml#
121 - $ref: /schemas/interrupt-controller/msi-controller.yaml#
126 const: brcm,bcm4908-pcie
143 const: brcm,bcm7216-pcie
161 const: brcm,bcm7712-pcie
178 unevaluatedProperties: false
182 #include <dt-bindings/interrupt-controller/irq.h>
183 #include <dt-bindings/interrupt-controller/arm-gic.h>
186 #address-cells = <2>;
188 pcie0: pcie@7d500000 {
189 compatible = "brcm,bcm2711-pcie";
190 reg = <0x0 0x7d500000 0x9310>;
192 #address-cells = <3>;
194 #interrupt-cells = <1>;
195 interrupts = <GIC_SPI 147 IRQ_TYPE_LEVEL_HIGH>,
196 <GIC_SPI 148 IRQ_TYPE_LEVEL_HIGH>;
197 interrupt-names = "pcie", "msi";
198 interrupt-map-mask = <0x0 0x0 0x0 0x7>;
199 interrupt-map = <0 0 0 1 &gicv2 GIC_SPI 143 IRQ_TYPE_LEVEL_HIGH
200 0 0 0 2 &gicv2 GIC_SPI 144 IRQ_TYPE_LEVEL_HIGH
201 0 0 0 3 &gicv2 GIC_SPI 145 IRQ_TYPE_LEVEL_HIGH
202 0 0 0 4 &gicv2 GIC_SPI 146 IRQ_TYPE_LEVEL_HIGH>;
204 msi-parent = <&pcie0>;
206 ranges = <0x02000000 0x0 0xf8000000 0x6 0x00000000 0x0 0x04000000>;
207 dma-ranges = <0x42000000 0x1 0x00000000 0x0 0x40000000 0x0 0x80000000>,
208 <0x42000000 0x1 0x80000000 0x3 0x00000000 0x0 0x80000000>;
210 brcm,scb-sizes = <0x0000000080000000 0x0000000080000000>;
212 /* PCIe bridge, Root Port */
214 #address-cells = <3>;
216 reg = <0x0 0x0 0x0 0x0 0x0>;
217 compatible = "pciclass,0604";
219 vpcie3v3-supply = <&vreg7>;
225 <0x82010000 0x0 0xf8000000 0x6 0x00000000 0x0 0x2000>;
226 reg = <0x0 0x0 0x0 0x0 0x0>;
227 compatible = "pci14e4,1688";