* [PATCH v1 0/3] Add i.MX8Q PCIe PHY driver
@ 2023-08-29 6:45 ` Richard Zhu
0 siblings, 0 replies; 30+ messages in thread
From: Richard Zhu @ 2023-08-29 6:45 UTC (permalink / raw)
To: vkoul, kishon, robh+dt, krzysztof.kozlowski+dt, conor+dt,
shawnguo, s.hauer, festevam, l.stach, a.fatoum, u.kleine-koenig
Cc: hongxing.zhu, linux-phy, devicetree, linux-arm-kernel,
linux-kernel, kernel, linux-imx
i.MX8QM HSIO(High Speed IO) module has three instances of single lane
SERDES PHYs, an instance of two lanes PCIe GEN3 controller, an
instance of single lane PCIe GEN3 controller, as well as an instance
of SATA 3.0 controller.
The HSIO module can be configured as the following different usecases.
1 - A two lanes PCIea and a single lane SATA.
2 - A single lane PCIea, a single lane PCIeb and a single lane SATA.
3 - A two lanes PCIea, a single lane PCIeb.
Add i.MX8Q PCIe PHY driver to support these different usecases, and had
been verified on i.MX8QM and i.MX8QXP MEK boards.
[PATCH v1 1/3] dt-bindings: phy: Add i.MX8QM PCIe PHY binding
[PATCH v1 2/3] dt-bindings: phy: phy-imx8-pcie: Add binding for
[PATCH v1 3/3] phy: freescale: imx8q-pcie: Add i.MX8Q PCIe PHY driver
Documentation/devicetree/bindings/phy/fsl,imx8-pcie-phy.yaml | 70 ++++++++++-
drivers/phy/freescale/Kconfig | 8 ++
drivers/phy/freescale/Makefile | 1 +
drivers/phy/freescale/phy-fsl-imx8q-pcie.c | 562 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
include/dt-bindings/phy/phy-imx8-pcie.h | 7 ++
5 files changed, 645 insertions(+), 3 deletions(-)
^ permalink raw reply [flat|nested] 30+ messages in thread
* [PATCH v1 0/3] Add i.MX8Q PCIe PHY driver
@ 2023-08-29 6:45 ` Richard Zhu
0 siblings, 0 replies; 30+ messages in thread
From: Richard Zhu @ 2023-08-29 6:45 UTC (permalink / raw)
To: vkoul, kishon, robh+dt, krzysztof.kozlowski+dt, conor+dt,
shawnguo, s.hauer, festevam, l.stach, a.fatoum, u.kleine-koenig
Cc: hongxing.zhu, linux-phy, devicetree, linux-arm-kernel,
linux-kernel, kernel, linux-imx
i.MX8QM HSIO(High Speed IO) module has three instances of single lane
SERDES PHYs, an instance of two lanes PCIe GEN3 controller, an
instance of single lane PCIe GEN3 controller, as well as an instance
of SATA 3.0 controller.
The HSIO module can be configured as the following different usecases.
1 - A two lanes PCIea and a single lane SATA.
2 - A single lane PCIea, a single lane PCIeb and a single lane SATA.
3 - A two lanes PCIea, a single lane PCIeb.
Add i.MX8Q PCIe PHY driver to support these different usecases, and had
been verified on i.MX8QM and i.MX8QXP MEK boards.
[PATCH v1 1/3] dt-bindings: phy: Add i.MX8QM PCIe PHY binding
[PATCH v1 2/3] dt-bindings: phy: phy-imx8-pcie: Add binding for
[PATCH v1 3/3] phy: freescale: imx8q-pcie: Add i.MX8Q PCIe PHY driver
Documentation/devicetree/bindings/phy/fsl,imx8-pcie-phy.yaml | 70 ++++++++++-
drivers/phy/freescale/Kconfig | 8 ++
drivers/phy/freescale/Makefile | 1 +
drivers/phy/freescale/phy-fsl-imx8q-pcie.c | 562 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
include/dt-bindings/phy/phy-imx8-pcie.h | 7 ++
5 files changed, 645 insertions(+), 3 deletions(-)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 30+ messages in thread
* [PATCH v1 0/3] Add i.MX8Q PCIe PHY driver
@ 2023-08-29 6:45 ` Richard Zhu
0 siblings, 0 replies; 30+ messages in thread
From: Richard Zhu @ 2023-08-29 6:45 UTC (permalink / raw)
To: vkoul, kishon, robh+dt, krzysztof.kozlowski+dt, conor+dt,
shawnguo, s.hauer, festevam, l.stach, a.fatoum, u.kleine-koenig
Cc: hongxing.zhu, linux-phy, devicetree, linux-arm-kernel,
linux-kernel, kernel, linux-imx
i.MX8QM HSIO(High Speed IO) module has three instances of single lane
SERDES PHYs, an instance of two lanes PCIe GEN3 controller, an
instance of single lane PCIe GEN3 controller, as well as an instance
of SATA 3.0 controller.
The HSIO module can be configured as the following different usecases.
1 - A two lanes PCIea and a single lane SATA.
2 - A single lane PCIea, a single lane PCIeb and a single lane SATA.
3 - A two lanes PCIea, a single lane PCIeb.
Add i.MX8Q PCIe PHY driver to support these different usecases, and had
been verified on i.MX8QM and i.MX8QXP MEK boards.
[PATCH v1 1/3] dt-bindings: phy: Add i.MX8QM PCIe PHY binding
[PATCH v1 2/3] dt-bindings: phy: phy-imx8-pcie: Add binding for
[PATCH v1 3/3] phy: freescale: imx8q-pcie: Add i.MX8Q PCIe PHY driver
Documentation/devicetree/bindings/phy/fsl,imx8-pcie-phy.yaml | 70 ++++++++++-
drivers/phy/freescale/Kconfig | 8 ++
drivers/phy/freescale/Makefile | 1 +
drivers/phy/freescale/phy-fsl-imx8q-pcie.c | 562 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
include/dt-bindings/phy/phy-imx8-pcie.h | 7 ++
5 files changed, 645 insertions(+), 3 deletions(-)
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
^ permalink raw reply [flat|nested] 30+ messages in thread
* [PATCH v1 1/3] dt-bindings: phy: Add i.MX8QM PCIe PHY binding
2023-08-29 6:45 ` Richard Zhu
(?)
@ 2023-08-29 6:45 ` Richard Zhu
-1 siblings, 0 replies; 30+ messages in thread
From: Richard Zhu @ 2023-08-29 6:45 UTC (permalink / raw)
To: vkoul, kishon, robh+dt, krzysztof.kozlowski+dt, conor+dt,
shawnguo, s.hauer, festevam, l.stach, a.fatoum, u.kleine-koenig
Cc: hongxing.zhu, linux-phy, devicetree, linux-arm-kernel,
linux-kernel, kernel, linux-imx
Add i.MX8QM PCIe PHY binding.
i.MX8QM HSIO(High Speed IO) module has three instances of single lane
SERDES PHYs, an instance of two lanes PCIe GEN3 controller, an
instance of single lane PCIe GEN3 controller, as well as an instance
of SATA 3.0 controller.
The HSIO module can be configured as the following different usecases.
1 - A two lanes PCIea and a single lane SATA.
2 - A single lane PCIea, a single lane PCIeb and a single lane SATA.
3 - A two lanes PCIea, a single lane PCIeb.
Signed-off-by: Richard Zhu <hongxing.zhu@nxp.com>
---
.../bindings/phy/fsl,imx8-pcie-phy.yaml | 70 ++++++++++++++++++-
1 file changed, 67 insertions(+), 3 deletions(-)
diff --git a/Documentation/devicetree/bindings/phy/fsl,imx8-pcie-phy.yaml b/Documentation/devicetree/bindings/phy/fsl,imx8-pcie-phy.yaml
index 182a219387b0..764790f2b10b 100644
--- a/Documentation/devicetree/bindings/phy/fsl,imx8-pcie-phy.yaml
+++ b/Documentation/devicetree/bindings/phy/fsl,imx8-pcie-phy.yaml
@@ -17,16 +17,18 @@ properties:
enum:
- fsl,imx8mm-pcie-phy
- fsl,imx8mp-pcie-phy
+ - fsl,imx8qm-pcie-phy
reg:
maxItems: 1
clocks:
- maxItems: 1
+ minItems: 1
+ maxItems: 5
clock-names:
- items:
- - const: ref
+ minItems: 1
+ maxItems: 5
resets:
minItems: 1
@@ -70,6 +72,36 @@ properties:
description: PCIe PHY power domain (optional).
maxItems: 1
+ hsio-cfg:
+ description: |
+ Specifies the different usecases supported by the HSIO(High Speed IO)
+ module. PCIEAX2SATA means two lanes PCIea and a single lane SATA.
+ PCIEAX1PCIEBX1SATA represents a single lane PCIea, a single lane
+ PCIeb and a single lane SATA. PCIEAX2PCIEBX1 on behalf of a two
+ lanes PCIea, a single lane PCIeb.
+ Refer include/dt-bindings/phy/phy-imx8-pcie.h for the constants to
+ be used (optional).
+ $ref: /schemas/types.yaml#/definitions/uint32
+ enum: [ 1, 2, 3 ]
+
+ ctrl-csr:
+ $ref: /schemas/types.yaml#/definitions/phandle
+ description:
+ phandle to the ctrl-csr region containing the HSIO control and
+ status registers for PCIe or SATA controller (optional).
+
+ misc-csr:
+ $ref: /schemas/types.yaml#/definitions/phandle
+ description:
+ phandle to the misc-csr region containing the HSIO control and
+ status registers for misc (optional).
+
+ phy-csr:
+ $ref: /schemas/types.yaml#/definitions/phandle
+ description:
+ phandle to the phy-csr region containing the HSIO control and
+ status registers for phy (optional).
+
required:
- "#phy-cells"
- compatible
@@ -78,6 +110,38 @@ required:
- clock-names
- fsl,refclk-pad-mode
+allOf:
+ - if:
+ properties:
+ compatible:
+ enum:
+ - fsl,imx8qm-pcie-phy
+ then:
+ properties:
+ clocks:
+ minItems: 4
+ maxItems: 5
+ clock-names:
+ oneOf:
+ - items:
+ - const: pipe_pclk
+ - const: ctrl_ips_clk
+ - const: phy_ips_clk
+ - const: misc_ips_clk
+ - items:
+ - const: apb_pclk
+ - const: pipe_pclk
+ - const: ctrl_ips_clk
+ - const: phy_ips_clk
+ - const: misc_ips_clk
+ else:
+ properties:
+ clocks:
+ maxItems: 1
+ clock-names:
+ items:
+ - const: ref
+
additionalProperties: false
examples:
--
2.34.1
^ permalink raw reply related [flat|nested] 30+ messages in thread
* [PATCH v1 1/3] dt-bindings: phy: Add i.MX8QM PCIe PHY binding
@ 2023-08-29 6:45 ` Richard Zhu
0 siblings, 0 replies; 30+ messages in thread
From: Richard Zhu @ 2023-08-29 6:45 UTC (permalink / raw)
To: vkoul, kishon, robh+dt, krzysztof.kozlowski+dt, conor+dt,
shawnguo, s.hauer, festevam, l.stach, a.fatoum, u.kleine-koenig
Cc: hongxing.zhu, linux-phy, devicetree, linux-arm-kernel,
linux-kernel, kernel, linux-imx
Add i.MX8QM PCIe PHY binding.
i.MX8QM HSIO(High Speed IO) module has three instances of single lane
SERDES PHYs, an instance of two lanes PCIe GEN3 controller, an
instance of single lane PCIe GEN3 controller, as well as an instance
of SATA 3.0 controller.
The HSIO module can be configured as the following different usecases.
1 - A two lanes PCIea and a single lane SATA.
2 - A single lane PCIea, a single lane PCIeb and a single lane SATA.
3 - A two lanes PCIea, a single lane PCIeb.
Signed-off-by: Richard Zhu <hongxing.zhu@nxp.com>
---
.../bindings/phy/fsl,imx8-pcie-phy.yaml | 70 ++++++++++++++++++-
1 file changed, 67 insertions(+), 3 deletions(-)
diff --git a/Documentation/devicetree/bindings/phy/fsl,imx8-pcie-phy.yaml b/Documentation/devicetree/bindings/phy/fsl,imx8-pcie-phy.yaml
index 182a219387b0..764790f2b10b 100644
--- a/Documentation/devicetree/bindings/phy/fsl,imx8-pcie-phy.yaml
+++ b/Documentation/devicetree/bindings/phy/fsl,imx8-pcie-phy.yaml
@@ -17,16 +17,18 @@ properties:
enum:
- fsl,imx8mm-pcie-phy
- fsl,imx8mp-pcie-phy
+ - fsl,imx8qm-pcie-phy
reg:
maxItems: 1
clocks:
- maxItems: 1
+ minItems: 1
+ maxItems: 5
clock-names:
- items:
- - const: ref
+ minItems: 1
+ maxItems: 5
resets:
minItems: 1
@@ -70,6 +72,36 @@ properties:
description: PCIe PHY power domain (optional).
maxItems: 1
+ hsio-cfg:
+ description: |
+ Specifies the different usecases supported by the HSIO(High Speed IO)
+ module. PCIEAX2SATA means two lanes PCIea and a single lane SATA.
+ PCIEAX1PCIEBX1SATA represents a single lane PCIea, a single lane
+ PCIeb and a single lane SATA. PCIEAX2PCIEBX1 on behalf of a two
+ lanes PCIea, a single lane PCIeb.
+ Refer include/dt-bindings/phy/phy-imx8-pcie.h for the constants to
+ be used (optional).
+ $ref: /schemas/types.yaml#/definitions/uint32
+ enum: [ 1, 2, 3 ]
+
+ ctrl-csr:
+ $ref: /schemas/types.yaml#/definitions/phandle
+ description:
+ phandle to the ctrl-csr region containing the HSIO control and
+ status registers for PCIe or SATA controller (optional).
+
+ misc-csr:
+ $ref: /schemas/types.yaml#/definitions/phandle
+ description:
+ phandle to the misc-csr region containing the HSIO control and
+ status registers for misc (optional).
+
+ phy-csr:
+ $ref: /schemas/types.yaml#/definitions/phandle
+ description:
+ phandle to the phy-csr region containing the HSIO control and
+ status registers for phy (optional).
+
required:
- "#phy-cells"
- compatible
@@ -78,6 +110,38 @@ required:
- clock-names
- fsl,refclk-pad-mode
+allOf:
+ - if:
+ properties:
+ compatible:
+ enum:
+ - fsl,imx8qm-pcie-phy
+ then:
+ properties:
+ clocks:
+ minItems: 4
+ maxItems: 5
+ clock-names:
+ oneOf:
+ - items:
+ - const: pipe_pclk
+ - const: ctrl_ips_clk
+ - const: phy_ips_clk
+ - const: misc_ips_clk
+ - items:
+ - const: apb_pclk
+ - const: pipe_pclk
+ - const: ctrl_ips_clk
+ - const: phy_ips_clk
+ - const: misc_ips_clk
+ else:
+ properties:
+ clocks:
+ maxItems: 1
+ clock-names:
+ items:
+ - const: ref
+
additionalProperties: false
examples:
--
2.34.1
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
^ permalink raw reply related [flat|nested] 30+ messages in thread
* [PATCH v1 1/3] dt-bindings: phy: Add i.MX8QM PCIe PHY binding
@ 2023-08-29 6:45 ` Richard Zhu
0 siblings, 0 replies; 30+ messages in thread
From: Richard Zhu @ 2023-08-29 6:45 UTC (permalink / raw)
To: vkoul, kishon, robh+dt, krzysztof.kozlowski+dt, conor+dt,
shawnguo, s.hauer, festevam, l.stach, a.fatoum, u.kleine-koenig
Cc: hongxing.zhu, linux-phy, devicetree, linux-arm-kernel,
linux-kernel, kernel, linux-imx
Add i.MX8QM PCIe PHY binding.
i.MX8QM HSIO(High Speed IO) module has three instances of single lane
SERDES PHYs, an instance of two lanes PCIe GEN3 controller, an
instance of single lane PCIe GEN3 controller, as well as an instance
of SATA 3.0 controller.
The HSIO module can be configured as the following different usecases.
1 - A two lanes PCIea and a single lane SATA.
2 - A single lane PCIea, a single lane PCIeb and a single lane SATA.
3 - A two lanes PCIea, a single lane PCIeb.
Signed-off-by: Richard Zhu <hongxing.zhu@nxp.com>
---
.../bindings/phy/fsl,imx8-pcie-phy.yaml | 70 ++++++++++++++++++-
1 file changed, 67 insertions(+), 3 deletions(-)
diff --git a/Documentation/devicetree/bindings/phy/fsl,imx8-pcie-phy.yaml b/Documentation/devicetree/bindings/phy/fsl,imx8-pcie-phy.yaml
index 182a219387b0..764790f2b10b 100644
--- a/Documentation/devicetree/bindings/phy/fsl,imx8-pcie-phy.yaml
+++ b/Documentation/devicetree/bindings/phy/fsl,imx8-pcie-phy.yaml
@@ -17,16 +17,18 @@ properties:
enum:
- fsl,imx8mm-pcie-phy
- fsl,imx8mp-pcie-phy
+ - fsl,imx8qm-pcie-phy
reg:
maxItems: 1
clocks:
- maxItems: 1
+ minItems: 1
+ maxItems: 5
clock-names:
- items:
- - const: ref
+ minItems: 1
+ maxItems: 5
resets:
minItems: 1
@@ -70,6 +72,36 @@ properties:
description: PCIe PHY power domain (optional).
maxItems: 1
+ hsio-cfg:
+ description: |
+ Specifies the different usecases supported by the HSIO(High Speed IO)
+ module. PCIEAX2SATA means two lanes PCIea and a single lane SATA.
+ PCIEAX1PCIEBX1SATA represents a single lane PCIea, a single lane
+ PCIeb and a single lane SATA. PCIEAX2PCIEBX1 on behalf of a two
+ lanes PCIea, a single lane PCIeb.
+ Refer include/dt-bindings/phy/phy-imx8-pcie.h for the constants to
+ be used (optional).
+ $ref: /schemas/types.yaml#/definitions/uint32
+ enum: [ 1, 2, 3 ]
+
+ ctrl-csr:
+ $ref: /schemas/types.yaml#/definitions/phandle
+ description:
+ phandle to the ctrl-csr region containing the HSIO control and
+ status registers for PCIe or SATA controller (optional).
+
+ misc-csr:
+ $ref: /schemas/types.yaml#/definitions/phandle
+ description:
+ phandle to the misc-csr region containing the HSIO control and
+ status registers for misc (optional).
+
+ phy-csr:
+ $ref: /schemas/types.yaml#/definitions/phandle
+ description:
+ phandle to the phy-csr region containing the HSIO control and
+ status registers for phy (optional).
+
required:
- "#phy-cells"
- compatible
@@ -78,6 +110,38 @@ required:
- clock-names
- fsl,refclk-pad-mode
+allOf:
+ - if:
+ properties:
+ compatible:
+ enum:
+ - fsl,imx8qm-pcie-phy
+ then:
+ properties:
+ clocks:
+ minItems: 4
+ maxItems: 5
+ clock-names:
+ oneOf:
+ - items:
+ - const: pipe_pclk
+ - const: ctrl_ips_clk
+ - const: phy_ips_clk
+ - const: misc_ips_clk
+ - items:
+ - const: apb_pclk
+ - const: pipe_pclk
+ - const: ctrl_ips_clk
+ - const: phy_ips_clk
+ - const: misc_ips_clk
+ else:
+ properties:
+ clocks:
+ maxItems: 1
+ clock-names:
+ items:
+ - const: ref
+
additionalProperties: false
examples:
--
2.34.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply related [flat|nested] 30+ messages in thread
* [PATCH v1 2/3] dt-bindings: phy: phy-imx8-pcie: Add binding for different usecases of i.MX8QM PCIe PHYs
2023-08-29 6:45 ` Richard Zhu
(?)
@ 2023-08-29 6:45 ` Richard Zhu
-1 siblings, 0 replies; 30+ messages in thread
From: Richard Zhu @ 2023-08-29 6:45 UTC (permalink / raw)
To: vkoul, kishon, robh+dt, krzysztof.kozlowski+dt, conor+dt,
shawnguo, s.hauer, festevam, l.stach, a.fatoum, u.kleine-koenig
Cc: hongxing.zhu, linux-phy, devicetree, linux-arm-kernel,
linux-kernel, kernel, linux-imx
Add binding for different usecases of i.MX8QM PCIe PHYs.
Signed-off-by: Richard Zhu <hongxing.zhu@nxp.com>
---
include/dt-bindings/phy/phy-imx8-pcie.h | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/include/dt-bindings/phy/phy-imx8-pcie.h b/include/dt-bindings/phy/phy-imx8-pcie.h
index 8bbe2d6538d8..c8425c172118 100644
--- a/include/dt-bindings/phy/phy-imx8-pcie.h
+++ b/include/dt-bindings/phy/phy-imx8-pcie.h
@@ -11,4 +11,11 @@
#define IMX8_PCIE_REFCLK_PAD_INPUT 1
#define IMX8_PCIE_REFCLK_PAD_OUTPUT 2
+/*
+ * Different usecases of i.MX8QM HSIO(High Speed IO) module.
+ */
+#define PCIEAX2SATA 1
+#define PCIEAX1PCIEBX1SATA 2
+#define PCIEAX2PCIEBX1 3
+
#endif /* _DT_BINDINGS_IMX8_PCIE_H */
--
2.34.1
^ permalink raw reply related [flat|nested] 30+ messages in thread
* [PATCH v1 2/3] dt-bindings: phy: phy-imx8-pcie: Add binding for different usecases of i.MX8QM PCIe PHYs
@ 2023-08-29 6:45 ` Richard Zhu
0 siblings, 0 replies; 30+ messages in thread
From: Richard Zhu @ 2023-08-29 6:45 UTC (permalink / raw)
To: vkoul, kishon, robh+dt, krzysztof.kozlowski+dt, conor+dt,
shawnguo, s.hauer, festevam, l.stach, a.fatoum, u.kleine-koenig
Cc: hongxing.zhu, linux-phy, devicetree, linux-arm-kernel,
linux-kernel, kernel, linux-imx
Add binding for different usecases of i.MX8QM PCIe PHYs.
Signed-off-by: Richard Zhu <hongxing.zhu@nxp.com>
---
include/dt-bindings/phy/phy-imx8-pcie.h | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/include/dt-bindings/phy/phy-imx8-pcie.h b/include/dt-bindings/phy/phy-imx8-pcie.h
index 8bbe2d6538d8..c8425c172118 100644
--- a/include/dt-bindings/phy/phy-imx8-pcie.h
+++ b/include/dt-bindings/phy/phy-imx8-pcie.h
@@ -11,4 +11,11 @@
#define IMX8_PCIE_REFCLK_PAD_INPUT 1
#define IMX8_PCIE_REFCLK_PAD_OUTPUT 2
+/*
+ * Different usecases of i.MX8QM HSIO(High Speed IO) module.
+ */
+#define PCIEAX2SATA 1
+#define PCIEAX1PCIEBX1SATA 2
+#define PCIEAX2PCIEBX1 3
+
#endif /* _DT_BINDINGS_IMX8_PCIE_H */
--
2.34.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply related [flat|nested] 30+ messages in thread
* [PATCH v1 2/3] dt-bindings: phy: phy-imx8-pcie: Add binding for different usecases of i.MX8QM PCIe PHYs
@ 2023-08-29 6:45 ` Richard Zhu
0 siblings, 0 replies; 30+ messages in thread
From: Richard Zhu @ 2023-08-29 6:45 UTC (permalink / raw)
To: vkoul, kishon, robh+dt, krzysztof.kozlowski+dt, conor+dt,
shawnguo, s.hauer, festevam, l.stach, a.fatoum, u.kleine-koenig
Cc: hongxing.zhu, linux-phy, devicetree, linux-arm-kernel,
linux-kernel, kernel, linux-imx
Add binding for different usecases of i.MX8QM PCIe PHYs.
Signed-off-by: Richard Zhu <hongxing.zhu@nxp.com>
---
include/dt-bindings/phy/phy-imx8-pcie.h | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/include/dt-bindings/phy/phy-imx8-pcie.h b/include/dt-bindings/phy/phy-imx8-pcie.h
index 8bbe2d6538d8..c8425c172118 100644
--- a/include/dt-bindings/phy/phy-imx8-pcie.h
+++ b/include/dt-bindings/phy/phy-imx8-pcie.h
@@ -11,4 +11,11 @@
#define IMX8_PCIE_REFCLK_PAD_INPUT 1
#define IMX8_PCIE_REFCLK_PAD_OUTPUT 2
+/*
+ * Different usecases of i.MX8QM HSIO(High Speed IO) module.
+ */
+#define PCIEAX2SATA 1
+#define PCIEAX1PCIEBX1SATA 2
+#define PCIEAX2PCIEBX1 3
+
#endif /* _DT_BINDINGS_IMX8_PCIE_H */
--
2.34.1
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
^ permalink raw reply related [flat|nested] 30+ messages in thread
* [PATCH v1 3/3] phy: freescale: imx8q-pcie: Add i.MX8Q PCIe PHY driver
2023-08-29 6:45 ` Richard Zhu
(?)
@ 2023-08-29 6:45 ` Richard Zhu
-1 siblings, 0 replies; 30+ messages in thread
From: Richard Zhu @ 2023-08-29 6:45 UTC (permalink / raw)
To: vkoul, kishon, robh+dt, krzysztof.kozlowski+dt, conor+dt,
shawnguo, s.hauer, festevam, l.stach, a.fatoum, u.kleine-koenig
Cc: hongxing.zhu, linux-phy, devicetree, linux-arm-kernel,
linux-kernel, kernel, linux-imx
i.MX8QM HSIO(High Speed IO) module has three instances of single lane
SERDES PHYs, an instance of two lanes PCIe GEN3 controller, an
instance of single lane PCIe GEN3 controller, as well as an instance
of SATA 3.0 controller.
The HSIO module can be configured as the following different usecases.
1 - A two lanes PCIea and a single lane SATA.
2 - A single lane PCIea, a single lane PCIeb and a single lane SATA.
3 - A two lanes PCIea, a single lane PCIeb.
Add i.MX8Q PCIe PHY driver to support these different usecases.
- Add the runtime PM support, thus the PCIe PHY PD can be turned off
when PCIe probe is failed.
- The APB_PCLK is required only when PHY is configured as PCIE mode.
Note:
Although the RM document doesn't specify it, but the LPCG clocks should
be handled by a different procedure when the PHY is configured in PCIe
or SATA modes based on the practical oberservations.
When PHY is configured into PCIe mode.
- apb_pclk is mandatory required.
- apb_pclk and pipe_pclk should be enabled just before polling
PM_REQ_CORE_RST is cleared or not.
When PHY is configured as SATA mode.
- There is no apb_pclk.
- pipe_pclk should be enabled together with other LPCG clocks.
Signed-off-by: Richard Zhu <hongxing.zhu@nxp.com>
---
drivers/phy/freescale/Kconfig | 8 +
drivers/phy/freescale/Makefile | 1 +
drivers/phy/freescale/phy-fsl-imx8q-pcie.c | 562 +++++++++++++++++++++
3 files changed, 571 insertions(+)
create mode 100644 drivers/phy/freescale/phy-fsl-imx8q-pcie.c
diff --git a/drivers/phy/freescale/Kconfig b/drivers/phy/freescale/Kconfig
index 853958fb2c06..6f81fbf5f5e6 100644
--- a/drivers/phy/freescale/Kconfig
+++ b/drivers/phy/freescale/Kconfig
@@ -35,6 +35,14 @@ config PHY_FSL_IMX8M_PCIE
Enable this to add support for the PCIE PHY as found on
i.MX8M family of SOCs.
+config PHY_FSL_IMX8Q_PCIE
+ tristate "Freescale i.MX8Q PCIE PHY"
+ depends on OF && HAS_IOMEM
+ select GENERIC_PHY
+ help
+ Enable this to add support for the PCIE PHY as found on
+ i.MX8Q family of SOCs.
+
endif
config PHY_FSL_LYNX_28G
diff --git a/drivers/phy/freescale/Makefile b/drivers/phy/freescale/Makefile
index cedb328bc4d2..afa84807c40c 100644
--- a/drivers/phy/freescale/Makefile
+++ b/drivers/phy/freescale/Makefile
@@ -3,4 +3,5 @@ obj-$(CONFIG_PHY_FSL_IMX8MQ_USB) += phy-fsl-imx8mq-usb.o
obj-$(CONFIG_PHY_MIXEL_LVDS_PHY) += phy-fsl-imx8qm-lvds-phy.o
obj-$(CONFIG_PHY_MIXEL_MIPI_DPHY) += phy-fsl-imx8-mipi-dphy.o
obj-$(CONFIG_PHY_FSL_IMX8M_PCIE) += phy-fsl-imx8m-pcie.o
+obj-$(CONFIG_PHY_FSL_IMX8Q_PCIE) += phy-fsl-imx8q-pcie.o
obj-$(CONFIG_PHY_FSL_LYNX_28G) += phy-fsl-lynx-28g.o
diff --git a/drivers/phy/freescale/phy-fsl-imx8q-pcie.c b/drivers/phy/freescale/phy-fsl-imx8q-pcie.c
new file mode 100644
index 000000000000..3f1589628be1
--- /dev/null
+++ b/drivers/phy/freescale/phy-fsl-imx8q-pcie.c
@@ -0,0 +1,562 @@
+// SPDX-License-Identifier: GPL-2.0+
+/*
+ * Copyright 2023 NXP
+ */
+
+#include <linux/bitfield.h>
+#include <linux/clk.h>
+#include <linux/delay.h>
+#include <linux/io.h>
+#include <linux/iopoll.h>
+#include <linux/mfd/syscon.h>
+#include <linux/module.h>
+#include <linux/of_address.h>
+#include <linux/of_device.h>
+#include <linux/phy/phy.h>
+#include <linux/platform_device.h>
+#include <linux/regmap.h>
+
+#include <dt-bindings/phy/phy-imx8-pcie.h>
+
+/* i.MX8Q HSIO registers */
+#define IMX8Q_PHY_CTRL0_OFFSET 0x0
+#define IMX8Q_PHYX2_CTRL0_APB_MASK GENMASK(1, 0)
+#define IMX8Q_PHY_CTRL0_APB_RSTN_0 BIT(0)
+#define IMX8Q_PHY_CTRL0_APB_RSTN_1 BIT(1)
+#define IMX8Q_PHY_MODE_MASK GENMASK(20, 17)
+#define IMX8Q_PHY_MODE_SATA BIT(19)
+#define IMX8Q_PHY_PIPE_RSTN_0_MASK GENMASK(25, 24)
+#define IMX8Q_PHY_PIPE_RSTN_1_MASK GENMASK(27, 26)
+
+#define IMX8Q_PHY_STTS0_OFFSET 0x4
+#define IMX8Q_STTS0_LANE0_TX_PLL_LOCK BIT(4)
+#define IMX8Q_STTS0_LANE1_TX_PLL_LOCK BIT(12)
+
+#define IMX8Q_PCIE_CTRL2_OFFSET 0x8
+#define IMX8Q_CTRL_BUTTON_RST_N BIT(21)
+#define IMX8Q_CTRL_PERST_N BIT(22)
+#define IMX8Q_CTRL_POWER_UP_RST_N BIT(23)
+
+#define IMX8Q_PCIE_STTS0_OFFSET 0xC
+#define IMX8Q_CTRL_STTS0_PM_REQ_CORE_RST BIT(19)
+
+#define IMX8Q_SATA_CTRL0_OFFSET 0x0
+#define IMX8Q_SATA_CTRL_EPCS_TXDEEMP BIT(5)
+#define IMX8Q_SATA_CTRL_EPCS_TXDEEMP_SEL BIT(6)
+#define IMX8Q_SATA_CTRL_EPCS_PHYRESET_N BIT(7)
+#define IMX8Q_SATA_CTRL_RESET_N BIT(12)
+
+#define IMX8Q_MISC_CTRL0_OFFSET 0x0
+#define IMX8Q_MISC_IOB_RXENA BIT(0)
+#define IMX8Q_MISC_IOB_TXENA BIT(1)
+#define IMX8Q_MISC_IOB_A_0_TXOE BIT(2)
+#define IMX8Q_MISC_IOB_A_0_M1M0_MASK GENMASK(4, 3)
+#define IMX8Q_MISC_IOB_A_0_M1M0_2 BIT(4)
+#define IMX8Q_MISC_PHYX1_EPCS_SEL BIT(12)
+#define IMX8Q_MISC_PCIE_AB_SELECT BIT(13)
+#define IMX8Q_MISC_CLKREQN_OUT_OVERRIDE_1 BIT(24)
+#define IMX8Q_MISC_CLKREQN_OUT_OVERRIDE_0 BIT(25)
+
+#define IMX8Q_PHY_REG48_PMA_STATUS 0x30
+#define IMX8Q_PHY_REG48_PMA_RDY BIT(7)
+
+#define IMX8Q_PHYX2_LANE1_BASE_ADDR 0x5F190000
+#define IMX8Q_PHYX1_LANE0_BASE_ADDR 0x5F1A0000
+
+/* Parameters for the waiting for PCIe PHY PLL to lock */
+#define PHY_INIT_WAIT_USLEEP_MAX 10
+#define PHY_INIT_WAIT_TIMEOUT (1000 * PHY_INIT_WAIT_USLEEP_MAX)
+
+enum imx8q_pcie_phy_mode {
+ IMX8Q_PHY_PCIE_MODE,
+ IMX8Q_PHY_SATA_MODE,
+};
+
+struct imx8q_pcie_phy {
+ void __iomem *base;
+ struct clk *apb_pclk;
+ struct clk *ctrl_ips_clk;
+ struct clk *misc_ips_clk;
+ struct clk *phy_ips_clk;
+ struct clk *pipe_pclk;
+ struct device *dev;
+ struct phy *phy;
+ struct regmap *ctrl_gpr;
+ struct regmap *misc_gpr;
+ struct regmap *phy_gpr;
+ u32 hsio_cfg;
+ u32 lane_id;
+ u32 refclk_pad_mode;
+ enum imx8q_pcie_phy_mode mode;
+};
+
+static int imx8q_pcie_phy_init(struct phy *phy)
+{
+ int ret;
+ struct imx8q_pcie_phy *imx8_phy = phy_get_drvdata(phy);
+
+ if (imx8_phy->mode == IMX8Q_PHY_SATA_MODE) {
+ ret = clk_prepare_enable(imx8_phy->pipe_pclk);
+ if (ret) {
+ dev_err(imx8_phy->dev, "can't enable pipe clock\n");
+ return ret;
+ }
+ }
+
+ ret = clk_prepare_enable(imx8_phy->ctrl_ips_clk);
+ if (ret) {
+ dev_err(imx8_phy->dev, "can't enable ctrl_ips clock\n");
+ goto err_ctrl_ips_clk;
+ }
+
+ ret = clk_prepare_enable(imx8_phy->phy_ips_clk);
+ if (ret) {
+ dev_err(imx8_phy->dev, "can't enable phy_ips clock\n");
+ goto err_phy_ips_clk;
+ }
+
+ ret = clk_prepare_enable(imx8_phy->misc_ips_clk);
+ if (ret) {
+ dev_err(imx8_phy->dev, "can't enable misc_ips clock\n");
+ goto err_misc_ips_clk;
+ }
+
+ /* allow the clocks to stabilize */
+ usleep_range(200, 500);
+
+ return ret;
+
+err_misc_ips_clk:
+ clk_disable_unprepare(imx8_phy->phy_ips_clk);
+err_phy_ips_clk:
+ clk_disable_unprepare(imx8_phy->ctrl_ips_clk);
+err_ctrl_ips_clk:
+ if (imx8_phy->mode == IMX8Q_PHY_SATA_MODE)
+ clk_disable_unprepare(imx8_phy->pipe_pclk);
+
+ return ret;
+}
+
+static int imx8q_pcie_phy_exit(struct phy *phy)
+{
+ struct imx8q_pcie_phy *imx8_phy = phy_get_drvdata(phy);
+
+ clk_disable_unprepare(imx8_phy->misc_ips_clk);
+ clk_disable_unprepare(imx8_phy->phy_ips_clk);
+ clk_disable_unprepare(imx8_phy->ctrl_ips_clk);
+ if (imx8_phy->mode == IMX8Q_PHY_SATA_MODE)
+ clk_disable_unprepare(imx8_phy->pipe_pclk);
+
+ return 0;
+}
+
+static void imx8q_pcie_phy_reset_pcie(struct phy *phy)
+{
+ struct imx8q_pcie_phy *imx8_phy = phy_get_drvdata(phy);
+
+ regmap_update_bits(imx8_phy->ctrl_gpr, IMX8Q_PCIE_CTRL2_OFFSET,
+ IMX8Q_CTRL_BUTTON_RST_N, 0);
+ regmap_update_bits(imx8_phy->ctrl_gpr, IMX8Q_PCIE_CTRL2_OFFSET,
+ IMX8Q_CTRL_PERST_N, 0);
+ regmap_update_bits(imx8_phy->ctrl_gpr, IMX8Q_PCIE_CTRL2_OFFSET,
+ IMX8Q_CTRL_POWER_UP_RST_N, 0);
+ mdelay(1);
+ regmap_update_bits(imx8_phy->ctrl_gpr, IMX8Q_PCIE_CTRL2_OFFSET,
+ IMX8Q_CTRL_BUTTON_RST_N, IMX8Q_CTRL_BUTTON_RST_N);
+ regmap_update_bits(imx8_phy->ctrl_gpr, IMX8Q_PCIE_CTRL2_OFFSET,
+ IMX8Q_CTRL_PERST_N, IMX8Q_CTRL_PERST_N);
+ regmap_update_bits(imx8_phy->ctrl_gpr, IMX8Q_PCIE_CTRL2_OFFSET,
+ IMX8Q_CTRL_POWER_UP_RST_N, IMX8Q_CTRL_POWER_UP_RST_N);
+}
+
+static void imx8q_pcie_phy_set_clock_mode(struct phy *phy)
+{
+ u32 pad_mode;
+ struct imx8q_pcie_phy *imx8_phy = phy_get_drvdata(phy);
+
+ pad_mode = imx8_phy->refclk_pad_mode;
+ if (pad_mode == IMX8_PCIE_REFCLK_PAD_INPUT ||
+ pad_mode == IMX8_PCIE_REFCLK_PAD_UNUSED) {
+ /* Configure the PAD as input mode */
+ regmap_update_bits(imx8_phy->misc_gpr, IMX8Q_MISC_CTRL0_OFFSET,
+ IMX8Q_MISC_IOB_RXENA, IMX8Q_MISC_IOB_RXENA);
+ regmap_update_bits(imx8_phy->misc_gpr, IMX8Q_MISC_CTRL0_OFFSET,
+ IMX8Q_MISC_IOB_TXENA, 0);
+ usleep_range(200, 500);
+ } else {
+ /* Configure the PHY to output the refclock via PAD */
+ regmap_update_bits(imx8_phy->misc_gpr, IMX8Q_MISC_CTRL0_OFFSET,
+ IMX8Q_MISC_IOB_RXENA, 0);
+ regmap_update_bits(imx8_phy->misc_gpr, IMX8Q_MISC_CTRL0_OFFSET,
+ IMX8Q_MISC_IOB_TXENA, IMX8Q_MISC_IOB_TXENA);
+ regmap_update_bits(imx8_phy->misc_gpr, IMX8Q_MISC_CTRL0_OFFSET,
+ IMX8Q_MISC_IOB_A_0_TXOE | IMX8Q_MISC_IOB_A_0_M1M0_MASK,
+ IMX8Q_MISC_IOB_A_0_TXOE | IMX8Q_MISC_IOB_A_0_M1M0_2);
+ }
+}
+
+static void imx8q_pcie_phy_reset_sata(struct phy *phy)
+{
+ struct imx8q_pcie_phy *imx8_phy = phy_get_drvdata(phy);
+
+ /* clear PHY RST, then set it */
+ regmap_update_bits(imx8_phy->ctrl_gpr, IMX8Q_SATA_CTRL0_OFFSET,
+ IMX8Q_SATA_CTRL_EPCS_PHYRESET_N, 0);
+
+ regmap_update_bits(imx8_phy->ctrl_gpr, IMX8Q_SATA_CTRL0_OFFSET,
+ IMX8Q_SATA_CTRL_EPCS_PHYRESET_N,
+ IMX8Q_SATA_CTRL_EPCS_PHYRESET_N);
+
+ /* CTRL RST: SET -> delay 1 us -> CLEAR -> SET */
+ regmap_update_bits(imx8_phy->ctrl_gpr, IMX8Q_SATA_CTRL0_OFFSET,
+ IMX8Q_SATA_CTRL_RESET_N, IMX8Q_SATA_CTRL_RESET_N);
+ udelay(1);
+ regmap_update_bits(imx8_phy->ctrl_gpr, IMX8Q_SATA_CTRL0_OFFSET,
+ IMX8Q_SATA_CTRL_RESET_N, 0);
+ regmap_update_bits(imx8_phy->ctrl_gpr, IMX8Q_SATA_CTRL0_OFFSET,
+ IMX8Q_SATA_CTRL_RESET_N, IMX8Q_SATA_CTRL_RESET_N);
+
+ usleep_range(50, 100);
+}
+
+static int imx8q_pcie_phy_power_on(struct phy *phy)
+{
+ int ret;
+ u32 val, cond;
+ struct imx8q_pcie_phy *imx8_phy = phy_get_drvdata(phy);
+
+ if (imx8_phy->mode == IMX8Q_PHY_SATA_MODE) {
+ /* SATA mode PHY */
+ regmap_update_bits(imx8_phy->phy_gpr, IMX8Q_PHY_CTRL0_OFFSET,
+ IMX8Q_PHY_MODE_MASK, IMX8Q_PHY_MODE_SATA);
+ /*
+ * It is possible, for PCIe and SATA are sharing
+ * the same clock source, HPLL or external oscillator.
+ * When PCIe is in low power modes (L1.X or L2 etc),
+ * the clock source can be turned off. In this case,
+ * if this clock source is required to be toggling by
+ * SATA, then SATA functions will be abnormal.
+ * Set the override here to avoid it.
+ */
+ regmap_update_bits(imx8_phy->misc_gpr, IMX8Q_MISC_CTRL0_OFFSET,
+ IMX8Q_MISC_CLKREQN_OUT_OVERRIDE_1 |
+ IMX8Q_MISC_CLKREQN_OUT_OVERRIDE_0,
+ IMX8Q_MISC_CLKREQN_OUT_OVERRIDE_1 |
+ IMX8Q_MISC_CLKREQN_OUT_OVERRIDE_0);
+ } else {
+ /* PCIe mode PHY */
+ imx8q_pcie_phy_reset_pcie(phy);
+ }
+
+ if (imx8_phy->hsio_cfg == PCIEAX2SATA) {
+ if (imx8_phy->lane_id == 0) {
+ regmap_update_bits(imx8_phy->phy_gpr,
+ IMX8Q_PHY_CTRL0_OFFSET,
+ IMX8Q_PHYX2_CTRL0_APB_MASK,
+ IMX8Q_PHY_CTRL0_APB_RSTN_0 |
+ IMX8Q_PHY_CTRL0_APB_RSTN_1);
+ regmap_update_bits(imx8_phy->phy_gpr,
+ IMX8Q_PHY_CTRL0_OFFSET,
+ IMX8Q_PHY_PIPE_RSTN_0_MASK |
+ IMX8Q_PHY_PIPE_RSTN_1_MASK,
+ IMX8Q_PHY_PIPE_RSTN_0_MASK |
+ IMX8Q_PHY_PIPE_RSTN_1_MASK);
+ } else if (imx8_phy->lane_id == 2) {
+ regmap_update_bits(imx8_phy->phy_gpr,
+ IMX8Q_PHY_CTRL0_OFFSET,
+ IMX8Q_PHY_CTRL0_APB_RSTN_0,
+ IMX8Q_PHY_CTRL0_APB_RSTN_0);
+ }
+
+ regmap_update_bits(imx8_phy->misc_gpr, IMX8Q_MISC_CTRL0_OFFSET,
+ IMX8Q_MISC_PHYX1_EPCS_SEL, IMX8Q_MISC_PHYX1_EPCS_SEL);
+ regmap_update_bits(imx8_phy->misc_gpr, IMX8Q_MISC_CTRL0_OFFSET,
+ IMX8Q_MISC_PCIE_AB_SELECT, 0);
+ } else if (imx8_phy->hsio_cfg == PCIEAX1PCIEBX1SATA) {
+ if (imx8_phy->lane_id == 0) {
+ regmap_update_bits(imx8_phy->phy_gpr,
+ IMX8Q_PHY_CTRL0_OFFSET,
+ IMX8Q_PHY_CTRL0_APB_RSTN_0,
+ IMX8Q_PHY_CTRL0_APB_RSTN_0);
+ regmap_update_bits(imx8_phy->phy_gpr,
+ IMX8Q_PHY_CTRL0_OFFSET,
+ IMX8Q_PHY_PIPE_RSTN_0_MASK,
+ IMX8Q_PHY_PIPE_RSTN_0_MASK);
+ } else if (imx8_phy->lane_id == 1) {
+ regmap_update_bits(imx8_phy->phy_gpr,
+ IMX8Q_PHY_CTRL0_OFFSET,
+ IMX8Q_PHY_CTRL0_APB_RSTN_1,
+ IMX8Q_PHY_CTRL0_APB_RSTN_1);
+ regmap_update_bits(imx8_phy->phy_gpr,
+ IMX8Q_PHY_CTRL0_OFFSET,
+ IMX8Q_PHY_PIPE_RSTN_1_MASK,
+ IMX8Q_PHY_PIPE_RSTN_1_MASK);
+ } else if (imx8_phy->lane_id == 2) {
+ regmap_update_bits(imx8_phy->phy_gpr,
+ IMX8Q_PHY_CTRL0_OFFSET,
+ IMX8Q_PHY_CTRL0_APB_RSTN_0,
+ IMX8Q_PHY_CTRL0_APB_RSTN_0);
+ }
+
+ regmap_update_bits(imx8_phy->misc_gpr, IMX8Q_MISC_CTRL0_OFFSET,
+ IMX8Q_MISC_PCIE_AB_SELECT, IMX8Q_MISC_PCIE_AB_SELECT);
+ regmap_update_bits(imx8_phy->misc_gpr, IMX8Q_MISC_CTRL0_OFFSET,
+ IMX8Q_MISC_PHYX1_EPCS_SEL, IMX8Q_MISC_PHYX1_EPCS_SEL);
+ } else if (imx8_phy->hsio_cfg == PCIEAX2PCIEBX1) {
+ if (imx8_phy->lane_id == 0) {
+ regmap_update_bits(imx8_phy->phy_gpr,
+ IMX8Q_PHY_CTRL0_OFFSET,
+ IMX8Q_PHYX2_CTRL0_APB_MASK,
+ IMX8Q_PHY_CTRL0_APB_RSTN_0 |
+ IMX8Q_PHY_CTRL0_APB_RSTN_1);
+ regmap_update_bits(imx8_phy->phy_gpr,
+ IMX8Q_PHY_CTRL0_OFFSET,
+ IMX8Q_PHY_PIPE_RSTN_0_MASK |
+ IMX8Q_PHY_PIPE_RSTN_1_MASK,
+ IMX8Q_PHY_PIPE_RSTN_0_MASK |
+ IMX8Q_PHY_PIPE_RSTN_1_MASK);
+ } else if (imx8_phy->lane_id == 2) {
+ regmap_update_bits(imx8_phy->phy_gpr,
+ IMX8Q_PHY_CTRL0_OFFSET,
+ IMX8Q_PHY_CTRL0_APB_RSTN_0,
+ IMX8Q_PHY_CTRL0_APB_RSTN_0);
+ regmap_update_bits(imx8_phy->phy_gpr,
+ IMX8Q_PHY_CTRL0_OFFSET,
+ IMX8Q_PHY_PIPE_RSTN_0_MASK,
+ IMX8Q_PHY_PIPE_RSTN_0_MASK);
+ }
+
+ regmap_update_bits(imx8_phy->misc_gpr, IMX8Q_MISC_CTRL0_OFFSET,
+ IMX8Q_MISC_PHYX1_EPCS_SEL, 0);
+ regmap_update_bits(imx8_phy->misc_gpr, IMX8Q_MISC_CTRL0_OFFSET,
+ IMX8Q_MISC_PCIE_AB_SELECT, IMX8Q_MISC_PCIE_AB_SELECT);
+ }
+
+ imx8q_pcie_phy_set_clock_mode(phy);
+
+ if (imx8_phy->mode == IMX8Q_PHY_SATA_MODE) {
+ regmap_update_bits(imx8_phy->ctrl_gpr, IMX8Q_SATA_CTRL0_OFFSET,
+ IMX8Q_SATA_CTRL_EPCS_TXDEEMP,
+ IMX8Q_SATA_CTRL_EPCS_TXDEEMP);
+ regmap_update_bits(imx8_phy->ctrl_gpr, IMX8Q_SATA_CTRL0_OFFSET,
+ IMX8Q_SATA_CTRL_EPCS_TXDEEMP_SEL,
+ IMX8Q_SATA_CTRL_EPCS_TXDEEMP_SEL);
+
+ imx8q_pcie_phy_reset_sata(phy);
+ } else {
+ ret = clk_prepare_enable(imx8_phy->apb_pclk);
+ if (ret) {
+ dev_err(imx8_phy->dev, "can't enable apb_pclk clock\n");
+ return ret;
+ }
+ ret = clk_prepare_enable(imx8_phy->pipe_pclk);
+ if (ret) {
+ dev_err(imx8_phy->dev, "can't enable pipe_pclk clock\n");
+ clk_disable_unprepare(imx8_phy->apb_pclk);
+ return ret;
+ }
+
+ /* Bit19 PM_REQ_CORE_RST of PCIe_STTS0 should be cleared. */
+ ret = regmap_read_poll_timeout(imx8_phy->ctrl_gpr,
+ IMX8Q_PCIE_STTS0_OFFSET, val,
+ (val & IMX8Q_CTRL_STTS0_PM_REQ_CORE_RST) == 0,
+ PHY_INIT_WAIT_USLEEP_MAX,
+ PHY_INIT_WAIT_TIMEOUT);
+ if (ret) {
+ dev_err(imx8_phy->dev, "PM_REQ_CORE_RST is set\n");
+ goto err_exit;
+ }
+ }
+
+ /* Polling to check the PHY is ready or not. */
+ if (imx8_phy->lane_id == 1)
+ cond = IMX8Q_STTS0_LANE1_TX_PLL_LOCK;
+ else
+ cond = IMX8Q_STTS0_LANE0_TX_PLL_LOCK;
+
+ ret = regmap_read_poll_timeout(imx8_phy->phy_gpr,
+ IMX8Q_PHY_STTS0_OFFSET, val, ((val & cond) == cond),
+ PHY_INIT_WAIT_USLEEP_MAX, PHY_INIT_WAIT_TIMEOUT);
+ if (ret) {
+ dev_err(imx8_phy->dev, "PHY PLL lock timeout\n");
+ goto err_exit;
+ } else {
+ dev_info(imx8_phy->dev, "PHY PLL is locked\n");
+ }
+
+ if (imx8_phy->mode == IMX8Q_PHY_SATA_MODE) {
+ cond = IMX8Q_PHY_REG48_PMA_RDY;
+ ret = read_poll_timeout(readb, val, ((val & cond) == cond),
+ PHY_INIT_WAIT_USLEEP_MAX,
+ PHY_INIT_WAIT_TIMEOUT, false,
+ imx8_phy->base + IMX8Q_PHY_REG48_PMA_STATUS);
+ if (ret)
+ dev_err(imx8_phy->dev, "PHY calibration is timeout\n");
+ else
+ dev_info(imx8_phy->dev, "PHY calibration is done\n");
+ }
+
+ return ret;
+
+err_exit:
+ if (imx8_phy->mode == IMX8Q_PHY_PCIE_MODE) {
+ clk_disable_unprepare(imx8_phy->pipe_pclk);
+ clk_disable_unprepare(imx8_phy->apb_pclk);
+ }
+
+ return ret;
+}
+
+static int imx8q_pcie_phy_power_off(struct phy *phy)
+{
+ struct imx8q_pcie_phy *imx8_phy = phy_get_drvdata(phy);
+
+ if (imx8_phy->mode == IMX8Q_PHY_PCIE_MODE) {
+ clk_disable_unprepare(imx8_phy->pipe_pclk);
+ clk_disable_unprepare(imx8_phy->apb_pclk);
+ }
+
+ return 0;
+}
+
+static const struct phy_ops imx8q_pcie_phy_ops = {
+ .init = imx8q_pcie_phy_init,
+ .exit = imx8q_pcie_phy_exit,
+ .power_on = imx8q_pcie_phy_power_on,
+ .power_off = imx8q_pcie_phy_power_off,
+ .owner = THIS_MODULE,
+};
+
+static const struct of_device_id imx8q_pcie_phy_of_match[] = {
+ {.compatible = "fsl,imx8qm-pcie-phy", },
+ { },
+};
+
+MODULE_DEVICE_TABLE(of, imx8q_pcie_phy_of_match);
+
+static int imx8q_pcie_phy_probe(struct platform_device *pdev)
+{
+ int ret;
+ struct device *dev = &pdev->dev;
+ struct device_node *np = dev->of_node;
+ struct imx8q_pcie_phy *imx8_phy;
+ const struct of_device_id *of_id;
+ struct phy_provider *phy_provider;
+ struct resource *res;
+
+ of_id = of_match_device(imx8q_pcie_phy_of_match, dev);
+ if (!of_id)
+ return -EINVAL;
+
+ imx8_phy = devm_kzalloc(dev, sizeof(*imx8_phy), GFP_KERNEL);
+ if (!imx8_phy)
+ return -ENOMEM;
+
+ imx8_phy->dev = dev;
+
+ /* Get PHY refclk pad mode */
+ of_property_read_u32(np, "fsl,refclk-pad-mode",
+ &imx8_phy->refclk_pad_mode);
+
+ /* Get HSIO configuration mode */
+ if (of_property_read_u32(np, "hsio-cfg", &imx8_phy->hsio_cfg))
+ imx8_phy->hsio_cfg = 0;
+
+ res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
+ imx8_phy->base = devm_ioremap_resource(dev, res);
+ if (IS_ERR(imx8_phy->base))
+ return PTR_ERR(imx8_phy->base);
+
+ if (res->start == IMX8Q_PHYX2_LANE1_BASE_ADDR)
+ imx8_phy->lane_id = 1;
+ else if (res->start == IMX8Q_PHYX1_LANE0_BASE_ADDR)
+ imx8_phy->lane_id = 2;
+
+ if (unlikely((imx8_phy->lane_id == 2) &&
+ (imx8_phy->hsio_cfg != PCIEAX2PCIEBX1)))
+ imx8_phy->mode = IMX8Q_PHY_SATA_MODE;
+ else
+ imx8_phy->mode = IMX8Q_PHY_PCIE_MODE;
+
+ /* Fetch clocks */
+ if (imx8_phy->mode == IMX8Q_PHY_PCIE_MODE) {
+ /* APB clock is not required by SATA */
+ imx8_phy->apb_pclk = devm_clk_get(dev, "apb_pclk");
+ if (IS_ERR(imx8_phy->apb_pclk))
+ return dev_err_probe(dev, PTR_ERR(imx8_phy->apb_pclk),
+ "can't get apb_pclk clock\n");
+ }
+
+ imx8_phy->ctrl_ips_clk = devm_clk_get(dev, "ctrl_ips_clk");
+ if (IS_ERR(imx8_phy->ctrl_ips_clk))
+ return dev_err_probe(dev, PTR_ERR(imx8_phy->ctrl_ips_clk),
+ "can't get ctrl_ips_clk clock\n");
+
+ imx8_phy->misc_ips_clk = devm_clk_get(dev, "misc_ips_clk");
+ if (IS_ERR(imx8_phy->misc_ips_clk))
+ return dev_err_probe(dev, PTR_ERR(imx8_phy->misc_ips_clk),
+ "can't get misc_ips_clk clock\n");
+
+ imx8_phy->pipe_pclk = devm_clk_get(dev, "pipe_pclk");
+ if (IS_ERR(imx8_phy->pipe_pclk))
+ return dev_err_probe(dev, PTR_ERR(imx8_phy->pipe_pclk),
+ "can't get pipe_pclk clock\n");
+
+ imx8_phy->phy_ips_clk = devm_clk_get(dev, "phy_ips_clk");
+ if (IS_ERR(imx8_phy->phy_ips_clk))
+ return dev_err_probe(dev, PTR_ERR(imx8_phy->phy_ips_clk),
+ "can't get phy_ips_clk clock\n");
+
+ /* Grab GPR config register range */
+ imx8_phy->ctrl_gpr = syscon_regmap_lookup_by_phandle(np, "ctrl-csr");
+ if (IS_ERR(imx8_phy->ctrl_gpr))
+ return dev_err_probe(dev, PTR_ERR(imx8_phy->ctrl_gpr),
+ "can't get hsio ctrl registers\n");
+
+ imx8_phy->misc_gpr = syscon_regmap_lookup_by_phandle(np, "misc-csr");
+ if (IS_ERR(imx8_phy->misc_gpr))
+ return dev_err_probe(dev, PTR_ERR(imx8_phy->misc_gpr),
+ "can't get hsio misc registers\n");
+
+ imx8_phy->phy_gpr = syscon_regmap_lookup_by_phandle(np, "phy-csr");
+ if (IS_ERR(imx8_phy->phy_gpr))
+ return dev_err_probe(dev, PTR_ERR(imx8_phy->phy_gpr),
+ "can't get hsio phy registers\n");
+
+ pm_runtime_set_active(dev);
+ pm_runtime_enable(dev);
+
+ imx8_phy->phy = devm_phy_create(dev, NULL, &imx8q_pcie_phy_ops);
+ if (IS_ERR(imx8_phy->phy)) {
+ ret = PTR_ERR(imx8_phy->phy);
+ goto err_exit;
+ }
+
+ phy_set_drvdata(imx8_phy->phy, imx8_phy);
+
+ phy_provider = devm_of_phy_provider_register(dev, of_phy_simple_xlate);
+
+ ret = PTR_ERR_OR_ZERO(phy_provider);
+ if (ret < 0)
+ goto err_exit;
+
+ return ret;
+
+err_exit:
+ pm_runtime_disable(dev);
+ pm_runtime_set_suspended(dev);
+
+ return ret;
+}
+
+static struct platform_driver imx8q_pcie_phy_driver = {
+ .probe = imx8q_pcie_phy_probe,
+ .driver = {
+ .name = "imx8q-pcie-phy",
+ .of_match_table = imx8q_pcie_phy_of_match,
+ }
+};
+module_platform_driver(imx8q_pcie_phy_driver);
+
+MODULE_DESCRIPTION("FSL IMX8Q PCIE PHY driver");
+MODULE_LICENSE("GPL");
--
2.34.1
^ permalink raw reply related [flat|nested] 30+ messages in thread
* [PATCH v1 3/3] phy: freescale: imx8q-pcie: Add i.MX8Q PCIe PHY driver
@ 2023-08-29 6:45 ` Richard Zhu
0 siblings, 0 replies; 30+ messages in thread
From: Richard Zhu @ 2023-08-29 6:45 UTC (permalink / raw)
To: vkoul, kishon, robh+dt, krzysztof.kozlowski+dt, conor+dt,
shawnguo, s.hauer, festevam, l.stach, a.fatoum, u.kleine-koenig
Cc: hongxing.zhu, linux-phy, devicetree, linux-arm-kernel,
linux-kernel, kernel, linux-imx
i.MX8QM HSIO(High Speed IO) module has three instances of single lane
SERDES PHYs, an instance of two lanes PCIe GEN3 controller, an
instance of single lane PCIe GEN3 controller, as well as an instance
of SATA 3.0 controller.
The HSIO module can be configured as the following different usecases.
1 - A two lanes PCIea and a single lane SATA.
2 - A single lane PCIea, a single lane PCIeb and a single lane SATA.
3 - A two lanes PCIea, a single lane PCIeb.
Add i.MX8Q PCIe PHY driver to support these different usecases.
- Add the runtime PM support, thus the PCIe PHY PD can be turned off
when PCIe probe is failed.
- The APB_PCLK is required only when PHY is configured as PCIE mode.
Note:
Although the RM document doesn't specify it, but the LPCG clocks should
be handled by a different procedure when the PHY is configured in PCIe
or SATA modes based on the practical oberservations.
When PHY is configured into PCIe mode.
- apb_pclk is mandatory required.
- apb_pclk and pipe_pclk should be enabled just before polling
PM_REQ_CORE_RST is cleared or not.
When PHY is configured as SATA mode.
- There is no apb_pclk.
- pipe_pclk should be enabled together with other LPCG clocks.
Signed-off-by: Richard Zhu <hongxing.zhu@nxp.com>
---
drivers/phy/freescale/Kconfig | 8 +
drivers/phy/freescale/Makefile | 1 +
drivers/phy/freescale/phy-fsl-imx8q-pcie.c | 562 +++++++++++++++++++++
3 files changed, 571 insertions(+)
create mode 100644 drivers/phy/freescale/phy-fsl-imx8q-pcie.c
diff --git a/drivers/phy/freescale/Kconfig b/drivers/phy/freescale/Kconfig
index 853958fb2c06..6f81fbf5f5e6 100644
--- a/drivers/phy/freescale/Kconfig
+++ b/drivers/phy/freescale/Kconfig
@@ -35,6 +35,14 @@ config PHY_FSL_IMX8M_PCIE
Enable this to add support for the PCIE PHY as found on
i.MX8M family of SOCs.
+config PHY_FSL_IMX8Q_PCIE
+ tristate "Freescale i.MX8Q PCIE PHY"
+ depends on OF && HAS_IOMEM
+ select GENERIC_PHY
+ help
+ Enable this to add support for the PCIE PHY as found on
+ i.MX8Q family of SOCs.
+
endif
config PHY_FSL_LYNX_28G
diff --git a/drivers/phy/freescale/Makefile b/drivers/phy/freescale/Makefile
index cedb328bc4d2..afa84807c40c 100644
--- a/drivers/phy/freescale/Makefile
+++ b/drivers/phy/freescale/Makefile
@@ -3,4 +3,5 @@ obj-$(CONFIG_PHY_FSL_IMX8MQ_USB) += phy-fsl-imx8mq-usb.o
obj-$(CONFIG_PHY_MIXEL_LVDS_PHY) += phy-fsl-imx8qm-lvds-phy.o
obj-$(CONFIG_PHY_MIXEL_MIPI_DPHY) += phy-fsl-imx8-mipi-dphy.o
obj-$(CONFIG_PHY_FSL_IMX8M_PCIE) += phy-fsl-imx8m-pcie.o
+obj-$(CONFIG_PHY_FSL_IMX8Q_PCIE) += phy-fsl-imx8q-pcie.o
obj-$(CONFIG_PHY_FSL_LYNX_28G) += phy-fsl-lynx-28g.o
diff --git a/drivers/phy/freescale/phy-fsl-imx8q-pcie.c b/drivers/phy/freescale/phy-fsl-imx8q-pcie.c
new file mode 100644
index 000000000000..3f1589628be1
--- /dev/null
+++ b/drivers/phy/freescale/phy-fsl-imx8q-pcie.c
@@ -0,0 +1,562 @@
+// SPDX-License-Identifier: GPL-2.0+
+/*
+ * Copyright 2023 NXP
+ */
+
+#include <linux/bitfield.h>
+#include <linux/clk.h>
+#include <linux/delay.h>
+#include <linux/io.h>
+#include <linux/iopoll.h>
+#include <linux/mfd/syscon.h>
+#include <linux/module.h>
+#include <linux/of_address.h>
+#include <linux/of_device.h>
+#include <linux/phy/phy.h>
+#include <linux/platform_device.h>
+#include <linux/regmap.h>
+
+#include <dt-bindings/phy/phy-imx8-pcie.h>
+
+/* i.MX8Q HSIO registers */
+#define IMX8Q_PHY_CTRL0_OFFSET 0x0
+#define IMX8Q_PHYX2_CTRL0_APB_MASK GENMASK(1, 0)
+#define IMX8Q_PHY_CTRL0_APB_RSTN_0 BIT(0)
+#define IMX8Q_PHY_CTRL0_APB_RSTN_1 BIT(1)
+#define IMX8Q_PHY_MODE_MASK GENMASK(20, 17)
+#define IMX8Q_PHY_MODE_SATA BIT(19)
+#define IMX8Q_PHY_PIPE_RSTN_0_MASK GENMASK(25, 24)
+#define IMX8Q_PHY_PIPE_RSTN_1_MASK GENMASK(27, 26)
+
+#define IMX8Q_PHY_STTS0_OFFSET 0x4
+#define IMX8Q_STTS0_LANE0_TX_PLL_LOCK BIT(4)
+#define IMX8Q_STTS0_LANE1_TX_PLL_LOCK BIT(12)
+
+#define IMX8Q_PCIE_CTRL2_OFFSET 0x8
+#define IMX8Q_CTRL_BUTTON_RST_N BIT(21)
+#define IMX8Q_CTRL_PERST_N BIT(22)
+#define IMX8Q_CTRL_POWER_UP_RST_N BIT(23)
+
+#define IMX8Q_PCIE_STTS0_OFFSET 0xC
+#define IMX8Q_CTRL_STTS0_PM_REQ_CORE_RST BIT(19)
+
+#define IMX8Q_SATA_CTRL0_OFFSET 0x0
+#define IMX8Q_SATA_CTRL_EPCS_TXDEEMP BIT(5)
+#define IMX8Q_SATA_CTRL_EPCS_TXDEEMP_SEL BIT(6)
+#define IMX8Q_SATA_CTRL_EPCS_PHYRESET_N BIT(7)
+#define IMX8Q_SATA_CTRL_RESET_N BIT(12)
+
+#define IMX8Q_MISC_CTRL0_OFFSET 0x0
+#define IMX8Q_MISC_IOB_RXENA BIT(0)
+#define IMX8Q_MISC_IOB_TXENA BIT(1)
+#define IMX8Q_MISC_IOB_A_0_TXOE BIT(2)
+#define IMX8Q_MISC_IOB_A_0_M1M0_MASK GENMASK(4, 3)
+#define IMX8Q_MISC_IOB_A_0_M1M0_2 BIT(4)
+#define IMX8Q_MISC_PHYX1_EPCS_SEL BIT(12)
+#define IMX8Q_MISC_PCIE_AB_SELECT BIT(13)
+#define IMX8Q_MISC_CLKREQN_OUT_OVERRIDE_1 BIT(24)
+#define IMX8Q_MISC_CLKREQN_OUT_OVERRIDE_0 BIT(25)
+
+#define IMX8Q_PHY_REG48_PMA_STATUS 0x30
+#define IMX8Q_PHY_REG48_PMA_RDY BIT(7)
+
+#define IMX8Q_PHYX2_LANE1_BASE_ADDR 0x5F190000
+#define IMX8Q_PHYX1_LANE0_BASE_ADDR 0x5F1A0000
+
+/* Parameters for the waiting for PCIe PHY PLL to lock */
+#define PHY_INIT_WAIT_USLEEP_MAX 10
+#define PHY_INIT_WAIT_TIMEOUT (1000 * PHY_INIT_WAIT_USLEEP_MAX)
+
+enum imx8q_pcie_phy_mode {
+ IMX8Q_PHY_PCIE_MODE,
+ IMX8Q_PHY_SATA_MODE,
+};
+
+struct imx8q_pcie_phy {
+ void __iomem *base;
+ struct clk *apb_pclk;
+ struct clk *ctrl_ips_clk;
+ struct clk *misc_ips_clk;
+ struct clk *phy_ips_clk;
+ struct clk *pipe_pclk;
+ struct device *dev;
+ struct phy *phy;
+ struct regmap *ctrl_gpr;
+ struct regmap *misc_gpr;
+ struct regmap *phy_gpr;
+ u32 hsio_cfg;
+ u32 lane_id;
+ u32 refclk_pad_mode;
+ enum imx8q_pcie_phy_mode mode;
+};
+
+static int imx8q_pcie_phy_init(struct phy *phy)
+{
+ int ret;
+ struct imx8q_pcie_phy *imx8_phy = phy_get_drvdata(phy);
+
+ if (imx8_phy->mode == IMX8Q_PHY_SATA_MODE) {
+ ret = clk_prepare_enable(imx8_phy->pipe_pclk);
+ if (ret) {
+ dev_err(imx8_phy->dev, "can't enable pipe clock\n");
+ return ret;
+ }
+ }
+
+ ret = clk_prepare_enable(imx8_phy->ctrl_ips_clk);
+ if (ret) {
+ dev_err(imx8_phy->dev, "can't enable ctrl_ips clock\n");
+ goto err_ctrl_ips_clk;
+ }
+
+ ret = clk_prepare_enable(imx8_phy->phy_ips_clk);
+ if (ret) {
+ dev_err(imx8_phy->dev, "can't enable phy_ips clock\n");
+ goto err_phy_ips_clk;
+ }
+
+ ret = clk_prepare_enable(imx8_phy->misc_ips_clk);
+ if (ret) {
+ dev_err(imx8_phy->dev, "can't enable misc_ips clock\n");
+ goto err_misc_ips_clk;
+ }
+
+ /* allow the clocks to stabilize */
+ usleep_range(200, 500);
+
+ return ret;
+
+err_misc_ips_clk:
+ clk_disable_unprepare(imx8_phy->phy_ips_clk);
+err_phy_ips_clk:
+ clk_disable_unprepare(imx8_phy->ctrl_ips_clk);
+err_ctrl_ips_clk:
+ if (imx8_phy->mode == IMX8Q_PHY_SATA_MODE)
+ clk_disable_unprepare(imx8_phy->pipe_pclk);
+
+ return ret;
+}
+
+static int imx8q_pcie_phy_exit(struct phy *phy)
+{
+ struct imx8q_pcie_phy *imx8_phy = phy_get_drvdata(phy);
+
+ clk_disable_unprepare(imx8_phy->misc_ips_clk);
+ clk_disable_unprepare(imx8_phy->phy_ips_clk);
+ clk_disable_unprepare(imx8_phy->ctrl_ips_clk);
+ if (imx8_phy->mode == IMX8Q_PHY_SATA_MODE)
+ clk_disable_unprepare(imx8_phy->pipe_pclk);
+
+ return 0;
+}
+
+static void imx8q_pcie_phy_reset_pcie(struct phy *phy)
+{
+ struct imx8q_pcie_phy *imx8_phy = phy_get_drvdata(phy);
+
+ regmap_update_bits(imx8_phy->ctrl_gpr, IMX8Q_PCIE_CTRL2_OFFSET,
+ IMX8Q_CTRL_BUTTON_RST_N, 0);
+ regmap_update_bits(imx8_phy->ctrl_gpr, IMX8Q_PCIE_CTRL2_OFFSET,
+ IMX8Q_CTRL_PERST_N, 0);
+ regmap_update_bits(imx8_phy->ctrl_gpr, IMX8Q_PCIE_CTRL2_OFFSET,
+ IMX8Q_CTRL_POWER_UP_RST_N, 0);
+ mdelay(1);
+ regmap_update_bits(imx8_phy->ctrl_gpr, IMX8Q_PCIE_CTRL2_OFFSET,
+ IMX8Q_CTRL_BUTTON_RST_N, IMX8Q_CTRL_BUTTON_RST_N);
+ regmap_update_bits(imx8_phy->ctrl_gpr, IMX8Q_PCIE_CTRL2_OFFSET,
+ IMX8Q_CTRL_PERST_N, IMX8Q_CTRL_PERST_N);
+ regmap_update_bits(imx8_phy->ctrl_gpr, IMX8Q_PCIE_CTRL2_OFFSET,
+ IMX8Q_CTRL_POWER_UP_RST_N, IMX8Q_CTRL_POWER_UP_RST_N);
+}
+
+static void imx8q_pcie_phy_set_clock_mode(struct phy *phy)
+{
+ u32 pad_mode;
+ struct imx8q_pcie_phy *imx8_phy = phy_get_drvdata(phy);
+
+ pad_mode = imx8_phy->refclk_pad_mode;
+ if (pad_mode == IMX8_PCIE_REFCLK_PAD_INPUT ||
+ pad_mode == IMX8_PCIE_REFCLK_PAD_UNUSED) {
+ /* Configure the PAD as input mode */
+ regmap_update_bits(imx8_phy->misc_gpr, IMX8Q_MISC_CTRL0_OFFSET,
+ IMX8Q_MISC_IOB_RXENA, IMX8Q_MISC_IOB_RXENA);
+ regmap_update_bits(imx8_phy->misc_gpr, IMX8Q_MISC_CTRL0_OFFSET,
+ IMX8Q_MISC_IOB_TXENA, 0);
+ usleep_range(200, 500);
+ } else {
+ /* Configure the PHY to output the refclock via PAD */
+ regmap_update_bits(imx8_phy->misc_gpr, IMX8Q_MISC_CTRL0_OFFSET,
+ IMX8Q_MISC_IOB_RXENA, 0);
+ regmap_update_bits(imx8_phy->misc_gpr, IMX8Q_MISC_CTRL0_OFFSET,
+ IMX8Q_MISC_IOB_TXENA, IMX8Q_MISC_IOB_TXENA);
+ regmap_update_bits(imx8_phy->misc_gpr, IMX8Q_MISC_CTRL0_OFFSET,
+ IMX8Q_MISC_IOB_A_0_TXOE | IMX8Q_MISC_IOB_A_0_M1M0_MASK,
+ IMX8Q_MISC_IOB_A_0_TXOE | IMX8Q_MISC_IOB_A_0_M1M0_2);
+ }
+}
+
+static void imx8q_pcie_phy_reset_sata(struct phy *phy)
+{
+ struct imx8q_pcie_phy *imx8_phy = phy_get_drvdata(phy);
+
+ /* clear PHY RST, then set it */
+ regmap_update_bits(imx8_phy->ctrl_gpr, IMX8Q_SATA_CTRL0_OFFSET,
+ IMX8Q_SATA_CTRL_EPCS_PHYRESET_N, 0);
+
+ regmap_update_bits(imx8_phy->ctrl_gpr, IMX8Q_SATA_CTRL0_OFFSET,
+ IMX8Q_SATA_CTRL_EPCS_PHYRESET_N,
+ IMX8Q_SATA_CTRL_EPCS_PHYRESET_N);
+
+ /* CTRL RST: SET -> delay 1 us -> CLEAR -> SET */
+ regmap_update_bits(imx8_phy->ctrl_gpr, IMX8Q_SATA_CTRL0_OFFSET,
+ IMX8Q_SATA_CTRL_RESET_N, IMX8Q_SATA_CTRL_RESET_N);
+ udelay(1);
+ regmap_update_bits(imx8_phy->ctrl_gpr, IMX8Q_SATA_CTRL0_OFFSET,
+ IMX8Q_SATA_CTRL_RESET_N, 0);
+ regmap_update_bits(imx8_phy->ctrl_gpr, IMX8Q_SATA_CTRL0_OFFSET,
+ IMX8Q_SATA_CTRL_RESET_N, IMX8Q_SATA_CTRL_RESET_N);
+
+ usleep_range(50, 100);
+}
+
+static int imx8q_pcie_phy_power_on(struct phy *phy)
+{
+ int ret;
+ u32 val, cond;
+ struct imx8q_pcie_phy *imx8_phy = phy_get_drvdata(phy);
+
+ if (imx8_phy->mode == IMX8Q_PHY_SATA_MODE) {
+ /* SATA mode PHY */
+ regmap_update_bits(imx8_phy->phy_gpr, IMX8Q_PHY_CTRL0_OFFSET,
+ IMX8Q_PHY_MODE_MASK, IMX8Q_PHY_MODE_SATA);
+ /*
+ * It is possible, for PCIe and SATA are sharing
+ * the same clock source, HPLL or external oscillator.
+ * When PCIe is in low power modes (L1.X or L2 etc),
+ * the clock source can be turned off. In this case,
+ * if this clock source is required to be toggling by
+ * SATA, then SATA functions will be abnormal.
+ * Set the override here to avoid it.
+ */
+ regmap_update_bits(imx8_phy->misc_gpr, IMX8Q_MISC_CTRL0_OFFSET,
+ IMX8Q_MISC_CLKREQN_OUT_OVERRIDE_1 |
+ IMX8Q_MISC_CLKREQN_OUT_OVERRIDE_0,
+ IMX8Q_MISC_CLKREQN_OUT_OVERRIDE_1 |
+ IMX8Q_MISC_CLKREQN_OUT_OVERRIDE_0);
+ } else {
+ /* PCIe mode PHY */
+ imx8q_pcie_phy_reset_pcie(phy);
+ }
+
+ if (imx8_phy->hsio_cfg == PCIEAX2SATA) {
+ if (imx8_phy->lane_id == 0) {
+ regmap_update_bits(imx8_phy->phy_gpr,
+ IMX8Q_PHY_CTRL0_OFFSET,
+ IMX8Q_PHYX2_CTRL0_APB_MASK,
+ IMX8Q_PHY_CTRL0_APB_RSTN_0 |
+ IMX8Q_PHY_CTRL0_APB_RSTN_1);
+ regmap_update_bits(imx8_phy->phy_gpr,
+ IMX8Q_PHY_CTRL0_OFFSET,
+ IMX8Q_PHY_PIPE_RSTN_0_MASK |
+ IMX8Q_PHY_PIPE_RSTN_1_MASK,
+ IMX8Q_PHY_PIPE_RSTN_0_MASK |
+ IMX8Q_PHY_PIPE_RSTN_1_MASK);
+ } else if (imx8_phy->lane_id == 2) {
+ regmap_update_bits(imx8_phy->phy_gpr,
+ IMX8Q_PHY_CTRL0_OFFSET,
+ IMX8Q_PHY_CTRL0_APB_RSTN_0,
+ IMX8Q_PHY_CTRL0_APB_RSTN_0);
+ }
+
+ regmap_update_bits(imx8_phy->misc_gpr, IMX8Q_MISC_CTRL0_OFFSET,
+ IMX8Q_MISC_PHYX1_EPCS_SEL, IMX8Q_MISC_PHYX1_EPCS_SEL);
+ regmap_update_bits(imx8_phy->misc_gpr, IMX8Q_MISC_CTRL0_OFFSET,
+ IMX8Q_MISC_PCIE_AB_SELECT, 0);
+ } else if (imx8_phy->hsio_cfg == PCIEAX1PCIEBX1SATA) {
+ if (imx8_phy->lane_id == 0) {
+ regmap_update_bits(imx8_phy->phy_gpr,
+ IMX8Q_PHY_CTRL0_OFFSET,
+ IMX8Q_PHY_CTRL0_APB_RSTN_0,
+ IMX8Q_PHY_CTRL0_APB_RSTN_0);
+ regmap_update_bits(imx8_phy->phy_gpr,
+ IMX8Q_PHY_CTRL0_OFFSET,
+ IMX8Q_PHY_PIPE_RSTN_0_MASK,
+ IMX8Q_PHY_PIPE_RSTN_0_MASK);
+ } else if (imx8_phy->lane_id == 1) {
+ regmap_update_bits(imx8_phy->phy_gpr,
+ IMX8Q_PHY_CTRL0_OFFSET,
+ IMX8Q_PHY_CTRL0_APB_RSTN_1,
+ IMX8Q_PHY_CTRL0_APB_RSTN_1);
+ regmap_update_bits(imx8_phy->phy_gpr,
+ IMX8Q_PHY_CTRL0_OFFSET,
+ IMX8Q_PHY_PIPE_RSTN_1_MASK,
+ IMX8Q_PHY_PIPE_RSTN_1_MASK);
+ } else if (imx8_phy->lane_id == 2) {
+ regmap_update_bits(imx8_phy->phy_gpr,
+ IMX8Q_PHY_CTRL0_OFFSET,
+ IMX8Q_PHY_CTRL0_APB_RSTN_0,
+ IMX8Q_PHY_CTRL0_APB_RSTN_0);
+ }
+
+ regmap_update_bits(imx8_phy->misc_gpr, IMX8Q_MISC_CTRL0_OFFSET,
+ IMX8Q_MISC_PCIE_AB_SELECT, IMX8Q_MISC_PCIE_AB_SELECT);
+ regmap_update_bits(imx8_phy->misc_gpr, IMX8Q_MISC_CTRL0_OFFSET,
+ IMX8Q_MISC_PHYX1_EPCS_SEL, IMX8Q_MISC_PHYX1_EPCS_SEL);
+ } else if (imx8_phy->hsio_cfg == PCIEAX2PCIEBX1) {
+ if (imx8_phy->lane_id == 0) {
+ regmap_update_bits(imx8_phy->phy_gpr,
+ IMX8Q_PHY_CTRL0_OFFSET,
+ IMX8Q_PHYX2_CTRL0_APB_MASK,
+ IMX8Q_PHY_CTRL0_APB_RSTN_0 |
+ IMX8Q_PHY_CTRL0_APB_RSTN_1);
+ regmap_update_bits(imx8_phy->phy_gpr,
+ IMX8Q_PHY_CTRL0_OFFSET,
+ IMX8Q_PHY_PIPE_RSTN_0_MASK |
+ IMX8Q_PHY_PIPE_RSTN_1_MASK,
+ IMX8Q_PHY_PIPE_RSTN_0_MASK |
+ IMX8Q_PHY_PIPE_RSTN_1_MASK);
+ } else if (imx8_phy->lane_id == 2) {
+ regmap_update_bits(imx8_phy->phy_gpr,
+ IMX8Q_PHY_CTRL0_OFFSET,
+ IMX8Q_PHY_CTRL0_APB_RSTN_0,
+ IMX8Q_PHY_CTRL0_APB_RSTN_0);
+ regmap_update_bits(imx8_phy->phy_gpr,
+ IMX8Q_PHY_CTRL0_OFFSET,
+ IMX8Q_PHY_PIPE_RSTN_0_MASK,
+ IMX8Q_PHY_PIPE_RSTN_0_MASK);
+ }
+
+ regmap_update_bits(imx8_phy->misc_gpr, IMX8Q_MISC_CTRL0_OFFSET,
+ IMX8Q_MISC_PHYX1_EPCS_SEL, 0);
+ regmap_update_bits(imx8_phy->misc_gpr, IMX8Q_MISC_CTRL0_OFFSET,
+ IMX8Q_MISC_PCIE_AB_SELECT, IMX8Q_MISC_PCIE_AB_SELECT);
+ }
+
+ imx8q_pcie_phy_set_clock_mode(phy);
+
+ if (imx8_phy->mode == IMX8Q_PHY_SATA_MODE) {
+ regmap_update_bits(imx8_phy->ctrl_gpr, IMX8Q_SATA_CTRL0_OFFSET,
+ IMX8Q_SATA_CTRL_EPCS_TXDEEMP,
+ IMX8Q_SATA_CTRL_EPCS_TXDEEMP);
+ regmap_update_bits(imx8_phy->ctrl_gpr, IMX8Q_SATA_CTRL0_OFFSET,
+ IMX8Q_SATA_CTRL_EPCS_TXDEEMP_SEL,
+ IMX8Q_SATA_CTRL_EPCS_TXDEEMP_SEL);
+
+ imx8q_pcie_phy_reset_sata(phy);
+ } else {
+ ret = clk_prepare_enable(imx8_phy->apb_pclk);
+ if (ret) {
+ dev_err(imx8_phy->dev, "can't enable apb_pclk clock\n");
+ return ret;
+ }
+ ret = clk_prepare_enable(imx8_phy->pipe_pclk);
+ if (ret) {
+ dev_err(imx8_phy->dev, "can't enable pipe_pclk clock\n");
+ clk_disable_unprepare(imx8_phy->apb_pclk);
+ return ret;
+ }
+
+ /* Bit19 PM_REQ_CORE_RST of PCIe_STTS0 should be cleared. */
+ ret = regmap_read_poll_timeout(imx8_phy->ctrl_gpr,
+ IMX8Q_PCIE_STTS0_OFFSET, val,
+ (val & IMX8Q_CTRL_STTS0_PM_REQ_CORE_RST) == 0,
+ PHY_INIT_WAIT_USLEEP_MAX,
+ PHY_INIT_WAIT_TIMEOUT);
+ if (ret) {
+ dev_err(imx8_phy->dev, "PM_REQ_CORE_RST is set\n");
+ goto err_exit;
+ }
+ }
+
+ /* Polling to check the PHY is ready or not. */
+ if (imx8_phy->lane_id == 1)
+ cond = IMX8Q_STTS0_LANE1_TX_PLL_LOCK;
+ else
+ cond = IMX8Q_STTS0_LANE0_TX_PLL_LOCK;
+
+ ret = regmap_read_poll_timeout(imx8_phy->phy_gpr,
+ IMX8Q_PHY_STTS0_OFFSET, val, ((val & cond) == cond),
+ PHY_INIT_WAIT_USLEEP_MAX, PHY_INIT_WAIT_TIMEOUT);
+ if (ret) {
+ dev_err(imx8_phy->dev, "PHY PLL lock timeout\n");
+ goto err_exit;
+ } else {
+ dev_info(imx8_phy->dev, "PHY PLL is locked\n");
+ }
+
+ if (imx8_phy->mode == IMX8Q_PHY_SATA_MODE) {
+ cond = IMX8Q_PHY_REG48_PMA_RDY;
+ ret = read_poll_timeout(readb, val, ((val & cond) == cond),
+ PHY_INIT_WAIT_USLEEP_MAX,
+ PHY_INIT_WAIT_TIMEOUT, false,
+ imx8_phy->base + IMX8Q_PHY_REG48_PMA_STATUS);
+ if (ret)
+ dev_err(imx8_phy->dev, "PHY calibration is timeout\n");
+ else
+ dev_info(imx8_phy->dev, "PHY calibration is done\n");
+ }
+
+ return ret;
+
+err_exit:
+ if (imx8_phy->mode == IMX8Q_PHY_PCIE_MODE) {
+ clk_disable_unprepare(imx8_phy->pipe_pclk);
+ clk_disable_unprepare(imx8_phy->apb_pclk);
+ }
+
+ return ret;
+}
+
+static int imx8q_pcie_phy_power_off(struct phy *phy)
+{
+ struct imx8q_pcie_phy *imx8_phy = phy_get_drvdata(phy);
+
+ if (imx8_phy->mode == IMX8Q_PHY_PCIE_MODE) {
+ clk_disable_unprepare(imx8_phy->pipe_pclk);
+ clk_disable_unprepare(imx8_phy->apb_pclk);
+ }
+
+ return 0;
+}
+
+static const struct phy_ops imx8q_pcie_phy_ops = {
+ .init = imx8q_pcie_phy_init,
+ .exit = imx8q_pcie_phy_exit,
+ .power_on = imx8q_pcie_phy_power_on,
+ .power_off = imx8q_pcie_phy_power_off,
+ .owner = THIS_MODULE,
+};
+
+static const struct of_device_id imx8q_pcie_phy_of_match[] = {
+ {.compatible = "fsl,imx8qm-pcie-phy", },
+ { },
+};
+
+MODULE_DEVICE_TABLE(of, imx8q_pcie_phy_of_match);
+
+static int imx8q_pcie_phy_probe(struct platform_device *pdev)
+{
+ int ret;
+ struct device *dev = &pdev->dev;
+ struct device_node *np = dev->of_node;
+ struct imx8q_pcie_phy *imx8_phy;
+ const struct of_device_id *of_id;
+ struct phy_provider *phy_provider;
+ struct resource *res;
+
+ of_id = of_match_device(imx8q_pcie_phy_of_match, dev);
+ if (!of_id)
+ return -EINVAL;
+
+ imx8_phy = devm_kzalloc(dev, sizeof(*imx8_phy), GFP_KERNEL);
+ if (!imx8_phy)
+ return -ENOMEM;
+
+ imx8_phy->dev = dev;
+
+ /* Get PHY refclk pad mode */
+ of_property_read_u32(np, "fsl,refclk-pad-mode",
+ &imx8_phy->refclk_pad_mode);
+
+ /* Get HSIO configuration mode */
+ if (of_property_read_u32(np, "hsio-cfg", &imx8_phy->hsio_cfg))
+ imx8_phy->hsio_cfg = 0;
+
+ res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
+ imx8_phy->base = devm_ioremap_resource(dev, res);
+ if (IS_ERR(imx8_phy->base))
+ return PTR_ERR(imx8_phy->base);
+
+ if (res->start == IMX8Q_PHYX2_LANE1_BASE_ADDR)
+ imx8_phy->lane_id = 1;
+ else if (res->start == IMX8Q_PHYX1_LANE0_BASE_ADDR)
+ imx8_phy->lane_id = 2;
+
+ if (unlikely((imx8_phy->lane_id == 2) &&
+ (imx8_phy->hsio_cfg != PCIEAX2PCIEBX1)))
+ imx8_phy->mode = IMX8Q_PHY_SATA_MODE;
+ else
+ imx8_phy->mode = IMX8Q_PHY_PCIE_MODE;
+
+ /* Fetch clocks */
+ if (imx8_phy->mode == IMX8Q_PHY_PCIE_MODE) {
+ /* APB clock is not required by SATA */
+ imx8_phy->apb_pclk = devm_clk_get(dev, "apb_pclk");
+ if (IS_ERR(imx8_phy->apb_pclk))
+ return dev_err_probe(dev, PTR_ERR(imx8_phy->apb_pclk),
+ "can't get apb_pclk clock\n");
+ }
+
+ imx8_phy->ctrl_ips_clk = devm_clk_get(dev, "ctrl_ips_clk");
+ if (IS_ERR(imx8_phy->ctrl_ips_clk))
+ return dev_err_probe(dev, PTR_ERR(imx8_phy->ctrl_ips_clk),
+ "can't get ctrl_ips_clk clock\n");
+
+ imx8_phy->misc_ips_clk = devm_clk_get(dev, "misc_ips_clk");
+ if (IS_ERR(imx8_phy->misc_ips_clk))
+ return dev_err_probe(dev, PTR_ERR(imx8_phy->misc_ips_clk),
+ "can't get misc_ips_clk clock\n");
+
+ imx8_phy->pipe_pclk = devm_clk_get(dev, "pipe_pclk");
+ if (IS_ERR(imx8_phy->pipe_pclk))
+ return dev_err_probe(dev, PTR_ERR(imx8_phy->pipe_pclk),
+ "can't get pipe_pclk clock\n");
+
+ imx8_phy->phy_ips_clk = devm_clk_get(dev, "phy_ips_clk");
+ if (IS_ERR(imx8_phy->phy_ips_clk))
+ return dev_err_probe(dev, PTR_ERR(imx8_phy->phy_ips_clk),
+ "can't get phy_ips_clk clock\n");
+
+ /* Grab GPR config register range */
+ imx8_phy->ctrl_gpr = syscon_regmap_lookup_by_phandle(np, "ctrl-csr");
+ if (IS_ERR(imx8_phy->ctrl_gpr))
+ return dev_err_probe(dev, PTR_ERR(imx8_phy->ctrl_gpr),
+ "can't get hsio ctrl registers\n");
+
+ imx8_phy->misc_gpr = syscon_regmap_lookup_by_phandle(np, "misc-csr");
+ if (IS_ERR(imx8_phy->misc_gpr))
+ return dev_err_probe(dev, PTR_ERR(imx8_phy->misc_gpr),
+ "can't get hsio misc registers\n");
+
+ imx8_phy->phy_gpr = syscon_regmap_lookup_by_phandle(np, "phy-csr");
+ if (IS_ERR(imx8_phy->phy_gpr))
+ return dev_err_probe(dev, PTR_ERR(imx8_phy->phy_gpr),
+ "can't get hsio phy registers\n");
+
+ pm_runtime_set_active(dev);
+ pm_runtime_enable(dev);
+
+ imx8_phy->phy = devm_phy_create(dev, NULL, &imx8q_pcie_phy_ops);
+ if (IS_ERR(imx8_phy->phy)) {
+ ret = PTR_ERR(imx8_phy->phy);
+ goto err_exit;
+ }
+
+ phy_set_drvdata(imx8_phy->phy, imx8_phy);
+
+ phy_provider = devm_of_phy_provider_register(dev, of_phy_simple_xlate);
+
+ ret = PTR_ERR_OR_ZERO(phy_provider);
+ if (ret < 0)
+ goto err_exit;
+
+ return ret;
+
+err_exit:
+ pm_runtime_disable(dev);
+ pm_runtime_set_suspended(dev);
+
+ return ret;
+}
+
+static struct platform_driver imx8q_pcie_phy_driver = {
+ .probe = imx8q_pcie_phy_probe,
+ .driver = {
+ .name = "imx8q-pcie-phy",
+ .of_match_table = imx8q_pcie_phy_of_match,
+ }
+};
+module_platform_driver(imx8q_pcie_phy_driver);
+
+MODULE_DESCRIPTION("FSL IMX8Q PCIE PHY driver");
+MODULE_LICENSE("GPL");
--
2.34.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply related [flat|nested] 30+ messages in thread
* [PATCH v1 3/3] phy: freescale: imx8q-pcie: Add i.MX8Q PCIe PHY driver
@ 2023-08-29 6:45 ` Richard Zhu
0 siblings, 0 replies; 30+ messages in thread
From: Richard Zhu @ 2023-08-29 6:45 UTC (permalink / raw)
To: vkoul, kishon, robh+dt, krzysztof.kozlowski+dt, conor+dt,
shawnguo, s.hauer, festevam, l.stach, a.fatoum, u.kleine-koenig
Cc: hongxing.zhu, linux-phy, devicetree, linux-arm-kernel,
linux-kernel, kernel, linux-imx
i.MX8QM HSIO(High Speed IO) module has three instances of single lane
SERDES PHYs, an instance of two lanes PCIe GEN3 controller, an
instance of single lane PCIe GEN3 controller, as well as an instance
of SATA 3.0 controller.
The HSIO module can be configured as the following different usecases.
1 - A two lanes PCIea and a single lane SATA.
2 - A single lane PCIea, a single lane PCIeb and a single lane SATA.
3 - A two lanes PCIea, a single lane PCIeb.
Add i.MX8Q PCIe PHY driver to support these different usecases.
- Add the runtime PM support, thus the PCIe PHY PD can be turned off
when PCIe probe is failed.
- The APB_PCLK is required only when PHY is configured as PCIE mode.
Note:
Although the RM document doesn't specify it, but the LPCG clocks should
be handled by a different procedure when the PHY is configured in PCIe
or SATA modes based on the practical oberservations.
When PHY is configured into PCIe mode.
- apb_pclk is mandatory required.
- apb_pclk and pipe_pclk should be enabled just before polling
PM_REQ_CORE_RST is cleared or not.
When PHY is configured as SATA mode.
- There is no apb_pclk.
- pipe_pclk should be enabled together with other LPCG clocks.
Signed-off-by: Richard Zhu <hongxing.zhu@nxp.com>
---
drivers/phy/freescale/Kconfig | 8 +
drivers/phy/freescale/Makefile | 1 +
drivers/phy/freescale/phy-fsl-imx8q-pcie.c | 562 +++++++++++++++++++++
3 files changed, 571 insertions(+)
create mode 100644 drivers/phy/freescale/phy-fsl-imx8q-pcie.c
diff --git a/drivers/phy/freescale/Kconfig b/drivers/phy/freescale/Kconfig
index 853958fb2c06..6f81fbf5f5e6 100644
--- a/drivers/phy/freescale/Kconfig
+++ b/drivers/phy/freescale/Kconfig
@@ -35,6 +35,14 @@ config PHY_FSL_IMX8M_PCIE
Enable this to add support for the PCIE PHY as found on
i.MX8M family of SOCs.
+config PHY_FSL_IMX8Q_PCIE
+ tristate "Freescale i.MX8Q PCIE PHY"
+ depends on OF && HAS_IOMEM
+ select GENERIC_PHY
+ help
+ Enable this to add support for the PCIE PHY as found on
+ i.MX8Q family of SOCs.
+
endif
config PHY_FSL_LYNX_28G
diff --git a/drivers/phy/freescale/Makefile b/drivers/phy/freescale/Makefile
index cedb328bc4d2..afa84807c40c 100644
--- a/drivers/phy/freescale/Makefile
+++ b/drivers/phy/freescale/Makefile
@@ -3,4 +3,5 @@ obj-$(CONFIG_PHY_FSL_IMX8MQ_USB) += phy-fsl-imx8mq-usb.o
obj-$(CONFIG_PHY_MIXEL_LVDS_PHY) += phy-fsl-imx8qm-lvds-phy.o
obj-$(CONFIG_PHY_MIXEL_MIPI_DPHY) += phy-fsl-imx8-mipi-dphy.o
obj-$(CONFIG_PHY_FSL_IMX8M_PCIE) += phy-fsl-imx8m-pcie.o
+obj-$(CONFIG_PHY_FSL_IMX8Q_PCIE) += phy-fsl-imx8q-pcie.o
obj-$(CONFIG_PHY_FSL_LYNX_28G) += phy-fsl-lynx-28g.o
diff --git a/drivers/phy/freescale/phy-fsl-imx8q-pcie.c b/drivers/phy/freescale/phy-fsl-imx8q-pcie.c
new file mode 100644
index 000000000000..3f1589628be1
--- /dev/null
+++ b/drivers/phy/freescale/phy-fsl-imx8q-pcie.c
@@ -0,0 +1,562 @@
+// SPDX-License-Identifier: GPL-2.0+
+/*
+ * Copyright 2023 NXP
+ */
+
+#include <linux/bitfield.h>
+#include <linux/clk.h>
+#include <linux/delay.h>
+#include <linux/io.h>
+#include <linux/iopoll.h>
+#include <linux/mfd/syscon.h>
+#include <linux/module.h>
+#include <linux/of_address.h>
+#include <linux/of_device.h>
+#include <linux/phy/phy.h>
+#include <linux/platform_device.h>
+#include <linux/regmap.h>
+
+#include <dt-bindings/phy/phy-imx8-pcie.h>
+
+/* i.MX8Q HSIO registers */
+#define IMX8Q_PHY_CTRL0_OFFSET 0x0
+#define IMX8Q_PHYX2_CTRL0_APB_MASK GENMASK(1, 0)
+#define IMX8Q_PHY_CTRL0_APB_RSTN_0 BIT(0)
+#define IMX8Q_PHY_CTRL0_APB_RSTN_1 BIT(1)
+#define IMX8Q_PHY_MODE_MASK GENMASK(20, 17)
+#define IMX8Q_PHY_MODE_SATA BIT(19)
+#define IMX8Q_PHY_PIPE_RSTN_0_MASK GENMASK(25, 24)
+#define IMX8Q_PHY_PIPE_RSTN_1_MASK GENMASK(27, 26)
+
+#define IMX8Q_PHY_STTS0_OFFSET 0x4
+#define IMX8Q_STTS0_LANE0_TX_PLL_LOCK BIT(4)
+#define IMX8Q_STTS0_LANE1_TX_PLL_LOCK BIT(12)
+
+#define IMX8Q_PCIE_CTRL2_OFFSET 0x8
+#define IMX8Q_CTRL_BUTTON_RST_N BIT(21)
+#define IMX8Q_CTRL_PERST_N BIT(22)
+#define IMX8Q_CTRL_POWER_UP_RST_N BIT(23)
+
+#define IMX8Q_PCIE_STTS0_OFFSET 0xC
+#define IMX8Q_CTRL_STTS0_PM_REQ_CORE_RST BIT(19)
+
+#define IMX8Q_SATA_CTRL0_OFFSET 0x0
+#define IMX8Q_SATA_CTRL_EPCS_TXDEEMP BIT(5)
+#define IMX8Q_SATA_CTRL_EPCS_TXDEEMP_SEL BIT(6)
+#define IMX8Q_SATA_CTRL_EPCS_PHYRESET_N BIT(7)
+#define IMX8Q_SATA_CTRL_RESET_N BIT(12)
+
+#define IMX8Q_MISC_CTRL0_OFFSET 0x0
+#define IMX8Q_MISC_IOB_RXENA BIT(0)
+#define IMX8Q_MISC_IOB_TXENA BIT(1)
+#define IMX8Q_MISC_IOB_A_0_TXOE BIT(2)
+#define IMX8Q_MISC_IOB_A_0_M1M0_MASK GENMASK(4, 3)
+#define IMX8Q_MISC_IOB_A_0_M1M0_2 BIT(4)
+#define IMX8Q_MISC_PHYX1_EPCS_SEL BIT(12)
+#define IMX8Q_MISC_PCIE_AB_SELECT BIT(13)
+#define IMX8Q_MISC_CLKREQN_OUT_OVERRIDE_1 BIT(24)
+#define IMX8Q_MISC_CLKREQN_OUT_OVERRIDE_0 BIT(25)
+
+#define IMX8Q_PHY_REG48_PMA_STATUS 0x30
+#define IMX8Q_PHY_REG48_PMA_RDY BIT(7)
+
+#define IMX8Q_PHYX2_LANE1_BASE_ADDR 0x5F190000
+#define IMX8Q_PHYX1_LANE0_BASE_ADDR 0x5F1A0000
+
+/* Parameters for the waiting for PCIe PHY PLL to lock */
+#define PHY_INIT_WAIT_USLEEP_MAX 10
+#define PHY_INIT_WAIT_TIMEOUT (1000 * PHY_INIT_WAIT_USLEEP_MAX)
+
+enum imx8q_pcie_phy_mode {
+ IMX8Q_PHY_PCIE_MODE,
+ IMX8Q_PHY_SATA_MODE,
+};
+
+struct imx8q_pcie_phy {
+ void __iomem *base;
+ struct clk *apb_pclk;
+ struct clk *ctrl_ips_clk;
+ struct clk *misc_ips_clk;
+ struct clk *phy_ips_clk;
+ struct clk *pipe_pclk;
+ struct device *dev;
+ struct phy *phy;
+ struct regmap *ctrl_gpr;
+ struct regmap *misc_gpr;
+ struct regmap *phy_gpr;
+ u32 hsio_cfg;
+ u32 lane_id;
+ u32 refclk_pad_mode;
+ enum imx8q_pcie_phy_mode mode;
+};
+
+static int imx8q_pcie_phy_init(struct phy *phy)
+{
+ int ret;
+ struct imx8q_pcie_phy *imx8_phy = phy_get_drvdata(phy);
+
+ if (imx8_phy->mode == IMX8Q_PHY_SATA_MODE) {
+ ret = clk_prepare_enable(imx8_phy->pipe_pclk);
+ if (ret) {
+ dev_err(imx8_phy->dev, "can't enable pipe clock\n");
+ return ret;
+ }
+ }
+
+ ret = clk_prepare_enable(imx8_phy->ctrl_ips_clk);
+ if (ret) {
+ dev_err(imx8_phy->dev, "can't enable ctrl_ips clock\n");
+ goto err_ctrl_ips_clk;
+ }
+
+ ret = clk_prepare_enable(imx8_phy->phy_ips_clk);
+ if (ret) {
+ dev_err(imx8_phy->dev, "can't enable phy_ips clock\n");
+ goto err_phy_ips_clk;
+ }
+
+ ret = clk_prepare_enable(imx8_phy->misc_ips_clk);
+ if (ret) {
+ dev_err(imx8_phy->dev, "can't enable misc_ips clock\n");
+ goto err_misc_ips_clk;
+ }
+
+ /* allow the clocks to stabilize */
+ usleep_range(200, 500);
+
+ return ret;
+
+err_misc_ips_clk:
+ clk_disable_unprepare(imx8_phy->phy_ips_clk);
+err_phy_ips_clk:
+ clk_disable_unprepare(imx8_phy->ctrl_ips_clk);
+err_ctrl_ips_clk:
+ if (imx8_phy->mode == IMX8Q_PHY_SATA_MODE)
+ clk_disable_unprepare(imx8_phy->pipe_pclk);
+
+ return ret;
+}
+
+static int imx8q_pcie_phy_exit(struct phy *phy)
+{
+ struct imx8q_pcie_phy *imx8_phy = phy_get_drvdata(phy);
+
+ clk_disable_unprepare(imx8_phy->misc_ips_clk);
+ clk_disable_unprepare(imx8_phy->phy_ips_clk);
+ clk_disable_unprepare(imx8_phy->ctrl_ips_clk);
+ if (imx8_phy->mode == IMX8Q_PHY_SATA_MODE)
+ clk_disable_unprepare(imx8_phy->pipe_pclk);
+
+ return 0;
+}
+
+static void imx8q_pcie_phy_reset_pcie(struct phy *phy)
+{
+ struct imx8q_pcie_phy *imx8_phy = phy_get_drvdata(phy);
+
+ regmap_update_bits(imx8_phy->ctrl_gpr, IMX8Q_PCIE_CTRL2_OFFSET,
+ IMX8Q_CTRL_BUTTON_RST_N, 0);
+ regmap_update_bits(imx8_phy->ctrl_gpr, IMX8Q_PCIE_CTRL2_OFFSET,
+ IMX8Q_CTRL_PERST_N, 0);
+ regmap_update_bits(imx8_phy->ctrl_gpr, IMX8Q_PCIE_CTRL2_OFFSET,
+ IMX8Q_CTRL_POWER_UP_RST_N, 0);
+ mdelay(1);
+ regmap_update_bits(imx8_phy->ctrl_gpr, IMX8Q_PCIE_CTRL2_OFFSET,
+ IMX8Q_CTRL_BUTTON_RST_N, IMX8Q_CTRL_BUTTON_RST_N);
+ regmap_update_bits(imx8_phy->ctrl_gpr, IMX8Q_PCIE_CTRL2_OFFSET,
+ IMX8Q_CTRL_PERST_N, IMX8Q_CTRL_PERST_N);
+ regmap_update_bits(imx8_phy->ctrl_gpr, IMX8Q_PCIE_CTRL2_OFFSET,
+ IMX8Q_CTRL_POWER_UP_RST_N, IMX8Q_CTRL_POWER_UP_RST_N);
+}
+
+static void imx8q_pcie_phy_set_clock_mode(struct phy *phy)
+{
+ u32 pad_mode;
+ struct imx8q_pcie_phy *imx8_phy = phy_get_drvdata(phy);
+
+ pad_mode = imx8_phy->refclk_pad_mode;
+ if (pad_mode == IMX8_PCIE_REFCLK_PAD_INPUT ||
+ pad_mode == IMX8_PCIE_REFCLK_PAD_UNUSED) {
+ /* Configure the PAD as input mode */
+ regmap_update_bits(imx8_phy->misc_gpr, IMX8Q_MISC_CTRL0_OFFSET,
+ IMX8Q_MISC_IOB_RXENA, IMX8Q_MISC_IOB_RXENA);
+ regmap_update_bits(imx8_phy->misc_gpr, IMX8Q_MISC_CTRL0_OFFSET,
+ IMX8Q_MISC_IOB_TXENA, 0);
+ usleep_range(200, 500);
+ } else {
+ /* Configure the PHY to output the refclock via PAD */
+ regmap_update_bits(imx8_phy->misc_gpr, IMX8Q_MISC_CTRL0_OFFSET,
+ IMX8Q_MISC_IOB_RXENA, 0);
+ regmap_update_bits(imx8_phy->misc_gpr, IMX8Q_MISC_CTRL0_OFFSET,
+ IMX8Q_MISC_IOB_TXENA, IMX8Q_MISC_IOB_TXENA);
+ regmap_update_bits(imx8_phy->misc_gpr, IMX8Q_MISC_CTRL0_OFFSET,
+ IMX8Q_MISC_IOB_A_0_TXOE | IMX8Q_MISC_IOB_A_0_M1M0_MASK,
+ IMX8Q_MISC_IOB_A_0_TXOE | IMX8Q_MISC_IOB_A_0_M1M0_2);
+ }
+}
+
+static void imx8q_pcie_phy_reset_sata(struct phy *phy)
+{
+ struct imx8q_pcie_phy *imx8_phy = phy_get_drvdata(phy);
+
+ /* clear PHY RST, then set it */
+ regmap_update_bits(imx8_phy->ctrl_gpr, IMX8Q_SATA_CTRL0_OFFSET,
+ IMX8Q_SATA_CTRL_EPCS_PHYRESET_N, 0);
+
+ regmap_update_bits(imx8_phy->ctrl_gpr, IMX8Q_SATA_CTRL0_OFFSET,
+ IMX8Q_SATA_CTRL_EPCS_PHYRESET_N,
+ IMX8Q_SATA_CTRL_EPCS_PHYRESET_N);
+
+ /* CTRL RST: SET -> delay 1 us -> CLEAR -> SET */
+ regmap_update_bits(imx8_phy->ctrl_gpr, IMX8Q_SATA_CTRL0_OFFSET,
+ IMX8Q_SATA_CTRL_RESET_N, IMX8Q_SATA_CTRL_RESET_N);
+ udelay(1);
+ regmap_update_bits(imx8_phy->ctrl_gpr, IMX8Q_SATA_CTRL0_OFFSET,
+ IMX8Q_SATA_CTRL_RESET_N, 0);
+ regmap_update_bits(imx8_phy->ctrl_gpr, IMX8Q_SATA_CTRL0_OFFSET,
+ IMX8Q_SATA_CTRL_RESET_N, IMX8Q_SATA_CTRL_RESET_N);
+
+ usleep_range(50, 100);
+}
+
+static int imx8q_pcie_phy_power_on(struct phy *phy)
+{
+ int ret;
+ u32 val, cond;
+ struct imx8q_pcie_phy *imx8_phy = phy_get_drvdata(phy);
+
+ if (imx8_phy->mode == IMX8Q_PHY_SATA_MODE) {
+ /* SATA mode PHY */
+ regmap_update_bits(imx8_phy->phy_gpr, IMX8Q_PHY_CTRL0_OFFSET,
+ IMX8Q_PHY_MODE_MASK, IMX8Q_PHY_MODE_SATA);
+ /*
+ * It is possible, for PCIe and SATA are sharing
+ * the same clock source, HPLL or external oscillator.
+ * When PCIe is in low power modes (L1.X or L2 etc),
+ * the clock source can be turned off. In this case,
+ * if this clock source is required to be toggling by
+ * SATA, then SATA functions will be abnormal.
+ * Set the override here to avoid it.
+ */
+ regmap_update_bits(imx8_phy->misc_gpr, IMX8Q_MISC_CTRL0_OFFSET,
+ IMX8Q_MISC_CLKREQN_OUT_OVERRIDE_1 |
+ IMX8Q_MISC_CLKREQN_OUT_OVERRIDE_0,
+ IMX8Q_MISC_CLKREQN_OUT_OVERRIDE_1 |
+ IMX8Q_MISC_CLKREQN_OUT_OVERRIDE_0);
+ } else {
+ /* PCIe mode PHY */
+ imx8q_pcie_phy_reset_pcie(phy);
+ }
+
+ if (imx8_phy->hsio_cfg == PCIEAX2SATA) {
+ if (imx8_phy->lane_id == 0) {
+ regmap_update_bits(imx8_phy->phy_gpr,
+ IMX8Q_PHY_CTRL0_OFFSET,
+ IMX8Q_PHYX2_CTRL0_APB_MASK,
+ IMX8Q_PHY_CTRL0_APB_RSTN_0 |
+ IMX8Q_PHY_CTRL0_APB_RSTN_1);
+ regmap_update_bits(imx8_phy->phy_gpr,
+ IMX8Q_PHY_CTRL0_OFFSET,
+ IMX8Q_PHY_PIPE_RSTN_0_MASK |
+ IMX8Q_PHY_PIPE_RSTN_1_MASK,
+ IMX8Q_PHY_PIPE_RSTN_0_MASK |
+ IMX8Q_PHY_PIPE_RSTN_1_MASK);
+ } else if (imx8_phy->lane_id == 2) {
+ regmap_update_bits(imx8_phy->phy_gpr,
+ IMX8Q_PHY_CTRL0_OFFSET,
+ IMX8Q_PHY_CTRL0_APB_RSTN_0,
+ IMX8Q_PHY_CTRL0_APB_RSTN_0);
+ }
+
+ regmap_update_bits(imx8_phy->misc_gpr, IMX8Q_MISC_CTRL0_OFFSET,
+ IMX8Q_MISC_PHYX1_EPCS_SEL, IMX8Q_MISC_PHYX1_EPCS_SEL);
+ regmap_update_bits(imx8_phy->misc_gpr, IMX8Q_MISC_CTRL0_OFFSET,
+ IMX8Q_MISC_PCIE_AB_SELECT, 0);
+ } else if (imx8_phy->hsio_cfg == PCIEAX1PCIEBX1SATA) {
+ if (imx8_phy->lane_id == 0) {
+ regmap_update_bits(imx8_phy->phy_gpr,
+ IMX8Q_PHY_CTRL0_OFFSET,
+ IMX8Q_PHY_CTRL0_APB_RSTN_0,
+ IMX8Q_PHY_CTRL0_APB_RSTN_0);
+ regmap_update_bits(imx8_phy->phy_gpr,
+ IMX8Q_PHY_CTRL0_OFFSET,
+ IMX8Q_PHY_PIPE_RSTN_0_MASK,
+ IMX8Q_PHY_PIPE_RSTN_0_MASK);
+ } else if (imx8_phy->lane_id == 1) {
+ regmap_update_bits(imx8_phy->phy_gpr,
+ IMX8Q_PHY_CTRL0_OFFSET,
+ IMX8Q_PHY_CTRL0_APB_RSTN_1,
+ IMX8Q_PHY_CTRL0_APB_RSTN_1);
+ regmap_update_bits(imx8_phy->phy_gpr,
+ IMX8Q_PHY_CTRL0_OFFSET,
+ IMX8Q_PHY_PIPE_RSTN_1_MASK,
+ IMX8Q_PHY_PIPE_RSTN_1_MASK);
+ } else if (imx8_phy->lane_id == 2) {
+ regmap_update_bits(imx8_phy->phy_gpr,
+ IMX8Q_PHY_CTRL0_OFFSET,
+ IMX8Q_PHY_CTRL0_APB_RSTN_0,
+ IMX8Q_PHY_CTRL0_APB_RSTN_0);
+ }
+
+ regmap_update_bits(imx8_phy->misc_gpr, IMX8Q_MISC_CTRL0_OFFSET,
+ IMX8Q_MISC_PCIE_AB_SELECT, IMX8Q_MISC_PCIE_AB_SELECT);
+ regmap_update_bits(imx8_phy->misc_gpr, IMX8Q_MISC_CTRL0_OFFSET,
+ IMX8Q_MISC_PHYX1_EPCS_SEL, IMX8Q_MISC_PHYX1_EPCS_SEL);
+ } else if (imx8_phy->hsio_cfg == PCIEAX2PCIEBX1) {
+ if (imx8_phy->lane_id == 0) {
+ regmap_update_bits(imx8_phy->phy_gpr,
+ IMX8Q_PHY_CTRL0_OFFSET,
+ IMX8Q_PHYX2_CTRL0_APB_MASK,
+ IMX8Q_PHY_CTRL0_APB_RSTN_0 |
+ IMX8Q_PHY_CTRL0_APB_RSTN_1);
+ regmap_update_bits(imx8_phy->phy_gpr,
+ IMX8Q_PHY_CTRL0_OFFSET,
+ IMX8Q_PHY_PIPE_RSTN_0_MASK |
+ IMX8Q_PHY_PIPE_RSTN_1_MASK,
+ IMX8Q_PHY_PIPE_RSTN_0_MASK |
+ IMX8Q_PHY_PIPE_RSTN_1_MASK);
+ } else if (imx8_phy->lane_id == 2) {
+ regmap_update_bits(imx8_phy->phy_gpr,
+ IMX8Q_PHY_CTRL0_OFFSET,
+ IMX8Q_PHY_CTRL0_APB_RSTN_0,
+ IMX8Q_PHY_CTRL0_APB_RSTN_0);
+ regmap_update_bits(imx8_phy->phy_gpr,
+ IMX8Q_PHY_CTRL0_OFFSET,
+ IMX8Q_PHY_PIPE_RSTN_0_MASK,
+ IMX8Q_PHY_PIPE_RSTN_0_MASK);
+ }
+
+ regmap_update_bits(imx8_phy->misc_gpr, IMX8Q_MISC_CTRL0_OFFSET,
+ IMX8Q_MISC_PHYX1_EPCS_SEL, 0);
+ regmap_update_bits(imx8_phy->misc_gpr, IMX8Q_MISC_CTRL0_OFFSET,
+ IMX8Q_MISC_PCIE_AB_SELECT, IMX8Q_MISC_PCIE_AB_SELECT);
+ }
+
+ imx8q_pcie_phy_set_clock_mode(phy);
+
+ if (imx8_phy->mode == IMX8Q_PHY_SATA_MODE) {
+ regmap_update_bits(imx8_phy->ctrl_gpr, IMX8Q_SATA_CTRL0_OFFSET,
+ IMX8Q_SATA_CTRL_EPCS_TXDEEMP,
+ IMX8Q_SATA_CTRL_EPCS_TXDEEMP);
+ regmap_update_bits(imx8_phy->ctrl_gpr, IMX8Q_SATA_CTRL0_OFFSET,
+ IMX8Q_SATA_CTRL_EPCS_TXDEEMP_SEL,
+ IMX8Q_SATA_CTRL_EPCS_TXDEEMP_SEL);
+
+ imx8q_pcie_phy_reset_sata(phy);
+ } else {
+ ret = clk_prepare_enable(imx8_phy->apb_pclk);
+ if (ret) {
+ dev_err(imx8_phy->dev, "can't enable apb_pclk clock\n");
+ return ret;
+ }
+ ret = clk_prepare_enable(imx8_phy->pipe_pclk);
+ if (ret) {
+ dev_err(imx8_phy->dev, "can't enable pipe_pclk clock\n");
+ clk_disable_unprepare(imx8_phy->apb_pclk);
+ return ret;
+ }
+
+ /* Bit19 PM_REQ_CORE_RST of PCIe_STTS0 should be cleared. */
+ ret = regmap_read_poll_timeout(imx8_phy->ctrl_gpr,
+ IMX8Q_PCIE_STTS0_OFFSET, val,
+ (val & IMX8Q_CTRL_STTS0_PM_REQ_CORE_RST) == 0,
+ PHY_INIT_WAIT_USLEEP_MAX,
+ PHY_INIT_WAIT_TIMEOUT);
+ if (ret) {
+ dev_err(imx8_phy->dev, "PM_REQ_CORE_RST is set\n");
+ goto err_exit;
+ }
+ }
+
+ /* Polling to check the PHY is ready or not. */
+ if (imx8_phy->lane_id == 1)
+ cond = IMX8Q_STTS0_LANE1_TX_PLL_LOCK;
+ else
+ cond = IMX8Q_STTS0_LANE0_TX_PLL_LOCK;
+
+ ret = regmap_read_poll_timeout(imx8_phy->phy_gpr,
+ IMX8Q_PHY_STTS0_OFFSET, val, ((val & cond) == cond),
+ PHY_INIT_WAIT_USLEEP_MAX, PHY_INIT_WAIT_TIMEOUT);
+ if (ret) {
+ dev_err(imx8_phy->dev, "PHY PLL lock timeout\n");
+ goto err_exit;
+ } else {
+ dev_info(imx8_phy->dev, "PHY PLL is locked\n");
+ }
+
+ if (imx8_phy->mode == IMX8Q_PHY_SATA_MODE) {
+ cond = IMX8Q_PHY_REG48_PMA_RDY;
+ ret = read_poll_timeout(readb, val, ((val & cond) == cond),
+ PHY_INIT_WAIT_USLEEP_MAX,
+ PHY_INIT_WAIT_TIMEOUT, false,
+ imx8_phy->base + IMX8Q_PHY_REG48_PMA_STATUS);
+ if (ret)
+ dev_err(imx8_phy->dev, "PHY calibration is timeout\n");
+ else
+ dev_info(imx8_phy->dev, "PHY calibration is done\n");
+ }
+
+ return ret;
+
+err_exit:
+ if (imx8_phy->mode == IMX8Q_PHY_PCIE_MODE) {
+ clk_disable_unprepare(imx8_phy->pipe_pclk);
+ clk_disable_unprepare(imx8_phy->apb_pclk);
+ }
+
+ return ret;
+}
+
+static int imx8q_pcie_phy_power_off(struct phy *phy)
+{
+ struct imx8q_pcie_phy *imx8_phy = phy_get_drvdata(phy);
+
+ if (imx8_phy->mode == IMX8Q_PHY_PCIE_MODE) {
+ clk_disable_unprepare(imx8_phy->pipe_pclk);
+ clk_disable_unprepare(imx8_phy->apb_pclk);
+ }
+
+ return 0;
+}
+
+static const struct phy_ops imx8q_pcie_phy_ops = {
+ .init = imx8q_pcie_phy_init,
+ .exit = imx8q_pcie_phy_exit,
+ .power_on = imx8q_pcie_phy_power_on,
+ .power_off = imx8q_pcie_phy_power_off,
+ .owner = THIS_MODULE,
+};
+
+static const struct of_device_id imx8q_pcie_phy_of_match[] = {
+ {.compatible = "fsl,imx8qm-pcie-phy", },
+ { },
+};
+
+MODULE_DEVICE_TABLE(of, imx8q_pcie_phy_of_match);
+
+static int imx8q_pcie_phy_probe(struct platform_device *pdev)
+{
+ int ret;
+ struct device *dev = &pdev->dev;
+ struct device_node *np = dev->of_node;
+ struct imx8q_pcie_phy *imx8_phy;
+ const struct of_device_id *of_id;
+ struct phy_provider *phy_provider;
+ struct resource *res;
+
+ of_id = of_match_device(imx8q_pcie_phy_of_match, dev);
+ if (!of_id)
+ return -EINVAL;
+
+ imx8_phy = devm_kzalloc(dev, sizeof(*imx8_phy), GFP_KERNEL);
+ if (!imx8_phy)
+ return -ENOMEM;
+
+ imx8_phy->dev = dev;
+
+ /* Get PHY refclk pad mode */
+ of_property_read_u32(np, "fsl,refclk-pad-mode",
+ &imx8_phy->refclk_pad_mode);
+
+ /* Get HSIO configuration mode */
+ if (of_property_read_u32(np, "hsio-cfg", &imx8_phy->hsio_cfg))
+ imx8_phy->hsio_cfg = 0;
+
+ res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
+ imx8_phy->base = devm_ioremap_resource(dev, res);
+ if (IS_ERR(imx8_phy->base))
+ return PTR_ERR(imx8_phy->base);
+
+ if (res->start == IMX8Q_PHYX2_LANE1_BASE_ADDR)
+ imx8_phy->lane_id = 1;
+ else if (res->start == IMX8Q_PHYX1_LANE0_BASE_ADDR)
+ imx8_phy->lane_id = 2;
+
+ if (unlikely((imx8_phy->lane_id == 2) &&
+ (imx8_phy->hsio_cfg != PCIEAX2PCIEBX1)))
+ imx8_phy->mode = IMX8Q_PHY_SATA_MODE;
+ else
+ imx8_phy->mode = IMX8Q_PHY_PCIE_MODE;
+
+ /* Fetch clocks */
+ if (imx8_phy->mode == IMX8Q_PHY_PCIE_MODE) {
+ /* APB clock is not required by SATA */
+ imx8_phy->apb_pclk = devm_clk_get(dev, "apb_pclk");
+ if (IS_ERR(imx8_phy->apb_pclk))
+ return dev_err_probe(dev, PTR_ERR(imx8_phy->apb_pclk),
+ "can't get apb_pclk clock\n");
+ }
+
+ imx8_phy->ctrl_ips_clk = devm_clk_get(dev, "ctrl_ips_clk");
+ if (IS_ERR(imx8_phy->ctrl_ips_clk))
+ return dev_err_probe(dev, PTR_ERR(imx8_phy->ctrl_ips_clk),
+ "can't get ctrl_ips_clk clock\n");
+
+ imx8_phy->misc_ips_clk = devm_clk_get(dev, "misc_ips_clk");
+ if (IS_ERR(imx8_phy->misc_ips_clk))
+ return dev_err_probe(dev, PTR_ERR(imx8_phy->misc_ips_clk),
+ "can't get misc_ips_clk clock\n");
+
+ imx8_phy->pipe_pclk = devm_clk_get(dev, "pipe_pclk");
+ if (IS_ERR(imx8_phy->pipe_pclk))
+ return dev_err_probe(dev, PTR_ERR(imx8_phy->pipe_pclk),
+ "can't get pipe_pclk clock\n");
+
+ imx8_phy->phy_ips_clk = devm_clk_get(dev, "phy_ips_clk");
+ if (IS_ERR(imx8_phy->phy_ips_clk))
+ return dev_err_probe(dev, PTR_ERR(imx8_phy->phy_ips_clk),
+ "can't get phy_ips_clk clock\n");
+
+ /* Grab GPR config register range */
+ imx8_phy->ctrl_gpr = syscon_regmap_lookup_by_phandle(np, "ctrl-csr");
+ if (IS_ERR(imx8_phy->ctrl_gpr))
+ return dev_err_probe(dev, PTR_ERR(imx8_phy->ctrl_gpr),
+ "can't get hsio ctrl registers\n");
+
+ imx8_phy->misc_gpr = syscon_regmap_lookup_by_phandle(np, "misc-csr");
+ if (IS_ERR(imx8_phy->misc_gpr))
+ return dev_err_probe(dev, PTR_ERR(imx8_phy->misc_gpr),
+ "can't get hsio misc registers\n");
+
+ imx8_phy->phy_gpr = syscon_regmap_lookup_by_phandle(np, "phy-csr");
+ if (IS_ERR(imx8_phy->phy_gpr))
+ return dev_err_probe(dev, PTR_ERR(imx8_phy->phy_gpr),
+ "can't get hsio phy registers\n");
+
+ pm_runtime_set_active(dev);
+ pm_runtime_enable(dev);
+
+ imx8_phy->phy = devm_phy_create(dev, NULL, &imx8q_pcie_phy_ops);
+ if (IS_ERR(imx8_phy->phy)) {
+ ret = PTR_ERR(imx8_phy->phy);
+ goto err_exit;
+ }
+
+ phy_set_drvdata(imx8_phy->phy, imx8_phy);
+
+ phy_provider = devm_of_phy_provider_register(dev, of_phy_simple_xlate);
+
+ ret = PTR_ERR_OR_ZERO(phy_provider);
+ if (ret < 0)
+ goto err_exit;
+
+ return ret;
+
+err_exit:
+ pm_runtime_disable(dev);
+ pm_runtime_set_suspended(dev);
+
+ return ret;
+}
+
+static struct platform_driver imx8q_pcie_phy_driver = {
+ .probe = imx8q_pcie_phy_probe,
+ .driver = {
+ .name = "imx8q-pcie-phy",
+ .of_match_table = imx8q_pcie_phy_of_match,
+ }
+};
+module_platform_driver(imx8q_pcie_phy_driver);
+
+MODULE_DESCRIPTION("FSL IMX8Q PCIE PHY driver");
+MODULE_LICENSE("GPL");
--
2.34.1
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
^ permalink raw reply related [flat|nested] 30+ messages in thread
* Re: [PATCH v1 1/3] dt-bindings: phy: Add i.MX8QM PCIe PHY binding
2023-08-29 6:45 ` Richard Zhu
(?)
@ 2023-08-29 7:47 ` Krzysztof Kozlowski
-1 siblings, 0 replies; 30+ messages in thread
From: Krzysztof Kozlowski @ 2023-08-29 7:47 UTC (permalink / raw)
To: Richard Zhu, vkoul, kishon, robh+dt, krzysztof.kozlowski+dt,
conor+dt, shawnguo, s.hauer, festevam, l.stach, a.fatoum,
u.kleine-koenig
Cc: linux-phy, devicetree, linux-arm-kernel, linux-kernel, kernel, linux-imx
On 29/08/2023 08:45, Richard Zhu wrote:
> Add i.MX8QM PCIe PHY binding.
>
> i.MX8QM HSIO(High Speed IO) module has three instances of single lane
> SERDES PHYs, an instance of two lanes PCIe GEN3 controller, an
> instance of single lane PCIe GEN3 controller, as well as an instance
> of SATA 3.0 controller.
>
> The HSIO module can be configured as the following different usecases.
> 1 - A two lanes PCIea and a single lane SATA.
> 2 - A single lane PCIea, a single lane PCIeb and a single lane SATA.
> 3 - A two lanes PCIea, a single lane PCIeb.
>
> Signed-off-by: Richard Zhu <hongxing.zhu@nxp.com>
> ---
> .../bindings/phy/fsl,imx8-pcie-phy.yaml | 70 ++++++++++++++++++-
> 1 file changed, 67 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/phy/fsl,imx8-pcie-phy.yaml b/Documentation/devicetree/bindings/phy/fsl,imx8-pcie-phy.yaml
> index 182a219387b0..764790f2b10b 100644
> --- a/Documentation/devicetree/bindings/phy/fsl,imx8-pcie-phy.yaml
> +++ b/Documentation/devicetree/bindings/phy/fsl,imx8-pcie-phy.yaml
> @@ -17,16 +17,18 @@ properties:
> enum:
> - fsl,imx8mm-pcie-phy
> - fsl,imx8mp-pcie-phy
> + - fsl,imx8qm-pcie-phy
>
> reg:
> maxItems: 1
>
> clocks:
> - maxItems: 1
> + minItems: 1
> + maxItems: 5
>
> clock-names:
> - items:
> - - const: ref
> + minItems: 1
> + maxItems: 5
>
> resets:
> minItems: 1
> @@ -70,6 +72,36 @@ properties:
> description: PCIe PHY power domain (optional).
> maxItems: 1
>
> + hsio-cfg:
Missing vendor prefix because it does not look like generic property.
> + description: |
> + Specifies the different usecases supported by the HSIO(High Speed IO)
I don't know what are the usecases...
> + module. PCIEAX2SATA means two lanes PCIea and a single lane SATA.
> + PCIEAX1PCIEBX1SATA represents a single lane PCIea, a single lane
> + PCIeb and a single lane SATA. PCIEAX2PCIEBX1 on behalf of a two
> + lanes PCIea, a single lane PCIeb.
> + Refer include/dt-bindings/phy/phy-imx8-pcie.h for the constants to
> + be used (optional).
None of all this helped me to understand what part of hardware this is
responsible for. It seems you just want to program a register, but
instead you should use one of existing properties like phy-modes etc.
> + $ref: /schemas/types.yaml#/definitions/uint32
> + enum: [ 1, 2, 3 ]
> +
> + ctrl-csr:
> + $ref: /schemas/types.yaml#/definitions/phandle
> + description:
> + phandle to the ctrl-csr region containing the HSIO control and
> + status registers for PCIe or SATA controller (optional).
Please try some internal review before posting to patches. Community is
not cheap reviewers taking this duty from NXP. I am pretty sure NXP can
afford someone looking at the code.
This misses vendor prefix, as explained many times for every syscon
phandle. Also optional is redundant.
But anyway status of PCIe or SATA controller is not a property of the
phy, so it looks to me you stuff here some properties belonging to some
other missing devices.
> +
> + misc-csr:
> + $ref: /schemas/types.yaml#/definitions/phandle
> + description:
> + phandle to the misc-csr region containing the HSIO control and
> + status registers for misc (optional).
Same problems.
> +
> + phy-csr:
> + $ref: /schemas/types.yaml#/definitions/phandle
> + description:
> + phandle to the phy-csr region containing the HSIO control and
> + status registers for phy (optional).
Same problems.
> +
> required:
> - "#phy-cells"
> - compatible
> @@ -78,6 +110,38 @@ required:
> - clock-names
> - fsl,refclk-pad-mode
>
> +allOf:
> + - if:
> + properties:
> + compatible:
> + enum:
> + - fsl,imx8qm-pcie-phy
> + then:
> + properties:
> + clocks:
> + minItems: 4
> + maxItems: 5
> + clock-names:
> + oneOf:
> + - items:
> + - const: pipe_pclk
> + - const: ctrl_ips_clk
> + - const: phy_ips_clk
> + - const: misc_ips_clk
Drop clk everywhere.
> + - items:
> + - const: apb_pclk
No, optional clock goes to the end and please explain why APB is optional.
Best regards,
Krzysztof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [PATCH v1 1/3] dt-bindings: phy: Add i.MX8QM PCIe PHY binding
@ 2023-08-29 7:47 ` Krzysztof Kozlowski
0 siblings, 0 replies; 30+ messages in thread
From: Krzysztof Kozlowski @ 2023-08-29 7:47 UTC (permalink / raw)
To: Richard Zhu, vkoul, kishon, robh+dt, krzysztof.kozlowski+dt,
conor+dt, shawnguo, s.hauer, festevam, l.stach, a.fatoum,
u.kleine-koenig
Cc: linux-phy, devicetree, linux-arm-kernel, linux-kernel, kernel, linux-imx
On 29/08/2023 08:45, Richard Zhu wrote:
> Add i.MX8QM PCIe PHY binding.
>
> i.MX8QM HSIO(High Speed IO) module has three instances of single lane
> SERDES PHYs, an instance of two lanes PCIe GEN3 controller, an
> instance of single lane PCIe GEN3 controller, as well as an instance
> of SATA 3.0 controller.
>
> The HSIO module can be configured as the following different usecases.
> 1 - A two lanes PCIea and a single lane SATA.
> 2 - A single lane PCIea, a single lane PCIeb and a single lane SATA.
> 3 - A two lanes PCIea, a single lane PCIeb.
>
> Signed-off-by: Richard Zhu <hongxing.zhu@nxp.com>
> ---
> .../bindings/phy/fsl,imx8-pcie-phy.yaml | 70 ++++++++++++++++++-
> 1 file changed, 67 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/phy/fsl,imx8-pcie-phy.yaml b/Documentation/devicetree/bindings/phy/fsl,imx8-pcie-phy.yaml
> index 182a219387b0..764790f2b10b 100644
> --- a/Documentation/devicetree/bindings/phy/fsl,imx8-pcie-phy.yaml
> +++ b/Documentation/devicetree/bindings/phy/fsl,imx8-pcie-phy.yaml
> @@ -17,16 +17,18 @@ properties:
> enum:
> - fsl,imx8mm-pcie-phy
> - fsl,imx8mp-pcie-phy
> + - fsl,imx8qm-pcie-phy
>
> reg:
> maxItems: 1
>
> clocks:
> - maxItems: 1
> + minItems: 1
> + maxItems: 5
>
> clock-names:
> - items:
> - - const: ref
> + minItems: 1
> + maxItems: 5
>
> resets:
> minItems: 1
> @@ -70,6 +72,36 @@ properties:
> description: PCIe PHY power domain (optional).
> maxItems: 1
>
> + hsio-cfg:
Missing vendor prefix because it does not look like generic property.
> + description: |
> + Specifies the different usecases supported by the HSIO(High Speed IO)
I don't know what are the usecases...
> + module. PCIEAX2SATA means two lanes PCIea and a single lane SATA.
> + PCIEAX1PCIEBX1SATA represents a single lane PCIea, a single lane
> + PCIeb and a single lane SATA. PCIEAX2PCIEBX1 on behalf of a two
> + lanes PCIea, a single lane PCIeb.
> + Refer include/dt-bindings/phy/phy-imx8-pcie.h for the constants to
> + be used (optional).
None of all this helped me to understand what part of hardware this is
responsible for. It seems you just want to program a register, but
instead you should use one of existing properties like phy-modes etc.
> + $ref: /schemas/types.yaml#/definitions/uint32
> + enum: [ 1, 2, 3 ]
> +
> + ctrl-csr:
> + $ref: /schemas/types.yaml#/definitions/phandle
> + description:
> + phandle to the ctrl-csr region containing the HSIO control and
> + status registers for PCIe or SATA controller (optional).
Please try some internal review before posting to patches. Community is
not cheap reviewers taking this duty from NXP. I am pretty sure NXP can
afford someone looking at the code.
This misses vendor prefix, as explained many times for every syscon
phandle. Also optional is redundant.
But anyway status of PCIe or SATA controller is not a property of the
phy, so it looks to me you stuff here some properties belonging to some
other missing devices.
> +
> + misc-csr:
> + $ref: /schemas/types.yaml#/definitions/phandle
> + description:
> + phandle to the misc-csr region containing the HSIO control and
> + status registers for misc (optional).
Same problems.
> +
> + phy-csr:
> + $ref: /schemas/types.yaml#/definitions/phandle
> + description:
> + phandle to the phy-csr region containing the HSIO control and
> + status registers for phy (optional).
Same problems.
> +
> required:
> - "#phy-cells"
> - compatible
> @@ -78,6 +110,38 @@ required:
> - clock-names
> - fsl,refclk-pad-mode
>
> +allOf:
> + - if:
> + properties:
> + compatible:
> + enum:
> + - fsl,imx8qm-pcie-phy
> + then:
> + properties:
> + clocks:
> + minItems: 4
> + maxItems: 5
> + clock-names:
> + oneOf:
> + - items:
> + - const: pipe_pclk
> + - const: ctrl_ips_clk
> + - const: phy_ips_clk
> + - const: misc_ips_clk
Drop clk everywhere.
> + - items:
> + - const: apb_pclk
No, optional clock goes to the end and please explain why APB is optional.
Best regards,
Krzysztof
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [PATCH v1 1/3] dt-bindings: phy: Add i.MX8QM PCIe PHY binding
@ 2023-08-29 7:47 ` Krzysztof Kozlowski
0 siblings, 0 replies; 30+ messages in thread
From: Krzysztof Kozlowski @ 2023-08-29 7:47 UTC (permalink / raw)
To: Richard Zhu, vkoul, kishon, robh+dt, krzysztof.kozlowski+dt,
conor+dt, shawnguo, s.hauer, festevam, l.stach, a.fatoum,
u.kleine-koenig
Cc: linux-phy, devicetree, linux-arm-kernel, linux-kernel, kernel, linux-imx
On 29/08/2023 08:45, Richard Zhu wrote:
> Add i.MX8QM PCIe PHY binding.
>
> i.MX8QM HSIO(High Speed IO) module has three instances of single lane
> SERDES PHYs, an instance of two lanes PCIe GEN3 controller, an
> instance of single lane PCIe GEN3 controller, as well as an instance
> of SATA 3.0 controller.
>
> The HSIO module can be configured as the following different usecases.
> 1 - A two lanes PCIea and a single lane SATA.
> 2 - A single lane PCIea, a single lane PCIeb and a single lane SATA.
> 3 - A two lanes PCIea, a single lane PCIeb.
>
> Signed-off-by: Richard Zhu <hongxing.zhu@nxp.com>
> ---
> .../bindings/phy/fsl,imx8-pcie-phy.yaml | 70 ++++++++++++++++++-
> 1 file changed, 67 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/phy/fsl,imx8-pcie-phy.yaml b/Documentation/devicetree/bindings/phy/fsl,imx8-pcie-phy.yaml
> index 182a219387b0..764790f2b10b 100644
> --- a/Documentation/devicetree/bindings/phy/fsl,imx8-pcie-phy.yaml
> +++ b/Documentation/devicetree/bindings/phy/fsl,imx8-pcie-phy.yaml
> @@ -17,16 +17,18 @@ properties:
> enum:
> - fsl,imx8mm-pcie-phy
> - fsl,imx8mp-pcie-phy
> + - fsl,imx8qm-pcie-phy
>
> reg:
> maxItems: 1
>
> clocks:
> - maxItems: 1
> + minItems: 1
> + maxItems: 5
>
> clock-names:
> - items:
> - - const: ref
> + minItems: 1
> + maxItems: 5
>
> resets:
> minItems: 1
> @@ -70,6 +72,36 @@ properties:
> description: PCIe PHY power domain (optional).
> maxItems: 1
>
> + hsio-cfg:
Missing vendor prefix because it does not look like generic property.
> + description: |
> + Specifies the different usecases supported by the HSIO(High Speed IO)
I don't know what are the usecases...
> + module. PCIEAX2SATA means two lanes PCIea and a single lane SATA.
> + PCIEAX1PCIEBX1SATA represents a single lane PCIea, a single lane
> + PCIeb and a single lane SATA. PCIEAX2PCIEBX1 on behalf of a two
> + lanes PCIea, a single lane PCIeb.
> + Refer include/dt-bindings/phy/phy-imx8-pcie.h for the constants to
> + be used (optional).
None of all this helped me to understand what part of hardware this is
responsible for. It seems you just want to program a register, but
instead you should use one of existing properties like phy-modes etc.
> + $ref: /schemas/types.yaml#/definitions/uint32
> + enum: [ 1, 2, 3 ]
> +
> + ctrl-csr:
> + $ref: /schemas/types.yaml#/definitions/phandle
> + description:
> + phandle to the ctrl-csr region containing the HSIO control and
> + status registers for PCIe or SATA controller (optional).
Please try some internal review before posting to patches. Community is
not cheap reviewers taking this duty from NXP. I am pretty sure NXP can
afford someone looking at the code.
This misses vendor prefix, as explained many times for every syscon
phandle. Also optional is redundant.
But anyway status of PCIe or SATA controller is not a property of the
phy, so it looks to me you stuff here some properties belonging to some
other missing devices.
> +
> + misc-csr:
> + $ref: /schemas/types.yaml#/definitions/phandle
> + description:
> + phandle to the misc-csr region containing the HSIO control and
> + status registers for misc (optional).
Same problems.
> +
> + phy-csr:
> + $ref: /schemas/types.yaml#/definitions/phandle
> + description:
> + phandle to the phy-csr region containing the HSIO control and
> + status registers for phy (optional).
Same problems.
> +
> required:
> - "#phy-cells"
> - compatible
> @@ -78,6 +110,38 @@ required:
> - clock-names
> - fsl,refclk-pad-mode
>
> +allOf:
> + - if:
> + properties:
> + compatible:
> + enum:
> + - fsl,imx8qm-pcie-phy
> + then:
> + properties:
> + clocks:
> + minItems: 4
> + maxItems: 5
> + clock-names:
> + oneOf:
> + - items:
> + - const: pipe_pclk
> + - const: ctrl_ips_clk
> + - const: phy_ips_clk
> + - const: misc_ips_clk
Drop clk everywhere.
> + - items:
> + - const: apb_pclk
No, optional clock goes to the end and please explain why APB is optional.
Best regards,
Krzysztof
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [PATCH v1 2/3] dt-bindings: phy: phy-imx8-pcie: Add binding for different usecases of i.MX8QM PCIe PHYs
2023-08-29 6:45 ` Richard Zhu
(?)
@ 2023-08-29 7:49 ` Krzysztof Kozlowski
-1 siblings, 0 replies; 30+ messages in thread
From: Krzysztof Kozlowski @ 2023-08-29 7:49 UTC (permalink / raw)
To: Richard Zhu, vkoul, kishon, robh+dt, krzysztof.kozlowski+dt,
conor+dt, shawnguo, s.hauer, festevam, l.stach, a.fatoum,
u.kleine-koenig
Cc: linux-phy, devicetree, linux-arm-kernel, linux-kernel, kernel, linux-imx
On 29/08/2023 08:45, Richard Zhu wrote:
> Add binding for different usecases of i.MX8QM PCIe PHYs.
>
> Signed-off-by: Richard Zhu <hongxing.zhu@nxp.com>
This patch does not make sense on its own. Otherwise your previous patch
has invalid path.
> ---
> include/dt-bindings/phy/phy-imx8-pcie.h | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/include/dt-bindings/phy/phy-imx8-pcie.h b/include/dt-bindings/phy/phy-imx8-pcie.h
> index 8bbe2d6538d8..c8425c172118 100644
> --- a/include/dt-bindings/phy/phy-imx8-pcie.h
> +++ b/include/dt-bindings/phy/phy-imx8-pcie.h
> @@ -11,4 +11,11 @@
> #define IMX8_PCIE_REFCLK_PAD_INPUT 1
> #define IMX8_PCIE_REFCLK_PAD_OUTPUT 2
>
> +/*
> + * Different usecases of i.MX8QM HSIO(High Speed IO) module.
> + */
> +#define PCIEAX2SATA 1
> +#define PCIEAX1PCIEBX1SATA 2
> +#define PCIEAX2PCIEBX1 3
Drop indentation. Look at the define few lines above and compare.
Anyway, this is neither explained nor looking like hardware property.
Nothing in the commit msg or in doc here justifies these constants. Drop
and use existing properties.
Best regards,
Krzysztof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [PATCH v1 2/3] dt-bindings: phy: phy-imx8-pcie: Add binding for different usecases of i.MX8QM PCIe PHYs
@ 2023-08-29 7:49 ` Krzysztof Kozlowski
0 siblings, 0 replies; 30+ messages in thread
From: Krzysztof Kozlowski @ 2023-08-29 7:49 UTC (permalink / raw)
To: Richard Zhu, vkoul, kishon, robh+dt, krzysztof.kozlowski+dt,
conor+dt, shawnguo, s.hauer, festevam, l.stach, a.fatoum,
u.kleine-koenig
Cc: linux-phy, devicetree, linux-arm-kernel, linux-kernel, kernel, linux-imx
On 29/08/2023 08:45, Richard Zhu wrote:
> Add binding for different usecases of i.MX8QM PCIe PHYs.
>
> Signed-off-by: Richard Zhu <hongxing.zhu@nxp.com>
This patch does not make sense on its own. Otherwise your previous patch
has invalid path.
> ---
> include/dt-bindings/phy/phy-imx8-pcie.h | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/include/dt-bindings/phy/phy-imx8-pcie.h b/include/dt-bindings/phy/phy-imx8-pcie.h
> index 8bbe2d6538d8..c8425c172118 100644
> --- a/include/dt-bindings/phy/phy-imx8-pcie.h
> +++ b/include/dt-bindings/phy/phy-imx8-pcie.h
> @@ -11,4 +11,11 @@
> #define IMX8_PCIE_REFCLK_PAD_INPUT 1
> #define IMX8_PCIE_REFCLK_PAD_OUTPUT 2
>
> +/*
> + * Different usecases of i.MX8QM HSIO(High Speed IO) module.
> + */
> +#define PCIEAX2SATA 1
> +#define PCIEAX1PCIEBX1SATA 2
> +#define PCIEAX2PCIEBX1 3
Drop indentation. Look at the define few lines above and compare.
Anyway, this is neither explained nor looking like hardware property.
Nothing in the commit msg or in doc here justifies these constants. Drop
and use existing properties.
Best regards,
Krzysztof
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [PATCH v1 2/3] dt-bindings: phy: phy-imx8-pcie: Add binding for different usecases of i.MX8QM PCIe PHYs
@ 2023-08-29 7:49 ` Krzysztof Kozlowski
0 siblings, 0 replies; 30+ messages in thread
From: Krzysztof Kozlowski @ 2023-08-29 7:49 UTC (permalink / raw)
To: Richard Zhu, vkoul, kishon, robh+dt, krzysztof.kozlowski+dt,
conor+dt, shawnguo, s.hauer, festevam, l.stach, a.fatoum,
u.kleine-koenig
Cc: linux-phy, devicetree, linux-arm-kernel, linux-kernel, kernel, linux-imx
On 29/08/2023 08:45, Richard Zhu wrote:
> Add binding for different usecases of i.MX8QM PCIe PHYs.
>
> Signed-off-by: Richard Zhu <hongxing.zhu@nxp.com>
This patch does not make sense on its own. Otherwise your previous patch
has invalid path.
> ---
> include/dt-bindings/phy/phy-imx8-pcie.h | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/include/dt-bindings/phy/phy-imx8-pcie.h b/include/dt-bindings/phy/phy-imx8-pcie.h
> index 8bbe2d6538d8..c8425c172118 100644
> --- a/include/dt-bindings/phy/phy-imx8-pcie.h
> +++ b/include/dt-bindings/phy/phy-imx8-pcie.h
> @@ -11,4 +11,11 @@
> #define IMX8_PCIE_REFCLK_PAD_INPUT 1
> #define IMX8_PCIE_REFCLK_PAD_OUTPUT 2
>
> +/*
> + * Different usecases of i.MX8QM HSIO(High Speed IO) module.
> + */
> +#define PCIEAX2SATA 1
> +#define PCIEAX1PCIEBX1SATA 2
> +#define PCIEAX2PCIEBX1 3
Drop indentation. Look at the define few lines above and compare.
Anyway, this is neither explained nor looking like hardware property.
Nothing in the commit msg or in doc here justifies these constants. Drop
and use existing properties.
Best regards,
Krzysztof
^ permalink raw reply [flat|nested] 30+ messages in thread
* RE: [PATCH v1 1/3] dt-bindings: phy: Add i.MX8QM PCIe PHY binding
2023-08-29 7:47 ` Krzysztof Kozlowski
(?)
@ 2023-08-30 7:31 ` Hongxing Zhu
-1 siblings, 0 replies; 30+ messages in thread
From: Hongxing Zhu @ 2023-08-30 7:31 UTC (permalink / raw)
To: Krzysztof Kozlowski, vkoul, kishon, robh+dt,
krzysztof.kozlowski+dt, conor+dt, shawnguo, s.hauer, festevam,
l.stach, a.fatoum, u.kleine-koenig
Cc: linux-phy, devicetree, linux-arm-kernel, linux-kernel, kernel,
dl-linux-imx
Hi Krzsztof:
Thanks for your review.
> -----Original Message-----
> From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> Sent: 2023年8月29日 15:48
> To: Hongxing Zhu <hongxing.zhu@nxp.com>; vkoul@kernel.org;
> kishon@kernel.org; robh+dt@kernel.org; krzysztof.kozlowski+dt@linaro.org;
> conor+dt@kernel.org; shawnguo@kernel.org; s.hauer@pengutronix.de;
> festevam@gmail.com; l.stach@pengutronix.de; a.fatoum@pengutronix.de;
> u.kleine-koenig@pengutronix.de
> Cc: linux-phy@lists.infradead.org; devicetree@vger.kernel.org;
> linux-arm-kernel@lists.infradead.org; linux-kernel@vger.kernel.org;
> kernel@pengutronix.de; dl-linux-imx <linux-imx@nxp.com>
> Subject: Re: [PATCH v1 1/3] dt-bindings: phy: Add i.MX8QM PCIe PHY binding
>
> On 29/08/2023 08:45, Richard Zhu wrote:
> > Add i.MX8QM PCIe PHY binding.
> >
> > i.MX8QM HSIO(High Speed IO) module has three instances of single lane
> > SERDES PHYs, an instance of two lanes PCIe GEN3 controller, an
> > instance of single lane PCIe GEN3 controller, as well as an instance
> > of SATA 3.0 controller.
> >
> > The HSIO module can be configured as the following different usecases.
> > 1 - A two lanes PCIea and a single lane SATA.
> > 2 - A single lane PCIea, a single lane PCIeb and a single lane SATA.
> > 3 - A two lanes PCIea, a single lane PCIeb.
> >
> > Signed-off-by: Richard Zhu <hongxing.zhu@nxp.com>
> > ---
> > .../bindings/phy/fsl,imx8-pcie-phy.yaml | 70 ++++++++++++++++++-
> > 1 file changed, 67 insertions(+), 3 deletions(-)
> >
> > diff --git
> > a/Documentation/devicetree/bindings/phy/fsl,imx8-pcie-phy.yaml
> > b/Documentation/devicetree/bindings/phy/fsl,imx8-pcie-phy.yaml
> > index 182a219387b0..764790f2b10b 100644
> > --- a/Documentation/devicetree/bindings/phy/fsl,imx8-pcie-phy.yaml
> > +++ b/Documentation/devicetree/bindings/phy/fsl,imx8-pcie-phy.yaml
> > @@ -17,16 +17,18 @@ properties:
> > enum:
> > - fsl,imx8mm-pcie-phy
> > - fsl,imx8mp-pcie-phy
> > + - fsl,imx8qm-pcie-phy
> >
> > reg:
> > maxItems: 1
> >
> > clocks:
> > - maxItems: 1
> > + minItems: 1
> > + maxItems: 5
> >
> > clock-names:
> > - items:
> > - - const: ref
> > + minItems: 1
> > + maxItems: 5
> >
> > resets:
> > minItems: 1
> > @@ -70,6 +72,36 @@ properties:
> > description: PCIe PHY power domain (optional).
> > maxItems: 1
> >
> > + hsio-cfg:
>
> Missing vendor prefix because it does not look like generic property.
Okay, would add the fsl,hsio- prefix later.
>
> > + description: |
> > + Specifies the different usecases supported by the HSIO(High
> > + Speed IO)
>
> I don't know what are the usecases...
Sorry, miss one space between "use" and "cases".
i.MX8QM HSIO module can be controlled by DSC/software in these three
different modes. So I add this property (fsl,hsio-cfg) here to specify the
work mode of HSIO.
>
> > + module. PCIEAX2SATA means two lanes PCIea and a single lane SATA.
> > + PCIEAX1PCIEBX1SATA represents a single lane PCIea, a single lane
> > + PCIeb and a single lane SATA. PCIEAX2PCIEBX1 on behalf of a two
> > + lanes PCIea, a single lane PCIeb.
> > + Refer include/dt-bindings/phy/phy-imx8-pcie.h for the constants to
> > + be used (optional).
>
> None of all this helped me to understand what part of hardware this is responsible
> for. It seems you just want to program a register, but instead you should use one
> of existing properties like phy-modes etc.
It's my bad. Didn't describe the HW clearly above.
The fsl,hsio-cfg is used to specify the work mode of HSIO subsystem, not only
the PHY mode. Since the PHYs are contained in the HSIO subsystem, can't be
used by PCIe or SATA controller freely. The usage of these PHYs are limited
by the HSIO work modes. BTW, up to now, I still don't have a good idea to
describe the HSIO by phy-modes property although I prefer this way in my mind.
>
> > + $ref: /schemas/types.yaml#/definitions/uint32
> > + enum: [ 1, 2, 3 ]
> > +
> > + ctrl-csr:
> > + $ref: /schemas/types.yaml#/definitions/phandle
> > + description:
> > + phandle to the ctrl-csr region containing the HSIO control and
> > + status registers for PCIe or SATA controller (optional).
>
> Please try some internal review before posting to patches. Community is not cheap
> reviewers taking this duty from NXP. I am pretty sure NXP can afford someone
> looking at the code.
>
> This misses vendor prefix, as explained many times for every syscon phandle. Also
> optional is redundant.
Sorry about the missing prefix. The prefix would be added later.
And the optional would be removed. Thanks.
>
> But anyway status of PCIe or SATA controller is not a property of the phy, so it
> looks to me you stuff here some properties belonging to some other missing
> devices.
I see. You're right the status of PCIe or SATA controller is not a property
of the PHY. Some bits contained in the ctrl-csr region, are used to kick
off resets through the internal glue logic. So, this property is added
for phy driver.
>
> > +
> > + misc-csr:
> > + $ref: /schemas/types.yaml#/definitions/phandle
> > + description:
> > + phandle to the misc-csr region containing the HSIO control and
> > + status registers for misc (optional).
>
> Same problems.
>
"fsl,hsio-" prefix would be added later.
> > +
> > + phy-csr:
> > + $ref: /schemas/types.yaml#/definitions/phandle
> > + description:
> > + phandle to the phy-csr region containing the HSIO control and
> > + status registers for phy (optional).
>
> Same problems.
"fsl,hsio-" prefix would be added later.
>
>
> > +
> > required:
> > - "#phy-cells"
> > - compatible
> > @@ -78,6 +110,38 @@ required:
> > - clock-names
> > - fsl,refclk-pad-mode
> >
> > +allOf:
> > + - if:
> > + properties:
> > + compatible:
> > + enum:
> > + - fsl,imx8qm-pcie-phy
> > + then:
> > + properties:
> > + clocks:
> > + minItems: 4
> > + maxItems: 5
> > + clock-names:
> > + oneOf:
> > + - items:
> > + - const: pipe_pclk
> > + - const: ctrl_ips_clk
> > + - const: phy_ips_clk
> > + - const: misc_ips_clk
>
> Drop clk everywhere.
Sorry, would be changed and aligned later.
> > + - items:
> > + - const: apb_pclk
>
> No, optional clock goes to the end and please explain why APB is optional.
I understand that phy should have the apb_pclk whatever it is used in
which mode. Would keep aligned in the clock definitions later. Thanks.
Best Regards
Richard Zhu
>
>
>
> Best regards,
> Krzysztof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 30+ messages in thread
* RE: [PATCH v1 1/3] dt-bindings: phy: Add i.MX8QM PCIe PHY binding
@ 2023-08-30 7:31 ` Hongxing Zhu
0 siblings, 0 replies; 30+ messages in thread
From: Hongxing Zhu @ 2023-08-30 7:31 UTC (permalink / raw)
To: Krzysztof Kozlowski, vkoul, kishon, robh+dt,
krzysztof.kozlowski+dt, conor+dt, shawnguo, s.hauer, festevam,
l.stach, a.fatoum, u.kleine-koenig
Cc: linux-phy, devicetree, linux-arm-kernel, linux-kernel, kernel,
dl-linux-imx
Hi Krzsztof:
Thanks for your review.
> -----Original Message-----
> From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> Sent: 2023年8月29日 15:48
> To: Hongxing Zhu <hongxing.zhu@nxp.com>; vkoul@kernel.org;
> kishon@kernel.org; robh+dt@kernel.org; krzysztof.kozlowski+dt@linaro.org;
> conor+dt@kernel.org; shawnguo@kernel.org; s.hauer@pengutronix.de;
> festevam@gmail.com; l.stach@pengutronix.de; a.fatoum@pengutronix.de;
> u.kleine-koenig@pengutronix.de
> Cc: linux-phy@lists.infradead.org; devicetree@vger.kernel.org;
> linux-arm-kernel@lists.infradead.org; linux-kernel@vger.kernel.org;
> kernel@pengutronix.de; dl-linux-imx <linux-imx@nxp.com>
> Subject: Re: [PATCH v1 1/3] dt-bindings: phy: Add i.MX8QM PCIe PHY binding
>
> On 29/08/2023 08:45, Richard Zhu wrote:
> > Add i.MX8QM PCIe PHY binding.
> >
> > i.MX8QM HSIO(High Speed IO) module has three instances of single lane
> > SERDES PHYs, an instance of two lanes PCIe GEN3 controller, an
> > instance of single lane PCIe GEN3 controller, as well as an instance
> > of SATA 3.0 controller.
> >
> > The HSIO module can be configured as the following different usecases.
> > 1 - A two lanes PCIea and a single lane SATA.
> > 2 - A single lane PCIea, a single lane PCIeb and a single lane SATA.
> > 3 - A two lanes PCIea, a single lane PCIeb.
> >
> > Signed-off-by: Richard Zhu <hongxing.zhu@nxp.com>
> > ---
> > .../bindings/phy/fsl,imx8-pcie-phy.yaml | 70 ++++++++++++++++++-
> > 1 file changed, 67 insertions(+), 3 deletions(-)
> >
> > diff --git
> > a/Documentation/devicetree/bindings/phy/fsl,imx8-pcie-phy.yaml
> > b/Documentation/devicetree/bindings/phy/fsl,imx8-pcie-phy.yaml
> > index 182a219387b0..764790f2b10b 100644
> > --- a/Documentation/devicetree/bindings/phy/fsl,imx8-pcie-phy.yaml
> > +++ b/Documentation/devicetree/bindings/phy/fsl,imx8-pcie-phy.yaml
> > @@ -17,16 +17,18 @@ properties:
> > enum:
> > - fsl,imx8mm-pcie-phy
> > - fsl,imx8mp-pcie-phy
> > + - fsl,imx8qm-pcie-phy
> >
> > reg:
> > maxItems: 1
> >
> > clocks:
> > - maxItems: 1
> > + minItems: 1
> > + maxItems: 5
> >
> > clock-names:
> > - items:
> > - - const: ref
> > + minItems: 1
> > + maxItems: 5
> >
> > resets:
> > minItems: 1
> > @@ -70,6 +72,36 @@ properties:
> > description: PCIe PHY power domain (optional).
> > maxItems: 1
> >
> > + hsio-cfg:
>
> Missing vendor prefix because it does not look like generic property.
Okay, would add the fsl,hsio- prefix later.
>
> > + description: |
> > + Specifies the different usecases supported by the HSIO(High
> > + Speed IO)
>
> I don't know what are the usecases...
Sorry, miss one space between "use" and "cases".
i.MX8QM HSIO module can be controlled by DSC/software in these three
different modes. So I add this property (fsl,hsio-cfg) here to specify the
work mode of HSIO.
>
> > + module. PCIEAX2SATA means two lanes PCIea and a single lane SATA.
> > + PCIEAX1PCIEBX1SATA represents a single lane PCIea, a single lane
> > + PCIeb and a single lane SATA. PCIEAX2PCIEBX1 on behalf of a two
> > + lanes PCIea, a single lane PCIeb.
> > + Refer include/dt-bindings/phy/phy-imx8-pcie.h for the constants to
> > + be used (optional).
>
> None of all this helped me to understand what part of hardware this is responsible
> for. It seems you just want to program a register, but instead you should use one
> of existing properties like phy-modes etc.
It's my bad. Didn't describe the HW clearly above.
The fsl,hsio-cfg is used to specify the work mode of HSIO subsystem, not only
the PHY mode. Since the PHYs are contained in the HSIO subsystem, can't be
used by PCIe or SATA controller freely. The usage of these PHYs are limited
by the HSIO work modes. BTW, up to now, I still don't have a good idea to
describe the HSIO by phy-modes property although I prefer this way in my mind.
>
> > + $ref: /schemas/types.yaml#/definitions/uint32
> > + enum: [ 1, 2, 3 ]
> > +
> > + ctrl-csr:
> > + $ref: /schemas/types.yaml#/definitions/phandle
> > + description:
> > + phandle to the ctrl-csr region containing the HSIO control and
> > + status registers for PCIe or SATA controller (optional).
>
> Please try some internal review before posting to patches. Community is not cheap
> reviewers taking this duty from NXP. I am pretty sure NXP can afford someone
> looking at the code.
>
> This misses vendor prefix, as explained many times for every syscon phandle. Also
> optional is redundant.
Sorry about the missing prefix. The prefix would be added later.
And the optional would be removed. Thanks.
>
> But anyway status of PCIe or SATA controller is not a property of the phy, so it
> looks to me you stuff here some properties belonging to some other missing
> devices.
I see. You're right the status of PCIe or SATA controller is not a property
of the PHY. Some bits contained in the ctrl-csr region, are used to kick
off resets through the internal glue logic. So, this property is added
for phy driver.
>
> > +
> > + misc-csr:
> > + $ref: /schemas/types.yaml#/definitions/phandle
> > + description:
> > + phandle to the misc-csr region containing the HSIO control and
> > + status registers for misc (optional).
>
> Same problems.
>
"fsl,hsio-" prefix would be added later.
> > +
> > + phy-csr:
> > + $ref: /schemas/types.yaml#/definitions/phandle
> > + description:
> > + phandle to the phy-csr region containing the HSIO control and
> > + status registers for phy (optional).
>
> Same problems.
"fsl,hsio-" prefix would be added later.
>
>
> > +
> > required:
> > - "#phy-cells"
> > - compatible
> > @@ -78,6 +110,38 @@ required:
> > - clock-names
> > - fsl,refclk-pad-mode
> >
> > +allOf:
> > + - if:
> > + properties:
> > + compatible:
> > + enum:
> > + - fsl,imx8qm-pcie-phy
> > + then:
> > + properties:
> > + clocks:
> > + minItems: 4
> > + maxItems: 5
> > + clock-names:
> > + oneOf:
> > + - items:
> > + - const: pipe_pclk
> > + - const: ctrl_ips_clk
> > + - const: phy_ips_clk
> > + - const: misc_ips_clk
>
> Drop clk everywhere.
Sorry, would be changed and aligned later.
> > + - items:
> > + - const: apb_pclk
>
> No, optional clock goes to the end and please explain why APB is optional.
I understand that phy should have the apb_pclk whatever it is used in
which mode. Would keep aligned in the clock definitions later. Thanks.
Best Regards
Richard Zhu
>
>
>
> Best regards,
> Krzysztof
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
^ permalink raw reply [flat|nested] 30+ messages in thread
* RE: [PATCH v1 1/3] dt-bindings: phy: Add i.MX8QM PCIe PHY binding
@ 2023-08-30 7:31 ` Hongxing Zhu
0 siblings, 0 replies; 30+ messages in thread
From: Hongxing Zhu @ 2023-08-30 7:31 UTC (permalink / raw)
To: Krzysztof Kozlowski, vkoul, kishon, robh+dt,
krzysztof.kozlowski+dt, conor+dt, shawnguo, s.hauer, festevam,
l.stach, a.fatoum, u.kleine-koenig
Cc: linux-phy, devicetree, linux-arm-kernel, linux-kernel, kernel,
dl-linux-imx
Hi Krzsztof:
Thanks for your review.
> -----Original Message-----
> From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> Sent: 2023年8月29日 15:48
> To: Hongxing Zhu <hongxing.zhu@nxp.com>; vkoul@kernel.org;
> kishon@kernel.org; robh+dt@kernel.org; krzysztof.kozlowski+dt@linaro.org;
> conor+dt@kernel.org; shawnguo@kernel.org; s.hauer@pengutronix.de;
> festevam@gmail.com; l.stach@pengutronix.de; a.fatoum@pengutronix.de;
> u.kleine-koenig@pengutronix.de
> Cc: linux-phy@lists.infradead.org; devicetree@vger.kernel.org;
> linux-arm-kernel@lists.infradead.org; linux-kernel@vger.kernel.org;
> kernel@pengutronix.de; dl-linux-imx <linux-imx@nxp.com>
> Subject: Re: [PATCH v1 1/3] dt-bindings: phy: Add i.MX8QM PCIe PHY binding
>
> On 29/08/2023 08:45, Richard Zhu wrote:
> > Add i.MX8QM PCIe PHY binding.
> >
> > i.MX8QM HSIO(High Speed IO) module has three instances of single lane
> > SERDES PHYs, an instance of two lanes PCIe GEN3 controller, an
> > instance of single lane PCIe GEN3 controller, as well as an instance
> > of SATA 3.0 controller.
> >
> > The HSIO module can be configured as the following different usecases.
> > 1 - A two lanes PCIea and a single lane SATA.
> > 2 - A single lane PCIea, a single lane PCIeb and a single lane SATA.
> > 3 - A two lanes PCIea, a single lane PCIeb.
> >
> > Signed-off-by: Richard Zhu <hongxing.zhu@nxp.com>
> > ---
> > .../bindings/phy/fsl,imx8-pcie-phy.yaml | 70 ++++++++++++++++++-
> > 1 file changed, 67 insertions(+), 3 deletions(-)
> >
> > diff --git
> > a/Documentation/devicetree/bindings/phy/fsl,imx8-pcie-phy.yaml
> > b/Documentation/devicetree/bindings/phy/fsl,imx8-pcie-phy.yaml
> > index 182a219387b0..764790f2b10b 100644
> > --- a/Documentation/devicetree/bindings/phy/fsl,imx8-pcie-phy.yaml
> > +++ b/Documentation/devicetree/bindings/phy/fsl,imx8-pcie-phy.yaml
> > @@ -17,16 +17,18 @@ properties:
> > enum:
> > - fsl,imx8mm-pcie-phy
> > - fsl,imx8mp-pcie-phy
> > + - fsl,imx8qm-pcie-phy
> >
> > reg:
> > maxItems: 1
> >
> > clocks:
> > - maxItems: 1
> > + minItems: 1
> > + maxItems: 5
> >
> > clock-names:
> > - items:
> > - - const: ref
> > + minItems: 1
> > + maxItems: 5
> >
> > resets:
> > minItems: 1
> > @@ -70,6 +72,36 @@ properties:
> > description: PCIe PHY power domain (optional).
> > maxItems: 1
> >
> > + hsio-cfg:
>
> Missing vendor prefix because it does not look like generic property.
Okay, would add the fsl,hsio- prefix later.
>
> > + description: |
> > + Specifies the different usecases supported by the HSIO(High
> > + Speed IO)
>
> I don't know what are the usecases...
Sorry, miss one space between "use" and "cases".
i.MX8QM HSIO module can be controlled by DSC/software in these three
different modes. So I add this property (fsl,hsio-cfg) here to specify the
work mode of HSIO.
>
> > + module. PCIEAX2SATA means two lanes PCIea and a single lane SATA.
> > + PCIEAX1PCIEBX1SATA represents a single lane PCIea, a single lane
> > + PCIeb and a single lane SATA. PCIEAX2PCIEBX1 on behalf of a two
> > + lanes PCIea, a single lane PCIeb.
> > + Refer include/dt-bindings/phy/phy-imx8-pcie.h for the constants to
> > + be used (optional).
>
> None of all this helped me to understand what part of hardware this is responsible
> for. It seems you just want to program a register, but instead you should use one
> of existing properties like phy-modes etc.
It's my bad. Didn't describe the HW clearly above.
The fsl,hsio-cfg is used to specify the work mode of HSIO subsystem, not only
the PHY mode. Since the PHYs are contained in the HSIO subsystem, can't be
used by PCIe or SATA controller freely. The usage of these PHYs are limited
by the HSIO work modes. BTW, up to now, I still don't have a good idea to
describe the HSIO by phy-modes property although I prefer this way in my mind.
>
> > + $ref: /schemas/types.yaml#/definitions/uint32
> > + enum: [ 1, 2, 3 ]
> > +
> > + ctrl-csr:
> > + $ref: /schemas/types.yaml#/definitions/phandle
> > + description:
> > + phandle to the ctrl-csr region containing the HSIO control and
> > + status registers for PCIe or SATA controller (optional).
>
> Please try some internal review before posting to patches. Community is not cheap
> reviewers taking this duty from NXP. I am pretty sure NXP can afford someone
> looking at the code.
>
> This misses vendor prefix, as explained many times for every syscon phandle. Also
> optional is redundant.
Sorry about the missing prefix. The prefix would be added later.
And the optional would be removed. Thanks.
>
> But anyway status of PCIe or SATA controller is not a property of the phy, so it
> looks to me you stuff here some properties belonging to some other missing
> devices.
I see. You're right the status of PCIe or SATA controller is not a property
of the PHY. Some bits contained in the ctrl-csr region, are used to kick
off resets through the internal glue logic. So, this property is added
for phy driver.
>
> > +
> > + misc-csr:
> > + $ref: /schemas/types.yaml#/definitions/phandle
> > + description:
> > + phandle to the misc-csr region containing the HSIO control and
> > + status registers for misc (optional).
>
> Same problems.
>
"fsl,hsio-" prefix would be added later.
> > +
> > + phy-csr:
> > + $ref: /schemas/types.yaml#/definitions/phandle
> > + description:
> > + phandle to the phy-csr region containing the HSIO control and
> > + status registers for phy (optional).
>
> Same problems.
"fsl,hsio-" prefix would be added later.
>
>
> > +
> > required:
> > - "#phy-cells"
> > - compatible
> > @@ -78,6 +110,38 @@ required:
> > - clock-names
> > - fsl,refclk-pad-mode
> >
> > +allOf:
> > + - if:
> > + properties:
> > + compatible:
> > + enum:
> > + - fsl,imx8qm-pcie-phy
> > + then:
> > + properties:
> > + clocks:
> > + minItems: 4
> > + maxItems: 5
> > + clock-names:
> > + oneOf:
> > + - items:
> > + - const: pipe_pclk
> > + - const: ctrl_ips_clk
> > + - const: phy_ips_clk
> > + - const: misc_ips_clk
>
> Drop clk everywhere.
Sorry, would be changed and aligned later.
> > + - items:
> > + - const: apb_pclk
>
> No, optional clock goes to the end and please explain why APB is optional.
I understand that phy should have the apb_pclk whatever it is used in
which mode. Would keep aligned in the clock definitions later. Thanks.
Best Regards
Richard Zhu
>
>
>
> Best regards,
> Krzysztof
^ permalink raw reply [flat|nested] 30+ messages in thread
* RE: [PATCH v1 2/3] dt-bindings: phy: phy-imx8-pcie: Add binding for different usecases of i.MX8QM PCIe PHYs
2023-08-29 7:49 ` Krzysztof Kozlowski
(?)
@ 2023-08-30 7:31 ` Hongxing Zhu
-1 siblings, 0 replies; 30+ messages in thread
From: Hongxing Zhu @ 2023-08-30 7:31 UTC (permalink / raw)
To: Krzysztof Kozlowski, vkoul, kishon, robh+dt,
krzysztof.kozlowski+dt, conor+dt, shawnguo, s.hauer, festevam,
l.stach, a.fatoum, u.kleine-koenig
Cc: linux-phy, devicetree, linux-arm-kernel, linux-kernel, kernel,
dl-linux-imx
> -----Original Message-----
> From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> Sent: 2023年8月29日 15:50
> To: Hongxing Zhu <hongxing.zhu@nxp.com>; vkoul@kernel.org;
> kishon@kernel.org; robh+dt@kernel.org; krzysztof.kozlowski+dt@linaro.org;
> conor+dt@kernel.org; shawnguo@kernel.org; s.hauer@pengutronix.de;
> festevam@gmail.com; l.stach@pengutronix.de; a.fatoum@pengutronix.de;
> u.kleine-koenig@pengutronix.de
> Cc: linux-phy@lists.infradead.org; devicetree@vger.kernel.org;
> linux-arm-kernel@lists.infradead.org; linux-kernel@vger.kernel.org;
> kernel@pengutronix.de; dl-linux-imx <linux-imx@nxp.com>
> Subject: Re: [PATCH v1 2/3] dt-bindings: phy: phy-imx8-pcie: Add binding for
> different usecases of i.MX8QM PCIe PHYs
>
> On 29/08/2023 08:45, Richard Zhu wrote:
> > Add binding for different usecases of i.MX8QM PCIe PHYs.
> >
> > Signed-off-by: Richard Zhu <hongxing.zhu@nxp.com>
>
> This patch does not make sense on its own. Otherwise your previous patch has
> invalid path.
>
> > ---
> > include/dt-bindings/phy/phy-imx8-pcie.h | 7 +++++++
> > 1 file changed, 7 insertions(+)
> >
> > diff --git a/include/dt-bindings/phy/phy-imx8-pcie.h
> > b/include/dt-bindings/phy/phy-imx8-pcie.h
> > index 8bbe2d6538d8..c8425c172118 100644
> > --- a/include/dt-bindings/phy/phy-imx8-pcie.h
> > +++ b/include/dt-bindings/phy/phy-imx8-pcie.h
> > @@ -11,4 +11,11 @@
> > #define IMX8_PCIE_REFCLK_PAD_INPUT 1
> > #define IMX8_PCIE_REFCLK_PAD_OUTPUT 2
> >
> > +/*
> > + * Different usecases of i.MX8QM HSIO(High Speed IO) module.
> > + */
> > +#define PCIEAX2SATA 1
> > +#define PCIEAX1PCIEBX1SATA 2
> > +#define PCIEAX2PCIEBX1 3
>
> Drop indentation. Look at the define few lines above and compare.
>
> Anyway, this is neither explained nor looking like hardware property.
> Nothing in the commit msg or in doc here justifies these constants. Drop and use
> existing properties.
This property is used to specify the work mode of HSIO subsystem.
The HSIO and the PHYs contained in it would be initialized together refer to
the different work modes. See the detailed discussion in #1 patch.
Best Regards
Richard Zhu
>
>
> Best regards,
> Krzysztof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 30+ messages in thread
* RE: [PATCH v1 2/3] dt-bindings: phy: phy-imx8-pcie: Add binding for different usecases of i.MX8QM PCIe PHYs
@ 2023-08-30 7:31 ` Hongxing Zhu
0 siblings, 0 replies; 30+ messages in thread
From: Hongxing Zhu @ 2023-08-30 7:31 UTC (permalink / raw)
To: Krzysztof Kozlowski, vkoul, kishon, robh+dt,
krzysztof.kozlowski+dt, conor+dt, shawnguo, s.hauer, festevam,
l.stach, a.fatoum, u.kleine-koenig
Cc: linux-phy, devicetree, linux-arm-kernel, linux-kernel, kernel,
dl-linux-imx
> -----Original Message-----
> From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> Sent: 2023年8月29日 15:50
> To: Hongxing Zhu <hongxing.zhu@nxp.com>; vkoul@kernel.org;
> kishon@kernel.org; robh+dt@kernel.org; krzysztof.kozlowski+dt@linaro.org;
> conor+dt@kernel.org; shawnguo@kernel.org; s.hauer@pengutronix.de;
> festevam@gmail.com; l.stach@pengutronix.de; a.fatoum@pengutronix.de;
> u.kleine-koenig@pengutronix.de
> Cc: linux-phy@lists.infradead.org; devicetree@vger.kernel.org;
> linux-arm-kernel@lists.infradead.org; linux-kernel@vger.kernel.org;
> kernel@pengutronix.de; dl-linux-imx <linux-imx@nxp.com>
> Subject: Re: [PATCH v1 2/3] dt-bindings: phy: phy-imx8-pcie: Add binding for
> different usecases of i.MX8QM PCIe PHYs
>
> On 29/08/2023 08:45, Richard Zhu wrote:
> > Add binding for different usecases of i.MX8QM PCIe PHYs.
> >
> > Signed-off-by: Richard Zhu <hongxing.zhu@nxp.com>
>
> This patch does not make sense on its own. Otherwise your previous patch has
> invalid path.
>
> > ---
> > include/dt-bindings/phy/phy-imx8-pcie.h | 7 +++++++
> > 1 file changed, 7 insertions(+)
> >
> > diff --git a/include/dt-bindings/phy/phy-imx8-pcie.h
> > b/include/dt-bindings/phy/phy-imx8-pcie.h
> > index 8bbe2d6538d8..c8425c172118 100644
> > --- a/include/dt-bindings/phy/phy-imx8-pcie.h
> > +++ b/include/dt-bindings/phy/phy-imx8-pcie.h
> > @@ -11,4 +11,11 @@
> > #define IMX8_PCIE_REFCLK_PAD_INPUT 1
> > #define IMX8_PCIE_REFCLK_PAD_OUTPUT 2
> >
> > +/*
> > + * Different usecases of i.MX8QM HSIO(High Speed IO) module.
> > + */
> > +#define PCIEAX2SATA 1
> > +#define PCIEAX1PCIEBX1SATA 2
> > +#define PCIEAX2PCIEBX1 3
>
> Drop indentation. Look at the define few lines above and compare.
>
> Anyway, this is neither explained nor looking like hardware property.
> Nothing in the commit msg or in doc here justifies these constants. Drop and use
> existing properties.
This property is used to specify the work mode of HSIO subsystem.
The HSIO and the PHYs contained in it would be initialized together refer to
the different work modes. See the detailed discussion in #1 patch.
Best Regards
Richard Zhu
>
>
> Best regards,
> Krzysztof
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
^ permalink raw reply [flat|nested] 30+ messages in thread
* RE: [PATCH v1 2/3] dt-bindings: phy: phy-imx8-pcie: Add binding for different usecases of i.MX8QM PCIe PHYs
@ 2023-08-30 7:31 ` Hongxing Zhu
0 siblings, 0 replies; 30+ messages in thread
From: Hongxing Zhu @ 2023-08-30 7:31 UTC (permalink / raw)
To: Krzysztof Kozlowski, vkoul, kishon, robh+dt,
krzysztof.kozlowski+dt, conor+dt, shawnguo, s.hauer, festevam,
l.stach, a.fatoum, u.kleine-koenig
Cc: linux-phy, devicetree, linux-arm-kernel, linux-kernel, kernel,
dl-linux-imx
> -----Original Message-----
> From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> Sent: 2023年8月29日 15:50
> To: Hongxing Zhu <hongxing.zhu@nxp.com>; vkoul@kernel.org;
> kishon@kernel.org; robh+dt@kernel.org; krzysztof.kozlowski+dt@linaro.org;
> conor+dt@kernel.org; shawnguo@kernel.org; s.hauer@pengutronix.de;
> festevam@gmail.com; l.stach@pengutronix.de; a.fatoum@pengutronix.de;
> u.kleine-koenig@pengutronix.de
> Cc: linux-phy@lists.infradead.org; devicetree@vger.kernel.org;
> linux-arm-kernel@lists.infradead.org; linux-kernel@vger.kernel.org;
> kernel@pengutronix.de; dl-linux-imx <linux-imx@nxp.com>
> Subject: Re: [PATCH v1 2/3] dt-bindings: phy: phy-imx8-pcie: Add binding for
> different usecases of i.MX8QM PCIe PHYs
>
> On 29/08/2023 08:45, Richard Zhu wrote:
> > Add binding for different usecases of i.MX8QM PCIe PHYs.
> >
> > Signed-off-by: Richard Zhu <hongxing.zhu@nxp.com>
>
> This patch does not make sense on its own. Otherwise your previous patch has
> invalid path.
>
> > ---
> > include/dt-bindings/phy/phy-imx8-pcie.h | 7 +++++++
> > 1 file changed, 7 insertions(+)
> >
> > diff --git a/include/dt-bindings/phy/phy-imx8-pcie.h
> > b/include/dt-bindings/phy/phy-imx8-pcie.h
> > index 8bbe2d6538d8..c8425c172118 100644
> > --- a/include/dt-bindings/phy/phy-imx8-pcie.h
> > +++ b/include/dt-bindings/phy/phy-imx8-pcie.h
> > @@ -11,4 +11,11 @@
> > #define IMX8_PCIE_REFCLK_PAD_INPUT 1
> > #define IMX8_PCIE_REFCLK_PAD_OUTPUT 2
> >
> > +/*
> > + * Different usecases of i.MX8QM HSIO(High Speed IO) module.
> > + */
> > +#define PCIEAX2SATA 1
> > +#define PCIEAX1PCIEBX1SATA 2
> > +#define PCIEAX2PCIEBX1 3
>
> Drop indentation. Look at the define few lines above and compare.
>
> Anyway, this is neither explained nor looking like hardware property.
> Nothing in the commit msg or in doc here justifies these constants. Drop and use
> existing properties.
This property is used to specify the work mode of HSIO subsystem.
The HSIO and the PHYs contained in it would be initialized together refer to
the different work modes. See the detailed discussion in #1 patch.
Best Regards
Richard Zhu
>
>
> Best regards,
> Krzysztof
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [PATCH v1 1/3] dt-bindings: phy: Add i.MX8QM PCIe PHY binding
2023-08-30 7:31 ` Hongxing Zhu
(?)
@ 2023-08-30 7:37 ` Krzysztof Kozlowski
-1 siblings, 0 replies; 30+ messages in thread
From: Krzysztof Kozlowski @ 2023-08-30 7:37 UTC (permalink / raw)
To: Hongxing Zhu, vkoul, kishon, robh+dt, krzysztof.kozlowski+dt,
conor+dt, shawnguo, s.hauer, festevam, l.stach, a.fatoum,
u.kleine-koenig
Cc: linux-phy, devicetree, linux-arm-kernel, linux-kernel, kernel,
dl-linux-imx
On 30/08/2023 09:31, Hongxing Zhu wrote:
>>
>>> + description: |
>>> + Specifies the different usecases supported by the HSIO(High
>>> + Speed IO)
>>
>> I don't know what are the usecases...
> Sorry, miss one space between "use" and "cases".
I did not mean language typo, but in general - what are you describing here?
> i.MX8QM HSIO module can be controlled by DSC/software in these three
> different modes. So I add this property (fsl,hsio-cfg) here to specify the
> work mode of HSIO.
So modes of work? Or different device attached to the PHY? Or what?
There is no use case in hardware and you should describe hardware.
>>
>>> + module. PCIEAX2SATA means two lanes PCIea and a single lane SATA.
>>> + PCIEAX1PCIEBX1SATA represents a single lane PCIea, a single lane
>>> + PCIeb and a single lane SATA. PCIEAX2PCIEBX1 on behalf of a two
>>> + lanes PCIea, a single lane PCIeb.
>>> + Refer include/dt-bindings/phy/phy-imx8-pcie.h for the constants to
>>> + be used (optional).
>>
>> None of all this helped me to understand what part of hardware this is responsible
>> for. It seems you just want to program a register, but instead you should use one
>> of existing properties like phy-modes etc.
> It's my bad. Didn't describe the HW clearly above.
> The fsl,hsio-cfg is used to specify the work mode of HSIO subsystem, not only
> the PHY mode. Since the PHYs are contained in the HSIO subsystem, can't be
> used by PCIe or SATA controller freely. The usage of these PHYs are limited
> by the HSIO work modes. BTW, up to now, I still don't have a good idea to
> describe the HSIO by phy-modes property although I prefer this way in my mind.
What is HSIO and why does it appear in context of this phy?
Specifically, if this is separate subsystem, why do you put HSIO
property in the phy? No, that does not seem right.
>>
>>> + $ref: /schemas/types.yaml#/definitions/uint32
>>> + enum: [ 1, 2, 3 ]
>>> +
>>> + ctrl-csr:
>>> + $ref: /schemas/types.yaml#/definitions/phandle
>>> + description:
>>> + phandle to the ctrl-csr region containing the HSIO control and
>>> + status registers for PCIe or SATA controller (optional).
>>
>> Please try some internal review before posting to patches. Community is not cheap
>> reviewers taking this duty from NXP. I am pretty sure NXP can afford someone
>> looking at the code.
>>
>> This misses vendor prefix, as explained many times for every syscon phandle. Also
>> optional is redundant.
> Sorry about the missing prefix. The prefix would be added later.
> And the optional would be removed. Thanks.
>>
>> But anyway status of PCIe or SATA controller is not a property of the phy, so it
>> looks to me you stuff here some properties belonging to some other missing
>> devices.
> I see. You're right the status of PCIe or SATA controller is not a property
> of the PHY. Some bits contained in the ctrl-csr region, are used to kick
> off resets through the internal glue logic. So, this property is added
> for phy driver.
Sorry, I am really fed up with the syscons. See here:
https://lore.kernel.org/all/20230830031846.127957-2-william.qiu@starfivetech.com/
I cannot trust you on this anymore. Describe hardware properly. If you
have resets, you have reset controller. If you have clocks, then clock
controller.
>>
>>> +
>>> + misc-csr:
>>> + $ref: /schemas/types.yaml#/definitions/phandle
>>> + description:
>>> + phandle to the misc-csr region containing the HSIO control and
>>> + status registers for misc (optional).
>>
>> Same problems.
>>
> "fsl,hsio-" prefix would be added later.
If you have some HSIO block, why do you reference it via phandle and why
do you put its properties (mode) here? What is the relation between HSIO
and this? So many questions... from your commit description all this
looks entirely wrong. You messed description of HSIO and now try to
bandage it with such properties. No.
NAK.
Best regards,
Krzysztof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [PATCH v1 1/3] dt-bindings: phy: Add i.MX8QM PCIe PHY binding
@ 2023-08-30 7:37 ` Krzysztof Kozlowski
0 siblings, 0 replies; 30+ messages in thread
From: Krzysztof Kozlowski @ 2023-08-30 7:37 UTC (permalink / raw)
To: Hongxing Zhu, vkoul, kishon, robh+dt, krzysztof.kozlowski+dt,
conor+dt, shawnguo, s.hauer, festevam, l.stach, a.fatoum,
u.kleine-koenig
Cc: linux-phy, devicetree, linux-arm-kernel, linux-kernel, kernel,
dl-linux-imx
On 30/08/2023 09:31, Hongxing Zhu wrote:
>>
>>> + description: |
>>> + Specifies the different usecases supported by the HSIO(High
>>> + Speed IO)
>>
>> I don't know what are the usecases...
> Sorry, miss one space between "use" and "cases".
I did not mean language typo, but in general - what are you describing here?
> i.MX8QM HSIO module can be controlled by DSC/software in these three
> different modes. So I add this property (fsl,hsio-cfg) here to specify the
> work mode of HSIO.
So modes of work? Or different device attached to the PHY? Or what?
There is no use case in hardware and you should describe hardware.
>>
>>> + module. PCIEAX2SATA means two lanes PCIea and a single lane SATA.
>>> + PCIEAX1PCIEBX1SATA represents a single lane PCIea, a single lane
>>> + PCIeb and a single lane SATA. PCIEAX2PCIEBX1 on behalf of a two
>>> + lanes PCIea, a single lane PCIeb.
>>> + Refer include/dt-bindings/phy/phy-imx8-pcie.h for the constants to
>>> + be used (optional).
>>
>> None of all this helped me to understand what part of hardware this is responsible
>> for. It seems you just want to program a register, but instead you should use one
>> of existing properties like phy-modes etc.
> It's my bad. Didn't describe the HW clearly above.
> The fsl,hsio-cfg is used to specify the work mode of HSIO subsystem, not only
> the PHY mode. Since the PHYs are contained in the HSIO subsystem, can't be
> used by PCIe or SATA controller freely. The usage of these PHYs are limited
> by the HSIO work modes. BTW, up to now, I still don't have a good idea to
> describe the HSIO by phy-modes property although I prefer this way in my mind.
What is HSIO and why does it appear in context of this phy?
Specifically, if this is separate subsystem, why do you put HSIO
property in the phy? No, that does not seem right.
>>
>>> + $ref: /schemas/types.yaml#/definitions/uint32
>>> + enum: [ 1, 2, 3 ]
>>> +
>>> + ctrl-csr:
>>> + $ref: /schemas/types.yaml#/definitions/phandle
>>> + description:
>>> + phandle to the ctrl-csr region containing the HSIO control and
>>> + status registers for PCIe or SATA controller (optional).
>>
>> Please try some internal review before posting to patches. Community is not cheap
>> reviewers taking this duty from NXP. I am pretty sure NXP can afford someone
>> looking at the code.
>>
>> This misses vendor prefix, as explained many times for every syscon phandle. Also
>> optional is redundant.
> Sorry about the missing prefix. The prefix would be added later.
> And the optional would be removed. Thanks.
>>
>> But anyway status of PCIe or SATA controller is not a property of the phy, so it
>> looks to me you stuff here some properties belonging to some other missing
>> devices.
> I see. You're right the status of PCIe or SATA controller is not a property
> of the PHY. Some bits contained in the ctrl-csr region, are used to kick
> off resets through the internal glue logic. So, this property is added
> for phy driver.
Sorry, I am really fed up with the syscons. See here:
https://lore.kernel.org/all/20230830031846.127957-2-william.qiu@starfivetech.com/
I cannot trust you on this anymore. Describe hardware properly. If you
have resets, you have reset controller. If you have clocks, then clock
controller.
>>
>>> +
>>> + misc-csr:
>>> + $ref: /schemas/types.yaml#/definitions/phandle
>>> + description:
>>> + phandle to the misc-csr region containing the HSIO control and
>>> + status registers for misc (optional).
>>
>> Same problems.
>>
> "fsl,hsio-" prefix would be added later.
If you have some HSIO block, why do you reference it via phandle and why
do you put its properties (mode) here? What is the relation between HSIO
and this? So many questions... from your commit description all this
looks entirely wrong. You messed description of HSIO and now try to
bandage it with such properties. No.
NAK.
Best regards,
Krzysztof
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [PATCH v1 1/3] dt-bindings: phy: Add i.MX8QM PCIe PHY binding
@ 2023-08-30 7:37 ` Krzysztof Kozlowski
0 siblings, 0 replies; 30+ messages in thread
From: Krzysztof Kozlowski @ 2023-08-30 7:37 UTC (permalink / raw)
To: Hongxing Zhu, vkoul, kishon, robh+dt, krzysztof.kozlowski+dt,
conor+dt, shawnguo, s.hauer, festevam, l.stach, a.fatoum,
u.kleine-koenig
Cc: linux-phy, devicetree, linux-arm-kernel, linux-kernel, kernel,
dl-linux-imx
On 30/08/2023 09:31, Hongxing Zhu wrote:
>>
>>> + description: |
>>> + Specifies the different usecases supported by the HSIO(High
>>> + Speed IO)
>>
>> I don't know what are the usecases...
> Sorry, miss one space between "use" and "cases".
I did not mean language typo, but in general - what are you describing here?
> i.MX8QM HSIO module can be controlled by DSC/software in these three
> different modes. So I add this property (fsl,hsio-cfg) here to specify the
> work mode of HSIO.
So modes of work? Or different device attached to the PHY? Or what?
There is no use case in hardware and you should describe hardware.
>>
>>> + module. PCIEAX2SATA means two lanes PCIea and a single lane SATA.
>>> + PCIEAX1PCIEBX1SATA represents a single lane PCIea, a single lane
>>> + PCIeb and a single lane SATA. PCIEAX2PCIEBX1 on behalf of a two
>>> + lanes PCIea, a single lane PCIeb.
>>> + Refer include/dt-bindings/phy/phy-imx8-pcie.h for the constants to
>>> + be used (optional).
>>
>> None of all this helped me to understand what part of hardware this is responsible
>> for. It seems you just want to program a register, but instead you should use one
>> of existing properties like phy-modes etc.
> It's my bad. Didn't describe the HW clearly above.
> The fsl,hsio-cfg is used to specify the work mode of HSIO subsystem, not only
> the PHY mode. Since the PHYs are contained in the HSIO subsystem, can't be
> used by PCIe or SATA controller freely. The usage of these PHYs are limited
> by the HSIO work modes. BTW, up to now, I still don't have a good idea to
> describe the HSIO by phy-modes property although I prefer this way in my mind.
What is HSIO and why does it appear in context of this phy?
Specifically, if this is separate subsystem, why do you put HSIO
property in the phy? No, that does not seem right.
>>
>>> + $ref: /schemas/types.yaml#/definitions/uint32
>>> + enum: [ 1, 2, 3 ]
>>> +
>>> + ctrl-csr:
>>> + $ref: /schemas/types.yaml#/definitions/phandle
>>> + description:
>>> + phandle to the ctrl-csr region containing the HSIO control and
>>> + status registers for PCIe or SATA controller (optional).
>>
>> Please try some internal review before posting to patches. Community is not cheap
>> reviewers taking this duty from NXP. I am pretty sure NXP can afford someone
>> looking at the code.
>>
>> This misses vendor prefix, as explained many times for every syscon phandle. Also
>> optional is redundant.
> Sorry about the missing prefix. The prefix would be added later.
> And the optional would be removed. Thanks.
>>
>> But anyway status of PCIe or SATA controller is not a property of the phy, so it
>> looks to me you stuff here some properties belonging to some other missing
>> devices.
> I see. You're right the status of PCIe or SATA controller is not a property
> of the PHY. Some bits contained in the ctrl-csr region, are used to kick
> off resets through the internal glue logic. So, this property is added
> for phy driver.
Sorry, I am really fed up with the syscons. See here:
https://lore.kernel.org/all/20230830031846.127957-2-william.qiu@starfivetech.com/
I cannot trust you on this anymore. Describe hardware properly. If you
have resets, you have reset controller. If you have clocks, then clock
controller.
>>
>>> +
>>> + misc-csr:
>>> + $ref: /schemas/types.yaml#/definitions/phandle
>>> + description:
>>> + phandle to the misc-csr region containing the HSIO control and
>>> + status registers for misc (optional).
>>
>> Same problems.
>>
> "fsl,hsio-" prefix would be added later.
If you have some HSIO block, why do you reference it via phandle and why
do you put its properties (mode) here? What is the relation between HSIO
and this? So many questions... from your commit description all this
looks entirely wrong. You messed description of HSIO and now try to
bandage it with such properties. No.
NAK.
Best regards,
Krzysztof
^ permalink raw reply [flat|nested] 30+ messages in thread
* RE: [PATCH v1 1/3] dt-bindings: phy: Add i.MX8QM PCIe PHY binding
2023-08-30 7:37 ` Krzysztof Kozlowski
(?)
@ 2023-08-31 6:33 ` Hongxing Zhu
-1 siblings, 0 replies; 30+ messages in thread
From: Hongxing Zhu @ 2023-08-31 6:33 UTC (permalink / raw)
To: Krzysztof Kozlowski, vkoul, kishon, robh+dt,
krzysztof.kozlowski+dt, conor+dt, shawnguo, s.hauer, festevam,
l.stach, a.fatoum, u.kleine-koenig
Cc: linux-phy, devicetree, linux-arm-kernel, linux-kernel, kernel,
dl-linux-imx
> -----Original Message-----
> From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> Sent: 2023年8月30日 15:37
> To: Hongxing Zhu <hongxing.zhu@nxp.com>; vkoul@kernel.org;
> kishon@kernel.org; robh+dt@kernel.org; krzysztof.kozlowski+dt@linaro.org;
> conor+dt@kernel.org; shawnguo@kernel.org; s.hauer@pengutronix.de;
> festevam@gmail.com; l.stach@pengutronix.de; a.fatoum@pengutronix.de;
> u.kleine-koenig@pengutronix.de
> Cc: linux-phy@lists.infradead.org; devicetree@vger.kernel.org;
> linux-arm-kernel@lists.infradead.org; linux-kernel@vger.kernel.org;
> kernel@pengutronix.de; dl-linux-imx <linux-imx@nxp.com>
> Subject: Re: [PATCH v1 1/3] dt-bindings: phy: Add i.MX8QM PCIe PHY binding
>
> On 30/08/2023 09:31, Hongxing Zhu wrote:
> >>
> >>> + description: |
> >>> + Specifies the different usecases supported by the HSIO(High
> >>> + Speed IO)
> >>
> >> I don't know what are the usecases...
> > Sorry, miss one space between "use" and "cases".
>
> I did not mean language typo, but in general - what are you describing here?
>
> > i.MX8QM HSIO module can be controlled by DSC/software in these three
> > different modes. So I add this property (fsl,hsio-cfg) here to specify
> > the work mode of HSIO.
>
> So modes of work? Or different device attached to the PHY? Or what?
> There is no use case in hardware and you should describe hardware.
>
Okay, I see.
More exactly, HSIO subsystem defines three use cases.
Anyway, it's should be another stuffs, and shouldn't be described
in PHY dt-bindings.
> >>
> >>> + module. PCIEAX2SATA means two lanes PCIea and a single lane SATA.
> >>> + PCIEAX1PCIEBX1SATA represents a single lane PCIea, a single lane
> >>> + PCIeb and a single lane SATA. PCIEAX2PCIEBX1 on behalf of a two
> >>> + lanes PCIea, a single lane PCIeb.
> >>> + Refer include/dt-bindings/phy/phy-imx8-pcie.h for the constants to
> >>> + be used (optional).
> >>
> >> None of all this helped me to understand what part of hardware this
> >> is responsible for. It seems you just want to program a register, but
> >> instead you should use one of existing properties like phy-modes etc.
> > It's my bad. Didn't describe the HW clearly above.
> > The fsl,hsio-cfg is used to specify the work mode of HSIO subsystem,
> > not only the PHY mode. Since the PHYs are contained in the HSIO
> > subsystem, can't be used by PCIe or SATA controller freely. The usage
> > of these PHYs are limited by the HSIO work modes. BTW, up to now, I
> > still don't have a good idea to describe the HSIO by phy-modes property
> although I prefer this way in my mind.
>
> What is HSIO and why does it appear in context of this phy?
> Specifically, if this is separate subsystem, why do you put HSIO property in the
> phy? No, that does not seem right.
>
Understand, the descriptions of HSIO subsystem shouldn't be contained in the
PHY dt-binding document.
> >>
> >>> + $ref: /schemas/types.yaml#/definitions/uint32
> >>> + enum: [ 1, 2, 3 ]
> >>> +
> >>> + ctrl-csr:
> >>> + $ref: /schemas/types.yaml#/definitions/phandle
> >>> + description:
> >>> + phandle to the ctrl-csr region containing the HSIO control and
> >>> + status registers for PCIe or SATA controller (optional).
> >>
> >> Please try some internal review before posting to patches. Community
> >> is not cheap reviewers taking this duty from NXP. I am pretty sure
> >> NXP can afford someone looking at the code.
> >>
> >> This misses vendor prefix, as explained many times for every syscon
> >> phandle. Also optional is redundant.
> > Sorry about the missing prefix. The prefix would be added later.
> > And the optional would be removed. Thanks.
> >>
> >> But anyway status of PCIe or SATA controller is not a property of the
> >> phy, so it looks to me you stuff here some properties belonging to
> >> some other missing devices.
> > I see. You're right the status of PCIe or SATA controller is not a
> > property of the PHY. Some bits contained in the ctrl-csr region, are
> > used to kick off resets through the internal glue logic. So, this
> > property is added for phy driver.
>
> Sorry, I am really fed up with the syscons. See here:
> https://lore.kern/
> el.org%2Fall%2F20230830031846.127957-2-william.qiu%40starfivetech.com%
> 2F&data=05%7C01%7Chongxing.zhu%40nxp.com%7C4c2a5cffc6d248121c860
> 8dba92bf3b5%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C63828
> 9778466923849%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJ
> QIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata
> =2mYhvXFxcQstDD9yC969S1CRvzz19eN2lZykLhxz9A0%3D&reserved=0
>
> I cannot trust you on this anymore. Describe hardware properly. If you have
> resets, you have reset controller. If you have clocks, then clock controller.
>
> >>
> >>> +
> >>> + misc-csr:
> >>> + $ref: /schemas/types.yaml#/definitions/phandle
> >>> + description:
> >>> + phandle to the misc-csr region containing the HSIO control and
> >>> + status registers for misc (optional).
> >>
> >> Same problems.
> >>
> > "fsl,hsio-" prefix would be added later.
>
>
> If you have some HSIO block, why do you reference it via phandle and why do
> you put its properties (mode) here? What is the relation between HSIO and this?
> So many questions... from your commit description all this looks entirely wrong.
> You messed description of HSIO and now try to bandage it with such properties.
> No.
Thanks for your comments. Now, I have much more clearer view. PHY dt-binding
should only have the HW descriptions of the PHY, the HSIO subsystem shouldn't
be mentioned and be messed with PHY dt-binding here.
I would remove all the HSIO description in next step, thanks for your review
again.
Best Regards
Richard Zhu
>
> NAK.
>
>
>
> Best regards,
> Krzysztof
^ permalink raw reply [flat|nested] 30+ messages in thread
* RE: [PATCH v1 1/3] dt-bindings: phy: Add i.MX8QM PCIe PHY binding
@ 2023-08-31 6:33 ` Hongxing Zhu
0 siblings, 0 replies; 30+ messages in thread
From: Hongxing Zhu @ 2023-08-31 6:33 UTC (permalink / raw)
To: Krzysztof Kozlowski, vkoul, kishon, robh+dt,
krzysztof.kozlowski+dt, conor+dt, shawnguo, s.hauer, festevam,
l.stach, a.fatoum, u.kleine-koenig
Cc: linux-phy, devicetree, linux-arm-kernel, linux-kernel, kernel,
dl-linux-imx
> -----Original Message-----
> From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> Sent: 2023年8月30日 15:37
> To: Hongxing Zhu <hongxing.zhu@nxp.com>; vkoul@kernel.org;
> kishon@kernel.org; robh+dt@kernel.org; krzysztof.kozlowski+dt@linaro.org;
> conor+dt@kernel.org; shawnguo@kernel.org; s.hauer@pengutronix.de;
> festevam@gmail.com; l.stach@pengutronix.de; a.fatoum@pengutronix.de;
> u.kleine-koenig@pengutronix.de
> Cc: linux-phy@lists.infradead.org; devicetree@vger.kernel.org;
> linux-arm-kernel@lists.infradead.org; linux-kernel@vger.kernel.org;
> kernel@pengutronix.de; dl-linux-imx <linux-imx@nxp.com>
> Subject: Re: [PATCH v1 1/3] dt-bindings: phy: Add i.MX8QM PCIe PHY binding
>
> On 30/08/2023 09:31, Hongxing Zhu wrote:
> >>
> >>> + description: |
> >>> + Specifies the different usecases supported by the HSIO(High
> >>> + Speed IO)
> >>
> >> I don't know what are the usecases...
> > Sorry, miss one space between "use" and "cases".
>
> I did not mean language typo, but in general - what are you describing here?
>
> > i.MX8QM HSIO module can be controlled by DSC/software in these three
> > different modes. So I add this property (fsl,hsio-cfg) here to specify
> > the work mode of HSIO.
>
> So modes of work? Or different device attached to the PHY? Or what?
> There is no use case in hardware and you should describe hardware.
>
Okay, I see.
More exactly, HSIO subsystem defines three use cases.
Anyway, it's should be another stuffs, and shouldn't be described
in PHY dt-bindings.
> >>
> >>> + module. PCIEAX2SATA means two lanes PCIea and a single lane SATA.
> >>> + PCIEAX1PCIEBX1SATA represents a single lane PCIea, a single lane
> >>> + PCIeb and a single lane SATA. PCIEAX2PCIEBX1 on behalf of a two
> >>> + lanes PCIea, a single lane PCIeb.
> >>> + Refer include/dt-bindings/phy/phy-imx8-pcie.h for the constants to
> >>> + be used (optional).
> >>
> >> None of all this helped me to understand what part of hardware this
> >> is responsible for. It seems you just want to program a register, but
> >> instead you should use one of existing properties like phy-modes etc.
> > It's my bad. Didn't describe the HW clearly above.
> > The fsl,hsio-cfg is used to specify the work mode of HSIO subsystem,
> > not only the PHY mode. Since the PHYs are contained in the HSIO
> > subsystem, can't be used by PCIe or SATA controller freely. The usage
> > of these PHYs are limited by the HSIO work modes. BTW, up to now, I
> > still don't have a good idea to describe the HSIO by phy-modes property
> although I prefer this way in my mind.
>
> What is HSIO and why does it appear in context of this phy?
> Specifically, if this is separate subsystem, why do you put HSIO property in the
> phy? No, that does not seem right.
>
Understand, the descriptions of HSIO subsystem shouldn't be contained in the
PHY dt-binding document.
> >>
> >>> + $ref: /schemas/types.yaml#/definitions/uint32
> >>> + enum: [ 1, 2, 3 ]
> >>> +
> >>> + ctrl-csr:
> >>> + $ref: /schemas/types.yaml#/definitions/phandle
> >>> + description:
> >>> + phandle to the ctrl-csr region containing the HSIO control and
> >>> + status registers for PCIe or SATA controller (optional).
> >>
> >> Please try some internal review before posting to patches. Community
> >> is not cheap reviewers taking this duty from NXP. I am pretty sure
> >> NXP can afford someone looking at the code.
> >>
> >> This misses vendor prefix, as explained many times for every syscon
> >> phandle. Also optional is redundant.
> > Sorry about the missing prefix. The prefix would be added later.
> > And the optional would be removed. Thanks.
> >>
> >> But anyway status of PCIe or SATA controller is not a property of the
> >> phy, so it looks to me you stuff here some properties belonging to
> >> some other missing devices.
> > I see. You're right the status of PCIe or SATA controller is not a
> > property of the PHY. Some bits contained in the ctrl-csr region, are
> > used to kick off resets through the internal glue logic. So, this
> > property is added for phy driver.
>
> Sorry, I am really fed up with the syscons. See here:
> https://lore.kern/
> el.org%2Fall%2F20230830031846.127957-2-william.qiu%40starfivetech.com%
> 2F&data=05%7C01%7Chongxing.zhu%40nxp.com%7C4c2a5cffc6d248121c860
> 8dba92bf3b5%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C63828
> 9778466923849%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJ
> QIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata
> =2mYhvXFxcQstDD9yC969S1CRvzz19eN2lZykLhxz9A0%3D&reserved=0
>
> I cannot trust you on this anymore. Describe hardware properly. If you have
> resets, you have reset controller. If you have clocks, then clock controller.
>
> >>
> >>> +
> >>> + misc-csr:
> >>> + $ref: /schemas/types.yaml#/definitions/phandle
> >>> + description:
> >>> + phandle to the misc-csr region containing the HSIO control and
> >>> + status registers for misc (optional).
> >>
> >> Same problems.
> >>
> > "fsl,hsio-" prefix would be added later.
>
>
> If you have some HSIO block, why do you reference it via phandle and why do
> you put its properties (mode) here? What is the relation between HSIO and this?
> So many questions... from your commit description all this looks entirely wrong.
> You messed description of HSIO and now try to bandage it with such properties.
> No.
Thanks for your comments. Now, I have much more clearer view. PHY dt-binding
should only have the HW descriptions of the PHY, the HSIO subsystem shouldn't
be mentioned and be messed with PHY dt-binding here.
I would remove all the HSIO description in next step, thanks for your review
again.
Best Regards
Richard Zhu
>
> NAK.
>
>
>
> Best regards,
> Krzysztof
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
^ permalink raw reply [flat|nested] 30+ messages in thread
* RE: [PATCH v1 1/3] dt-bindings: phy: Add i.MX8QM PCIe PHY binding
@ 2023-08-31 6:33 ` Hongxing Zhu
0 siblings, 0 replies; 30+ messages in thread
From: Hongxing Zhu @ 2023-08-31 6:33 UTC (permalink / raw)
To: Krzysztof Kozlowski, vkoul, kishon, robh+dt,
krzysztof.kozlowski+dt, conor+dt, shawnguo, s.hauer, festevam,
l.stach, a.fatoum, u.kleine-koenig
Cc: linux-phy, devicetree, linux-arm-kernel, linux-kernel, kernel,
dl-linux-imx
> -----Original Message-----
> From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> Sent: 2023年8月30日 15:37
> To: Hongxing Zhu <hongxing.zhu@nxp.com>; vkoul@kernel.org;
> kishon@kernel.org; robh+dt@kernel.org; krzysztof.kozlowski+dt@linaro.org;
> conor+dt@kernel.org; shawnguo@kernel.org; s.hauer@pengutronix.de;
> festevam@gmail.com; l.stach@pengutronix.de; a.fatoum@pengutronix.de;
> u.kleine-koenig@pengutronix.de
> Cc: linux-phy@lists.infradead.org; devicetree@vger.kernel.org;
> linux-arm-kernel@lists.infradead.org; linux-kernel@vger.kernel.org;
> kernel@pengutronix.de; dl-linux-imx <linux-imx@nxp.com>
> Subject: Re: [PATCH v1 1/3] dt-bindings: phy: Add i.MX8QM PCIe PHY binding
>
> On 30/08/2023 09:31, Hongxing Zhu wrote:
> >>
> >>> + description: |
> >>> + Specifies the different usecases supported by the HSIO(High
> >>> + Speed IO)
> >>
> >> I don't know what are the usecases...
> > Sorry, miss one space between "use" and "cases".
>
> I did not mean language typo, but in general - what are you describing here?
>
> > i.MX8QM HSIO module can be controlled by DSC/software in these three
> > different modes. So I add this property (fsl,hsio-cfg) here to specify
> > the work mode of HSIO.
>
> So modes of work? Or different device attached to the PHY? Or what?
> There is no use case in hardware and you should describe hardware.
>
Okay, I see.
More exactly, HSIO subsystem defines three use cases.
Anyway, it's should be another stuffs, and shouldn't be described
in PHY dt-bindings.
> >>
> >>> + module. PCIEAX2SATA means two lanes PCIea and a single lane SATA.
> >>> + PCIEAX1PCIEBX1SATA represents a single lane PCIea, a single lane
> >>> + PCIeb and a single lane SATA. PCIEAX2PCIEBX1 on behalf of a two
> >>> + lanes PCIea, a single lane PCIeb.
> >>> + Refer include/dt-bindings/phy/phy-imx8-pcie.h for the constants to
> >>> + be used (optional).
> >>
> >> None of all this helped me to understand what part of hardware this
> >> is responsible for. It seems you just want to program a register, but
> >> instead you should use one of existing properties like phy-modes etc.
> > It's my bad. Didn't describe the HW clearly above.
> > The fsl,hsio-cfg is used to specify the work mode of HSIO subsystem,
> > not only the PHY mode. Since the PHYs are contained in the HSIO
> > subsystem, can't be used by PCIe or SATA controller freely. The usage
> > of these PHYs are limited by the HSIO work modes. BTW, up to now, I
> > still don't have a good idea to describe the HSIO by phy-modes property
> although I prefer this way in my mind.
>
> What is HSIO and why does it appear in context of this phy?
> Specifically, if this is separate subsystem, why do you put HSIO property in the
> phy? No, that does not seem right.
>
Understand, the descriptions of HSIO subsystem shouldn't be contained in the
PHY dt-binding document.
> >>
> >>> + $ref: /schemas/types.yaml#/definitions/uint32
> >>> + enum: [ 1, 2, 3 ]
> >>> +
> >>> + ctrl-csr:
> >>> + $ref: /schemas/types.yaml#/definitions/phandle
> >>> + description:
> >>> + phandle to the ctrl-csr region containing the HSIO control and
> >>> + status registers for PCIe or SATA controller (optional).
> >>
> >> Please try some internal review before posting to patches. Community
> >> is not cheap reviewers taking this duty from NXP. I am pretty sure
> >> NXP can afford someone looking at the code.
> >>
> >> This misses vendor prefix, as explained many times for every syscon
> >> phandle. Also optional is redundant.
> > Sorry about the missing prefix. The prefix would be added later.
> > And the optional would be removed. Thanks.
> >>
> >> But anyway status of PCIe or SATA controller is not a property of the
> >> phy, so it looks to me you stuff here some properties belonging to
> >> some other missing devices.
> > I see. You're right the status of PCIe or SATA controller is not a
> > property of the PHY. Some bits contained in the ctrl-csr region, are
> > used to kick off resets through the internal glue logic. So, this
> > property is added for phy driver.
>
> Sorry, I am really fed up with the syscons. See here:
> https://lore.kern/
> el.org%2Fall%2F20230830031846.127957-2-william.qiu%40starfivetech.com%
> 2F&data=05%7C01%7Chongxing.zhu%40nxp.com%7C4c2a5cffc6d248121c860
> 8dba92bf3b5%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C63828
> 9778466923849%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJ
> QIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata
> =2mYhvXFxcQstDD9yC969S1CRvzz19eN2lZykLhxz9A0%3D&reserved=0
>
> I cannot trust you on this anymore. Describe hardware properly. If you have
> resets, you have reset controller. If you have clocks, then clock controller.
>
> >>
> >>> +
> >>> + misc-csr:
> >>> + $ref: /schemas/types.yaml#/definitions/phandle
> >>> + description:
> >>> + phandle to the misc-csr region containing the HSIO control and
> >>> + status registers for misc (optional).
> >>
> >> Same problems.
> >>
> > "fsl,hsio-" prefix would be added later.
>
>
> If you have some HSIO block, why do you reference it via phandle and why do
> you put its properties (mode) here? What is the relation between HSIO and this?
> So many questions... from your commit description all this looks entirely wrong.
> You messed description of HSIO and now try to bandage it with such properties.
> No.
Thanks for your comments. Now, I have much more clearer view. PHY dt-binding
should only have the HW descriptions of the PHY, the HSIO subsystem shouldn't
be mentioned and be messed with PHY dt-binding here.
I would remove all the HSIO description in next step, thanks for your review
again.
Best Regards
Richard Zhu
>
> NAK.
>
>
>
> Best regards,
> Krzysztof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 30+ messages in thread
end of thread, other threads:[~2023-08-31 6:33 UTC | newest]
Thread overview: 30+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-08-29 6:45 [PATCH v1 0/3] Add i.MX8Q PCIe PHY driver Richard Zhu
2023-08-29 6:45 ` Richard Zhu
2023-08-29 6:45 ` Richard Zhu
2023-08-29 6:45 ` [PATCH v1 1/3] dt-bindings: phy: Add i.MX8QM PCIe PHY binding Richard Zhu
2023-08-29 6:45 ` Richard Zhu
2023-08-29 6:45 ` Richard Zhu
2023-08-29 7:47 ` Krzysztof Kozlowski
2023-08-29 7:47 ` Krzysztof Kozlowski
2023-08-29 7:47 ` Krzysztof Kozlowski
2023-08-30 7:31 ` Hongxing Zhu
2023-08-30 7:31 ` Hongxing Zhu
2023-08-30 7:31 ` Hongxing Zhu
2023-08-30 7:37 ` Krzysztof Kozlowski
2023-08-30 7:37 ` Krzysztof Kozlowski
2023-08-30 7:37 ` Krzysztof Kozlowski
2023-08-31 6:33 ` Hongxing Zhu
2023-08-31 6:33 ` Hongxing Zhu
2023-08-31 6:33 ` Hongxing Zhu
2023-08-29 6:45 ` [PATCH v1 2/3] dt-bindings: phy: phy-imx8-pcie: Add binding for different usecases of i.MX8QM PCIe PHYs Richard Zhu
2023-08-29 6:45 ` Richard Zhu
2023-08-29 6:45 ` Richard Zhu
2023-08-29 7:49 ` Krzysztof Kozlowski
2023-08-29 7:49 ` Krzysztof Kozlowski
2023-08-29 7:49 ` Krzysztof Kozlowski
2023-08-30 7:31 ` Hongxing Zhu
2023-08-30 7:31 ` Hongxing Zhu
2023-08-30 7:31 ` Hongxing Zhu
2023-08-29 6:45 ` [PATCH v1 3/3] phy: freescale: imx8q-pcie: Add i.MX8Q PCIe PHY driver Richard Zhu
2023-08-29 6:45 ` Richard Zhu
2023-08-29 6:45 ` Richard Zhu
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.