arm64: dts: freescale: Add support for LX2162 SoM & Clearfog Board
Subsystems (3)
v3 cover arm64: dts: freescale: Add support for LX2162 SoM & Clearfog Board
Add support for the SolidRun LX2162A System on Module (SoM), and the Clearfog evaluation board.
This patch-set introduces:
- dt node for lx2160a serdes block #2
- dtsi for lx2162a system on module
- dts for lx2162 clearfog
Firstly Please note that checkpatch was complaining about the EEPROMS:
- DT compatible string "st,24c02" appears un-documented
- DT compatible string "st,24c2048" appears un-documented
- DT compatible string "atmel,24c2048" appears un-documented However to my eyes these *are* already documented in at24.yaml, and are also used in existing device-tree.
checkpatch is also complaining about various parts of lx2160a.dtsi, as well as the use of "sfp" property in dpmac nodes - which are common across layerscape based dts.
Secondly the MAINTAINERS file has not been modified. Is it required I add myself or *someone* for these new dts?
Changes since v2:
- fixed property order in som dts such that compatible is first property
- added reviewed-by tags to bindings patches
Changes since v1:
- fixed DT binding changes to not break existing boards
- explained new board / som DT binding in commit message
- added missing DT binding for dpaa2 mac "phys" property
- reordered "compatible" and "reg" properties: first "compatible", then "reg"
- replaced chip-specific DT node names with generic ones
Josua Mayer (4):
arm64: dts: lx2160a: describe the SerDes block #2
dt-bindings: net: dpaa2 mac: add phys property
dt-bindings: arm: Add SolidRun LX2162A SoM & Clearfog Board
arm64: dts: freescale: Add support for LX2162 SoM & Clearfog Board
.../devicetree/bindings/arm/fsl.yaml | 9 +- .../bindings/net/fsl,qoriq-mc-dpmac.yaml | 4 + arch/arm64/boot/dts/freescale/Makefile | 1 + .../arm64/boot/dts/freescale/fsl-lx2160a.dtsi | 6 + .../dts/freescale/fsl-lx2162a-clearfog.dts | 371 ++++++++++++++++++ .../dts/freescale/fsl-lx2162a-sr-som.dtsi | 73 ++++ 6 files changed, 463 insertions(+), 1 deletion(-) create mode 100644 arch/arm64/boot/dts/freescale/fsl-lx2162a-clearfog.dts create mode 100644 arch/arm64/boot/dts/freescale/fsl-lx2162a-sr-som.dtsi
Signature · 1 line
2.35.3
PATCH v3 1/4 arm64: dts: lx2160a: describe the SerDes block #2
Add description for the LX2160A second SerDes block. It is functionally identical to the first one already added in:
3cbe93a "arch: arm64: dts: lx2160a: describe the SerDes block #1"
--- arch/arm64/boot/dts/freescale/fsl-lx2160a.dtsi | 6 ++++++ 1 file changed, 6 insertions(+)
arch/arm64/boot/dts/freescale/fsl-lx2160a.dtsi +6 -0
@@ -626,6 +626,12 @@ serdes_1: phy@1ea0000 { #phy-cells = <1>; }; + serdes_2: phy@1eb0000 { + compatible = "fsl,lynx-28g"; + reg = <0x0 0x1eb0000 0x0 0x1e30>; + #phy-cells = <1>; + }; + crypto: crypto@8000000 { compatible = "fsl,sec-v5.0", "fsl,sec-v4.0"; fsl,sec-era = <10>;
Signature · 1 line
2.35.3
PATCH v3 2/4 dt-bindings: net: dpaa2 mac: add phys property
In reply to Josua Mayerdpaa2 mac supports runtime configuration of network protocols on a generic phy object specified via the "phys" property. It is currently used with the SerDes28G driver to switch SerDes protocol between SGMII and USXGMII at runtime.
Support was introduced with:
f978fe8 "dpaa2-mac: configure the SerDes phy on a protocol change"
Add bindings description for the missing "phys" property, to fix dtc_chk errors present in various layerscape based dts:
'phys' does not match any of the regexes: 'pinctrl-[0-9]+'
---
V1 -> V2: this patch is newly added to patch-set
Documentation/devicetree/bindings/net/fsl,qoriq-mc-dpmac.yaml | 4 ++++ 1 file changed, 4 insertions(+)
Documentation/devicetree/bindings/net/fsl,qoriq-mc-dpmac.yaml +4 -0
@@ -24,6 +24,10 @@ properties: maxItems: 1 description: The DPMAC number + phys: + maxItems: 1 + description: Generic PHY for SerDes runtime configuration. + phy-handle: true phy-connection-type: true
Signature · 1 line
2.35.3
PATCH v3 3/4 dt-bindings: arm: Add SolidRun LX2162A SoM & Clearfog Board
In reply to Josua MayerSolidRun now have 2 product lines around NXP Layerscape SoC:
- LX2160A COM Express 7
- LX2162A System on Module
LX2162 is a smaller package and reduced feature set to LX2160A; LX2162 SoM is also a smaller form factor and reduced feature set to CEX.
Since both product lines are physically incompatible,
the existing group "SolidRun LX2160A based Boards" has been renamed to include "CEX" in its name, meaning products based on LX2160A COM Express Module, following this pattern:
"solidrun,<board>", "solidrun,lx2160a-cex", "fsl,lx2160a"
Add DT compatible for both SolidRun LX2162A SoM, and LX2162 Clearfog boards to a new group based on LX2162A SoM, following this pattern:
"solidrun,<board>", "solidrun,lx2162a-som", "fsl,lx2160a"
---
V1 -> V2: fixed to not break existing boards
V1 -> V2: explained new board / som DT binding in commit message
Documentation/devicetree/bindings/arm/fsl.yaml | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-)
Documentation/devicetree/bindings/arm/fsl.yaml +8 -1
@@ -1370,7 +1370,7 @@ properties: - fsl,lx2162a-qds - const: fsl,lx2160a - - description: SolidRun LX2160A based Boards + - description: SolidRun LX2160A CEX-7 based Boards items: - enum: - solidrun,clearfog-cx
@@ -1378,6 +1378,13 @@ properties: - const: solidrun,lx2160a-cex7 - const: fsl,lx2160a + - description: SolidRun LX2162A SoM based Boards + items: + - enum: + - solidrun,lx2162a-clearfog + - const: solidrun,lx2162a-som + - const: fsl,lx2160a + - description: S32G2 based Boards items: - enum:
Signature · 1 line
2.35.3
PATCH v3 4/4 arm64: dts: freescale: Add support for LX2162 SoM & Clearfog Board
In reply to Josua MayerAdd support for the SolidRun LX2162A System on Module (SoM), and the Clearfog evaluation board.
The SoM has few software-controllable features:
- AR8035 Ethernet PHY
- eMMC
- SPI Flash
- fan controller
- various eeproms
The Clearfog evaluation board provides:
- microSD connector
- USB-A
- 2x 10Gbps SFP+
- 2x 25Gbps SFP+ with a retimer
- 8x 2.5Gbps RJ45
- 2x mPCI (assembly option / disables 2xRJ45)
The 8x RJ45 ports are connected with an 8-port PHY: Marvell 88E2580 supporting up to 5Gbps, while SoC and magnetics are limited to 2.5Gbps.
However 2500 speed is untested due to documentation and drivier limitations. To avoid confusion the phy nodes have been explicitly limited to 1000 for now.
The PCI nodes are disabled, but explicitly added to mark that this board can have pci.
It is expected that the bootloader will patch the status property "okay" and disable 2x RJ45 ports, according to active serdes configuration.
---
V1 -> V2: reordered "compatible" and "reg" properties
V1 -> V2: replaced chip-specific DT node names with generic ones V1 -> V2: removed dead code from fspi node
V2 -> V3: dropped deprecated address-cells, address-size props from flash node
arch/arm64/boot/dts/freescale/Makefile | 1 + .../dts/freescale/fsl-lx2162a-clearfog.dts | 371 ++++++++++++++++++ .../dts/freescale/fsl-lx2162a-sr-som.dtsi | 73 ++++ 3 files changed, 445 insertions(+) create mode 100644 arch/arm64/boot/dts/freescale/fsl-lx2162a-clearfog.dts create mode 100644 arch/arm64/boot/dts/freescale/fsl-lx2162a-sr-som.dtsi
arch/arm64/boot/dts/freescale/Makefile +1 -0
@@ -34,6 +34,7 @@ dtb-$(CONFIG_ARCH_LAYERSCAPE) += fsl-lx2160a-honeycomb.dtb dtb-$(CONFIG_ARCH_LAYERSCAPE) += fsl-lx2160a-qds.dtb dtb-$(CONFIG_ARCH_LAYERSCAPE) += fsl-lx2160a-rdb.dtb dtb-$(CONFIG_ARCH_LAYERSCAPE) += fsl-lx2162a-qds.dtb +dtb-$(CONFIG_ARCH_LAYERSCAPE) += fsl-lx2162a-clearfog.dtb fsl-ls1028a-qds-13bb-dtbs := fsl-ls1028a-qds.dtb fsl-ls1028a-qds-13bb.dtbo fsl-ls1028a-qds-65bb-dtbs := fsl-ls1028a-qds.dtb fsl-ls1028a-qds-65bb.dtbo
arch/arm64/boot/dts/freescale/fsl-lx2162a-clearfog.dts new file +371 -0
371 lines not on this page · raw message
arch/arm64/boot/dts/freescale/fsl-lx2162a-sr-som.dtsi new file +73 -0
73 lines not on this page · raw message
Signature · 1 line
2.35.3
Quoted 230 lines · Josua Mayer
Add support for the SolidRun LX2162A System on Module (SoM), and the Clearfog evaluation board.
The SoM has few software-controllable features:
- AR8035 Ethernet PHY
- eMMC
- SPI Flash
- fan controller
- various eepromsThe Clearfog evaluation board provides:
- microSD connector
- USB-A
- 2x 10Gbps SFP+
- 2x 25Gbps SFP+ with a retimer
- 8x 2.5Gbps RJ45
- 2x mPCI (assembly option / disables 2xRJ45)The 8x RJ45 ports are connected with an 8-port PHY: Marvell 88E2580 supporting up to 5Gbps, while SoC and magnetics are limited to 2.5Gbps.
However 2500 speed is untested due to documentation and drivier limitations. To avoid confusion the phy nodes have been explicitly limited to 1000 for now.
The PCI nodes are disabled, but explicitly added to mark that this board can have pci.
It is expected that the bootloader will patch the status property "okay" and disable 2x RJ45 ports, according to active serdes configuration.Signed-off-by Josua Mayer <[email protected]>---
V1 -> V2: reordered "compatible" and "reg" properties
V1 -> V2: replaced chip-specific DT node names with generic ones V1 -> V2: removed dead code from fspi node
V2 -> V3: dropped deprecated address-cells, address-size props from flash nodearch/arm64/boot/dts/freescale/Makefile | 1 + .../dts/freescale/fsl-lx2162a-clearfog.dts | 371 ++++++++++++++++++ .../dts/freescale/fsl-lx2162a-sr-som.dtsi | 73 ++++ 3 files changed, 445 insertions(+) create mode 100644 arch/arm64/boot/dts/freescale/fsl-lx2162a-clearfog.dts create mode 100644 arch/arm64/boot/dts/freescale/fsl-lx2162a-sr-som.dtsiarch/arm64/boot/dts/freescale/Makefile +1
-0@@ -34,6 +34,7 @@ dtb-$(CONFIG_ARCH_LAYERSCAPE) += fsl-lx2160a-honeycomb.dtb dtb-$(CONFIG_ARCH_LAYERSCAPE) += fsl-lx2160a-qds.dtb dtb-$(CONFIG_ARCH_LAYERSCAPE) += fsl-lx2160a-rdb.dtb dtb-$(CONFIG_ARCH_LAYERSCAPE) += fsl-lx2162a-qds.dtb +dtb-$(CONFIG_ARCH_LAYERSCAPE) += fsl-lx2162a-clearfog.dtb fsl-ls1028a-qds-13bb-dtbs := fsl-ls1028a-qds.dtb fsl-ls1028a-qds-13bb.dtbo fsl-ls1028a-qds-65bb-dtbs := fsl-ls1028a-qds.dtb fsl-ls1028a-qds-65bb.dtboarch/arm64/boot/dts/freescale/fsl-lx2162a-clearfog.dts new file +168
-0@@ -0,0 +1,371 @@ +// SPDX-License-Identifier: (GPL-2.0 OR MIT) +// +// Device Tree file for LX2162A Clearfog +// +// Copyright 2023 Josua Mayer <[email protected]> + +/dts-v1/; + +#include "fsl-lx2160a.dtsi" +#include "fsl-lx2162a-sr-som.dtsi" + +/ { + model = "SolidRun LX2162A Clearfog"; + compatible = "solidrun,lx2162a-clearfog", "solidrun,lx2162a-som", "fsl,lx2160a"; + + aliases { + crypto = &crypto; + i2c0 = &i2c0; + i2c1 = &i2c2; + i2c2 = &i2c4; + i2c3 = &sfp_i2c0; + i2c4 = &sfp_i2c1; + i2c5 = &sfp_i2c2; + i2c6 = &sfp_i2c3; + i2c7 = &mpcie1_i2c; + i2c8 = &mpcie0_i2c; + i2c9 = &pcieclk_i2c; + mmc0 = &esdhc0; + mmc1 = &esdhc1; + serial0 = &uart0; + }; + + chosen { + stdout-path = "serial0:115200n8"; + }; + + leds { + compatible = "gpio-leds"; + + led_sfp_at: led-sfp-at { + gpios = <&gpio2 5 GPIO_ACTIVE_HIGH>; /* PROC_IRQ5 */ + default-state = "off"; + }; + led_sfp_ab: led-sfp-ab { + gpios = <&gpio2 11 GPIO_ACTIVE_HIGH>; /* PROC_IRQ11 */ + default-state = "off"; + }; + led_sfp_bt: led-sfp-bt { + gpios = <&gpio2 13 GPIO_ACTIVE_HIGH>; /* EVT1_B */ + default-state = "off"; + }; + led_sfp_bb: led-sfp-bb { + gpios = <&gpio2 14 GPIO_ACTIVE_HIGH>; /* EVT2_B */ + default-state = "off"; + }; + }; + + sfp_at: sfp-at { + compatible = "sff,sfp"; + i2c-bus = <&sfp_i2c0>; + mod-def0-gpios = <&gpio2 16 GPIO_ACTIVE_LOW>; /* EVT4_B */ + maximum-power-milliwatt = <2000>; + }; + + sfp_ab: sfp-ab { + compatible = "sff,sfp"; + i2c-bus = <&sfp_i2c1>; + mod-def0-gpios = <&gpio2 1 GPIO_ACTIVE_LOW>; /* PROC_IRQ1 */ + maximum-power-milliwatt = <2000>; + }; + + sfp_bt: sfp-bt { + compatible = "sff,sfp"; + i2c-bus = <&sfp_i2c2>; + mod-def0-gpios = <&gpio2 10 GPIO_ACTIVE_LOW>; /* PROC_IRQ10 */ + maximum-power-milliwatt = <2000>; + }; + + sfp_bb: sfp-bb { + compatible = "sff,sfp"; + i2c-bus = <&sfp_i2c3>; + mod-def0-gpios = <&gpio2 15 GPIO_ACTIVE_LOW>; /* EVT3_B */ + maximum-power-milliwatt = <2000>; + }; +}; + +&i2c2 { + status = "okay"; + + /* retimer@18 */ + + i2c-mux@70 { + compatible = "nxp,pca9546"; + reg = <0x70>; + #address-cells = <1>; + #size-cells = <0>; + i2c-mux-idle-disconnect; + + sfp_i2c0: i2c@0 { + #address-cells = <1>; + #size-cells = <0>; + reg = <0>; + }; + + sfp_i2c1: i2c@1 { + #address-cells = <1>; + #size-cells = <0>; + reg = <1>; + }; + + sfp_i2c2: i2c@2 { + #address-cells = <1>; + #size-cells = <0>; + reg = <2>; + }; + + sfp_i2c3: i2c@3 { + #address-cells = <1>; + #size-cells = <0>; + reg = <3>; + }; + }; + + i2c-mux@71 { + compatible = "nxp,pca9546"; + reg = <0x71>; + #address-cells = <1>; + #size-cells = <0>; + i2c-mux-idle-disconnect; + + mpcie1_i2c: i2c@0 { + #address-cells = <1>; + #size-cells = <0>; + reg = <0>; + }; + + mpcie0_i2c: i2c@1 { + #address-cells = <1>; + #size-cells = <0>; + reg = <1>; + }; + + pcieclk_i2c: i2c@2 { + #address-cells = <1>; + #size-cells = <0>; + reg = <2>; + + /* clock-controller@6b */ + }; + }; +}; + +&dpmac3 { + sfp = <&sfp_at>; + managed = "in-band-status"; + phys = <&serdes_1 7>; +}; + +&dpmac4 { + sfp = <&sfp_ab>; + managed = "in-band-status"; + phys = <&serdes_1 6>; +}; + +&dpmac5 { + sfp = <&sfp_bt>; + managed = "in-band-status"; + phys = <&serdes_1 5>;
arch/arm64/boot/dts/freescale/fsl-lx2162a-clearfog.dts line 178
Quoted 10 lines
arch/arm64/boot/dts/freescale/fsl-lx2162a-clearfog.dts new file +10
-0+}; + +&dpmac6 { + sfp = <&sfp_bb>; + managed = "in-band-status"; + phys = <&serdes_1 4>; +}; + +&dpmac11 { + status = "okay";
We generally end property list with 'status'.
Shawn
Quoted 275 lines
arch/arm64/boot/dts/freescale/fsl-lx2162a-clearfog.dts new file +193
-0+ phys = <&serdes_2 0>; + phy-handle = <ðernet_phy2>; + phy-connection-type = "sgmii"; +}; + +&dpmac12 { + status = "okay"; + phys = <&serdes_2 1>; + phy-handle = <ðernet_phy0>; + phy-connection-type = "sgmii"; +}; + +&dpmac13 { + status = "okay"; + phys = <&serdes_2 6>; + phy-handle = <ðernet_phy5>; + phy-connection-type = "sgmii"; +}; + +&dpmac14 { + status = "okay"; + phys = <&serdes_2 7>; + phy-handle = <ðernet_phy7>; + phy-connection-type = "sgmii"; +}; + +&dpmac15 { + status = "okay"; + phys = <&serdes_2 4>; + phy-handle = <ðernet_phy3>; + phy-connection-type = "sgmii"; +}; + +&dpmac16 { + status = "okay"; + phys = <&serdes_2 5>; + phy-handle = <ðernet_phy1>; + phy-connection-type = "sgmii"; +}; + +&dpmac17 { + /* override connection to on-SoM phy */ + /delete-property/ phy-handle; + /delete-property/ phy-connection-type; + + status = "okay"; + phys = <&serdes_2 2>; + phy-handle = <ðernet_phy4>; + phy-connection-type = "sgmii"; +}; + +&dpmac18 { + status = "okay"; + phys = <&serdes_2 3>; + phy-handle = <ðernet_phy6>; + phy-connection-type = "sgmii"; +}; + +&emdio1 { + /* + * SoM has a phy at address 1 connected to SoC Ethernet Controller 1. + * It competes for WRIOP MAC17, and no connector has been wired. + */ + /delete-node/ ethernet-phy@1; + + ethernet_phy0: ethernet-phy@8 { + compatible = "ethernet-phy-ieee802.3-c45"; + reg = <8>; + max-speed = <1000>; + }; + + ethernet_phy1: ethernet-phy@9 { + compatible = "ethernet-phy-ieee802.3-c45"; + reg = <9>; + max-speed = <1000>; + }; + + ethernet_phy2: ethernet-phy@10 { + compatible = "ethernet-phy-ieee802.3-c45"; + reg = <10>; + max-speed = <1000>; + }; + + ethernet_phy3: ethernet-phy@11 { + compatible = "ethernet-phy-ieee802.3-c45"; + reg = <11>; + max-speed = <1000>; + }; + + ethernet_phy4: ethernet-phy@12 { + compatible = "ethernet-phy-ieee802.3-c45"; + reg = <12>; + max-speed = <1000>; + }; + + ethernet_phy5: ethernet-phy@13 { + compatible = "ethernet-phy-ieee802.3-c45"; + reg = <13>; + max-speed = <1000>; + }; + + ethernet_phy6: ethernet-phy@14 { + compatible = "ethernet-phy-ieee802.3-c45"; + reg = <14>; + max-speed = <1000>; + }; + + ethernet_phy7: ethernet-phy@15 { + compatible = "ethernet-phy-ieee802.3-c45"; + reg = <15>; + max-speed = <1000>; + }; +}; + +&esdhc0 { + status = "okay"; + sd-uhs-sdr104; + sd-uhs-sdr50; + sd-uhs-sdr25; + sd-uhs-sdr12; +}; + +&pcie3 { + status = "disabled"; +}; + +&pcie4 { + status = "disabled"; +}; + +&pcs_mdio3 { + status = "okay"; +}; + +&pcs_mdio4 { + status = "okay"; +}; + +&pcs_mdio5 { + status = "okay"; +}; + +&pcs_mdio6 { + status = "okay"; +}; + +&pcs_mdio11 { + status = "okay"; +}; + +&pcs_mdio12 { + status = "okay"; +}; + +&pcs_mdio13 { + status = "okay"; +}; + +&pcs_mdio14 { + status = "okay"; +}; + +&pcs_mdio15 { + status = "okay"; +}; + +&pcs_mdio16 { + status = "okay"; +}; + +&pcs_mdio17 { + status = "okay"; +}; + +&pcs_mdio18 { + status = "okay"; +}; + +&serdes_1 { + status = "okay"; +}; + +&serdes_2 { + status = "okay"; +}; + +&uart0 { + status = "okay"; +}; + +&usb0 { + status = "okay"; +};arch/arm64/boot/dts/freescale/fsl-lx2162a-sr-som.dtsi new file +73
-0@@ -0,0 +1,73 @@ +// SPDX-License-Identifier: (GPL-2.0 OR MIT) +// +// Device Tree file for LX2162A-SOM +// +// Copyright 2021 Rabeeh Khoury <[email protected]> +// Copyright 2023 Josua Mayer <[email protected]> + +&crypto { + status = "okay"; +}; + +&dpmac17 { + phy-handle = <ðernet_phy0>; + phy-connection-type = "rgmii-id"; +}; + +&emdio1 { + status = "okay"; + + ethernet_phy0: ethernet-phy@1 { + reg = <1>; + }; +}; + +&esdhc1 { + status = "okay"; + bus-width = <8>; + mmc-hs200-1_8v; + mmc-hs400-1_8v; +}; + +&fspi { + status = "okay"; + + flash@0 { + compatible = "jedec,spi-nor"; + reg = <0>; + m25p,fast-read; + spi-max-frequency = <50000000>; + /* The following setting enables 1-1-8 (CMD-ADDR-DATA) mode */ + spi-rx-bus-width = <8>; + spi-tx-bus-width = <1>; + }; +}; + +&i2c0 { + status = "okay"; + + fan-controller@18 { + compatible = "ti,amc6821"; + reg = <0x18>; + }; + + ddr_spd: eeprom@51 { + compatible = "st,24c02", "atmel,24c02"; + reg = <0x51>; + read-only; + }; + + config_eeprom: eeprom@57 { + compatible = "st,24c02", "atmel,24c02"; + reg = <0x57>; + }; +}; + +&i2c4 { + status = "okay"; + + variable_eeprom: eeprom@54 { + compatible = "st,24c2048", "atmel,24c2048"; + reg = <0x54>; + }; +};Signature · 1 line
2.35.3
Hi Shawn,
Thank you for reviewing.
Note I have added a general question inline below.
Am 18.07.23 um 04:46 schrieb Shawn Guo:
Quoted 7 lines · Josua Mayer
Review
Quoted 5 lines
Add support for the SolidRun LX2162A System on Module (SoM), and the Clearfog evaluation board.
+&dpmac11 {
(quoted diff) +1
-0+ status = "okay";We generally end property list with 'status'.
Okay, I will change the order for v4.
Quoted 14 lines
Shawn
arch/arm64/boot/dts/freescale/fsl-lx2162a-clearfog.dts line 242
Quoted 11 lines
arch/arm64/boot/dts/freescale/fsl-lx2162a-clearfog.dts new file +11
-0+ phys = <&serdes_2 0>; + phy-handle = <ðernet_phy2>; + phy-connection-type = "sgmii"; +}; + +&emdio1 { + /* + * SoM has a phy at address 1 connected to SoC Ethernet Controller 1. + * It competes for WRIOP MAC17, and no connector has been wired. + */ + /delete-node/ ethernet-phy@1;
Perhaps somebody can help here on what is best practice:
As outlined in the comment the SoM includes an ethernet phy at address 1, which is not used at all by the Clearfog carrier.
What is the best practice for unused but available components?
The phy can still communicate on mdio - just it will never receive rgmii signals from ether cpu or carrier.
I am leaning towards just keeping it with status okay, if only for the prospect that a smart driver might put it in a power-saving mode.
Quoted 7 lines
arch/arm64/boot/dts/freescale/fsl-lx2162a-clearfog.dts line 249
Quoted 7 lines
arch/arm64/boot/dts/freescale/fsl-lx2162a-clearfog.dts new file +7
-0+ + ethernet_phy0: ethernet-phy@8 { + compatible = "ethernet-phy-ieee802.3-c45"; + reg = <8>; + max-speed = <1000>; + }; +
- Josua Mayer
Quoted 33 lines · Josua Mayer
Hi Shawn,
Thank you for reviewing.
Note I have added a general question inline below.
Am 18.07.23 um 04:46 schrieb Shawn Guo:
Quoted 7 lines · Josua Mayer
Review
Quoted 5 lines
Add support for the SolidRun LX2162A System on Module (SoM), and the Clearfog evaluation board.
+&dpmac11 {
(quoted diff) +1
-0+ status = "okay";We generally end property list with 'status'.
Okay, I will change the order for v4.
Quoted 14 lines
Shawn
arch/arm64/boot/dts/freescale/fsl-lx2162a-clearfog.dts line 242
Quoted 11 lines
arch/arm64/boot/dts/freescale/fsl-lx2162a-clearfog.dts new file +11
-0+ phys = <&serdes_2 0>; + phy-handle = <ðernet_phy2>; + phy-connection-type = "sgmii"; +}; + +&emdio1 { + /* + * SoM has a phy at address 1 connected to SoC Ethernet Controller 1. + * It competes for WRIOP MAC17, and no connector has been wired. + */ + /delete-node/ ethernet-phy@1;Perhaps somebody can help here on what is best practice:
As outlined in the comment the SoM includes an ethernet phy at address 1, which is not used at all by the Clearfog carrier.
Quoted 1 line
What is the best practice for unused but available components?
If you are saying the connector is not wired on Clearfog, it might make more sense to give it a disabled status in clearfog dts, IMO.
Shawn
Quoted 13 lines
The phy can still communicate on mdio - just it will never receive rgmii signals from ether cpu or carrier.
I am leaning towards just keeping it with status okay, if only for the prospect that a smart driver might put it in a power-saving mode.Quoted 7 lines
Quoted 7 lines
arch/arm64/boot/dts/freescale/fsl-lx2162a-clearfog.dts new file +7
-0+ + ethernet_phy0: ethernet-phy@8 { + compatible = "ethernet-phy-ieee802.3-c45"; + reg = <8>; + max-speed = <1000>; + }; +