Message ID | 20231025165058.31697-3-laurent.pinchart@ideasonboard.com (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
Series | arm64: dts: freescale: Add Variscite i.MX8MP DART8MCustomBoard v2 | expand |
Hello Laurent, On 25.10.23 18:50, Laurent Pinchart wrote: > + reg_eqos_phy: regulator-eqos-phy { > + compatible = "regulator-fixed"; > + regulator-name = "eqos-phy"; > + regulator-min-microvolt = <3300000>; > + regulator-max-microvolt = <3300000>; > + gpio = <&gpio2 20 GPIO_ACTIVE_HIGH>; > + enable-active-high; > + regulator-always-on; Apparently, https://lore.kernel.org/all/20230721110345.3925719-1-m.felsch@pengutronix.de/ didn't make it upstream. Perhaps you mentioning that you could use this would help get it unstuck? :) > +&eqos { > + pinctrl-names = "default"; > + pinctrl-0 = <&pinctrl_eqos>; > + phy-mode = "rgmii"; > + phy-handle = <ðphy0>; > + status = "okay"; > + > + mdio { > + compatible = "snps,dwmac-mdio"; > + #address-cells = <1>; > + #size-cells = <0>; > + > + ethphy0: ethernet-phy@0 { > + compatible = "ethernet-phy-ieee802.3-c22"; > + reg = <0>; > + eee-broken-1000t; > + reset-gpios = <&gpio2 11 GPIO_ACTIVE_LOW>; Nitpick: Separate pinctrl entry for PHY GPIOs that's added to the PHY node? Makes it easier to check that all used signals are indeed muxed. > + pmic@25 { > + compatible = "nxp,pca9450c"; > + reg = <0x25>; > + pinctrl-names = "default"; > + pinctrl-0 = <&pinctrl_pmic>; > + interrupt-parent = <&gpio1>; > + interrupts = <3 IRQ_TYPE_LEVEL_LOW>; > + > + regulators { > + BUCK1 { > + regulator-name = "BUCK1"; > + regulator-min-microvolt = <600000>; > + regulator-max-microvolt = <2187500>; Nitpick: These may be the limits of what the BUCK can output, but they don't look like a safe operating range for the board. The Linux driver already has ranges hardcoded to cover what's possible by the hardware, so if you specify regulator range here, it should pertain to what the board and SoC are designed to handle. > +/* eMMC */ > +&usdhc3 { > + pinctrl-names = "default", "state_100mhz", "state_200mhz"; > + pinctrl-0 = <&pinctrl_usdhc3>; > + pinctrl-1 = <&pinctrl_usdhc3_100mhz>; > + pinctrl-2 = <&pinctrl_usdhc3_200mhz>; > + bus-width = <8>; > + non-removable; no-sd no-sdio may give you a tiny bit of speedup during probe, if you know that there will always be an eMMC here. > + pinctrl_i2c1: i2c1grp { > + fsl,pins = < > + MX8MP_IOMUXC_I2C1_SCL__I2C1_SCL 0x400001c2 > + MX8MP_IOMUXC_I2C1_SDA__I2C1_SDA 0x400001c2 > + >; > + }; > + > + pinctrl_i2c1_gpio: i2c1gpiogrp { > + fsl,pins = < > + MX8MP_IOMUXC_I2C1_SCL__GPIO5_IO14 0x1c2 > + MX8MP_IOMUXC_I2C1_SDA__GPIO5_IO15 0x1c2 This surprises me. I'd expect that the SION bit needs to be set for GPIO bus recovery. Cheers, Ahmad
On 27.11.23 06:58, Ahmad Fatoum wrote: > Hello Laurent, Ah, I see now, that this series was about to be merged. I missed it at first, because of the MAINTAINERS entry losing a F:, which I now sent a fix for. Anyways, should you resend to fix the binding errors, you could address some of the nitpicks, but I found nothing critical. Cheers, Ahmad > > On 25.10.23 18:50, Laurent Pinchart wrote: >> + reg_eqos_phy: regulator-eqos-phy { >> + compatible = "regulator-fixed"; >> + regulator-name = "eqos-phy"; >> + regulator-min-microvolt = <3300000>; >> + regulator-max-microvolt = <3300000>; >> + gpio = <&gpio2 20 GPIO_ACTIVE_HIGH>; >> + enable-active-high; >> + regulator-always-on; > > Apparently, https://lore.kernel.org/all/20230721110345.3925719-1-m.felsch@pengutronix.de/ > didn't make it upstream. Perhaps you mentioning that you could use this would help get > it unstuck? :) > >> +&eqos { >> + pinctrl-names = "default"; >> + pinctrl-0 = <&pinctrl_eqos>; >> + phy-mode = "rgmii"; >> + phy-handle = <ðphy0>; >> + status = "okay"; >> + >> + mdio { >> + compatible = "snps,dwmac-mdio"; >> + #address-cells = <1>; >> + #size-cells = <0>; >> + >> + ethphy0: ethernet-phy@0 { >> + compatible = "ethernet-phy-ieee802.3-c22"; >> + reg = <0>; >> + eee-broken-1000t; >> + reset-gpios = <&gpio2 11 GPIO_ACTIVE_LOW>; > > Nitpick: Separate pinctrl entry for PHY GPIOs that's added to the PHY node? > Makes it easier to check that all used signals are indeed muxed. > >> + pmic@25 { >> + compatible = "nxp,pca9450c"; >> + reg = <0x25>; >> + pinctrl-names = "default"; >> + pinctrl-0 = <&pinctrl_pmic>; >> + interrupt-parent = <&gpio1>; >> + interrupts = <3 IRQ_TYPE_LEVEL_LOW>; >> + >> + regulators { >> + BUCK1 { >> + regulator-name = "BUCK1"; >> + regulator-min-microvolt = <600000>; >> + regulator-max-microvolt = <2187500>; > > Nitpick: These may be the limits of what the BUCK can output, but they > don't look like a safe operating range for the board. The Linux driver already > has ranges hardcoded to cover what's possible by the hardware, so if you specify > regulator range here, it should pertain to what the board and SoC are designed > to handle. > >> +/* eMMC */ >> +&usdhc3 { >> + pinctrl-names = "default", "state_100mhz", "state_200mhz"; >> + pinctrl-0 = <&pinctrl_usdhc3>; >> + pinctrl-1 = <&pinctrl_usdhc3_100mhz>; >> + pinctrl-2 = <&pinctrl_usdhc3_200mhz>; >> + bus-width = <8>; >> + non-removable; > > no-sd > no-sdio > > may give you a tiny bit of speedup during probe, if you know that there will > always be an eMMC here. > >> + pinctrl_i2c1: i2c1grp { >> + fsl,pins = < >> + MX8MP_IOMUXC_I2C1_SCL__I2C1_SCL 0x400001c2 >> + MX8MP_IOMUXC_I2C1_SDA__I2C1_SDA 0x400001c2 >> + >; >> + }; >> + >> + pinctrl_i2c1_gpio: i2c1gpiogrp { >> + fsl,pins = < >> + MX8MP_IOMUXC_I2C1_SCL__GPIO5_IO14 0x1c2 >> + MX8MP_IOMUXC_I2C1_SDA__GPIO5_IO15 0x1c2 > > This surprises me. I'd expect that the SION bit needs to be set for GPIO bus recovery. > > Cheers, > Ahmad >
Hi Ahmad, On Mon, Nov 27, 2023 at 06:58:31AM +0100, Ahmad Fatoum wrote: > On 25.10.23 18:50, Laurent Pinchart wrote: > > + reg_eqos_phy: regulator-eqos-phy { > > + compatible = "regulator-fixed"; > > + regulator-name = "eqos-phy"; > > + regulator-min-microvolt = <3300000>; > > + regulator-max-microvolt = <3300000>; > > + gpio = <&gpio2 20 GPIO_ACTIVE_HIGH>; > > + enable-active-high; > > + regulator-always-on; > > Apparently, https://lore.kernel.org/all/20230721110345.3925719-1-m.felsch@pengutronix.de/ > didn't make it upstream. Perhaps you mentioning that you could use this would help get > it unstuck? :) I've replied to the series, but I agree with Rob, we need a better solution. Someone will need to do the work :-) > > +&eqos { > > + pinctrl-names = "default"; > > + pinctrl-0 = <&pinctrl_eqos>; > > + phy-mode = "rgmii"; > > + phy-handle = <ðphy0>; > > + status = "okay"; > > + > > + mdio { > > + compatible = "snps,dwmac-mdio"; > > + #address-cells = <1>; > > + #size-cells = <0>; > > + > > + ethphy0: ethernet-phy@0 { > > + compatible = "ethernet-phy-ieee802.3-c22"; > > + reg = <0>; > > + eee-broken-1000t; > > + reset-gpios = <&gpio2 11 GPIO_ACTIVE_LOW>; > > Nitpick: Separate pinctrl entry for PHY GPIOs that's added to the PHY node? > Makes it easier to check that all used signals are indeed muxed. Fine with me. > > + pmic@25 { > > + compatible = "nxp,pca9450c"; > > + reg = <0x25>; > > + pinctrl-names = "default"; > > + pinctrl-0 = <&pinctrl_pmic>; > > + interrupt-parent = <&gpio1>; > > + interrupts = <3 IRQ_TYPE_LEVEL_LOW>; > > + > > + regulators { > > + BUCK1 { > > + regulator-name = "BUCK1"; > > + regulator-min-microvolt = <600000>; > > + regulator-max-microvolt = <2187500>; > > Nitpick: These may be the limits of what the BUCK can output, but they > don't look like a safe operating range for the board. The Linux driver already > has ranges hardcoded to cover what's possible by the hardware, so if you specify > regulator range here, it should pertain to what the board and SoC are designed > to handle. I'll restrict that to [0.85V 0.95V], which are the typical voltages in nominal and overdrive mode. If someone wants to lower it down to 0.805V or increase it up to 1.0V, which are the minimum and maximum values specified in the SoC's operating ranges, they can send a patch. I will similarly restrict BUCK2 to [0.85V 1.0V]. BUCK4, BUCK5 and BUCK6 are more annoying. There is no public schematics, and little information in the board's documentation. For BUCK5, there's a mention in the board's documentation that indicates it powers NVCC_SAI1_SAI5 with 1.8V by default before LDO4 takes over. It is further set to 1.85V in U-Boot with a comment that states /* Set BUCK5 voltage to 1.85V to fix Ethernet PHY reset */ if (var_detect_board_id() == BOARD_ID_DART) pmic_reg_write(p, PCA9450_BUCK5OUT, 0x32); I will restrict the range to [1.65V 1.95V] as documented in the i.MX8MP operating ranges, and exclude the 3.3V operation mode given the explanation in the board's documentation. BUCK4 and BUCK6 are not mentioned anywhere, and not programmed by U-Boot. I can only assume they're used at their 3.3V and 1.1V defaults. BUCK6 likely powers NVCC_DRAM as in the EVK, which is consistent with the board using LPDDR4. I'll set the output voltages to 3.3V and 1.1V respectively. LDOs are even worse. Only LDO4 is mentioned in the documentation (as powering NVCC_SAI1_SAI5) and touched by the boot loader (set to 1.8V). I'll modify the LDO4 range from the current 3.3V fixed value to [1.8V 3.3V], and won't touch the other LDOs. > > +/* eMMC */ > > +&usdhc3 { > > + pinctrl-names = "default", "state_100mhz", "state_200mhz"; > > + pinctrl-0 = <&pinctrl_usdhc3>; > > + pinctrl-1 = <&pinctrl_usdhc3_100mhz>; > > + pinctrl-2 = <&pinctrl_usdhc3_200mhz>; > > + bus-width = <8>; > > + non-removable; > > no-sd > no-sdio > > may give you a tiny bit of speedup during probe, if you know that there will > always be an eMMC here. I'll add that, thanks. > > + pinctrl_i2c1: i2c1grp { > > + fsl,pins = < > > + MX8MP_IOMUXC_I2C1_SCL__I2C1_SCL 0x400001c2 > > + MX8MP_IOMUXC_I2C1_SDA__I2C1_SDA 0x400001c2 > > + >; > > + }; > > + > > + pinctrl_i2c1_gpio: i2c1gpiogrp { > > + fsl,pins = < > > + MX8MP_IOMUXC_I2C1_SCL__GPIO5_IO14 0x1c2 > > + MX8MP_IOMUXC_I2C1_SDA__GPIO5_IO15 0x1c2 > > This surprises me. I'd expect that the SION bit needs to be set for > GPIO bus recovery. I haven't tested GPIO bus recovery. I'll add the SION bits, as they make sense.
On Mon, Nov 27, 2023 at 07:13:37AM +0100, Ahmad Fatoum wrote: > On 27.11.23 06:58, Ahmad Fatoum wrote: > > Hello Laurent, > > Ah, I see now, that this series was about to be merged. I missed it at first, > because of the MAINTAINERS entry losing a F:, which I now sent a fix for. > > Anyways, should you resend to fix the binding errors, you could address some > of the nitpicks, but I found nothing critical. As the series hasn't been merged yet, I'll submit a v3 that addresses your comments. Thanks for the detailed review. > > On 25.10.23 18:50, Laurent Pinchart wrote: > >> + reg_eqos_phy: regulator-eqos-phy { > >> + compatible = "regulator-fixed"; > >> + regulator-name = "eqos-phy"; > >> + regulator-min-microvolt = <3300000>; > >> + regulator-max-microvolt = <3300000>; > >> + gpio = <&gpio2 20 GPIO_ACTIVE_HIGH>; > >> + enable-active-high; > >> + regulator-always-on; > > > > Apparently, https://lore.kernel.org/all/20230721110345.3925719-1-m.felsch@pengutronix.de/ > > didn't make it upstream. Perhaps you mentioning that you could use this would help get > > it unstuck? :) > > > >> +&eqos { > >> + pinctrl-names = "default"; > >> + pinctrl-0 = <&pinctrl_eqos>; > >> + phy-mode = "rgmii"; > >> + phy-handle = <ðphy0>; > >> + status = "okay"; > >> + > >> + mdio { > >> + compatible = "snps,dwmac-mdio"; > >> + #address-cells = <1>; > >> + #size-cells = <0>; > >> + > >> + ethphy0: ethernet-phy@0 { > >> + compatible = "ethernet-phy-ieee802.3-c22"; > >> + reg = <0>; > >> + eee-broken-1000t; > >> + reset-gpios = <&gpio2 11 GPIO_ACTIVE_LOW>; > > > > Nitpick: Separate pinctrl entry for PHY GPIOs that's added to the PHY node? > > Makes it easier to check that all used signals are indeed muxed. > > > >> + pmic@25 { > >> + compatible = "nxp,pca9450c"; > >> + reg = <0x25>; > >> + pinctrl-names = "default"; > >> + pinctrl-0 = <&pinctrl_pmic>; > >> + interrupt-parent = <&gpio1>; > >> + interrupts = <3 IRQ_TYPE_LEVEL_LOW>; > >> + > >> + regulators { > >> + BUCK1 { > >> + regulator-name = "BUCK1"; > >> + regulator-min-microvolt = <600000>; > >> + regulator-max-microvolt = <2187500>; > > > > Nitpick: These may be the limits of what the BUCK can output, but they > > don't look like a safe operating range for the board. The Linux driver already > > has ranges hardcoded to cover what's possible by the hardware, so if you specify > > regulator range here, it should pertain to what the board and SoC are designed > > to handle. > > > >> +/* eMMC */ > >> +&usdhc3 { > >> + pinctrl-names = "default", "state_100mhz", "state_200mhz"; > >> + pinctrl-0 = <&pinctrl_usdhc3>; > >> + pinctrl-1 = <&pinctrl_usdhc3_100mhz>; > >> + pinctrl-2 = <&pinctrl_usdhc3_200mhz>; > >> + bus-width = <8>; > >> + non-removable; > > > > no-sd > > no-sdio > > > > may give you a tiny bit of speedup during probe, if you know that there will > > always be an eMMC here. > > > >> + pinctrl_i2c1: i2c1grp { > >> + fsl,pins = < > >> + MX8MP_IOMUXC_I2C1_SCL__I2C1_SCL 0x400001c2 > >> + MX8MP_IOMUXC_I2C1_SDA__I2C1_SDA 0x400001c2 > >> + >; > >> + }; > >> + > >> + pinctrl_i2c1_gpio: i2c1gpiogrp { > >> + fsl,pins = < > >> + MX8MP_IOMUXC_I2C1_SCL__GPIO5_IO14 0x1c2 > >> + MX8MP_IOMUXC_I2C1_SDA__GPIO5_IO15 0x1c2 > > > > This surprises me. I'd expect that the SION bit needs to be set for GPIO bus recovery.
diff --git a/arch/arm64/boot/dts/freescale/imx8mp-var-dart.dtsi b/arch/arm64/boot/dts/freescale/imx8mp-var-dart.dtsi new file mode 100644 index 000000000000..d9a08dd3d218 --- /dev/null +++ b/arch/arm64/boot/dts/freescale/imx8mp-var-dart.dtsi @@ -0,0 +1,305 @@ +// SPDX-License-Identifier: GPL-2.0-or-later OR MIT +/* + * Copyright 2019 NXP + * Copyright 2020-2021 Variscite Ltd. + * Copyright 2023 Ideas on Board Oy + */ + +/dts-v1/; + +#include "imx8mp.dtsi" + +/ { + aliases { + ethernet0 = &eqos; + ethernet1 = &fec; + }; + + memory@40000000 { + device_type = "memory"; + reg = <0x0 0x40000000 0 0xc0000000>, + <0x1 0x00000000 0 0xc0000000>; + }; + + reg_eqos_phy: regulator-eqos-phy { + compatible = "regulator-fixed"; + regulator-name = "eqos-phy"; + regulator-min-microvolt = <3300000>; + regulator-max-microvolt = <3300000>; + gpio = <&gpio2 20 GPIO_ACTIVE_HIGH>; + enable-active-high; + regulator-always-on; + }; +}; + +&A53_0 { + cpu-supply = <®_arm>; +}; + +&A53_1 { + cpu-supply = <®_arm>; +}; + +&A53_2 { + cpu-supply = <®_arm>; +}; + +&A53_3 { + cpu-supply = <®_arm>; +}; + +&eqos { + pinctrl-names = "default"; + pinctrl-0 = <&pinctrl_eqos>; + phy-mode = "rgmii"; + phy-handle = <ðphy0>; + status = "okay"; + + mdio { + compatible = "snps,dwmac-mdio"; + #address-cells = <1>; + #size-cells = <0>; + + ethphy0: ethernet-phy@0 { + compatible = "ethernet-phy-ieee802.3-c22"; + reg = <0>; + eee-broken-1000t; + reset-gpios = <&gpio2 11 GPIO_ACTIVE_LOW>; + reset-assert-us = <10000>; + reset-deassert-us = <20000>; + }; + }; +}; + +&i2c1 { + clock-frequency = <400000>; + pinctrl-names = "default", "gpio"; + pinctrl-0 = <&pinctrl_i2c1>; + pinctrl-1 = <&pinctrl_i2c1_gpio>; + scl-gpios = <&gpio5 14 (GPIO_ACTIVE_HIGH | GPIO_OPEN_DRAIN)>; + sda-gpios = <&gpio5 15 (GPIO_ACTIVE_HIGH | GPIO_OPEN_DRAIN)>; + status = "okay"; + + pmic@25 { + compatible = "nxp,pca9450c"; + reg = <0x25>; + pinctrl-names = "default"; + pinctrl-0 = <&pinctrl_pmic>; + interrupt-parent = <&gpio1>; + interrupts = <3 IRQ_TYPE_LEVEL_LOW>; + + regulators { + BUCK1 { + regulator-name = "BUCK1"; + regulator-min-microvolt = <600000>; + regulator-max-microvolt = <2187500>; + regulator-boot-on; + regulator-always-on; + regulator-ramp-delay = <3125>; + }; + + reg_arm: BUCK2 { + regulator-name = "BUCK2"; + regulator-min-microvolt = <600000>; + regulator-max-microvolt = <2187500>; + regulator-boot-on; + regulator-always-on; + regulator-ramp-delay = <3125>; + nxp,dvs-run-voltage = <950000>; + nxp,dvs-standby-voltage = <850000>; + }; + + BUCK4 { + regulator-name = "BUCK4"; + regulator-min-microvolt = <600000>; + regulator-max-microvolt = <3400000>; + regulator-boot-on; + regulator-always-on; + }; + + BUCK5 { + regulator-name = "BUCK5"; + regulator-min-microvolt = <600000>; + regulator-max-microvolt = <3400000>; + regulator-boot-on; + regulator-always-on; + }; + + BUCK6 { + regulator-name = "BUCK6"; + regulator-min-microvolt = <600000>; + regulator-max-microvolt = <3400000>; + regulator-boot-on; + regulator-always-on; + }; + + LDO1 { + regulator-name = "LDO1"; + regulator-min-microvolt = <1600000>; + regulator-max-microvolt = <3300000>; + regulator-boot-on; + regulator-always-on; + }; + + LDO2 { + regulator-name = "LDO2"; + regulator-min-microvolt = <800000>; + regulator-max-microvolt = <1150000>; + regulator-boot-on; + regulator-always-on; + }; + + LDO3 { + regulator-name = "LDO3"; + regulator-min-microvolt = <800000>; + regulator-max-microvolt = <3300000>; + regulator-boot-on; + regulator-always-on; + }; + + ldo4: LDO4 { + regulator-name = "LDO4"; + regulator-min-microvolt = <3300000>; + regulator-max-microvolt = <3300000>; + regulator-always-on; + }; + + LDO5 { + regulator-name = "LDO5"; + regulator-min-microvolt = <1800000>; + regulator-max-microvolt = <3300000>; + }; + }; + }; +}; + +&snvs_pwrkey { + status = "okay"; +}; + +/* eMMC */ +&usdhc3 { + pinctrl-names = "default", "state_100mhz", "state_200mhz"; + pinctrl-0 = <&pinctrl_usdhc3>; + pinctrl-1 = <&pinctrl_usdhc3_100mhz>; + pinctrl-2 = <&pinctrl_usdhc3_200mhz>; + bus-width = <8>; + non-removable; + status = "okay"; +}; + +&wdog1 { + pinctrl-names = "default"; + pinctrl-0 = <&pinctrl_wdog>; + fsl,ext-reset-output; + status = "okay"; +}; + +&iomuxc { + pinctrl_eqos: eqosgrp { + fsl,pins = < + MX8MP_IOMUXC_ENET_MDC__ENET_QOS_MDC 0x2 + MX8MP_IOMUXC_ENET_MDIO__ENET_QOS_MDIO 0x2 + MX8MP_IOMUXC_ENET_RD0__ENET_QOS_RGMII_RD0 0x90 + MX8MP_IOMUXC_ENET_RD1__ENET_QOS_RGMII_RD1 0x90 + MX8MP_IOMUXC_ENET_RD2__ENET_QOS_RGMII_RD2 0x90 + MX8MP_IOMUXC_ENET_RD3__ENET_QOS_RGMII_RD3 0x90 + MX8MP_IOMUXC_ENET_RXC__CCM_ENET_QOS_CLOCK_GENERATE_RX_CLK 0x90 + MX8MP_IOMUXC_ENET_RX_CTL__ENET_QOS_RGMII_RX_CTL 0x90 + MX8MP_IOMUXC_ENET_TD0__ENET_QOS_RGMII_TD0 0x16 + MX8MP_IOMUXC_ENET_TD1__ENET_QOS_RGMII_TD1 0x16 + MX8MP_IOMUXC_ENET_TD2__ENET_QOS_RGMII_TD2 0x16 + MX8MP_IOMUXC_ENET_TD3__ENET_QOS_RGMII_TD3 0x16 + MX8MP_IOMUXC_ENET_TX_CTL__ENET_QOS_RGMII_TX_CTL 0x16 + MX8MP_IOMUXC_ENET_TXC__CCM_ENET_QOS_CLOCK_GENERATE_TX_CLK 0x16 + MX8MP_IOMUXC_SD2_WP__GPIO2_IO20 0x10 + MX8MP_IOMUXC_SD1_STROBE__GPIO2_IO11 0x10 + >; + }; + + pinctrl_i2c1: i2c1grp { + fsl,pins = < + MX8MP_IOMUXC_I2C1_SCL__I2C1_SCL 0x400001c2 + MX8MP_IOMUXC_I2C1_SDA__I2C1_SDA 0x400001c2 + >; + }; + + pinctrl_i2c1_gpio: i2c1gpiogrp { + fsl,pins = < + MX8MP_IOMUXC_I2C1_SCL__GPIO5_IO14 0x1c2 + MX8MP_IOMUXC_I2C1_SDA__GPIO5_IO15 0x1c2 + >; + }; + + pinctrl_pmic: pmicgrp { + fsl,pins = < + MX8MP_IOMUXC_GPIO1_IO03__GPIO1_IO03 0x1c0 + >; + }; + + pinctrl_sai3: sai3grp { + fsl,pins = < + MX8MP_IOMUXC_SAI3_TXFS__AUDIOMIX_SAI3_TX_SYNC 0xd6 + MX8MP_IOMUXC_SAI3_TXC__AUDIOMIX_SAI3_TX_BCLK 0xd6 + MX8MP_IOMUXC_SAI3_RXD__AUDIOMIX_SAI3_RX_DATA00 0xd6 + MX8MP_IOMUXC_SAI3_TXD__AUDIOMIX_SAI3_TX_DATA00 0xd6 + MX8MP_IOMUXC_SAI3_MCLK__AUDIOMIX_SAI3_MCLK 0xd6 + MX8MP_IOMUXC_SAI3_RXFS__AUDIOMIX_SAI3_RX_SYNC 0xd6 + MX8MP_IOMUXC_SAI3_RXC__AUDIOMIX_SAI3_RX_BCLK 0xd6 + >; + }; + + pinctrl_usdhc3: usdhc3grp { + fsl,pins = < + MX8MP_IOMUXC_NAND_WE_B__USDHC3_CLK 0x190 + MX8MP_IOMUXC_NAND_WP_B__USDHC3_CMD 0x1d0 + MX8MP_IOMUXC_NAND_DATA04__USDHC3_DATA0 0x1d0 + MX8MP_IOMUXC_NAND_DATA05__USDHC3_DATA1 0x1d0 + MX8MP_IOMUXC_NAND_DATA06__USDHC3_DATA2 0x1d0 + MX8MP_IOMUXC_NAND_DATA07__USDHC3_DATA3 0x1d0 + MX8MP_IOMUXC_NAND_RE_B__USDHC3_DATA4 0x1d0 + MX8MP_IOMUXC_NAND_CE2_B__USDHC3_DATA5 0x1d0 + MX8MP_IOMUXC_NAND_CE3_B__USDHC3_DATA6 0x1d0 + MX8MP_IOMUXC_NAND_CLE__USDHC3_DATA7 0x1d0 + MX8MP_IOMUXC_NAND_CE1_B__USDHC3_STROBE 0x190 + >; + }; + + pinctrl_usdhc3_100mhz: usdhc3-100mhzgrp { + fsl,pins = < + MX8MP_IOMUXC_NAND_WE_B__USDHC3_CLK 0x194 + MX8MP_IOMUXC_NAND_WP_B__USDHC3_CMD 0x1d4 + MX8MP_IOMUXC_NAND_DATA04__USDHC3_DATA0 0x1d4 + MX8MP_IOMUXC_NAND_DATA05__USDHC3_DATA1 0x1d4 + MX8MP_IOMUXC_NAND_DATA06__USDHC3_DATA2 0x1d4 + MX8MP_IOMUXC_NAND_DATA07__USDHC3_DATA3 0x1d4 + MX8MP_IOMUXC_NAND_RE_B__USDHC3_DATA4 0x1d4 + MX8MP_IOMUXC_NAND_CE2_B__USDHC3_DATA5 0x1d4 + MX8MP_IOMUXC_NAND_CE3_B__USDHC3_DATA6 0x1d4 + MX8MP_IOMUXC_NAND_CLE__USDHC3_DATA7 0x1d4 + MX8MP_IOMUXC_NAND_CE1_B__USDHC3_STROBE 0x194 + >; + }; + + pinctrl_usdhc3_200mhz: usdhc3-200mhzgrp { + fsl,pins = < + MX8MP_IOMUXC_NAND_WE_B__USDHC3_CLK 0x196 + MX8MP_IOMUXC_NAND_WP_B__USDHC3_CMD 0x1d6 + MX8MP_IOMUXC_NAND_DATA04__USDHC3_DATA0 0x1d6 + MX8MP_IOMUXC_NAND_DATA05__USDHC3_DATA1 0x1d6 + MX8MP_IOMUXC_NAND_DATA06__USDHC3_DATA2 0x1d6 + MX8MP_IOMUXC_NAND_DATA07__USDHC3_DATA3 0x1d6 + MX8MP_IOMUXC_NAND_RE_B__USDHC3_DATA4 0x1d6 + MX8MP_IOMUXC_NAND_CE2_B__USDHC3_DATA5 0x1d6 + MX8MP_IOMUXC_NAND_CE3_B__USDHC3_DATA6 0x1d6 + MX8MP_IOMUXC_NAND_CLE__USDHC3_DATA7 0x1d6 + MX8MP_IOMUXC_NAND_CE1_B__USDHC3_STROBE 0x196 + >; + }; + + pinctrl_wdog: wdoggrp { + fsl,pins = < + MX8MP_IOMUXC_GPIO1_IO02__WDOG1_WDOG_B 0xc6 + >; + }; +};
The DART-MX8M-PLUS is an i.MX8MP-based SoM from Variscite. Add a device tree file that models its core modules, based on the device tree from Variscite's BSP. Sound support has been stripped out, as the downstream and upstream DT bindings differ for the related devices, and the schematics of the SoM isn't publicly available to check how those devices are wired up. Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com> --- .../boot/dts/freescale/imx8mp-var-dart.dtsi | 305 ++++++++++++++++++ 1 file changed, 305 insertions(+) create mode 100644 arch/arm64/boot/dts/freescale/imx8mp-var-dart.dtsi