J7200: Add PCIe DT nodes to Enable PCIe
Subsystems (5)
v2 cover J7200: Add PCIe DT nodes to Enable PCIe
Add DT binding documentation and device tree nodes to enable PCIe in J7200.
Changes from v1:
*) Renamed "pcie-ctrl" to "syscon" DT node and expanded "syscon" DT
sub-node
*) Fixed "cdns,max-outbound-regions" in EP mode and removed
"cdns,max-outbound-regions" for RC mode.
*) Remove patches specific to J721E
V1 of the patch series can be found @:
http://lore.kernel.org/r/[email protected]
Kishon Vijay Abraham I (7):
dt-bindings: mfd: ti,j721e-system-controller.yaml: Document "syscon"
dt-bindings: PCI: Add host mode dt-bindings for TI's J7200 SoC
dt-bindings: PCI: Add EP mode dt-bindings for TI's J7200 SoC
arm64: dts: ti: k3-j7200-main: Add DT for WIZ and SERDES
arm64: dts: ti: k3-j7200-main: Add PCIe device tree node
arm64: dts: ti: k3-j7200-common-proc-board: Enable SERDES0
arm64: dts: ti: k3-j7200-common-proc-board: Enable PCIe
.../mfd/ti,j721e-system-controller.yaml | 40 ++++++ .../bindings/pci/ti,j721e-pci-ep.yaml | 10 +- .../bindings/pci/ti,j721e-pci-host.yaml | 16 ++- .../dts/ti/k3-j7200-common-proc-board.dts | 38 ++++++ arch/arm64/boot/dts/ti/k3-j7200-main.dtsi | 118 ++++++++++++++++++ 5 files changed, 217 insertions(+), 5 deletions(-)
Signature · 1 line
2.17.1
PATCH v2 1/7 dt-bindings: mfd: ti,j721e-system-controller.yaml: Document "syscon"
Add binding documentation for "syscon" which should be a subnode of the system controller (scm-conf).
--- .../mfd/ti,j721e-system-controller.yaml | 40 +++++++++++++++++++ 1 file changed, 40 insertions(+)
Documentation/devicetree/bindings/mfd/ti,j721e-system-controller.yaml +40 -0
@@ -50,6 +50,38 @@ patternProperties: specified in Documentation/devicetree/bindings/mux/reg-mux.txt + "^syscon@[0-9a-f]+$": + type: object + description: | + This is the system controller configuration required to configure PCIe + mode, lane width and speed. + + properties: + compatible: + items: + - enum: + - ti,j721e-system-controller + - const: syscon + - const: simple-mfd + + reg: + maxItems: 1 + + "#address-cells": + const: 1 + + "#size-cells": + const: 1 + + ranges: true + + required: + - compatible + - reg + - "#address-cells" + - "#size-cells" + - ranges + required: - compatible - reg
@@ -72,5 +104,13 @@ examples: compatible = "mmio-mux"; reg = <0x00004080 0x50>; }; + + pcie1_ctrl: syscon@4074 { + compatible = "ti,j721e-system-controller", "syscon", "simple-mfd"; + reg = <0x00004074 0x4>; + #address-cells = <1>; + #size-cells = <1>; + ranges = <0x4074 0x4074 0x4>; + }; }; ...
Signature · 1 line
2.17.1
Rob Herring
maintainerRe: [PATCH v2 1/7] dt-bindings: mfd: ti,j721e-system-controller.yaml: Document "syscon"
Quoted 13 lines · Kishon Vijay Abraham I
Add binding documentation for "syscon" which should be a subnode of the system controller (scm-conf).
Signed-off-by Kishon Vijay Abraham I <[email protected]>--- .../mfd/ti,j721e-system-controller.yaml | 40 +++++++++++++++++++ 1 file changed, 40 insertions(+)Documentation/devicetree/bindings/mfd/ti,j721e-system-controller.yaml +0
-0
Documentation/devicetree/bindings/mfd/ti,j721e-system-controller.yaml patternProperties: · line 55
Quoted 6 lines
Documentation/devicetree/bindings/mfd/ti,j721e-system-controller.yaml +3
-0@@ -50,6 +50,38 @@ patternProperties: specified in Documentation/devicetree/bindings/mux/reg-mux.txt + "^syscon@[0-9a-f]+$": + type: object + description: |
Don't need '|' if there's no formatting.
Documentation/devicetree/bindings/mfd/ti,j721e-system-controller.yaml patternProperties: · line 65
Quoted 10 lines
Documentation/devicetree/bindings/mfd/ti,j721e-system-controller.yaml +10
-0+ This is the system controller configuration required to configure PCIe + mode, lane width and speed. + + properties: + compatible: + items: + - enum: + - ti,j721e-system-controller + - const: syscon + - const: simple-mfd
Humm, then what are this node's sub-nodes? And the same compatible as the parent?
Quoted 23 lines
Documentation/devicetree/bindings/mfd/ti,j721e-system-controller.yaml +19
-0+ + reg: + maxItems: 1 + + "#address-cells": + const: 1 + + "#size-cells": + const: 1 + + ranges: true + + required: + - compatible + - reg + - "#address-cells" + - "#size-cells" + - ranges + required: - compatible - reg
Documentation/devicetree/bindings/mfd/ti,j721e-system-controller.yaml examples: · line 113
Quoted 10 lines
Documentation/devicetree/bindings/mfd/ti,j721e-system-controller.yaml +7
-0@@ -72,5 +104,13 @@ examples: compatible = "mmio-mux"; reg = <0x00004080 0x50>; }; + + pcie1_ctrl: syscon@4074 { + compatible = "ti,j721e-system-controller", "syscon", "simple-mfd"; + reg = <0x00004074 0x4>; + #address-cells = <1>; + #size-cells = <1>; + ranges = <0x4074 0x4074 0x4>;
Must be packing a bunch of functions into 4 byte region!
Quoted 6 lines
Documentation/devicetree/bindings/mfd/ti,j721e-system-controller.yaml +1
-0+ }; };Signature · 1 line
2.17.1
Re: [PATCH v2 1/7] dt-bindings: mfd: ti,j721e-system-controller.yaml: Document "syscon"
Hi Rob,
Quoted 17 lines · Rob Herring
Quoted 16 lines · Kishon Vijay Abraham I
Add binding documentation for "syscon" which should be a subnode of the system controller (scm-conf).
Signed-off-by Kishon Vijay Abraham I <[email protected]>--- .../mfd/ti,j721e-system-controller.yaml | 40 +++++++++++++++++++ 1 file changed, 40 insertions(+)Documentation/devicetree/bindings/mfd/ti,j721e-system-controller.yaml +0
-0@@ -50,6 +50,38 @@ patternProperties: specified in Documentation/devicetree/bindings/mux/reg-mux.txt
Quoted 5 lines
Documentation/devicetree/bindings/mfd/ti,j721e-system-controller.yaml patternProperties: · line 55
Quoted 3 lines
Documentation/devicetree/bindings/mfd/ti,j721e-system-controller.yaml +3
-0+ "^syscon@[0-9a-f]+$": + type: object + description: |Don't need '|' if there's no formatting.
Okay, will fix this.
Quoted 12 lines
Documentation/devicetree/bindings/mfd/ti,j721e-system-controller.yaml patternProperties: · line 65
Quoted 11 lines
Documentation/devicetree/bindings/mfd/ti,j721e-system-controller.yaml +10
-0+ This is the system controller configuration required to configure PCIe + mode, lane width and speed. + + properties: + compatible: + items: + - enum: + - ti,j721e-system-controller + - const: syscon + - const: simple-mfd
Quoted 3 lines
Humm, then what are this node's sub-nodes? And the same compatible as the parent?
This node doesn't have sub-nodes.
So one is the parent syscon node which has the entire system control region and then sub-nodes for each of the modules. In this case the PCIe in system control has only one 4 byte register that has to be configured.
Both the parent node and sub-node are syscon, so given the same compatible for both.
Quoted 27 lines
Quoted 27 lines
Documentation/devicetree/bindings/mfd/ti,j721e-system-controller.yaml +20
-0+ + reg: + maxItems: 1 + + "#address-cells": + const: 1 + + "#size-cells": + const: 1 + + ranges: true + + required: + - compatible + - reg + - "#address-cells" + - "#size-cells" + - ranges + required: - compatible - reg@@ -72,5 +104,13 @@ examples: compatible = "mmio-mux"; reg = <0x00004080 0x50>; }; +
Quoted 8 lines
Documentation/devicetree/bindings/mfd/ti,j721e-system-controller.yaml examples: · line 113
Quoted 6 lines
Documentation/devicetree/bindings/mfd/ti,j721e-system-controller.yaml +6
-0+ pcie1_ctrl: syscon@4074 { + compatible = "ti,j721e-system-controller", "syscon", "simple-mfd"; + reg = <0x00004074 0x4>; + #address-cells = <1>; + #size-cells = <1>; + ranges = <0x4074 0x4074 0x4>;Must be packing a bunch of functions into 4 byte region!
For the PCIe case, it only has a 4 byte register to be configured. The other option would be to get phandle to the parent syscon node and then hard-code the offset in the driver.
Thank You,
Kishon
_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Rob Herring
maintainerRe: [PATCH v2 1/7] dt-bindings: mfd: ti,j721e-system-controller.yaml: Document "syscon"
Quoted 44 lines · Kishon Vijay Abraham I
Hi Rob,
Quoted 17 lines · Rob Herring
Quoted 16 lines · Kishon Vijay Abraham I
Add binding documentation for "syscon" which should be a subnode of the system controller (scm-conf).
Signed-off-by Kishon Vijay Abraham I <[email protected]>--- .../mfd/ti,j721e-system-controller.yaml | 40 +++++++++++++++++++ 1 file changed, 40 insertions(+)Documentation/devicetree/bindings/mfd/ti,j721e-system-controller.yaml +0
-0@@ -50,6 +50,38 @@ patternProperties: specified in Documentation/devicetree/bindings/mux/reg-mux.txtQuoted 5 lines
Documentation/devicetree/bindings/mfd/ti,j721e-system-controller.yaml patternProperties: · line 55
Quoted 3 lines
Documentation/devicetree/bindings/mfd/ti,j721e-system-controller.yaml +3
-0+ "^syscon@[0-9a-f]+$": + type: object + description: |Don't need '|' if there's no formatting.
Okay, will fix this.
Quoted 12 lines
Documentation/devicetree/bindings/mfd/ti,j721e-system-controller.yaml patternProperties: · line 65
Quoted 11 lines
Documentation/devicetree/bindings/mfd/ti,j721e-system-controller.yaml +10
-0+ This is the system controller configuration required to configure PCIe + mode, lane width and speed. + + properties: + compatible: + items: + - enum: + - ti,j721e-system-controller + - const: syscon + - const: simple-mfdQuoted 3 lines
Humm, then what are this node's sub-nodes? And the same compatible as the parent?
Quoted 8 lines
This node doesn't have sub-nodes.
So one is the parent syscon node which has the entire system control region and then sub-nodes for each of the modules. In this case the PCIe in system control has only one 4 byte register that has to be configured.
Both the parent node and sub-node are syscon, so given the same compatible for both.
'syscon' is just a hint. It doesn't define what any h/w is. IMO, we never should have added it.
A compatible defines what the programming interface is for the node. This one should only ever appear more than once if you have multiple instances of the same block. So different registers, different compatible. What you have here is just completely broken.
I don't think you even need a child node here. Just have PCIe node point to the parent with an offset arg.
Rob
PATCH v2 2/7 dt-bindings: PCI: Add host mode dt-bindings for TI's J7200 SoC
In reply to Kishon Vijay Abraham IAdd host mode dt-bindings for TI's J7200 SoC.
--- .../bindings/pci/ti,j721e-pci-host.yaml | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-)
Documentation/devicetree/bindings/pci/ti,j721e-pci-host.yaml +13 -3
@@ -15,8 +15,14 @@ allOf: properties: compatible: - enum: - - ti,j721e-pcie-host + oneOf: + - description: PCIe controller in J7200 + items: + - const: ti,j7200-pcie-host + - const: ti,j721e-pcie-host + - description: PCIe controller in J721E + items: + - const: ti,j721e-pcie-host reg: maxItems: 4
@@ -48,7 +54,11 @@ properties: const: 0x104c device-id: - const: 0xb00d + oneOf: + - items: + - const: 0xb00d + - items: + - const: 0xb00f msi-map: true
Signature · 1 line
2.17.1
PATCH v2 3/7 dt-bindings: PCI: Add EP mode dt-bindings for TI's J7200 SoC
In reply to Kishon Vijay Abraham IAdd PCIe EP mode dt-bindings for TI's J7200 SoC.
--- .../devicetree/bindings/pci/ti,j721e-pci-ep.yaml | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-)
Documentation/devicetree/bindings/pci/ti,j721e-pci-ep.yaml +8 -2
@@ -15,8 +15,14 @@ allOf: properties: compatible: - enum: - - ti,j721e-pcie-ep + oneOf: + - description: PCIe EP controller in J7200 + items: + - const: ti,j7200-pcie-ep + - const: ti,j721e-pcie-ep + - description: PCIe EP controller in J721E + items: + - const: ti,j721e-pcie-ep reg: maxItems: 4
Signature · 1 line
2.17.1
PATCH v2 4/7 arm64: dts: ti: k3-j7200-main: Add DT for WIZ and SERDES
In reply to Kishon Vijay Abraham IAdd dt node for the single instance of WIZ and SERDES module shared by PCIe, CPSW (SGMII/QSGMII) and USB.
--- arch/arm64/boot/dts/ti/k3-j7200-main.dtsi | 61 +++++++++++++++++++++++ 1 file changed, 61 insertions(+)
arch/arm64/boot/dts/ti/k3-j7200-main.dtsi +61 -0
@@ -417,6 +417,67 @@ dma-coherent; }; + serdes_refclk: serdes_refclk { + #clock-cells = <0>; + compatible = "fixed-clock"; + }; + + serdes_wiz0: wiz@5060000 { + compatible = "ti,j721e-wiz-10g"; + #address-cells = <1>; + #size-cells = <1>; + power-domains = <&k3_pds 292 TI_SCI_PD_EXCLUSIVE>; + clocks = <&k3_clks 292 11>, <&k3_clks 292 85>, <&serdes_refclk>; + clock-names = "fck", "core_ref_clk", "ext_ref_clk"; + num-lanes = <4>; + #reset-cells = <1>; + ranges = <0x5060000 0x0 0x5060000 0x10000>; + + assigned-clocks = <&k3_clks 292 85>; + assigned-clock-parents = <&k3_clks 292 89>; + + wiz0_pll0_refclk: pll0-refclk { + clocks = <&k3_clks 292 85>, <&serdes_refclk>; + clock-output-names = "wiz0_pll0_refclk"; + #clock-cells = <0>; + assigned-clocks = <&wiz0_pll0_refclk>; + assigned-clock-parents = <&k3_clks 292 85>; + }; + + wiz0_pll1_refclk: pll1-refclk { + clocks = <&k3_clks 292 85>, <&serdes_refclk>; + clock-output-names = "wiz0_pll1_refclk"; + #clock-cells = <0>; + assigned-clocks = <&wiz0_pll1_refclk>; + assigned-clock-parents = <&k3_clks 292 85>; + }; + + wiz0_refclk_dig: refclk-dig { + clocks = <&k3_clks 292 85>, <&serdes_refclk>; + clock-output-names = "wiz0_refclk_dig"; + #clock-cells = <0>; + assigned-clocks = <&wiz0_refclk_dig>; + assigned-clock-parents = <&k3_clks 292 85>; + }; + + wiz0_cmn_refclk_dig_div: cmn-refclk-dig-div { + clocks = <&wiz0_refclk_dig>; + #clock-cells = <0>; + }; + + serdes0: serdes@5060000 { + compatible = "ti,j721e-serdes-10g"; + reg = <0x05060000 0x00010000>; + reg-names = "torrent_phy"; + resets = <&serdes_wiz0 0>; + reset-names = "torrent_reset"; + clocks = <&wiz0_pll0_refclk>; + clock-names = "refclk"; + #address-cells = <1>; + #size-cells = <0>; + }; + }; + usbss0: cdns-usb@4104000 { compatible = "ti,j721e-usb"; reg = <0x00 0x4104000 0x00 0x100>;
Signature · 1 line
2.17.1
PATCH v2 5/7 arm64: dts: ti: k3-j7200-main: Add PCIe device tree node
In reply to Kishon Vijay Abraham IAdd PCIe device tree node (both RC and EP) for the single PCIe instance present in j7200.
--- arch/arm64/boot/dts/ti/k3-j7200-main.dtsi | 57 +++++++++++++++++++++++ 1 file changed, 57 insertions(+)
arch/arm64/boot/dts/ti/k3-j7200-main.dtsi +57 -0
@@ -25,6 +25,14 @@ #size-cells = <1>; ranges = <0x00 0x00 0x00100000 0x1c000>; + pcie1_ctrl: syscon@4074 { + compatible = "ti,j721e-system-controller", "syscon", "simple-mfd"; + reg = <0x00004074 0x4>; + #address-cells = <1>; + #size-cells = <1>; + ranges = <0x4074 0x4074 0x4>; + }; + serdes_ln_ctrl: serdes-ln-ctrl@4080 { compatible = "mmio-mux"; #mux-control-cells = <1>;
@@ -478,6 +486,55 @@ }; }; + pcie1_rc: pcie@2910000 { + compatible = "ti,j7200-pcie-host", "ti,j721e-pcie-host"; + reg = <0x00 0x02910000 0x00 0x1000>, + <0x00 0x02917000 0x00 0x400>, + <0x00 0x0d800000 0x00 0x00800000>, + <0x00 0x18000000 0x00 0x00001000>; + reg-names = "intd_cfg", "user_cfg", "reg", "cfg"; + interrupt-names = "link_state"; + interrupts = <GIC_SPI 330 IRQ_TYPE_EDGE_RISING>; + device_type = "pci"; + ti,syscon-pcie-ctrl = <&pcie1_ctrl>; + max-link-speed = <3>; + num-lanes = <4>; + power-domains = <&k3_pds 240 TI_SCI_PD_EXCLUSIVE>; + clocks = <&k3_clks 240 6>; + clock-names = "fck"; + #address-cells = <3>; + #size-cells = <2>; + bus-range = <0x0 0xf>; + cdns,no-bar-match-nbits = <64>; + vendor-id = /bits/ 16 <0x104c>; + device-id = /bits/ 16 <0xb00f>; + msi-map = <0x0 &gic_its 0x0 0x10000>; + dma-coherent; + ranges = <0x01000000 0x0 0x18001000 0x00 0x18001000 0x0 0x0010000>, + <0x02000000 0x0 0x18011000 0x00 0x18011000 0x0 0x7fef000>; + dma-ranges = <0x02000000 0x0 0x0 0x0 0x0 0x10000 0x0>; + }; + + pcie1_ep: pcie-ep@2910000 { + compatible = "ti,j7200-pcie-ep", "ti,j721e-pcie-ep"; + reg = <0x00 0x02910000 0x00 0x1000>, + <0x00 0x02917000 0x00 0x400>, + <0x00 0x0d800000 0x00 0x00800000>, + <0x00 0x18000000 0x00 0x08000000>; + reg-names = "intd_cfg", "user_cfg", "reg", "mem"; + interrupt-names = "link_state"; + interrupts = <GIC_SPI 330 IRQ_TYPE_EDGE_RISING>; + ti,syscon-pcie-ctrl = <&pcie1_ctrl>; + max-link-speed = <3>; + num-lanes = <4>; + power-domains = <&k3_pds 240 TI_SCI_PD_EXCLUSIVE>; + clocks = <&k3_clks 240 6>; + clock-names = "fck"; + cdns,max-outbound-regions = <32>; + max-functions = /bits/ 8 <6>; + dma-coherent; + }; + usbss0: cdns-usb@4104000 { compatible = "ti,j721e-usb"; reg = <0x00 0x4104000 0x00 0x100>;
Signature · 1 line
2.17.1
Re: [PATCH v2 5/7] arm64: dts: ti: k3-j7200-main: Add PCIe device tree node
Quoted 3 lines · Kishon Vijay Abraham I
Add PCIe device tree node (both RC and EP) for the single PCIe instance present in j7200.
nit: s/j7200/J7200
Quoted 2 lines
Signed-off-by Kishon Vijay Abraham I <[email protected]>---
[...]
PATCH v2 6/7 arm64: dts: ti: k3-j7200-common-proc-board: Enable SERDES0
In reply to Kishon Vijay Abraham IAdd sub-nodes to SERDES0 DT node to represent SERDES0 is connected to PCIe and QSGMII (multi-link SERDES).
--- .../dts/ti/k3-j7200-common-proc-board.dts | 23 +++++++++++++++++++ 1 file changed, 23 insertions(+)
arch/arm64/boot/dts/ti/k3-j7200-common-proc-board.dts +23 -0
@@ -8,6 +8,7 @@ #include "k3-j7200-som-p0.dtsi" #include <dt-bindings/net/ti-dp83867.h> #include <dt-bindings/mux/ti-serdes.h> +#include <dt-bindings/phy/phy.h> / { chosen {
@@ -213,3 +214,25 @@ dr_mode = "otg"; maximum-speed = "high-speed"; }; + +&serdes_refclk { + clock-frequency = <100000000>; +}; + +&serdes0 { + serdes0_pcie_link: phy@0 { + reg = <0>; + cdns,num-lanes = <2>; + #phy-cells = <0>; + cdns,phy-type = <PHY_TYPE_PCIE>; + resets = <&serdes_wiz0 1>, <&serdes_wiz0 2>; + }; + + serdes0_qsgmii_link: phy@1 { + reg = <2>; + cdns,num-lanes = <1>; + #phy-cells = <0>; + cdns,phy-type = <PHY_TYPE_QSGMII>; + resets = <&serdes_wiz0 3>; + }; +};
Signature · 1 line
2.17.1
Vignesh Raghavendra
maintainerRe: [PATCH v2 6/7] arm64: dts: ti: k3-j7200-common-proc-board: Enable SERDES0
Quoted 21 lines · Kishon Vijay Abraham I
Add sub-nodes to SERDES0 DT node to represent SERDES0 is connected to PCIe and QSGMII (multi-link SERDES).
Signed-off-by Kishon Vijay Abraham I <[email protected]>--- .../dts/ti/k3-j7200-common-proc-board.dts | 23 +++++++++++++++++++ 1 file changed, 23 insertions(+)arch/arm64/boot/dts/ti/k3-j7200-common-proc-board.dts +1
-0@@ -8,6 +8,7 @@ #include "k3-j7200-som-p0.dtsi" #include <dt-bindings/net/ti-dp83867.h> #include <dt-bindings/mux/ti-serdes.h> +#include <dt-bindings/phy/phy.h> / { chosen {
arch/arm64/boot/dts/ti/k3-j7200-common-proc-board.dts line 220
Quoted 7 lines
arch/arm64/boot/dts/ti/k3-j7200-common-proc-board.dts +4
-0@@ -213,3 +214,25 @@ dr_mode = "otg"; maximum-speed = "high-speed"; }; + +&serdes_refclk { + clock-frequency = <100000000>; +};
Since this is a reference clk from the board, should the entire node be here instead of in k3-j7200-main.dtsi?
Quoted 19 lines
arch/arm64/boot/dts/ti/k3-j7200-common-proc-board.dts +18
-0+ +&serdes0 { + serdes0_pcie_link: phy@0 { + reg = <0>; + cdns,num-lanes = <2>; + #phy-cells = <0>; + cdns,phy-type = <PHY_TYPE_PCIE>; + resets = <&serdes_wiz0 1>, <&serdes_wiz0 2>; + }; + + serdes0_qsgmii_link: phy@1 { + reg = <2>; + cdns,num-lanes = <1>; + #phy-cells = <0>; + cdns,phy-type = <PHY_TYPE_QSGMII>; + resets = <&serdes_wiz0 3>; + }; +};
PATCH v2 7/7 arm64: dts: ti: k3-j7200-common-proc-board: Enable PCIe
In reply to Kishon Vijay Abraham Ix2 lane PCIe slot in the common processor board is enabled and connected to j7200 SOM. Add PCIe DT node in common processor board to reflect the same.
--- .../boot/dts/ti/k3-j7200-common-proc-board.dts | 15 +++++++++++++++ 1 file changed, 15 insertions(+)
arch/arm64/boot/dts/ti/k3-j7200-common-proc-board.dts +15 -0
@@ -6,6 +6,7 @@ /dts-v1/; #include "k3-j7200-som-p0.dtsi" +#include <dt-bindings/gpio/gpio.h> #include <dt-bindings/net/ti-dp83867.h> #include <dt-bindings/mux/ti-serdes.h> #include <dt-bindings/phy/phy.h>
@@ -236,3 +237,17 @@ resets = <&serdes_wiz0 3>; }; }; + +&pcie1_rc { + reset-gpios = <&exp1 2 GPIO_ACTIVE_HIGH>; + phys = <&serdes0_pcie_link>; + phy-names = "pcie-phy"; + num-lanes = <2>; +}; + +&pcie1_ep { + phys = <&serdes0_pcie_link>; + phy-names = "pcie-phy"; + num-lanes = <2>; + status = "disabled"; +};
Signature · 1 line
2.17.1
Re: [PATCH v2 7/7] arm64: dts: ti: k3-j7200-common-proc-board: Enable PCIe
Quoted 6 lines · Kishon Vijay Abraham I
x2 lane PCIe slot in the common processor board is enabled and connected to j7200 SOM. Add PCIe DT node in common processor board to reflect the same.
Signed-off-by Kishon Vijay Abraham I <[email protected]>---
Quoted 34 lines
.../boot/dts/ti/k3-j7200-common-proc-board.dts | 15 +++++++++++++++ 1 file changed, 15 insertions(+)arch/arm64/boot/dts/ti/k3-j7200-common-proc-board.dts +15
-0@@ -6,6 +6,7 @@ /dts-v1/; #include "k3-j7200-som-p0.dtsi" +#include <dt-bindings/gpio/gpio.h> #include <dt-bindings/net/ti-dp83867.h> #include <dt-bindings/mux/ti-serdes.h> #include <dt-bindings/phy/phy.h>@@ -236,3 +237,17 @@ resets = <&serdes_wiz0 3>; }; }; + +&pcie1_rc { + reset-gpios = <&exp1 2 GPIO_ACTIVE_HIGH>; + phys = <&serdes0_pcie_link>; + phy-names = "pcie-phy"; + num-lanes = <2>; +}; + +&pcie1_ep { + phys = <&serdes0_pcie_link>; + phy-names = "pcie-phy"; + num-lanes = <2>; + status = "disabled"; +};