From: Shawn Guo <shawnguo@kernel.org>
To: Mathew McBride <matt@traverse.com.au>
Cc: Li Yang <leoyang.li@nxp.com>,
Ioana Ciornei <ioana.ciornei@nxp.com>,
Rob Herring <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 5/5] arm64: dts: add device tree for Traverse Ten64 (LS1088A)
Date: Fri, 23 Jul 2021 17:46:12 +0800 [thread overview]
Message-ID: <20210723094608.GK30773@dragon> (raw)
In-Reply-To: <20210722042450.11862-6-matt@traverse.com.au>
On Thu, Jul 22, 2021 at 04:24:50AM +0000, Mathew McBride wrote:
> The Traverse Technologies Ten64 is a Mini-ITX form factor
> networking board using the NXP LS1088A SoC.
>
> This device tree only describes features which the mainline
> kernel currently has support for, such as some I2C-connected
> devices that are not described at present.
>
> System documentation may be found at ten64doc.traverse.com.au
>
> Signed-off-by: Mathew McBride <matt@traverse.com.au>
> ---
> arch/arm64/boot/dts/freescale/Makefile | 1 +
> .../boot/dts/freescale/fsl-ls1088a-ten64.dts | 375 ++++++++++++++++++
> 2 files changed, 376 insertions(+)
> create mode 100644 arch/arm64/boot/dts/freescale/fsl-ls1088a-ten64.dts
>
> diff --git a/arch/arm64/boot/dts/freescale/Makefile b/arch/arm64/boot/dts/freescale/Makefile
> index 25806c4924cb..2b3ee42e4a2a 100644
> --- a/arch/arm64/boot/dts/freescale/Makefile
> +++ b/arch/arm64/boot/dts/freescale/Makefile
> @@ -19,6 +19,7 @@ dtb-$(CONFIG_ARCH_LAYERSCAPE) += fsl-ls1046a-qds.dtb
> dtb-$(CONFIG_ARCH_LAYERSCAPE) += fsl-ls1046a-rdb.dtb
> dtb-$(CONFIG_ARCH_LAYERSCAPE) += fsl-ls1088a-qds.dtb
> dtb-$(CONFIG_ARCH_LAYERSCAPE) += fsl-ls1088a-rdb.dtb
> +dtb-$(CONFIG_ARCH_LAYERSCAPE) += fsl-ls1088a-ten64.dtb
> dtb-$(CONFIG_ARCH_LAYERSCAPE) += fsl-ls2080a-qds.dtb
> dtb-$(CONFIG_ARCH_LAYERSCAPE) += fsl-ls2080a-rdb.dtb
> dtb-$(CONFIG_ARCH_LAYERSCAPE) += fsl-ls2080a-simu.dtb
> diff --git a/arch/arm64/boot/dts/freescale/fsl-ls1088a-ten64.dts b/arch/arm64/boot/dts/freescale/fsl-ls1088a-ten64.dts
> new file mode 100644
> index 000000000000..7f1584f378fe
> --- /dev/null
> +++ b/arch/arm64/boot/dts/freescale/fsl-ls1088a-ten64.dts
> @@ -0,0 +1,375 @@
> +// SPDX-License-Identifier: (GPL-2.0+ OR MIT)
> +/*
> + * Device Tree file for Travese Ten64 (LS1088) board
> + * Based on fsl-ls1088a-rdb.dts
> + * Copyright 2017-2020 NXP
> + * Copyright 2019-2021 Traverse Technologies
> + *
> + * Author: Mathew McBride <matt@traverse.com.au>
> + */
> +
> +/dts-v1/;
> +
> +#include "fsl-ls1088a.dtsi"
> +
> +#include <dt-bindings/gpio/gpio.h>
> +#include <dt-bindings/input/input.h>
> +
> +/ {
> + model = "Traverse Ten64";
> + compatible = "traverse,ten64", "fsl,ls1088a";
> +
> + aliases {
> + serial0 = &duart0;
> + serial1 = &duart1;
> + };
> +
> + chosen {
> + stdout-path = "serial0:115200n8";
> + };
> +
> + buttons {
> + compatible = "gpio-keys";
Have a newline between property list and child node.
> + /* Fired by system controller when
> + * external power off (e.g ATX Power Button)
> + * asserted
> + */
> + powerdn {
> + label = "External Power Down";
> + gpios = <&gpio1 17 GPIO_ACTIVE_LOW>;
> + interrupts = <&gpio1 17 IRQ_TYPE_EDGE_FALLING>;
> + linux,code = <KEY_POWER>;
> + };
> +
> + /* Rear Panel 'ADMIN' button (GPIO_H) */
> + admin {
> + label = "ADMIN button";
> + gpios = <&gpio3 8 GPIO_ACTIVE_HIGH>;
> + interrupts = <&gpio3 8 IRQ_TYPE_EDGE_RISING>;
> + linux,code = <KEY_WPS_BUTTON>;
> + };
> + };
> +
> + leds {
> + compatible = "gpio-leds";
> +
> + sfp1down {
> + label = "ten64:green:sfp1:down";
> + gpios = <&gpio3 11 GPIO_ACTIVE_HIGH>;
> + };
> +
> + sfp2up {
> + label = "ten64:green:sfp2:up";
> + gpios = <&gpio3 12 GPIO_ACTIVE_HIGH>;
> + };
> +
> + admin {
> + label = "ten64:admin";
> + gpios = <&sfpgpio 12 GPIO_ACTIVE_HIGH>;
> + };
> + };
> +
> + sfp_xg0: dpmac2_sfp {
We generally use '-' instead of '_' in node name. sfp-dpmac2 might be
better.
> + compatible = "sff,sfp";
> + i2c-bus = <&sfplower_i2c>;
> + tx-fault-gpios = <&sfpgpio 0 GPIO_ACTIVE_HIGH>;
> + tx-disable-gpios = <&sfpgpio 1 GPIO_ACTIVE_HIGH>;
> + mod-def0-gpios = <&sfpgpio 2 GPIO_ACTIVE_LOW>;
> + los-gpios = <&sfpgpio 3 GPIO_ACTIVE_HIGH>;
> + maximum-power-milliwatt = <2000>;
> + };
> +
> + sfp_xg1: dpmac1_sfp {
> + compatible = "sff,sfp";
> + i2c-bus = <&sfpupper_i2c>;
> + tx-fault-gpios = <&sfpgpio 4 GPIO_ACTIVE_HIGH>;
> + tx-disable-gpios = <&sfpgpio 5 GPIO_ACTIVE_HIGH>;
> + mod-def0-gpios = <&sfpgpio 6 GPIO_ACTIVE_LOW>;
> + los-gpios = <&sfpgpio 7 GPIO_ACTIVE_HIGH>;
> + maximum-power-milliwatt = <2000>;
> + };
> +
> +};
> +
> +/* XG1 - Upper SFP */
> +&dpmac1 {
> + sfp = <&sfp_xg1>;
> + pcs-handle = <&pcs1>;
> + phy-connection-type = "10gbase-r";
> + managed = "in-band-status";
> +};
> +
> +/* XG0 - Lower SFP */
> +&dpmac2 {
> + sfp = <&sfp_xg0>;
> + pcs-handle = <&pcs2>;
> + phy-connection-type = "10gbase-r";
> + managed = "in-band-status";
> +};
> +
> +/* DPMAC3..6 is GE4 to GE8 */
> +&dpmac3 {
> + phy-handle = <&mdio1_phy5>;
> + phy-connection-type = "qsgmii";
> + managed = "in-band-status";
> + pcs-handle = <&pcs3_0>;
> +};
> +
> +&dpmac4 {
> + phy-handle = <&mdio1_phy6>;
> + phy-connection-type = "qsgmii";
> + managed = "in-band-status";
> + pcs-handle = <&pcs3_1>;
> +};
> +
> +&dpmac5 {
> + phy-handle = <&mdio1_phy7>;
> + phy-connection-type = "qsgmii";
> + managed = "in-band-status";
> + pcs-handle = <&pcs3_2>;
> +};
> +
> +&dpmac6 {
> + phy-handle = <&mdio1_phy8>;
> + phy-connection-type = "qsgmii";
> + managed = "in-band-status";
> + pcs-handle = <&pcs3_3>;
> +};
> +
> +/* DPMAC7..10 is GE0 to GE3 */
> +&dpmac7 {
> + phy-handle = <&mdio1_phy1>;
> + phy-connection-type = "qsgmii";
> + managed = "in-band-status";
> + pcs-handle = <&pcs7_0>;
> +};
> +
> +&dpmac8 {
> + phy-handle = <&mdio1_phy2>;
> + phy-connection-type = "qsgmii";
> + managed = "in-band-status";
> + pcs-handle = <&pcs7_1>;
> +};
> +
> +&dpmac9 {
> + phy-handle = <&mdio1_phy3>;
> + phy-connection-type = "qsgmii";
> + managed = "in-band-status";
> + pcs-handle = <&pcs7_2>;
> +};
> +
> +&dpmac10 {
> + phy-handle = <&mdio1_phy4>;
> + phy-connection-type = "qsgmii";
> + managed = "in-band-status";
> + pcs-handle = <&pcs7_3>;
> +};
> +
> +&emdio1 {
> + status = "okay";
> +
> + mdio1_phy5: ethernet-phy@c {
> + reg = <0xc>;
> + };
> +
> + mdio1_phy6: ethernet-phy@d {
> + reg = <0xd>;
> + };
> +
> + mdio1_phy7: ethernet-phy@e {
> + reg = <0xe>;
> + };
> +
> + mdio1_phy8: ethernet-phy@f {
> + reg = <0xf>;
> + };
> +
> + mdio1_phy1: ethernet-phy@1c {
> + reg = <0x1c>;
> + };
> +
> + mdio1_phy2: ethernet-phy@1d {
> + reg = <0x1d>;
> + };
> +
> + mdio1_phy3: ethernet-phy@1e {
> + reg = <0x1e>;
> + };
> +
> + mdio1_phy4: ethernet-phy@1f {
> + reg = <0x1f>;
> + };
> +};
> +
> +&i2c0 {
> + status = "okay";
> +
> + sfpgpio: gpio@76 {
> + reg = <0x76>;
> + compatible = "ti,tca9539";
We generally start property list with compatible.
> + #gpio-cells = <2>;
> + gpio-controller;
> +
> + admin_led_lower {
> + gpio-hog;
> + gpios = <13 GPIO_ACTIVE_HIGH>;
> + output-low;
> + };
> + };
> +
> + tpm: at97sc@29 {
> + reg = <0x29>;
> + compatible = "atmel,at97sc3204t";
Ditto
> + };
> +};
> +
> +&i2c2 {
> + status = "okay";
> +
> + rtc: rx8035@32 {
Node name should be generic while label can be specific, so
'rx8035: rtc@32' should make more sense.
> + reg = <0x32>;
> + compatible = "epson,rx8035";
> + };
> +};
> +
> +&i2c3 {
> + status = "okay";
> +
> + i2c-switch@70 {
> + compatible = "nxp,pca9540";
> + #address-cells = <1>;
> + #size-cells = <0>;
> + reg = <0x70 >;
> +
> + sfpupper_i2c: i2c@0 {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + reg = <0>;
> + };
> +
> + sfplower_i2c: i2c@1 {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + reg = <1>;
> + };
> + };
> +};
> +
> +&duart0 {
Please try to sort these labeling nodes alphabetically.
> + status = "okay";
> +};
> +
> +&duart1 {
> + status = "okay";
> +};
> +
> +&esdhc {
> + status = "okay";
> +};
> +
> +&pcs_mdio1 {
> + status = "okay";
> +};
> +
> +&pcs_mdio2 {
> + status = "okay";
> +};
> +
> +&pcs_mdio3 {
> + status = "okay";
> +};
> +
> +&pcs_mdio7 {
> + status = "okay";
> +};
> +
> +&qspi {
> + status = "okay";
> +
> + en25s64: flash@0 {
> + compatible = "jedec,spi-nor";
> + #address-cells = <1>;
> + #size-cells = <1>;
> + spi-max-frequency = <20000000>;
> + spi-rx-bus-width = <4>;
> + spi-tx-bus-width = <4>;
> + reg = <0>;
> +
> + bl2@0 {
Shouldn't the name be 'partition' just like nand flash below.
> + label = "bl2";
> + reg = <0 0x100000>;
> + };
> +
> + bl3@100000 {
> + label = "bl3";
> + reg = <0x100000 0x200000>;
> + };
> +
> + mcfirmware@300000 {
> + label = "mcfirmware";
> + reg = <0x300000 0x200000>;
> + };
> +
> + ubootenv@500000 {
> + label = "ubootenv";
> + reg = <0x500000 0x80000>;
> + };
Missing newline.
> + dpl@580000 {
> + label = "dpl";
> + reg = <0x580000 0x40000>;
> + };
> +
> + dpc@5C0000 {
> + label = "dpc";
> + reg = <0x5C0000 0x40000>;
> + };
> +
> + devicetree@600000 {
> + label = "devicetree";
> + reg = <0x600000 0x40000>;
> + };
> + };
> +
> + nand: flash@1 {
> + compatible = "spi-nand";
> + #address-cells = <1>;
> + #size-cells = <1>;
> + spi-max-frequency = <20000000>;
> + reg = <1>;
> + spi-rx-bus-width = <4>;
> + spi-tx-bus-width = <4>;
> +
> + /* reserved for future boot direct from NAND flash
> + * (this would use the same layout as the 8MiB NOR flash)
> + */
> + partition@0 {
> + label = "nand-boot-reserved";
> + reg = <0 0x800000>;
> + };
> +
> + /* recovery / install environment */
> + partition@800000 {
> + label = "recovery";
> + reg = <0x800000 0x2000000>;
> + };
> +
> + /* ubia (first OpenWrt) - a/b names to prevent confusion with ubi0/1/etc. */
> + partition@2800000 {
> + label = "ubia";
> + reg = <0x2800000 0x6C00000>;
> + };
Have a newline.
Shawn
> + /* ubib (second OpenWrt) */
> + partition@9400000 {
> + label = "ubib";
> + reg = <0x9400000 0x6C00000>;
> + };
> + };
> +};
> +
> +&usb0 {
> + status = "okay";
> +};
> +
> +&usb1 {
> + status = "okay";
> +};
> --
> 2.30.1
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org>
To: Mathew McBride <matt@traverse.com.au>
Cc: Li Yang <leoyang.li@nxp.com>,
Ioana Ciornei <ioana.ciornei@nxp.com>,
Rob Herring <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 5/5] arm64: dts: add device tree for Traverse Ten64 (LS1088A)
Date: Fri, 23 Jul 2021 17:46:12 +0800 [thread overview]
Message-ID: <20210723094608.GK30773@dragon> (raw)
In-Reply-To: <20210722042450.11862-6-matt@traverse.com.au>
On Thu, Jul 22, 2021 at 04:24:50AM +0000, Mathew McBride wrote:
> The Traverse Technologies Ten64 is a Mini-ITX form factor
> networking board using the NXP LS1088A SoC.
>
> This device tree only describes features which the mainline
> kernel currently has support for, such as some I2C-connected
> devices that are not described at present.
>
> System documentation may be found at ten64doc.traverse.com.au
>
> Signed-off-by: Mathew McBride <matt@traverse.com.au>
> ---
> arch/arm64/boot/dts/freescale/Makefile | 1 +
> .../boot/dts/freescale/fsl-ls1088a-ten64.dts | 375 ++++++++++++++++++
> 2 files changed, 376 insertions(+)
> create mode 100644 arch/arm64/boot/dts/freescale/fsl-ls1088a-ten64.dts
>
> diff --git a/arch/arm64/boot/dts/freescale/Makefile b/arch/arm64/boot/dts/freescale/Makefile
> index 25806c4924cb..2b3ee42e4a2a 100644
> --- a/arch/arm64/boot/dts/freescale/Makefile
> +++ b/arch/arm64/boot/dts/freescale/Makefile
> @@ -19,6 +19,7 @@ dtb-$(CONFIG_ARCH_LAYERSCAPE) += fsl-ls1046a-qds.dtb
> dtb-$(CONFIG_ARCH_LAYERSCAPE) += fsl-ls1046a-rdb.dtb
> dtb-$(CONFIG_ARCH_LAYERSCAPE) += fsl-ls1088a-qds.dtb
> dtb-$(CONFIG_ARCH_LAYERSCAPE) += fsl-ls1088a-rdb.dtb
> +dtb-$(CONFIG_ARCH_LAYERSCAPE) += fsl-ls1088a-ten64.dtb
> dtb-$(CONFIG_ARCH_LAYERSCAPE) += fsl-ls2080a-qds.dtb
> dtb-$(CONFIG_ARCH_LAYERSCAPE) += fsl-ls2080a-rdb.dtb
> dtb-$(CONFIG_ARCH_LAYERSCAPE) += fsl-ls2080a-simu.dtb
> diff --git a/arch/arm64/boot/dts/freescale/fsl-ls1088a-ten64.dts b/arch/arm64/boot/dts/freescale/fsl-ls1088a-ten64.dts
> new file mode 100644
> index 000000000000..7f1584f378fe
> --- /dev/null
> +++ b/arch/arm64/boot/dts/freescale/fsl-ls1088a-ten64.dts
> @@ -0,0 +1,375 @@
> +// SPDX-License-Identifier: (GPL-2.0+ OR MIT)
> +/*
> + * Device Tree file for Travese Ten64 (LS1088) board
> + * Based on fsl-ls1088a-rdb.dts
> + * Copyright 2017-2020 NXP
> + * Copyright 2019-2021 Traverse Technologies
> + *
> + * Author: Mathew McBride <matt@traverse.com.au>
> + */
> +
> +/dts-v1/;
> +
> +#include "fsl-ls1088a.dtsi"
> +
> +#include <dt-bindings/gpio/gpio.h>
> +#include <dt-bindings/input/input.h>
> +
> +/ {
> + model = "Traverse Ten64";
> + compatible = "traverse,ten64", "fsl,ls1088a";
> +
> + aliases {
> + serial0 = &duart0;
> + serial1 = &duart1;
> + };
> +
> + chosen {
> + stdout-path = "serial0:115200n8";
> + };
> +
> + buttons {
> + compatible = "gpio-keys";
Have a newline between property list and child node.
> + /* Fired by system controller when
> + * external power off (e.g ATX Power Button)
> + * asserted
> + */
> + powerdn {
> + label = "External Power Down";
> + gpios = <&gpio1 17 GPIO_ACTIVE_LOW>;
> + interrupts = <&gpio1 17 IRQ_TYPE_EDGE_FALLING>;
> + linux,code = <KEY_POWER>;
> + };
> +
> + /* Rear Panel 'ADMIN' button (GPIO_H) */
> + admin {
> + label = "ADMIN button";
> + gpios = <&gpio3 8 GPIO_ACTIVE_HIGH>;
> + interrupts = <&gpio3 8 IRQ_TYPE_EDGE_RISING>;
> + linux,code = <KEY_WPS_BUTTON>;
> + };
> + };
> +
> + leds {
> + compatible = "gpio-leds";
> +
> + sfp1down {
> + label = "ten64:green:sfp1:down";
> + gpios = <&gpio3 11 GPIO_ACTIVE_HIGH>;
> + };
> +
> + sfp2up {
> + label = "ten64:green:sfp2:up";
> + gpios = <&gpio3 12 GPIO_ACTIVE_HIGH>;
> + };
> +
> + admin {
> + label = "ten64:admin";
> + gpios = <&sfpgpio 12 GPIO_ACTIVE_HIGH>;
> + };
> + };
> +
> + sfp_xg0: dpmac2_sfp {
We generally use '-' instead of '_' in node name. sfp-dpmac2 might be
better.
> + compatible = "sff,sfp";
> + i2c-bus = <&sfplower_i2c>;
> + tx-fault-gpios = <&sfpgpio 0 GPIO_ACTIVE_HIGH>;
> + tx-disable-gpios = <&sfpgpio 1 GPIO_ACTIVE_HIGH>;
> + mod-def0-gpios = <&sfpgpio 2 GPIO_ACTIVE_LOW>;
> + los-gpios = <&sfpgpio 3 GPIO_ACTIVE_HIGH>;
> + maximum-power-milliwatt = <2000>;
> + };
> +
> + sfp_xg1: dpmac1_sfp {
> + compatible = "sff,sfp";
> + i2c-bus = <&sfpupper_i2c>;
> + tx-fault-gpios = <&sfpgpio 4 GPIO_ACTIVE_HIGH>;
> + tx-disable-gpios = <&sfpgpio 5 GPIO_ACTIVE_HIGH>;
> + mod-def0-gpios = <&sfpgpio 6 GPIO_ACTIVE_LOW>;
> + los-gpios = <&sfpgpio 7 GPIO_ACTIVE_HIGH>;
> + maximum-power-milliwatt = <2000>;
> + };
> +
> +};
> +
> +/* XG1 - Upper SFP */
> +&dpmac1 {
> + sfp = <&sfp_xg1>;
> + pcs-handle = <&pcs1>;
> + phy-connection-type = "10gbase-r";
> + managed = "in-band-status";
> +};
> +
> +/* XG0 - Lower SFP */
> +&dpmac2 {
> + sfp = <&sfp_xg0>;
> + pcs-handle = <&pcs2>;
> + phy-connection-type = "10gbase-r";
> + managed = "in-band-status";
> +};
> +
> +/* DPMAC3..6 is GE4 to GE8 */
> +&dpmac3 {
> + phy-handle = <&mdio1_phy5>;
> + phy-connection-type = "qsgmii";
> + managed = "in-band-status";
> + pcs-handle = <&pcs3_0>;
> +};
> +
> +&dpmac4 {
> + phy-handle = <&mdio1_phy6>;
> + phy-connection-type = "qsgmii";
> + managed = "in-band-status";
> + pcs-handle = <&pcs3_1>;
> +};
> +
> +&dpmac5 {
> + phy-handle = <&mdio1_phy7>;
> + phy-connection-type = "qsgmii";
> + managed = "in-band-status";
> + pcs-handle = <&pcs3_2>;
> +};
> +
> +&dpmac6 {
> + phy-handle = <&mdio1_phy8>;
> + phy-connection-type = "qsgmii";
> + managed = "in-band-status";
> + pcs-handle = <&pcs3_3>;
> +};
> +
> +/* DPMAC7..10 is GE0 to GE3 */
> +&dpmac7 {
> + phy-handle = <&mdio1_phy1>;
> + phy-connection-type = "qsgmii";
> + managed = "in-band-status";
> + pcs-handle = <&pcs7_0>;
> +};
> +
> +&dpmac8 {
> + phy-handle = <&mdio1_phy2>;
> + phy-connection-type = "qsgmii";
> + managed = "in-band-status";
> + pcs-handle = <&pcs7_1>;
> +};
> +
> +&dpmac9 {
> + phy-handle = <&mdio1_phy3>;
> + phy-connection-type = "qsgmii";
> + managed = "in-band-status";
> + pcs-handle = <&pcs7_2>;
> +};
> +
> +&dpmac10 {
> + phy-handle = <&mdio1_phy4>;
> + phy-connection-type = "qsgmii";
> + managed = "in-band-status";
> + pcs-handle = <&pcs7_3>;
> +};
> +
> +&emdio1 {
> + status = "okay";
> +
> + mdio1_phy5: ethernet-phy@c {
> + reg = <0xc>;
> + };
> +
> + mdio1_phy6: ethernet-phy@d {
> + reg = <0xd>;
> + };
> +
> + mdio1_phy7: ethernet-phy@e {
> + reg = <0xe>;
> + };
> +
> + mdio1_phy8: ethernet-phy@f {
> + reg = <0xf>;
> + };
> +
> + mdio1_phy1: ethernet-phy@1c {
> + reg = <0x1c>;
> + };
> +
> + mdio1_phy2: ethernet-phy@1d {
> + reg = <0x1d>;
> + };
> +
> + mdio1_phy3: ethernet-phy@1e {
> + reg = <0x1e>;
> + };
> +
> + mdio1_phy4: ethernet-phy@1f {
> + reg = <0x1f>;
> + };
> +};
> +
> +&i2c0 {
> + status = "okay";
> +
> + sfpgpio: gpio@76 {
> + reg = <0x76>;
> + compatible = "ti,tca9539";
We generally start property list with compatible.
> + #gpio-cells = <2>;
> + gpio-controller;
> +
> + admin_led_lower {
> + gpio-hog;
> + gpios = <13 GPIO_ACTIVE_HIGH>;
> + output-low;
> + };
> + };
> +
> + tpm: at97sc@29 {
> + reg = <0x29>;
> + compatible = "atmel,at97sc3204t";
Ditto
> + };
> +};
> +
> +&i2c2 {
> + status = "okay";
> +
> + rtc: rx8035@32 {
Node name should be generic while label can be specific, so
'rx8035: rtc@32' should make more sense.
> + reg = <0x32>;
> + compatible = "epson,rx8035";
> + };
> +};
> +
> +&i2c3 {
> + status = "okay";
> +
> + i2c-switch@70 {
> + compatible = "nxp,pca9540";
> + #address-cells = <1>;
> + #size-cells = <0>;
> + reg = <0x70 >;
> +
> + sfpupper_i2c: i2c@0 {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + reg = <0>;
> + };
> +
> + sfplower_i2c: i2c@1 {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + reg = <1>;
> + };
> + };
> +};
> +
> +&duart0 {
Please try to sort these labeling nodes alphabetically.
> + status = "okay";
> +};
> +
> +&duart1 {
> + status = "okay";
> +};
> +
> +&esdhc {
> + status = "okay";
> +};
> +
> +&pcs_mdio1 {
> + status = "okay";
> +};
> +
> +&pcs_mdio2 {
> + status = "okay";
> +};
> +
> +&pcs_mdio3 {
> + status = "okay";
> +};
> +
> +&pcs_mdio7 {
> + status = "okay";
> +};
> +
> +&qspi {
> + status = "okay";
> +
> + en25s64: flash@0 {
> + compatible = "jedec,spi-nor";
> + #address-cells = <1>;
> + #size-cells = <1>;
> + spi-max-frequency = <20000000>;
> + spi-rx-bus-width = <4>;
> + spi-tx-bus-width = <4>;
> + reg = <0>;
> +
> + bl2@0 {
Shouldn't the name be 'partition' just like nand flash below.
> + label = "bl2";
> + reg = <0 0x100000>;
> + };
> +
> + bl3@100000 {
> + label = "bl3";
> + reg = <0x100000 0x200000>;
> + };
> +
> + mcfirmware@300000 {
> + label = "mcfirmware";
> + reg = <0x300000 0x200000>;
> + };
> +
> + ubootenv@500000 {
> + label = "ubootenv";
> + reg = <0x500000 0x80000>;
> + };
Missing newline.
> + dpl@580000 {
> + label = "dpl";
> + reg = <0x580000 0x40000>;
> + };
> +
> + dpc@5C0000 {
> + label = "dpc";
> + reg = <0x5C0000 0x40000>;
> + };
> +
> + devicetree@600000 {
> + label = "devicetree";
> + reg = <0x600000 0x40000>;
> + };
> + };
> +
> + nand: flash@1 {
> + compatible = "spi-nand";
> + #address-cells = <1>;
> + #size-cells = <1>;
> + spi-max-frequency = <20000000>;
> + reg = <1>;
> + spi-rx-bus-width = <4>;
> + spi-tx-bus-width = <4>;
> +
> + /* reserved for future boot direct from NAND flash
> + * (this would use the same layout as the 8MiB NOR flash)
> + */
> + partition@0 {
> + label = "nand-boot-reserved";
> + reg = <0 0x800000>;
> + };
> +
> + /* recovery / install environment */
> + partition@800000 {
> + label = "recovery";
> + reg = <0x800000 0x2000000>;
> + };
> +
> + /* ubia (first OpenWrt) - a/b names to prevent confusion with ubi0/1/etc. */
> + partition@2800000 {
> + label = "ubia";
> + reg = <0x2800000 0x6C00000>;
> + };
Have a newline.
Shawn
> + /* ubib (second OpenWrt) */
> + partition@9400000 {
> + label = "ubib";
> + reg = <0x9400000 0x6C00000>;
> + };
> + };
> +};
> +
> +&usb0 {
> + status = "okay";
> +};
> +
> +&usb1 {
> + status = "okay";
> +};
> --
> 2.30.1
>
next prev parent reply other threads:[~2021-07-23 9:50 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-22 4:24 [PATCH 0/5] Add Traverse Technologies Ten64 board DTS Mathew McBride
2021-07-22 4:24 ` Mathew McBride
2021-07-22 4:24 ` [PATCH 1/5] arm64: dts: ls1088a: add internal PCS for DPMAC1 node Mathew McBride
2021-07-22 4:24 ` Mathew McBride
2021-07-22 7:48 ` Ioana Ciornei
2021-07-22 7:48 ` Ioana Ciornei
2021-07-22 4:24 ` [PATCH 2/5] arm64: dts: ls1088a: add missing PMU node Mathew McBride
2021-07-22 4:24 ` Mathew McBride
2021-07-23 8:36 ` Shawn Guo
2021-07-23 8:36 ` Shawn Guo
2021-07-22 4:24 ` [PATCH 3/5] dt-bindings: vendor-prefixes: add Traverse Technologies Mathew McBride
2021-07-22 4:24 ` Mathew McBride
2021-07-22 4:24 ` [PATCH 4/5] dt-bindings: arm: fsl: Add Traverse Ten64 (LS1088A) board Mathew McBride
2021-07-22 4:24 ` Mathew McBride
2021-07-22 4:24 ` [PATCH 5/5] arm64: dts: add device tree for Traverse Ten64 (LS1088A) Mathew McBride
2021-07-22 4:24 ` Mathew McBride
2021-07-22 8:44 ` Ioana Ciornei
2021-07-22 8:44 ` Ioana Ciornei
2021-07-23 9:46 ` Shawn Guo [this message]
2021-07-23 9:46 ` Shawn Guo
2021-07-26 7:12 ` [PATCH v2 0/5] Add Traverse Technologies Ten64 board DTS Mathew McBride
2021-07-26 7:12 ` Mathew McBride
2021-07-26 7:12 ` [PATCH v2 1/5] arm64: dts: ls1088a: add internal PCS for DPMAC1 node Mathew McBride
2021-07-26 7:12 ` Mathew McBride
2021-07-26 7:12 ` [PATCH v2 2/5] arm64: dts: ls1088a: add missing PMU node Mathew McBride
2021-07-26 7:12 ` Mathew McBride
2021-07-26 7:12 ` [PATCH v2 3/5] dt-bindings: vendor-prefixes: add Traverse Technologies Mathew McBride
2021-07-26 7:12 ` Mathew McBride
2021-07-29 22:41 ` Rob Herring
2021-07-29 22:41 ` Rob Herring
2021-07-26 7:12 ` [PATCH v2 4/5] dt-bindings: arm: fsl: Add Traverse Ten64 (LS1088A) board Mathew McBride
2021-07-26 7:12 ` Mathew McBride
2021-07-29 22:45 ` Rob Herring
2021-07-29 22:45 ` Rob Herring
2021-07-26 7:12 ` [PATCH v2 5/5] arm64: dts: add device tree for Traverse Ten64 (LS1088A) Mathew McBride
2021-07-26 7:12 ` Mathew McBride
2021-07-29 22:45 ` Rob Herring
2021-07-29 22:45 ` Rob Herring
2021-08-10 5:38 ` [PATCH v3 0/5] Add Traverse Technologies Ten64 board DTS Mathew McBride
2021-08-10 5:38 ` Mathew McBride
2021-08-10 5:38 ` [PATCH v3 1/5] arm64: dts: ls1088a: add internal PCS for DPMAC1 node Mathew McBride
2021-08-10 5:38 ` Mathew McBride
2021-08-10 5:38 ` [PATCH v3 2/5] arm64: dts: ls1088a: add missing PMU node Mathew McBride
2021-08-10 5:38 ` Mathew McBride
2021-08-10 5:38 ` [PATCH v3 3/5] dt-bindings: vendor-prefixes: add Traverse Technologies Mathew McBride
2021-08-10 5:38 ` Mathew McBride
2021-08-10 5:38 ` [PATCH v3 4/5] dt-bindings: arm: fsl: Add Traverse Ten64 (LS1088A) board Mathew McBride
2021-08-10 5:38 ` Mathew McBride
2021-08-10 5:38 ` [PATCH v3 5/5] arm64: dts: add device tree for Traverse Ten64 (LS1088A) Mathew McBride
2021-08-10 5:38 ` Mathew McBride
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210723094608.GK30773@dragon \
--to=shawnguo@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ioana.ciornei@nxp.com \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=matt@traverse.com.au \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.