RK3568 PCIe V3 support
Subsystems (5)
v2 cover RK3568 PCIe V3 support
From: Frank Wunderlich <[email protected]>
This series adds Rockchip PCIe V3 support found on rk3568 SOC.
It is based on "Enable rk356x PCIe controller" series of Peter Geis
v8: https://patchwork.kernel.org/project/linux-rockchip/list/?series=634925
Compared to PCIeV2 which uses the Naneng combphy, pciev3 uses a dedicated pci-phy.
This Version is still an RFC/RFT because i cannot only test PCIe-slot on R2Pro as the other is a M.2 Key-E where i don't have any Hardware.
last 3 Patches show a replacement for bifurcation setting to make it more useful for vendor-indepent lane-mapping.
Frank Wunderlich (11):
dt-bindings: phy: rockchip: add PCIe v3 phy
dt-bindings: soc: grf: add pcie30-{phy,pipe}-grf
dt-bindings: phy: rockchip: add PCIe v3 constants
phy: rockchip: Support PCIe v3
dt-bindings: pci: add bifurcation option to Rockchip DesignWare
binding
PCI: rockchip-dwc: add PCIe bifurcation
arm64: dts: rockchip: rk3568: Add PCIe v3 nodes
arm64: dts: rockchip: Add PCIe v3 nodes to BPI-R2-Pro
dt-bindings: pci: add lane-map to rockchip PCIe binding
PCI: rockchip: add a lane-map to rockchip pcie driver
arm64: dts: rockchip: add basic lane-map and drop bifurcation from
r2pro
.../bindings/pci/rockchip-dw-pcie.yaml | 3 + .../bindings/phy/rockchip,pcie3-phy.yaml | 84 ++++++ .../devicetree/bindings/soc/rockchip/grf.yaml | 3 + .../boot/dts/rockchip/rk3568-bpi-r2-pro.dts | 79 +++++ arch/arm64/boot/dts/rockchip/rk3568.dtsi | 122 ++++++++ drivers/pci/controller/dwc/pcie-dw-rockchip.c | 22 ++ drivers/phy/rockchip/Kconfig | 9 + drivers/phy/rockchip/Makefile | 1 + .../phy/rockchip/phy-rockchip-snps-pcie3.c | 278 ++++++++++++++++++ include/dt-bindings/phy/phy-rockchip-pcie3.h | 21 ++ include/linux/phy/pcie.h | 12 + 11 files changed, 634 insertions(+) create mode 100644 Documentation/devicetree/bindings/phy/rockchip,pcie3-phy.yaml create mode 100644 drivers/phy/rockchip/phy-rockchip-snps-pcie3.c create mode 100644 include/dt-bindings/phy/phy-rockchip-pcie3.h create mode 100644 include/linux/phy/pcie.h
Signature · 1 line
2.25.1
PATCH v2 1/11 dt-bindings: phy: rockchip: add PCIe v3 phy
From: Frank Wunderlich <[email protected]>
Add a new binding file for Rockchip PCIe v3 phy driver.
---
v2:
dt-bindings: rename yaml for PCIe v3 rockchip-pcie3-phy.yaml => rockchip,pcie3-phy.yaml
changes in pcie3 phy yaml
- change clock names to ordered const list
- extend pcie30-phymode description
- add phy-cells to required properties
- drop unevaluatedProperties
- example with 1 clock each line
- use default property instead of text describing it
- update license
--- .../bindings/phy/rockchip,pcie3-phy.yaml | 84 +++++++++++++++++++ 1 file changed, 84 insertions(+) create mode 100644 Documentation/devicetree/bindings/phy/rockchip,pcie3-phy.yaml
Documentation/devicetree/bindings/phy/rockchip,pcie3-phy.yaml new file +84 -0
@@ -0,0 +1,84 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/phy/rockchip,pcie3-phy.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Rockchip PCIe v3 phy + +maintainers: + - Heiko Stuebner <[email protected]> + +properties: + compatible: + enum: + - rockchip,rk3568-pcie3-phy + - rockchip,rk3588-pcie3-phy + + reg: + maxItems: 1 + + clocks: + minItems: 1 + maxItems: 3 + + clock-names: + items: + - const: "refclk_m" + - const: "refclk_n" + - const: "pclk" + + minItems: 1 + + "#phy-cells": + const: 0 + + resets: + maxItems: 1 + + reset-names: + const: phy + + rockchip,phy-grf: + $ref: /schemas/types.yaml#/definitions/phandle + description: phandle to the syscon managing the phy "general register files" + + rockchip,pipe-grf: + $ref: /schemas/types.yaml#/definitions/phandle + description: phandle to the syscon managing the pipe "general register files" + + rockchip,pcie30-phymode: + $ref: '/schemas/types.yaml#/definitions/uint32' + description: | + set the phy-mode for enabling bifurcation + bit0: bifurcation for port 0 + bit1: bifurcation for port 1 + bit2: aggregation + constants are defined in the dt-bindings/phy/phy-rockchip-pcie3.h + minimum: 0x0 + maximum: 0x4 + default: 0x4 + +required: + - compatible + - reg + - rockchip,phy-grf + - "#phy-cells" + +additionalProperties: false + +examples: + - | + #include <dt-bindings/clock/rk3568-cru.h> + pcie30phy: phy@fe8c0000 { + compatible = "rockchip,rk3568-pcie3-phy"; + reg = <0x0 0xfe8c0000 0x0 0x20000>; + #phy-cells = <0>; + clocks = <&pmucru CLK_PCIE30PHY_REF_M>, + <&pmucru CLK_PCIE30PHY_REF_N>, + <&cru PCLK_PCIE30PHY>; + clock-names = "refclk_m", "refclk_n", "pclk"; + resets = <&cru SRST_PCIE30PHY>; + reset-names = "phy"; + rockchip,phy-grf = <&pcie30_phy_grf>; + };
Signature · 1 line
2.25.1
PATCH v2 2/11 dt-bindings: soc: grf: add pcie30-{phy,pipe}-grf
In reply to Frank WunderlichFrom: Frank Wunderlich <[email protected]>
Add compatibles for PCIe v3 General Register Files.
---
changes in v2:
- add soc-part to pcie3-phy-grf
--- Documentation/devicetree/bindings/soc/rockchip/grf.yaml | 3 +++ 1 file changed, 3 insertions(+)
Documentation/devicetree/bindings/soc/rockchip/grf.yaml +3 -0
@@ -14,6 +14,9 @@ properties: oneOf: - items: - enum: + - rockchip,rk3568-pcie3-phy-grf + - rockchip,rk3588-pcie3-phy-grf + - rockchip,rk3588-pcie3-pipe-grf - rockchip,rk3288-sgrf - rockchip,rk3566-pipe-grf - rockchip,rk3568-usb2phy-grf
Signature · 1 line
2.25.1
PATCH v2 3/11 dt-bindings: phy: rockchip: add PCIe v3 constants
In reply to Frank WunderlichFrom: Frank Wunderlich <[email protected]>
Add constants that can be used in devicetree and driver for PCIe v3 phy.
---
v2:
- new patch because splitting out this file
- rename file from snps to rockchip
--- include/dt-bindings/phy/phy-rockchip-pcie3.h | 21 ++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 include/dt-bindings/phy/phy-rockchip-pcie3.h
include/dt-bindings/phy/phy-rockchip-pcie3.h new file +21 -0
@@ -0,0 +1,21 @@ +/* SPDX-License-Identifier: (GPL-2.0+ OR MIT) */ +/* +* Copyright (c) 2021 Rockchip Electronics Co., Ltd. +*/ + +#ifndef _DT_BINDINGS_PHY_ROCKCHIP_PCIE3 +#define _DT_BINDINGS_PHY_ROCKCHIP_PCIE3 + +/* +* pcie30_phy_mode[2:0] +* bit2: aggregation +* bit1: bifurcation for port 1 +* bit0: bifurcation for port 0 +*/ +#define PHY_MODE_PCIE_AGGREGATION 4/* PCIe3x4 */ +#define PHY_MODE_PCIE_NANBNB 0/* P1:PCIe3x2 + P0:PCIe3x2 */ +#define PHY_MODE_PCIE_NANBBI 1/* P1:PCIe3x2 + P0:PCIe3x1*2 */ +#define PHY_MODE_PCIE_NABINB 2/* P1:PCIe3x1*2 + P0:PCIe3x2 */ +#define PHY_MODE_PCIE_NABIBI 3/* P1:PCIe3x1*2 + P0:PCIe3x1*2 */ + +#endif /* _DT_BINDINGS_PHY_ROCKCHIP_PCIE3 */
Signature · 1 line
2.25.1
PATCH v2 6/11 PCI: rockchip-dwc: add PCIe bifurcation
In reply to Frank WunderlichFrom: Frank Wunderlich <[email protected]>
PCIe Lanes can be split to 2 slots with bifurcation. Add support for this in existing PCIe driver that can be enabled by new "bifurcation" devicetree property.
---
changes in v2:
- change rockchip,bifurcation to vendor unspecific bifurcation
--- drivers/pci/controller/dwc/pcie-dw-rockchip.c | 11 +++++++++++ 1 file changed, 11 insertions(+)
drivers/pci/controller/dwc/pcie-dw-rockchip.c +11 -0
@@ -20,6 +20,7 @@#include <linux/platform_device.h> #include <linux/regmap.h> #include <linux/reset.h> +#include <linux/phy/pcie.h> #include "pcie-designware.h"
@@ -58,6 +59,7 @@ struct rockchip_pcie {struct gpio_desc *rst_gpio;struct regulator *vpcie3v3;struct irq_domain *irq_domain; +bool bifurcation; }; static int rockchip_pcie_readl_apb(struct rockchip_pcie *rockchip,
@@ -259,6 +261,12 @@ static int rockchip_pcie_phy_init(struct rockchip_pcie *rockchip)return dev_err_probe (dev,PTR_ERR (rockchip->phy),"missing PHY\n" ); +if (rockchip->bifurcation) { + ret =phy_set_mode_ext (rockchip->phy,PHY_MODE_PCIE ,PHY_MODE_PCIE_BIFURCATION ); +if (ret) +return ret; + } + ret =phy_init (rockchip->phy);if (ret <0 )return ret;
@@ -319,6 +327,9 @@ static int rockchip_pcie_probe(struct platform_device *pdev) } } +if (device_property_read_bool (dev,"bifurcation" )) + rockchip->bifurcation = true; + ret =rockchip_pcie_phy_init (rockchip);if (ret) goto disable_regulator;
Signature · 1 line
2.25.1
PATCH v2 7/11 arm64: dts: rockchip: rk3568: Add PCIe v3 nodes
In reply to Frank WunderlichFrom: Frank Wunderlich <[email protected]>
Add nodes to rk356x devicetree to support PCIe v3.
---
changes in v2:
- change to compatible with soc-part
- change rockchip,bifurcation to vendor unspecific bifurcation
--- arch/arm64/boot/dts/rockchip/rk3568.dtsi | 122 +++++++++++++++++++++++ 1 file changed, 122 insertions(+)
arch/arm64/boot/dts/rockchip/rk3568.dtsi +122 -0
@@ -42,6 +42,128 @@ qos_sata0: qos@fe190200 { reg = <0x0 0xfe190200 0x0 0x20>; }; + pcie30_phy_grf: syscon@fdcb8000 { + compatible = "rockchip,rk3568-pcie3-phy-grf", "syscon"; + reg = <0x0 0xfdcb8000 0x0 0x10000>; + }; + + pcie30phy: phy@fe8c0000 { + compatible = "rockchip,rk3568-pcie3-phy"; + reg = <0x0 0xfe8c0000 0x0 0x20000>; + #phy-cells = <0>; + clocks = <&pmucru CLK_PCIE30PHY_REF_M>, <&pmucru CLK_PCIE30PHY_REF_N>, + <&cru PCLK_PCIE30PHY>; + clock-names = "refclk_m", "refclk_n", "pclk"; + resets = <&cru SRST_PCIE30PHY>; + reset-names = "phy"; + rockchip,phy-grf = <&pcie30_phy_grf>; + status = "disabled"; + }; + + pcie3x1: pcie@fe270000 { + compatible = "rockchip,rk3568-pcie"; + #address-cells = <3>; + #size-cells = <2>; + bus-range = <0x10 0x1f>; + clocks = <&cru ACLK_PCIE30X1_MST>, <&cru ACLK_PCIE30X1_SLV>, + <&cru ACLK_PCIE30X1_DBI>, <&cru PCLK_PCIE30X1>, + <&cru CLK_PCIE30X1_AUX_NDFT>; + clock-names = "aclk_mst", "aclk_slv", + "aclk_dbi", "pclk", "aux"; + device_type = "pci"; + interrupts = <GIC_SPI 160 IRQ_TYPE_LEVEL_HIGH>, + <GIC_SPI 159 IRQ_TYPE_LEVEL_HIGH>, + <GIC_SPI 158 IRQ_TYPE_LEVEL_HIGH>, + <GIC_SPI 157 IRQ_TYPE_LEVEL_HIGH>, + <GIC_SPI 156 IRQ_TYPE_LEVEL_HIGH>; + interrupt-names = "sys", "pmc", "msg", "legacy", "err"; + #interrupt-cells = <1>; + interrupt-map-mask = <0 0 0 7>; + interrupt-map = <0 0 0 1 &pcie3x1_intc 0>, + <0 0 0 2 &pcie3x1_intc 1>, + <0 0 0 3 &pcie3x1_intc 2>, + <0 0 0 4 &pcie3x1_intc 3>; + linux,pci-domain = <1>; + num-ib-windows = <6>; + num-ob-windows = <2>; + max-link-speed = <3>; + msi-map = <0x1000 &gic 0x1000 0x1000>; + num-lanes = <1>; + phys = <&pcie30phy>; + phy-names = "pcie-phy"; + power-domains = <&power RK3568_PD_PIPE>; + reg = <0x3 0xc0400000 0x0 0x00400000>, + <0x0 0xfe270000 0x0 0x00010000>, + <0x3 0x40000000 0x0 0x01000000>; + ranges = <0x01000000 0x0 0x01000000 0x3 0x41000000 0x0 0x00100000>, + <0x02000000 0x0 0x02000000 0x3 0x41100000 0x0 0x3ef00000>; + reg-names = "dbi", "apb", "config"; + resets = <&cru SRST_PCIE30X1_POWERUP>; + reset-names = "pipe"; + /* bifurcation; lane1 when using 1+1 */ + status = "disabled"; + + pcie3x1_intc: legacy-interrupt-controller { + interrupt-controller; + #address-cells = <0>; + #interrupt-cells = <1>; + interrupt-parent = <&gic>; + interrupts = <GIC_SPI 157 IRQ_TYPE_EDGE_RISING>; + }; + }; + + pcie3x2: pcie@fe280000 { + compatible = "rockchip,rk3568-pcie"; + #address-cells = <3>; + #size-cells = <2>; + bus-range = <0x20 0x2f>; + clocks = <&cru ACLK_PCIE30X2_MST>, <&cru ACLK_PCIE30X2_SLV>, + <&cru ACLK_PCIE30X2_DBI>, <&cru PCLK_PCIE30X2>, + <&cru CLK_PCIE30X2_AUX_NDFT>; + clock-names = "aclk_mst", "aclk_slv", + "aclk_dbi", "pclk", "aux"; + device_type = "pci"; + interrupts = <GIC_SPI 165 IRQ_TYPE_LEVEL_HIGH>, + <GIC_SPI 164 IRQ_TYPE_LEVEL_HIGH>, + <GIC_SPI 163 IRQ_TYPE_LEVEL_HIGH>, + <GIC_SPI 162 IRQ_TYPE_LEVEL_HIGH>, + <GIC_SPI 161 IRQ_TYPE_LEVEL_HIGH>; + interrupt-names = "sys", "pmc", "msg", "legacy", "err"; + #interrupt-cells = <1>; + interrupt-map-mask = <0 0 0 7>; + interrupt-map = <0 0 0 1 &pcie3x2_intc 0>, + <0 0 0 2 &pcie3x2_intc 1>, + <0 0 0 3 &pcie3x2_intc 2>, + <0 0 0 4 &pcie3x2_intc 3>; + linux,pci-domain = <2>; + num-ib-windows = <6>; + num-ob-windows = <2>; + max-link-speed = <3>; + msi-map = <0x2000 &gic 0x2000 0x1000>; + num-lanes = <2>; + phys = <&pcie30phy>; + phy-names = "pcie-phy"; + power-domains = <&power RK3568_PD_PIPE>; + reg = <0x3 0xc0800000 0x0 0x00400000>, + <0x0 0xfe280000 0x0 0x00010000>, + <0x3 0x80000000 0x0 0x01000000>; + ranges = <0x01000000 0x0 0x01000000 0x3 0x81000000 0x0 0x00100000>, + <0x02000000 0x0 0x02000000 0x3 0x81100000 0x0 0x3ef00000>; + reg-names = "dbi", "apb", "config"; + resets = <&cru SRST_PCIE30X2_POWERUP>; + reset-names = "pipe"; + /* bifurcation; lane0 when using 1+1 */ + status = "disabled"; + + pcie3x2_intc: legacy-interrupt-controller { + interrupt-controller; + #address-cells = <0>; + #interrupt-cells = <1>; + interrupt-parent = <&gic>; + interrupts = <GIC_SPI 162 IRQ_TYPE_EDGE_RISING>; + }; + }; + gmac0: ethernet@fe2a0000 { compatible = "rockchip,rk3568-gmac", "snps,dwmac-4.20a"; reg = <0x0 0xfe2a0000 0x0 0x10000>;
Signature · 1 line
2.25.1
PATCH v2 10/11 PCI: rockchip: add a lane-map to rockchip pcie driver
In reply to Frank WunderlichFrom: Frank Wunderlich <[email protected]>
Add a basic lane-map to define which PCIe lanes should be used with this controller.
Rockchip driver uses this for bifurcation (true/false) based on lanes should be splitted across controllers or not.
On rk3568 there are 2 PCIe Controllers which share PCIe lanes.
pcie3x1: pcie@fe270000 //lane1 when using 1+1
pcie3x2: pcie@fe280000 //lane0 when using 1+1
This ends up in one Controller (pcie3x1) uses lane-map = <0 1>; and the other lane-map = <1 0>; (pcie3x2)
This means there are 2 lanes (count of numbers), one (by position) is mapped to the first controller, the other one is used on the other controller.
In this driver the lane-map is simply converted to the bifurcation bool instead of direct mapping a specific lane to a controller.
---
v2:
- new patch
--- drivers/pci/controller/dwc/pcie-dw-rockchip.c | 15 +++++++++++++-- 1 file changed, 13 insertions(+), 2 deletions(-)
drivers/pci/controller/dwc/pcie-dw-rockchip.c +13 -2
@@ -60,6 +60,7 @@ struct rockchip_pcie {struct regulator *vpcie3v3;struct irq_domain *irq_domain;bool bifurcation; +u32 lane_map[2 ]; }; static int rockchip_pcie_readl_apb(struct rockchip_pcie *rockchip,
@@ -293,8 +294,10 @@ static int rockchip_pcie_probe(struct platform_device *pdev) {struct device *dev = &pdev->dev;struct rockchip_pcie *rockchip; +unsigned int lanecnt =0 ;struct pcie_port *pp;int ret; +int len; rockchip =devm_kzalloc (dev,sizeof (*rockchip),GFP_KERNEL );if (!rockchip)
@@ -327,8 +330,16 @@ static int rockchip_pcie_probe(struct platform_device *pdev) } } -if (device_property_read_bool (dev,"bifurcation" )) - rockchip->bifurcation = true; + len =of_property_read_variable_u32_array (dev->of_node,"lane-map" , rockchip->lane_map, +2 ,ARRAY_SIZE (rockchip->lane_map)); + +for (int i =0 ; i < len; i++) +if (rockchip->lane_map[i]) + lanecnt++; + + rockchip->bifurcation = ((lanecnt >0 ) && (lanecnt != len)); + +dev_info (dev,"bifurcation: %s\n" , rockchip->bifurcation ?"true" :"false" ); ret =rockchip_pcie_phy_init (rockchip);if (ret)
Signature · 1 line
2.25.1
PATCH v2 9/11 dt-bindings: pci: add lane-map to rockchip PCIe binding
In reply to Frank WunderlichFrom: Frank Wunderlich <[email protected]>
Create new property for (rockchip) PCIe controller binding to define lane mapping.
Rockchip driver uses this for bifurcation (true/false) based on lanes should be splitted across controllers or not.
On rk3568 there are 2 PCIe Controllers which share 2 PCIe lanes.
pcie3x1: pcie@fe270000 //lane1 when using 1+1
pcie3x2: pcie@fe280000 //lane0 when using 1+1
This ends up in one Controller (pcie3x1) uses lane-map = <0 1>; and the other lane-map = <1 0>; (pcie3x2)
This means there are 2 lanes (count of numbers), one (by position) is mapped to the first controller, the other one is used on the other controller.
In rockchip PCIe driver the lane-map is simply converted to the bifurcation bool instead of direct mapping a specific lane to a controller.
There is not yet any slot mapping below one controller. But for binding this may be possible like:
lane-map = <1 2 3 3 4 4 4 4>;
| | | ...
lane0 | |
lane1 |
lane2on a 8-lane phy.
This can map lane0 to port1 (number used at this position), lane1 to port2, lanes 2+3 to port 3 and lanes 4,5,6,7 to port 4.
---
v2:
- new patch
--- Documentation/devicetree/bindings/pci/rockchip-dw-pcie.yaml | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
Documentation/devicetree/bindings/pci/rockchip-dw-pcie.yaml +3 -2
@@ -52,6 +52,8 @@ properties: - const: pclk - const: aux + lane-map: true + msi-map: true num-lanes: true
@@ -74,8 +76,6 @@ properties: reset-names: const: pipe - bifurcation: true - vpcie3v3-supply: true required:
@@ -115,6 +115,7 @@ examples: "aclk_dbi", "pclk", "aux"; device_type = "pci"; + lane-map = <0 1>; linux,pci-domain = <2>; max-link-speed = <2>; msi-map = <0x2000 &its 0x2000 0x1000>;
Signature · 1 line
2.25.1
PATCH v2 11/11 arm64: dts: rockchip: add basic lane-map and drop bifurcation from r2pro
In reply to Frank WunderlichFrom: Frank Wunderlich <[email protected]>
Change DTS-Property from bifurcation to the new lane-map. The lane-map is more generic but PCIe controller driver converts it back to the bifurcation-bool.
---
changes in v2:
- new patch
--- arch/arm64/boot/dts/rockchip/rk3568-bpi-r2-pro.dts | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
arch/arm64/boot/dts/rockchip/rk3568-bpi-r2-pro.dts +2 -2
@@ -477,14 +477,14 @@ &pcie30phy { }; &pcie3x1 { - bifurcation; + lane-map = <0 1>; reset-gpios = <&gpio3 RK_PA1 GPIO_ACTIVE_HIGH>; vpcie3v3-supply = <&vcc3v3_ngff>; status = "okay"; }; &pcie3x2 { - bifurcation; + lane-map = <1 0>; reset-gpios = <&gpio2 RK_PD6 GPIO_ACTIVE_HIGH>; vpcie3v3-supply = <&vcc3v3_minipcie>; status = "okay";
Signature · 1 line
2.25.1
PATCH v2 5/11 dt-bindings: pci: add bifurcation option to Rockchip DesignWare binding
In reply to Frank WunderlichFrom: Frank Wunderlich <[email protected]>
Add bifurcation property for splitting PCIe lanes.
--- Documentation/devicetree/bindings/pci/rockchip-dw-pcie.yaml | 2 ++ 1 file changed, 2 insertions(+)
Documentation/devicetree/bindings/pci/rockchip-dw-pcie.yaml +2 -0
@@ -74,6 +74,8 @@ properties: reset-names: const: pipe + bifurcation: true + vpcie3v3-supply: true required:
Signature · 1 line
2.25.1
PATCH v2 8/11 arm64: dts: rockchip: Add PCIe v3 nodes to BPI-R2-Pro
In reply to Frank WunderlichFrom: Frank Wunderlich <[email protected]>
Add Nodes to Bananapi-R2-Pro board to support PCIe v3 and set PCIe related regulators to always on.
---
changes in v2:
- underscores in nodenames
- rockchip,bifurcation to vendor unspecific bifurcation
- fix trailing space
--- .../boot/dts/rockchip/rk3568-bpi-r2-pro.dts | 79 +++++++++++++++++++ 1 file changed, 79 insertions(+)
arch/arm64/boot/dts/rockchip/rk3568-bpi-r2-pro.dts +79 -0
@@ -74,6 +74,67 @@ vcc5v0_sys: vcc5v0-sys { vin-supply = <&dc_12v>; }; + pcie30_avdd0v9: pcie30-avdd0v9 { + compatible = "regulator-fixed"; + regulator-name = "pcie30_avdd0v9"; + regulator-always-on; + regulator-boot-on; + regulator-min-microvolt = <900000>; + regulator-max-microvolt = <900000>; + vin-supply = <&vcc3v3_sys>; + }; + + pcie30_avdd1v8: pcie30-avdd1v8 { + compatible = "regulator-fixed"; + regulator-name = "pcie30_avdd1v8"; + regulator-always-on; + regulator-boot-on; + regulator-min-microvolt = <1800000>; + regulator-max-microvolt = <1800000>; + vin-supply = <&vcc3v3_sys>; + }; + + /* pi6c pcie clock generator feeds both ports */ + vcc3v3_pi6c_05: vcc3v3-pi6c-05-regulator { + compatible = "regulator-fixed"; + regulator-name = "vcc3v3_pcie"; + regulator-min-microvolt = <3300000>; + regulator-max-microvolt = <3300000>; + regulator-always-on; + regulator-boot-on; + enable-active-high; + gpios = <&gpio0 RK_PD4 GPIO_ACTIVE_HIGH>; + startup-delay-us = <20000>; + vin-supply = <&vcc5v0_sys>; + }; + + /* actually fed by vcc3v3_sys, dependent on pi6c clock generator */ + vcc3v3_minipcie: vcc3v3-minipcie-regulator { + compatible = "regulator-fixed"; + regulator-name = "vcc3v3_minipcie"; + regulator-min-microvolt = <3300000>; + regulator-max-microvolt = <3300000>; + regulator-always-on; + regulator-boot-on; + enable-active-high; + gpio = <&gpio0 RK_PC6 GPIO_ACTIVE_HIGH>; + startup-delay-us = <5000>; + vin-supply = <&vcc3v3_pi6c_05>; + }; + + /* actually fed by vcc3v3_sys, dependent on pi6c clock generator */ + vcc3v3_ngff: vcc3v3-ngff-regulator { + compatible = "regulator-fixed"; + regulator-name = "vcc3v3_ngff"; + regulator-min-microvolt = <3300000>; + regulator-max-microvolt = <3300000>; + regulator-boot-on; + enable-active-high; + gpio = <&gpio4 RK_PC1 GPIO_ACTIVE_HIGH>; + startup-delay-us = <5000>; + vin-supply = <&vcc3v3_pi6c_05>; + }; + vbus: vbus { compatible = "regulator-fixed"; regulator-name = "vbus";
@@ -411,6 +472,24 @@ rgmii_phy1: ethernet-phy@0 { }; }; +&pcie30phy { + status = "okay"; +}; + +&pcie3x1 { + bifurcation; + reset-gpios = <&gpio3 RK_PA1 GPIO_ACTIVE_HIGH>; + vpcie3v3-supply = <&vcc3v3_ngff>; + status = "okay"; +}; + +&pcie3x2 { + bifurcation; + reset-gpios = <&gpio2 RK_PD6 GPIO_ACTIVE_HIGH>; + vpcie3v3-supply = <&vcc3v3_minipcie>; + status = "okay"; +}; + &pinctrl { leds { blue_led_pin: blue-led-pin {
Signature · 1 line
2.25.1
PATCH v2 4/11 phy: rockchip: Support PCIe v3
In reply to Frank WunderlichFrom: Frank Wunderlich <[email protected]>
RK3568 supports PCIe v3 using not Combphy like PCIe v2 on rk3566. It use a dedicated PCIe-phy. Add support for this.
---
changes in v2:
- move dt-bindings header into separate patch
- use BIT-macro
- make constants better readable
- use dev_err instead of pr_*
- change dt-binding include due to renaming (phy-snps-pcie3.h => phy-rockchip-pcie3.h)
- use exclusive variant of devm_reset_control_get{,_exclusive}
- fix semicolon.cocci warnings reported by kernel test robot <[email protected]>
---
driver was taken from linux 5.10 based on in
https://github.com/JeffyCN/mirrors
which now has disappeared
--- drivers/phy/rockchip/Kconfig | 9 + drivers/phy/rockchip/Makefile | 1 + .../phy/rockchip/phy-rockchip-snps-pcie3.c | 278 ++++++++++++++++++ include/linux/phy/pcie.h | 12 + 4 files changed, 300 insertions(+) create mode 100644 drivers/phy/rockchip/phy-rockchip-snps-pcie3.c create mode 100644 include/linux/phy/pcie.h
drivers/phy/rockchip/Kconfig +9 -0
@@ -83,6 +83,15 @@ config PHY_ROCKCHIP_PCIE help Enable this to support the Rockchip PCIe PHY. +config PHY_ROCKCHIP_SNPS_PCIE3 + tristate "Rockchip Snps PCIe3 PHY Driver" + depends on (ARCH_ROCKCHIP && OF) || COMPILE_TEST + depends on HAS_IOMEM + select GENERIC_PHY + select MFD_SYSCON + help + Enable this to support the Rockchip snps PCIe3 PHY. + config PHY_ROCKCHIP_TYPEC tristate "Rockchip TYPEC PHY Driver" depends on OF && (ARCH_ROCKCHIP || COMPILE_TEST)
drivers/phy/rockchip/Makefile +1 -0
@@ -8,5 +8,6 @@ obj-$(CONFIG_PHY_ROCKCHIP_INNO_HDMI) += phy-rockchip-inno-hdmi.o obj-$(CONFIG_PHY_ROCKCHIP_INNO_USB2) += phy-rockchip-inno-usb2.o obj-$(CONFIG_PHY_ROCKCHIP_NANENG_COMBO_PHY) += phy-rockchip-naneng-combphy.o obj-$(CONFIG_PHY_ROCKCHIP_PCIE) += phy-rockchip-pcie.o +obj-$(CONFIG_PHY_ROCKCHIP_SNPS_PCIE3) += phy-rockchip-snps-pcie3.o obj-$(CONFIG_PHY_ROCKCHIP_TYPEC) += phy-rockchip-typec.o obj-$(CONFIG_PHY_ROCKCHIP_USB) += phy-rockchip-usb.o
drivers/phy/rockchip/phy-rockchip-snps-pcie3.c new file +278 -0
278 lines not on this page · raw message
include/linux/phy/pcie.h new file +12 -0
@@ -0,0 +1,12 @@ +/* SPDX-License-Identifier: GPL-2.0 */ +/* +* Copyright (c) 2021 Rockchip Electronics Co., Ltd. +*/ +#ifndef __PHY_PCIE_H +#define __PHY_PCIE_H + +#define PHY_MODE_PCIE_RC 20 +#define PHY_MODE_PCIE_EP 21 +#define PHY_MODE_PCIE_BIFURCATION 22 + +#endif
Signature · 1 line
2.25.1
Quoted 16 lines · Frank Wunderlich
From: Frank Wunderlich <[email protected]>
This series adds Rockchip PCIe V3 support found on rk3568 SOC.
It is based on "Enable rk356x PCIe controller" series of Peter Geis
v8: https://patchwork.kernel.org/project/linux-rockchip/list/?series=634925Compared to PCIeV2 which uses the Naneng combphy, pciev3 uses a dedicated pci-phy.
This Version is still an RFC/RFT because i cannot only test PCIe-slot on R2Pro as the other is a M.2 Key-E where i don't have any Hardware.
last 3 Patches show a replacement for bifurcation setting to make it more useful for vendor-indepent lane-mapping.
Quoted 14 lines
Frank Wunderlich (11):
dt-bindings: phy: rockchip: add PCIe v3 phy
dt-bindings: soc: grf: add pcie30-{phy,pipe}-grf
dt-bindings: phy: rockchip: add PCIe v3 constants
phy: rockchip: Support PCIe v3
dt-bindings: pci: add bifurcation option to Rockchip DesignWare
binding
PCI: rockchip-dwc: add PCIe bifurcation
arm64: dts: rockchip: rk3568: Add PCIe v3 nodes
arm64: dts: rockchip: Add PCIe v3 nodes to BPI-R2-Pro
dt-bindings: pci: add lane-map to rockchip PCIe binding
PCI: rockchip: add a lane-map to rockchip pcie driver
arm64: dts: rockchip: add basic lane-map and drop bifurcation from
r2pro
Don't just make up new prefixes; copy what's been done in the past.
PCI: rockchip-dwc: add PCIe bifurcation
PCI: rockchip: add a lane-map to rockchip pcie driver
I think we decided [1] to use "rockchip-dwc" for this driver to distinguish it from the pcie-rockchip-host.c driver.
So both of these should use "PCI: rockchip-dwc:" as the prefix.
At least for the drivers/pci/ patches, capitalize the first word of the subject, i.e., "Add PCIe bifurcation" and "Add lane-map ..." I don't know the dt-bindings convention (I would use "git log --oneline" to find out).
s/pcie/PCIe/ in subjects, commit logs, comments, etc.
Wrap commit logs to fill 75 columns and add blank lines between paragraphs. Readers should not need to wonder "oh, the previous line was shorter than usual; is this one a new paragraph?"
[1] https://lore.kernel.org/r/20210624180723.GA3543267@bjorn-Precision-5520
Quoted 25 lines
.../bindings/pci/rockchip-dw-pcie.yaml | 3 + .../bindings/phy/rockchip,pcie3-phy.yaml | 84 ++++++ .../devicetree/bindings/soc/rockchip/grf.yaml | 3 + .../boot/dts/rockchip/rk3568-bpi-r2-pro.dts | 79 +++++ arch/arm64/boot/dts/rockchip/rk3568.dtsi | 122 ++++++++ drivers/pci/controller/dwc/pcie-dw-rockchip.c | 22 ++ drivers/phy/rockchip/Kconfig | 9 + drivers/phy/rockchip/Makefile | 1 + .../phy/rockchip/phy-rockchip-snps-pcie3.c | 278 ++++++++++++++++++ include/dt-bindings/phy/phy-rockchip-pcie3.h | 21 ++ include/linux/phy/pcie.h | 12 + 11 files changed, 634 insertions(+) create mode 100644 Documentation/devicetree/bindings/phy/rockchip,pcie3-phy.yaml create mode 100644 drivers/phy/rockchip/phy-rockchip-snps-pcie3.c create mode 100644 include/dt-bindings/phy/phy-rockchip-pcie3.h create mode 100644 include/linux/phy/pcie.hSignature · 7 lines
2.25.1 _______________________________________________ linux-arm-kernel mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Re: [RFC/RFT v2 09/11] dt-bindings: pci: add lane-map to rockchip PCIe binding
In reply to Frank WunderlichQuoted 60 lines · Frank Wunderlich
From: Frank Wunderlich <[email protected]>
Create new property for (rockchip) PCIe controller binding to define lane mapping.
Rockchip driver uses this for bifurcation (true/false) based on lanes should be splitted across controllers or not.
On rk3568 there are 2 PCIe Controllers which share 2 PCIe lanes.
pcie3x1: pcie@fe270000 //lane1 when using 1+1
pcie3x2: pcie@fe280000 //lane0 when using 1+1This ends up in one Controller (pcie3x1) uses lane-map = <0 1>; and the other lane-map = <1 0>; (pcie3x2)
This means there are 2 lanes (count of numbers), one (by position) is mapped to the first controller, the other one is used on the other controller.
In rockchip PCIe driver the lane-map is simply converted to the bifurcation bool instead of direct mapping a specific lane to a controller.
There is not yet any slot mapping below one controller. But for binding this may be possible like:
lane-map = <1 2 3 3 4 4 4 4>; | | | ... lane0 | | lane1 | lane2on a 8-lane phy.
This can map lane0 to port1 (number used at this position), lane1 to port2, lanes 2+3 to port 3 and lanes 4,5,6,7 to port 4.
Signed-off-by Frank Wunderlich <[email protected]>---
v2:
- new patch--- Documentation/devicetree/bindings/pci/rockchip-dw-pcie.yaml | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)Documentation/devicetree/bindings/pci/rockchip-dw-pcie.yaml +2
-0@@ -52,6 +52,8 @@ properties: - const: pclk - const: aux + lane-map: true + msi-map: true num-lanes: true
Documentation/devicetree/bindings/pci/rockchip-dw-pcie.yaml properties: · line 78
Quoted 5 lines
Documentation/devicetree/bindings/pci/rockchip-dw-pcie.yaml +0
-2@@ -74,8 +76,6 @@ properties: reset-names: const: pipe - bifurcation: true -
Why are you adding "bifurcation" earlier in the series, then immediately removing it? Why not just add "lane-map" directly and never mention "bifurcation" in the DT at all?
Quoted 19 lines
Documentation/devicetree/bindings/pci/rockchip-dw-pcie.yaml +1
-0vpcie3v3-supply: true required:@@ -115,6 +115,7 @@ examples: "aclk_dbi", "pclk", "aux"; device_type = "pci"; + lane-map = <0 1>; linux,pci-domain = <2>; max-link-speed = <2>; msi-map = <0x2000 &its 0x2000 0x1000>;Signature · 7 lines
2.25.1 -- linux-phy mailing list [email protected] https://lists.infradead.org/mailman/listinfo/linux-phy
Re: [RFC/RFT v2 10/11] PCI: rockchip: add a lane-map to rockchip pcie driver
In reply to Frank WunderlichThe subject line should be "PCI: rockchip-dwc: Add ..." so there's no need to mention "rockchip" again. No need to mention "pcie driver" either, because that's obvious from the context, so just something like:
PCI: rockchip-dwc: Add lane-map support
Quoted 55 lines · Frank Wunderlich
From: Frank Wunderlich <[email protected]>
Add a basic lane-map to define which PCIe lanes should be used with this controller.
Rockchip driver uses this for bifurcation (true/false) based on lanes should be splitted across controllers or not.
On rk3568 there are 2 PCIe Controllers which share PCIe lanes.
pcie3x1: pcie@fe270000 //lane1 when using 1+1
pcie3x2: pcie@fe280000 //lane0 when using 1+1This ends up in one Controller (pcie3x1) uses lane-map = <0 1>; and the other lane-map = <1 0>; (pcie3x2)
This means there are 2 lanes (count of numbers), one (by position) is mapped to the first controller, the other one is used on the other controller.
In this driver the lane-map is simply converted to the bifurcation bool instead of direct mapping a specific lane to a controller.
Signed-off-by Frank Wunderlich <[email protected]>---
v2:
- new patch--- drivers/pci/controller/dwc/pcie-dw-rockchip.c | 15 +++++++++++++-- 1 file changed, 13 insertions(+), 2 deletions(-)drivers/pci/controller/dwc/pcie-dw-rockchip.c +3
-0@@ -60,6 +60,7 @@ struct rockchip_pcie {struct regulator *vpcie3v3;struct irq_domain *irq_domain;bool bifurcation; +u32 lane_map[2 ]; }; static int rockchip_pcie_readl_apb(struct rockchip_pcie *rockchip,@@ -293,8 +294,10 @@ static int rockchip_pcie_probe(struct platform_device *pdev) {struct device *dev = &pdev->dev;struct rockchip_pcie *rockchip; +unsigned int lanecnt =0 ;struct pcie_port *pp;int ret; +int len; rockchip =devm_kzalloc (dev,sizeof (*rockchip),GFP_KERNEL );if (!rockchip)
drivers/pci/controller/dwc/pcie-dw-rockchip.c static int rockchip_pcie_probe(struct platform_device *pdev) · line 331
Quoted 5 lines
drivers/pci/controller/dwc/pcie-dw-rockchip.c +0
-2@@ -327,8 +330,16 @@ static int rockchip_pcie_probe(struct platform_device *pdev) } } -if (device_property_read_bool (dev,"bifurcation" )) - rockchip->bifurcation = true;
Skip adding the "bifurcation" DT support completely if you can.
Quoted 21 lines
drivers/pci/controller/dwc/pcie-dw-rockchip.c +10
-0+ len =of_property_read_variable_u32_array (dev->of_node,"lane-map" , rockchip->lane_map, +2 ,ARRAY_SIZE (rockchip->lane_map)); + +for (int i =0 ; i < len; i++) +if (rockchip->lane_map[i]) + lanecnt++; + + rockchip->bifurcation = ((lanecnt >0 ) && (lanecnt != len)); + +dev_info (dev,"bifurcation: %s\n" , rockchip->bifurcation ?"true" :"false" ); ret =rockchip_pcie_phy_init (rockchip);if (ret)Signature · 7 lines
2.25.1 -- linux-phy mailing list [email protected] https://lists.infradead.org/mailman/listinfo/linux-phy
Aw: Re: [RFC/RFT v2 09/11] dt-bindings: pci: add lane-map to rockchip PCIe binding
In reply to Bjorn HelgaasHi,
Quoted 9 lines
Gesendet: Dienstag, 26. April 2022 um 18:04 Uhr
Von: "Bjorn Helgaas" <[email protected]>Documentation/devicetree/bindings/pci/rockchip-dw-pcie.yaml properties: · line 78
Quoted 2 lines
Documentation/devicetree/bindings/pci/rockchip-dw-pcie.yaml +0
-2- bifurcation: true -Why are you adding "bifurcation" earlier in the series, then immediately removing it? Why not just add "lane-map" directly and never mention "bifurcation" in the DT at all?
The original driver used the bifurcation property with vendor prefix which i have dropped.
In v1 there was an Idea to replace this bifurcation setting by something more generic supporting more that just true/false. So i added lane-map to start discussion if this is the right way or if i should leave the bifurcation property.
if the lane-map is right, i squash the commits before the commits should land in linux... this is one cause i tagged the series as RFC.
regards Frank
_______________________________________________
Linux-rockchip mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-rockchip
Re: [RFC/RFT v2 01/11] dt-bindings: phy: rockchip: add PCIe v3 phy
In reply to Frank WunderlichQuoted 49 lines · Frank Wunderlich
From: Frank Wunderlich <[email protected]>
Add a new binding file for Rockchip PCIe v3 phy driver.
Signed-off-by Frank Wunderlich <[email protected]>---
v2:
dt-bindings: rename yaml for PCIe v3rockchip-pcie3-phy.yaml=> rockchip,pcie3-phy.yamlchanges in pcie3 phy yaml
- change clock names to ordered const list
- extend pcie30-phymode description
- add phy-cells to required properties
- drop unevaluatedProperties
- example with 1 clock each line
- use default property instead of text describing it
- update license--- .../bindings/phy/rockchip,pcie3-phy.yaml | 84 +++++++++++++++++++ 1 file changed, 84 insertions(+) create mode 100644 Documentation/devicetree/bindings/phy/rockchip,pcie3-phy.yamlDocumentation/devicetree/bindings/phy/rockchip,pcie3-phy.yaml new file +19
-0@@ -0,0 +1,84 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/phy/rockchip,pcie3-phy.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Rockchip PCIe v3 phy + +maintainers: + - Heiko Stuebner <[email protected]> + +properties: + compatible: + enum: + - rockchip,rk3568-pcie3-phy + - rockchip,rk3588-pcie3-phy + + reg: + maxItems: 1
Documentation/devicetree/bindings/phy/rockchip,pcie3-phy.yaml line 29
Quoted 10 lines
Documentation/devicetree/bindings/phy/rockchip,pcie3-phy.yaml new file +10
-0+ + clocks: + minItems: 1 + maxItems: 3 + + clock-names: + items: + - const: "refclk_m" + - const: "refclk_n" + - const: "pclk"
Drop quotes.
Documentation/devicetree/bindings/phy/rockchip,pcie3-phy.yaml line 31
Quoted 2 lines
Documentation/devicetree/bindings/phy/rockchip,pcie3-phy.yaml new file +2
-0+ + minItems: 1
I think we agreed to skip rk3588 or make the number of clocks strict?
Quoted 10 lines
Documentation/devicetree/bindings/phy/rockchip,pcie3-phy.yaml new file +10
-0+ + "#phy-cells": + const: 0 + + resets: + maxItems: 1 + + reset-names: + const: phy +
Documentation/devicetree/bindings/phy/rockchip,pcie3-phy.yaml line 51
Quoted 10 lines
Documentation/devicetree/bindings/phy/rockchip,pcie3-phy.yaml new file +10
-0+ rockchip,phy-grf: + $ref: /schemas/types.yaml#/definitions/phandle + description: phandle to the syscon managing the phy "general register files" + + rockchip,pipe-grf: + $ref: /schemas/types.yaml#/definitions/phandle + description: phandle to the syscon managing the pipe "general register files" + + rockchip,pcie30-phymode: + $ref: '/schemas/types.yaml#/definitions/uint32'
No need for quotes. You don't use it in other places.
Documentation/devicetree/bindings/phy/rockchip,pcie3-phy.yaml line 57
Quoted 6 lines
Documentation/devicetree/bindings/phy/rockchip,pcie3-phy.yaml new file +6
-0+ description: | + set the phy-mode for enabling bifurcation + bit0: bifurcation for port 0 + bit1: bifurcation for port 1 + bit2: aggregation + constants are defined in the dt-bindings/phy/phy-rockchip-pcie3.h
Full path. It should also follow vendor,device naming convention.
Quoted 17 lines
Documentation/devicetree/bindings/phy/rockchip,pcie3-phy.yaml new file +17
-0+ minimum: 0x0 + maximum: 0x4 + default: 0x4 + +required: + - compatible + - reg + - rockchip,phy-grf + - "#phy-cells" + +additionalProperties: false + +examples: + - | + #include <dt-bindings/clock/rk3568-cru.h> + pcie30phy: phy@fe8c0000 { + compatible = "rockchip,rk3568-pcie3-phy";
Documentation/devicetree/bindings/phy/rockchip,pcie3-phy.yaml line 84
Quoted 10 lines
Documentation/devicetree/bindings/phy/rockchip,pcie3-phy.yaml new file +10
-0+ reg = <0x0 0xfe8c0000 0x0 0x20000>; + #phy-cells = <0>; + clocks = <&pmucru CLK_PCIE30PHY_REF_M>, + <&pmucru CLK_PCIE30PHY_REF_N>, + <&cru PCLK_PCIE30PHY>; + clock-names = "refclk_m", "refclk_n", "pclk"; + resets = <&cru SRST_PCIE30PHY>; + reset-names = "phy"; + rockchip,phy-grf = <&pcie30_phy_grf>; + };
Best regards,
Krzysztof
Re: [RFC/RFT v2 02/11] dt-bindings: soc: grf: add pcie30-{phy,pipe}-grf
In reply to Frank WunderlichQuoted 18 lines · Frank Wunderlich
From: Frank Wunderlich <[email protected]>
Add compatibles for PCIe v3 General Register Files.
Signed-off-by Frank Wunderlich <[email protected]>---
changes in v2:
- add soc-part to pcie3-phy-grf--- Documentation/devicetree/bindings/soc/rockchip/grf.yaml | 3 +++ 1 file changed, 3 insertions(+)Documentation/devicetree/bindings/soc/rockchip/grf.yaml +0
-0
Documentation/devicetree/bindings/soc/rockchip/grf.yaml properties: · line 19
Quoted 6 lines
Documentation/devicetree/bindings/soc/rockchip/grf.yaml +3
-0@@ -14,6 +14,9 @@ properties: oneOf: - items: - enum: + - rockchip,rk3568-pcie3-phy-grf + - rockchip,rk3588-pcie3-phy-grf + - rockchip,rk3588-pcie3-pipe-grf
Order is now messed up.
Documentation/devicetree/bindings/soc/rockchip/grf.yaml properties: · line 22
Quoted 3 lines
Documentation/devicetree/bindings/soc/rockchip/grf.yaml +0
-0- rockchip,rk3288-sgrf - rockchip,rk3566-pipe-grf - rockchip,rk3568-usb2phy-grf
Best regards,
Krzysztof
Re: [RFC/RFT v2 03/11] dt-bindings: phy: rockchip: add PCIe v3 constants
In reply to Frank WunderlichQuoted 5 lines · Frank Wunderlich
From: Frank Wunderlich <[email protected]>
Add constants that can be used in devicetree and driver for PCIe v3 phy.
Quoted 7 lines
Signed-off-by Frank Wunderlich <[email protected]>---
v2:
- new patch because splitting out this file
- rename file from snps to rockchip--- include/dt-bindings/phy/phy-rockchip-pcie3.h | 21 ++++++++++++++++++++
Naming - vendor,device.
include/dt-bindings/phy/phy-rockchip-pcie3.h line 1
Quoted 10 lines
1 file changed, 21 insertions(+) create mode 100644 include/dt-bindings/phy/phy-rockchip-pcie3.hinclude/dt-bindings/phy/phy-rockchip-pcie3.h new file +1
-0@@ -0,0 +1,21 @@ +/* SPDX-License-Identifier: (GPL-2.0+ OR MIT) */
s/MIT/BSD-2-clause/ just like bindings because it is part of it. Unless you took it from something and it is already licensed like that?
Quoted 10 lines
include/dt-bindings/phy/phy-rockchip-pcie3.h new file +10
-0+/* +* Copyright (c) 2021 Rockchip Electronics Co., Ltd. +*/ + +#ifndef _DT_BINDINGS_PHY_ROCKCHIP_PCIE3 +#define _DT_BINDINGS_PHY_ROCKCHIP_PCIE3 + +/* +* pcie30_phy_mode[2:0] +* bit2: aggregation
include/dt-bindings/phy/phy-rockchip-pcie3.h line 21
Quoted 10 lines
include/dt-bindings/phy/phy-rockchip-pcie3.h new file +10
-0+* bit1: bifurcation for port 1 +* bit0: bifurcation for port 0 +*/ +#define PHY_MODE_PCIE_AGGREGATION 4/* PCIe3x4 */ +#define PHY_MODE_PCIE_NANBNB 0/* P1:PCIe3x2 + P0:PCIe3x2 */ +#define PHY_MODE_PCIE_NANBBI 1/* P1:PCIe3x2 + P0:PCIe3x1*2 */ +#define PHY_MODE_PCIE_NABINB 2/* P1:PCIe3x1*2 + P0:PCIe3x2 */ +#define PHY_MODE_PCIE_NABIBI 3/* P1:PCIe3x1*2 + P0:PCIe3x1*2 */ + +#endif /* _DT_BINDINGS_PHY_ROCKCHIP_PCIE3 */
Best regards,
Krzysztof
Re: [RFC/RFT v2 05/11] dt-bindings: pci: add bifurcation option to Rockchip DesignWare binding
In reply to Frank WunderlichQuoted 14 lines · Frank Wunderlich
From: Frank Wunderlich <[email protected]>
Add bifurcation property for splitting PCIe lanes.
Signed-off-by Frank Wunderlich <[email protected]>--- Documentation/devicetree/bindings/pci/rockchip-dw-pcie.yaml | 2 ++ 1 file changed, 2 insertions(+)Documentation/devicetree/bindings/pci/rockchip-dw-pcie.yaml +0
-0
Documentation/devicetree/bindings/pci/rockchip-dw-pcie.yaml properties: · line 78
Quoted 5 lines
Documentation/devicetree/bindings/pci/rockchip-dw-pcie.yaml +2
-0@@ -74,6 +74,8 @@ properties: reset-names: const: pipe + bifurcation: true +
Does not look like standard property. Is it already defined somewhere? All non-standard properties need vendor, type and description.
Best regards,
Krzysztof
Signature · 3 lines
linux-phy mailing list [email protected] https://lists.infradead.org/mailman/listinfo/linux-phy
Aw: Re: [RFC/RFT v2 05/11] dt-bindings: pci: add bifurcation option to Rockchip DesignWare binding
Hi
Quoted 20 lines
Gesendet: Donnerstag, 28. April 2022 um 08:37 Uhr
Von: "Krzysztof Kozlowski" <[email protected]>Quoted 17 lines · Frank Wunderlich
From: Frank Wunderlich <[email protected]>
Add bifurcation property for splitting PCIe lanes.
Signed-off-by Frank Wunderlich <[email protected]>--- Documentation/devicetree/bindings/pci/rockchip-dw-pcie.yaml | 2 ++ 1 file changed, 2 insertions(+)Documentation/devicetree/bindings/pci/rockchip-dw-pcie.yaml +0
-0@@ -74,6 +74,8 @@ properties: reset-names: const: pipe
Quoted 5 lines
Documentation/devicetree/bindings/pci/rockchip-dw-pcie.yaml properties: · line 78
Quoted 2 lines
Documentation/devicetree/bindings/pci/rockchip-dw-pcie.yaml +2
-0+ bifurcation: true +Does not look like standard property. Is it already defined somewhere? All non-standard properties need vendor, type and description.
have removed vendor-prefix from v1>v2 based on suggestion this can be useful for other vendors too.
but last 3 patches of this series replacing bifurcation property (which is only bool) by the more useful lane-map (left alone for discussion, will be squashed if the right way is found).
i guess same here, description+type needed, but how to describe an array of int in yaml? do you know any examples?
regards Frank
Signature · 3 lines
linux-phy mailing list [email protected] https://lists.infradead.org/mailman/listinfo/linux-phy
Re: Aw: Re: [RFC/RFT v2 05/11] dt-bindings: pci: add bifurcation option to Rockchip DesignWare binding
Quoted 2 lines · Frank Wunderlich
i guess same here, description+type needed, but how to describe an array of int in yaml? do you know any examples?
https://elixir.bootlin.com/linux/v5.17-rc4/source/Documentation/devicetree/bindings/arm/l2c2x0.yaml#L74
https://elixir.bootlin.com/linux/latest/source/Documentation/devicetree/bindings/display/msm/dsi-controller-main.yaml#L101
Best regards,
Krzysztof
Signature · 3 lines
linux-phy mailing list [email protected] https://lists.infradead.org/mailman/listinfo/linux-phy
Re: [RFC/RFT v2 04/11] phy: rockchip: Support PCIe v3
In reply to Frank WunderlichHi Frank,
drivers/phy/rockchip/phy-rockchip-snps-pcie3.c line 250
Quoted 5 lines · Frank Wunderlich
drivers/phy/rockchip/phy-rockchip-snps-pcie3.c new file +5
-0+ priv->p30phy =devm_reset_control_get_exclusive (dev,"phy" ); +if (IS_ERR (priv->p30phy)) { +dev_warn (dev,"no phy reset control specified\n" ); + priv->p30phy =NULL ; + }
Please use devm_reset_control_get_optional_exclusive() [1] instead, which already returns NULL if no reset control is specified, and return on errors.
[1] https://docs.kernel.org/driver-api/reset.html#c.devm_reset_control_get_optional_exclusive
regards
Philipp
Aw: Re: [RFC/RFT v2 03/11] dt-bindings: phy: rockchip: add PCIe v3 constants
In reply to Krzysztof KozlowskiHi
Quoted 9 lines
Gesendet: Donnerstag, 28. April 2022 um 08:34 Uhr
Von: "Krzysztof Kozlowski" <[email protected]>Quoted 3 lines · Frank Wunderlich
From: Frank Wunderlich <[email protected]>
include/dt-bindings/phy/phy-rockchip-pcie3.h | 21 ++++++++++++++++++++Naming - vendor,device.
ok, would rename to rockchip,pcie3-phy.h, is this ok?
Quoted 7 lines
include/dt-bindings/phy/phy-rockchip-pcie3.h line 1
Quoted 4 lines
include/dt-bindings/phy/phy-rockchip-pcie3.h new file +1
-0@@ -0,0 +1,21 @@ +/* SPDX-License-Identifier: (GPL-2.0+ OR MIT) */ s/MIT/BSD-2-clause/ just like bindings because it is part of it. Unless you took it from something and it is already licensed like that?
took this with this license from downstream-repo, only removed snps from name and changed name of include guarding.
regards Frank
Signature · 3 lines
linux-phy mailing list [email protected] https://lists.infradead.org/mailman/listinfo/linux-phy
Re: Aw: Re: [RFC/RFT v2 03/11] dt-bindings: phy: rockchip: add PCIe v3 constants
Quoted 5 lines · Frank Wunderlich
Hi
Quoted 3 lines
Gesendet: Donnerstag, 28. April 2022 um 08:34 Uhr
Von: "Krzysztof Kozlowski" <[email protected]>
Quoted 8 lines
Quoted 6 lines · Frank Wunderlich
Quoted 3 lines
From: Frank Wunderlich <[email protected]>
include/dt-bindings/phy/phy-rockchip-pcie3.h | 21 ++++++++++++++++++++Naming - vendor,device.
ok, would rename to rockchip,pcie3-phy.h, is this ok?
Yes.
Quoted 10 lines
Quoted 8 lines
include/dt-bindings/phy/phy-rockchip-pcie3.h line 1
Quoted 5 lines
include/dt-bindings/phy/phy-rockchip-pcie3.h new file +1
-0@@ -0,0 +1,21 @@ +/* SPDX-License-Identifier: (GPL-2.0+ OR MIT) */ s/MIT/BSD-2-clause/ just like bindings because it is part of it. Unless you took it from something and it is already licensed like that?
took this with this license from downstream-repo, only removed snps from name and changed name of include guarding.
Then you need to keep the original license, so it is ok.
Best regards,
Krzysztof
Signature · 3 lines
linux-phy mailing list [email protected] https://lists.infradead.org/mailman/listinfo/linux-phy