* [PATCH V2 0/4] arm64: imx: add imx8qxp support
@ 2018-10-14 14:34 A.s. Dong
2018-10-14 14:34 ` [PATCH V2 1/4] " A.s. Dong
` (3 more replies)
0 siblings, 4 replies; 21+ messages in thread
From: A.s. Dong @ 2018-10-14 14:34 UTC (permalink / raw)
To: linux-arm-kernel
Add imx8qxp mek basic support with the function
Lpuart
uSDHC
FEC
GPIO
Note it depends on the clock and pinctrl driver parts.
Dong Aisheng (4):
arm64: imx: add imx8qxp support
arm64: dts: imx: add imx8qxp support
arm64: dts: imx: add imx8qxp mek support
defconfig: arm64: add imx8qxp support
Documentation/devicetree/bindings/arm/fsl.txt | 8 +
arch/arm64/Kconfig.platforms | 22 +
arch/arm64/boot/dts/freescale/Makefile | 1 +
arch/arm64/boot/dts/freescale/imx8-ca35.dtsi | 61 ++
arch/arm64/boot/dts/freescale/imx8qxp-mek.dts | 134 ++++
arch/arm64/boot/dts/freescale/imx8qxp.dtsi | 861 ++++++++++++++++++++++++++
arch/arm64/configs/defconfig | 6 +
7 files changed, 1093 insertions(+)
create mode 100644 arch/arm64/boot/dts/freescale/imx8-ca35.dtsi
create mode 100644 arch/arm64/boot/dts/freescale/imx8qxp-mek.dts
create mode 100644 arch/arm64/boot/dts/freescale/imx8qxp.dtsi
--
2.7.4
^ permalink raw reply [flat|nested] 21+ messages in thread* [PATCH V2 1/4] arm64: imx: add imx8qxp support 2018-10-14 14:34 [PATCH V2 0/4] arm64: imx: add imx8qxp support A.s. Dong @ 2018-10-14 14:34 ` A.s. Dong 2018-10-14 14:34 ` [PATCH V2 2/4] arm64: dts: " A.s. Dong ` (2 subsequent siblings) 3 siblings, 0 replies; 21+ messages in thread From: A.s. Dong @ 2018-10-14 14:34 UTC (permalink / raw) To: linux-arm-kernel Add imx8qxp support. Cc: Catalin Marinas <catalin.marinas@arm.com> Cc: Will Deacon <will.deacon@arm.com> Cc: Linus Walleij <linus.walleij@linaro.org> Cc: Shawn Guo <shawnguo@kernel.org> Cc: Fabio Estevam <festevam@gmail.com> Signed-off-by: Dong Aisheng <aisheng.dong@nxp.com> --- v1->v2: * update CONFIG option name --- arch/arm64/Kconfig.platforms | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/arch/arm64/Kconfig.platforms b/arch/arm64/Kconfig.platforms index 393d2b5..c7324b1 100644 --- a/arch/arm64/Kconfig.platforms +++ b/arch/arm64/Kconfig.platforms @@ -139,6 +139,28 @@ config ARCH_MVEBU - Armada 7K SoC Family - Armada 8K SoC Family +config ARCH_MXC + bool "ARMv8 based NXP i.MX SoC family" + select GPIOLIB + select PINCTRL + select PM + select PM_GENERIC_DOMAINS + select SOC_BUS + help + This enables support for the ARMv8 based SoCs in the + NXP i.MX family. + +config SOC_IMX8QXP + bool "i.MX8QXP" + depends on ARCH_MXC + select IMX_MBOX + select IMX_SCU + select IMX_SCU_PD + select MXC_CLK_SCU + select PINCTRL_IMX8QXP + help + This enables support for NXP i.MX8QXP SoC. + config ARCH_QCOM bool "Qualcomm Platforms" select GPIOLIB -- 2.7.4 ^ permalink raw reply related [flat|nested] 21+ messages in thread
* [PATCH V2 2/4] arm64: dts: imx: add imx8qxp support 2018-10-14 14:34 [PATCH V2 0/4] arm64: imx: add imx8qxp support A.s. Dong 2018-10-14 14:34 ` [PATCH V2 1/4] " A.s. Dong @ 2018-10-14 14:34 ` A.s. Dong 2018-10-14 23:13 ` Fabio Estevam 2018-10-15 6:58 ` Sascha Hauer 2018-10-14 14:34 ` [PATCH V2 3/4] arm64: dts: imx: add imx8qxp mek support A.s. Dong 2018-10-14 14:35 ` [PATCH V2 4/4] defconfig: arm64: add imx8qxp support A.s. Dong 3 siblings, 2 replies; 21+ messages in thread From: A.s. Dong @ 2018-10-14 14:34 UTC (permalink / raw) To: linux-arm-kernel Add imx8qxp support Cc: Rob Herring <robh+dt@kernel.org> Cc: Mark Rutland <mark.rutland@arm.com> Cc: devicetree at vger.kernel.org Cc: Shawn Guo <shawnguo@kernel.org> Cc: Sascha Hauer <kernel@pengutronix.de> Cc: Fabio Estevam <fabio.estevam@nxp.com> Signed-off-by: Dong Aisheng <aisheng.dong@nxp.com> --- v1->v2: * mu binding usage update * no define for node address * do not use '_' for node name * drop 'fsl-' prefix for imx dtsi * no defines for unit address * generic node names * range map for 32bit register * separate board dts --- Documentation/devicetree/bindings/arm/fsl.txt | 4 + arch/arm64/boot/dts/freescale/imx8-ca35.dtsi | 61 ++ arch/arm64/boot/dts/freescale/imx8qxp.dtsi | 861 ++++++++++++++++++++++++++ 3 files changed, 926 insertions(+) create mode 100644 arch/arm64/boot/dts/freescale/imx8-ca35.dtsi create mode 100644 arch/arm64/boot/dts/freescale/imx8qxp.dtsi diff --git a/Documentation/devicetree/bindings/arm/fsl.txt b/Documentation/devicetree/bindings/arm/fsl.txt index 968f238..baeb1fc 100644 --- a/Documentation/devicetree/bindings/arm/fsl.txt +++ b/Documentation/devicetree/bindings/arm/fsl.txt @@ -119,6 +119,10 @@ i.MX6q generic board Required root node properties: - compatible = "fsl,imx6q"; +i.MX8QXP generic board +Required root node properties: + - compatible = "fsl,imx8qxp"; + Freescale Vybrid Platform Device Tree Bindings ---------------------------------------------- diff --git a/arch/arm64/boot/dts/freescale/imx8-ca35.dtsi b/arch/arm64/boot/dts/freescale/imx8-ca35.dtsi new file mode 100644 index 0000000..c79e97a --- /dev/null +++ b/arch/arm64/boot/dts/freescale/imx8-ca35.dtsi @@ -0,0 +1,61 @@ +// SPDX-License-Identifier: GPL-2.0+ +/* + * Copyright (C) 2016 Freescale Semiconductor, Inc. + * Copyright 2017~2018 NXP + */ + +#include <dt-bindings/interrupt-controller/arm-gic.h> + +/{ + cpus { + #address-cells = <2>; + #size-cells = <0>; + + /* We have 1 clusters with 4 Cortex-A35 cores */ + A35_0: cpu at 0 { + device_type = "cpu"; + compatible = "arm,cortex-a35"; + reg = <0x0 0x0>; + enable-method = "psci"; + next-level-cache = <&A35_L2>; + }; + + A35_1: cpu at 1 { + device_type = "cpu"; + compatible = "arm,cortex-a35"; + reg = <0x0 0x1>; + enable-method = "psci"; + next-level-cache = <&A35_L2>; + }; + + A35_2: cpu at 2 { + device_type = "cpu"; + compatible = "arm,cortex-a35"; + reg = <0x0 0x2>; + enable-method = "psci"; + next-level-cache = <&A35_L2>; + }; + + A35_3: cpu at 3 { + device_type = "cpu"; + compatible = "arm,cortex-a35"; + reg = <0x0 0x3>; + enable-method = "psci"; + next-level-cache = <&A35_L2>; + }; + + A35_L2: l2-cache0 { + compatible = "cache"; + }; + }; + + pmu { + compatible = "arm,armv8-pmuv3"; + interrupts = <GIC_PPI 7 IRQ_TYPE_LEVEL_HIGH>; + }; + + psci { + compatible = "arm,psci-1.0"; + method = "smc"; + }; +}; diff --git a/arch/arm64/boot/dts/freescale/imx8qxp.dtsi b/arch/arm64/boot/dts/freescale/imx8qxp.dtsi new file mode 100644 index 0000000..e1d2578 --- /dev/null +++ b/arch/arm64/boot/dts/freescale/imx8qxp.dtsi @@ -0,0 +1,861 @@ +// SPDX-License-Identifier: GPL-2.0+ +/* + * Copyright (C) 2016 Freescale Semiconductor, Inc. + * Copyright 2017~2018 NXP + * Dong Aisheng <aisheng.dong@nxp.com> + */ + +#include <dt-bindings/clock/imx8qxp-clock.h> +#include <dt-bindings/gpio/gpio.h> +#include <dt-bindings/pinctrl/pads-imx8qxp.h> + +#include "imx8-ca35.dtsi" + +/ { + interrupt-parent = <&gic>; + #address-cells = <2>; + #size-cells = <2>; + + aliases { + serial0 = &dma_lpuart0; + mmc0 = &usdhc1; + mmc1 = &usdhc2; + mmc2 = &usdhc3; + }; + + memory at 80000000 { + device_type = "memory"; + reg = <0x00000000 0x80000000 0 0x40000000>; + }; + + gic: interrupt-controller at 51a00000 { + compatible = "arm,gic-v3"; + reg = <0x0 0x51a00000 0 0x10000>, /* GIC Dist */ + <0x0 0x51b00000 0 0xc0000>; /* GICR (RD_base + SGI_base) */ + #interrupt-cells = <3>; + interrupt-controller; + interrupts = <GIC_PPI 9 IRQ_TYPE_LEVEL_HIGH>; + }; + + timer { + compatible = "arm,armv8-timer"; + interrupts = <GIC_PPI 13 IRQ_TYPE_LEVEL_LOW>, /* Physical Secure */ + <GIC_PPI 14 IRQ_TYPE_LEVEL_LOW>, /* Physical Non-Secure */ + <GIC_PPI 11 IRQ_TYPE_LEVEL_LOW>, /* Virtual */ + <GIC_PPI 10 IRQ_TYPE_LEVEL_LOW>; /* Hypervisor */ + }; + + scu { + compatible = "fsl,imx-scu"; + mbox-names = "tx0", "tx1", "tx2", "tx3", + "rx0", "rx1", "rx2", "rx3"; + mboxes = <&lsio_mu1 0 0 + &lsio_mu1 0 1 + &lsio_mu1 0 2 + &lsio_mu1 0 3 + &lsio_mu1 1 0 + &lsio_mu1 1 1 + &lsio_mu1 1 2 + &lsio_mu1 1 3>; + + clk: clock-controller { + compatible = "fsl,imx8qxp-clk"; + #clock-cells = <1>; + }; + + iomuxc: pinctrl { + compatible = "fsl,imx8qxp-iomuxc"; + }; + + imx8qx-pm { + compatible = "fsl,scu-pd"; + #address-cells = <1>; + #size-cells = <0>; + + pd_lsio: lsio-power-domain { + #power-domain-cells = <0>; + #address-cells = <1>; + #size-cells = <0>; + + pd_lsio_pwm0: lsio-pwm0 at 191 { + reg = <191>; + #power-domain-cells = <0>; + power-domains = <&pd_lsio>; + }; + + pd_lsio_pwm1: lsio-pwm1 at 192 { + reg = <192>; + #power-domain-cells = <0>; + power-domains = <&pd_lsio>; + }; + + pd_lsio_pwm2: lsio-pwm2 at 193 { + reg = <193>; + #power-domain-cells = <0>; + power-domains = <&pd_lsio>; + }; + + pd_lsio_pwm3: lsio-pwm3 at 194 { + reg = <194>; + #power-domain-cells = <0>; + power-domains = <&pd_lsio>; + }; + + pd_lsio_pwm4: lsio-pwm4 at 195 { + reg = <195>; + #power-domain-cells = <0>; + power-domains = <&pd_lsio>; + }; + + pd_lsio_pwm5: lsio-pwm5 at 196 { + reg = <196>; + #power-domain-cells = <0>; + power-domains = <&pd_lsio>; + }; + + pd_lsio_pwm6: lsio-pwm6 at 197 { + reg = <197>; + #power-domain-cells = <0>; + power-domains = <&pd_lsio>; + }; + + pd_lsio_pwm7: lsio-pwm7 at 198 { + reg = <198>; + #power-domain-cells = <0>; + power-domains = <&pd_lsio>; + }; + + pd_lsio_kpp: lsio-kpp at 212 { + reg = <212>; + #power-domain-cells = <0>; + power-domains = <&pd_lsio>; + }; + + pd_lsio_gpio0: lsio-gpio0 at 199 { + reg = <199>; + #power-domain-cells = <0>; + power-domains = <&pd_lsio>; + }; + + pd_lsio_gpio1: lsio-gpio1 at 200 { + reg = <200>; + #power-domain-cells = <0>; + power-domains = <&pd_lsio>; + }; + + pd_lsio_gpio2: lsio-gpio2 at 201 { + reg = <201>; + #power-domain-cells = <0>; + power-domains = <&pd_lsio>; + }; + + pd_lsio_gpio3: lsio-gpio3 at 202 { + reg = <202>; + #power-domain-cells = <0>; + power-domains = <&pd_lsio>; + }; + + pd_lsio_gpio4: lsio-gpio4 at 203 { + reg = <203>; + #power-domain-cells = <0>; + power-domains = <&pd_lsio>; + }; + + pd_lsio_gpio5: lsio-gpio5 at 204 { + reg = <204>; + #power-domain-cells = <0>; + power-domains = <&pd_lsio>; + }; + + pd_lsio_gpio6: lsio-gpio6 at 205 { + reg = <205>; + #power-domain-cells = <0>; + power-domains = <&pd_lsio>; + }; + + pd_lsio_gpio7: lsio-gpio7 at 206 { + reg = <206>; + #power-domain-cells = <0>; + power-domains = <&pd_lsio>; + }; + + pd_lsio_gpt0: lsio-gpt0 at 207 { + reg = <207>; + #power-domain-cells = <0>; + power-domains = <&pd_lsio>; + }; + + pd_lsio_gpt1: lsio-gpt1 at 208 { + reg = <208>; + #power-domain-cells = <0>; + power-domains = <&pd_lsio>; + }; + + pd_lsio_gpt2: lsio-gpt2 at 209 { + reg = <209>; + #power-domain-cells = <0>; + power-domains = <&pd_lsio>; + }; + + pd_lsio_gpt3: lsio-gpt3 at 210 { + reg = <210>; + #power-domain-cells = <0>; + power-domains = <&pd_lsio>; + }; + + pd_lsio_gpt4: lsio-gpt4 at 211 { + reg = <211>; + #power-domain-cells = <0>; + power-domains = <&pd_lsio>; + }; + + pd_lsio_flexspi0: lsio-fspi0 at 237 { + reg = <237>; + #power-domain-cells = <0>; + power-domains = <&pd_lsio>; + }; + + pd_lsio_flexspi1: lsio-fspi1 at 238 { + reg = <238>; + #power-domain-cells = <0>; + power-domains = <&pd_lsio>; + }; + }; + + pd_conn: connectivity-power-domain { + #power-domain-cells = <0>; + #address-cells = <1>; + #size-cells = <0>; + + pd_conn_usbotg0: conn-usb0 at 259 { + reg = <259>; + #power-domain-cells = <0>; + power-domains = <&pd_conn>; + }; + + pd_conn_usbotg0_phy: conn-usb0-phy at 261 { + reg = <261>; + #power-domain-cells = <0>; + power-domains = <&pd_conn>; + }; + + pd_conn_usbotg1: conn-usb1 at 260 { + reg = <260>; + #power-domain-cells = <0>; + power-domains = <&pd_conn>; + }; + + pd_conn_usb2: conn-usb2 at 262 { + reg = <262>; + #power-domain-cells = <0>; + power-domains = <&pd_conn>; + }; + + pd_conn_usb2_phy: conn-usb2-phy at 263 { + reg = <263>; + #power-domain-cells = <0>; + power-domains = <&pd_conn>; + }; + + pd_conn_sdhc0: conn-sdhc0 at 248 { + reg = <248>; + #power-domain-cells = <0>; + power-domains = <&pd_conn>; + }; + + pd_conn_sdhc1: conn-sdhc1 at 249 { + reg = <249>; + #power-domain-cells = <0>; + power-domains = <&pd_conn>; + }; + + pd_conn_sdhc2: conn-sdhc2 at 250 { + reg = <250>; + #power-domain-cells = <0>; + power-domains = <&pd_conn>; + }; + + pd_conn_enet0: conn-enet0 at 251 { + reg = <251>; + #power-domain-cells = <0>; + power-domains = <&pd_conn>; + }; + + pd_conn_enet1: conn-enet1 at 252 { + reg = <252>; + #power-domain-cells = <0>; + power-domains = <&pd_conn>; + }; + + pd_conn_nand: conn-nand at 265 { + reg = <265>; + #power-domain-cells = <0>; + power-domains = <&pd_conn>; + }; + + pd_conn_mlb0: conn-mlb0 at 253 { + reg = <253>; + #power-domain-cells = <0>; + power-domains = <&pd_conn>; + }; + + pd_conn_edma_ch0: conn-dma4-ch0 at 372 { + reg = <372>; + #power-domain-cells = <0>; + power-domains =<&pd_conn>; + }; + + pd_conn_edma_ch1: conn-dma4-ch1 at 373 { + reg = <373>; + #power-domain-cells = <0>; + power-domains =<&pd_conn>; + }; + + pd_conn_edma_ch2: conn-dma4-ch2 at 374 { + reg = <374>; + #power-domain-cells = <0>; + power-domains =<&pd_conn>; + }; + + pd_conn_edma_ch3: conn-dma4-ch3 at 375 { + reg = <375>; + #power-domain-cells = <0>; + power-domains =<&pd_conn>; + }; + + pd_conn_edma_ch4: conn-dma4-ch4 at 376 { + reg = <376>; + #power-domain-cells = <0>; + power-domains =<&pd_conn>; + }; + }; + + pd_dma: dma-power-domain { + #power-domain-cells = <0>; + #address-cells = <1>; + #size-cells = <0>; + + pd_dma_flexcan0: dma-flexcan0 at 105 { + reg = <105>; + #power-domain-cells = <0>; + power-domains = <&pd_dma>; + }; + + pd_dma_flexcan1: dma-flexcan1 at 106 { + reg = <106>; + #power-domain-cells = <0>; + power-domains = <&pd_dma>; + }; + + pd_dma_flexcan2: dma-flexcan2 at 107 { + reg = <107>; + #power-domain-cells = <0>; + power-domains = <&pd_dma>; + }; + + pd_dma_ftm0: dma-ftm0 at 103 { + reg = <103>; + #power-domain-cells = <0>; + power-domains = <&pd_dma>; + }; + + pd_dma_ftm1: dma-ftm1 at 104 { + reg = <104>; + #power-domain-cells = <0>; + power-domains = <&pd_dma>; + }; + + pd_dma_adc0: dma-adc0 at 101 { + reg = <101>; + #power-domain-cells = <0>; + power-domains = <&pd_dma>; + }; + + pd_dma_lpi2c0: dma-lpi2c0 at 96 { + reg = <96>; + #power-domain-cells = <0>; + power-domains = <&pd_dma>; + }; + + pd_dma_lpi2c1: dma-lpi2c1 at 97 { + reg = <97>; + #power-domain-cells = <0>; + power-domains = <&pd_dma>; + }; + + pd_dma_lpi2c2: dma-lpi2c2 at 98 { + reg = <98>; + #power-domain-cells = <0>; + power-domains = <&pd_dma>; + }; + + pd_dma_lpi2c3: dma-lpi2c3 at 99 { + reg = <99>; + #power-domain-cells = <0>; + power-domains = <&pd_dma>; + }; + + pd_dma_lpuart0: dma-lpuart0 at 57 { + reg = <57>; + #power-domain-cells = <0>; + power-domains = <&pd_dma>; + }; + + pd_dma_lpuart1: dma-lpuart1 at 58 { + reg = <58>; + #power-domain-cells = <0>; + power-domains = <&pd_dma>; + }; + + pd_dma_lpuart2: dma-lpuart2 at 59 { + reg = <59>; + #power-domain-cells = <0>; + power-domains = <&pd_dma>; + }; + + pd_dma_lpuart3: dma-lpuart3 at 60 { + reg = <60>; + #power-domain-cells = <0>; + power-domains = <&pd_dma>; + }; + + pd_dma_lpspi0: dma-spi0 at 53 { + reg = <53>; + #power-domain-cells = <0>; + power-domains = <&pd_dma>; + }; + + pd_dma_lpspi1: dma-spi1 at 54 { + reg = <54>; + #power-domain-cells = <0>; + power-domains = <&pd_dma>; + }; + + pd_dma_lpspi2: dma-spi2 at 55 { + reg = <55>; + #power-domain-cells = <0>; + power-domains = <&pd_dma>; + }; + + pd_dma_lpspi3: dma-spi3 at 56 { + reg = <56>; + #power-domain-cells = <0>; + power-domains = <&pd_dma>; + }; + + pd_dma_pwm0: dma-pwm0 at 188 { + reg = <188>; + #power-domain-cells = <0>; + power-domains = <&pd_dma>; + }; + + pd_dma_lcd0: dma-lcd0 at 187 { + reg = <187>; + #power-domain-cells = <0>; + power-domains = <&pd_dma>; + }; + }; + + pd_gpu: gpu-power-domain { + #power-domain-cells = <0>; + #address-cells = <1>; + #size-cells = <0>; + + pd_gpu0: gpu0 at 144 { + reg = <144>; + #power-domain-cells = <0>; + power-domains =<&pd_gpu>; + #address-cells = <1>; + #size-cells = <0>; + }; + }; + + pd_vpu: vpu-power-domain at 358 { + reg = <358>; + #power-domain-cells = <0>; + #address-cells = <1>; + #size-cells = <0>; + + pd_vpu_core: vpu-core at 367 { + reg = <367>; + #power-domain-cells = <0>; + power-domains =<&pd_vpu>; + }; + }; + + pd_hsio: hsio-power-domain { + #power-domain-cells = <0>; + #address-cells = <1>; + #size-cells = <0>; + + pd_pcie: hsio-pcie-pd at 152 { + reg = <152>; + #power-domain-cells = <0>; + power-domains =<&pd_hsio>; + }; + }; + + pd_dc: dc-power-domain { + #power-domain-cells = <0>; + #address-cells = <1>; + #size-cells = <0>; + + pd_dc0: dc0-power-domain at 32 { + reg = <32>; + #power-domain-cells = <0>; + power-domains =<&pd_dc>; + }; + }; + + pd_mipi_dsi: mipi0-dsi-power-domain at 393 { + reg = <393>; + #power-domain-cells = <0>; + #address-cells = <1>; + #size-cells = <0>; + + pd_mipi_dsi_i2c0: mipi0-dsi-i2c0 at 395 { + reg = <395>; + power-domains =<&pd_mipi_dsi>; + }; + + pd_mipi_dsi_i2c1: mipi0-dsi-i2c1 at 396 { + reg = <396>; + power-domains =<&pd_mipi_dsi>; + }; + + pd_mipi_pwm0: mipi0-dsi-pwm0 at 394 { + reg = <394>; + power-domains =<&pd_mipi_dsi>; + }; + }; + + pd_mipi_csi: mipi-csi0-power-domain at 401 { + reg = <401>; + #power-domain-cells = <0>; + #address-cells = <1>; + #size-cells = <0>; + + pd_mipi_csi0_i2c0: mipi-csi0-i2c at 403 { + reg = <403>; + power-domains =<&pd_mipi_csi>; + }; + + pd_mipi_csi0_pwm0: mipi-csi0-pwm at 402 { + reg = <402>; + power-domains =<&pd_mipi_csi>; + }; + }; + }; + }; + + audio_subsys: bus at 59000000 { + compatible = "simple-bus"; + #address-cells = <1>; + #size-cells = <1>; + ranges = <0x59000000 0x0 0x59000000 0x1000000>; + }; + + dma_subsys: bus at 5a000000 { + compatible = "simple-bus"; + #address-cells = <1>; + #size-cells = <1>; + ranges = <0x5a000000 0x0 0x5a000000 0x1000000>; + + dma_lpuart0: serial at 5a060000 { + compatible = "fsl,imx7ulp-lpuart"; + reg = <0x5a060000 0x1000>; + interrupts = <GIC_SPI 225 IRQ_TYPE_LEVEL_HIGH>; + interrupt-parent = <&gic>; + clocks = <&clk IMX8QXP_UART0_CLK>; + clock-names = "ipg"; + status = "disabled"; + }; + + dma_i2c0: i2c at 5a800000 { + compatible = "fsl,imx7ulp-lpi2c"; + reg = <0x5a800000 0x4000>; + interrupts = <GIC_SPI 220 IRQ_TYPE_LEVEL_HIGH>; + interrupt-parent = <&gic>; + clocks = <&clk IMX8QXP_I2C0_CLK>; + clock-names = "per"; + assigned-clocks = <&clk IMX8QXP_I2C0_CLK>; + assigned-clock-rates = <24000000>; + power-domains = <&pd_dma_lpi2c0>; + status = "disabled"; + }; + + dma_i2c1: i2c at 5a810000 { + compatible = "fsl,imx7ulp-lpi2c"; + reg = <0x5a810000 0x4000>; + interrupts = <GIC_SPI 221 IRQ_TYPE_LEVEL_HIGH>; + interrupt-parent = <&gic>; + clocks = <&clk IMX8QXP_I2C1_CLK>; + clock-names = "per"; + assigned-clocks = <&clk IMX8QXP_I2C1_CLK>; + assigned-clock-rates = <24000000>; + status = "disabled"; + }; + + dma_i2c2: i2c at 5a820000 { + compatible = "fsl,imx7ulp-lpi2c"; + reg = <0x5a820000 0x4000>; + interrupts = <GIC_SPI 222 IRQ_TYPE_LEVEL_HIGH>; + interrupt-parent = <&gic>; + clocks = <&clk IMX8QXP_I2C2_CLK>; + clock-names = "per"; + assigned-clocks = <&clk IMX8QXP_I2C2_CLK>; + assigned-clock-rates = <24000000>; + power-domains = <&pd_dma_lpi2c2>; + status = "disabled"; + }; + + dma_i2c3: i2c at 5a830000 { + compatible = "fsl,imx7ulp-lpi2c"; + reg = <0x5a830000 0x4000>; + interrupts = <GIC_SPI 223 IRQ_TYPE_LEVEL_HIGH>; + interrupt-parent = <&gic>; + clocks = <&clk IMX8QXP_I2C3_CLK>; + clock-names = "per"; + assigned-clocks = <&clk IMX8QXP_I2C3_CLK>; + assigned-clock-rates = <24000000>; + power-domains = <&pd_dma_lpi2c3>; + status = "disabled"; + }; + }; + + conn_subsys: bus at 5b000000 { + compatible = "simple-bus"; + #address-cells = <1>; + #size-cells = <1>; + ranges = <0x5b000000 0x0 0x5b000000 0x1000000>; + + usdhc1: mmc at 5b010000 { + compatible = "fsl,imx7d-usdhc"; + interrupt-parent = <&gic>; + interrupts = <GIC_SPI 232 IRQ_TYPE_LEVEL_HIGH>; + reg = <0x5b010000 0x10000>; + clocks = <&clk IMX8QXP_SDHC0_IPG_CLK>, + <&clk IMX8QXP_SDHC0_CLK>, + <&clk IMX8QXP_CLK_DUMMY>; + clock-names = "ipg", "per", "ahb"; + assigned-clocks = <&clk IMX8QXP_SDHC0_DIV>; + assigned-clock-rates = <200000000>; + power-domains = <&pd_conn_sdhc0>; + status = "disabled"; + }; + + usdhc2: mmc at 5b020000 { + compatible = "fsl,imx7d-usdhc"; + interrupt-parent = <&gic>; + interrupts = <GIC_SPI 233 IRQ_TYPE_LEVEL_HIGH>; + reg = <0x5b020000 0x10000>; + clocks = <&clk IMX8QXP_SDHC1_IPG_CLK>, + <&clk IMX8QXP_SDHC1_CLK>, + <&clk IMX8QXP_CLK_DUMMY>; + clock-names = "ipg", "per", "ahb"; + assigned-clocks = <&clk IMX8QXP_SDHC1_DIV>; + assigned-clock-rates = <200000000>; + power-domains = <&pd_conn_sdhc1>; + fsl,tuning-start-tap = <20>; + fsl,tuning-step= <2>; + status = "disabled"; + }; + + usdhc3: mmc at 5b030000 { + compatible = "fsl,imx7d-usdhc"; + interrupt-parent = <&gic>; + interrupts = <GIC_SPI 234 IRQ_TYPE_LEVEL_HIGH>; + reg = <0x5b030000 0x10000>; + clocks = <&clk IMX8QXP_SDHC2_IPG_CLK>, + <&clk IMX8QXP_SDHC2_CLK>, + <&clk IMX8QXP_CLK_DUMMY>; + clock-names = "ipg", "per", "ahb"; + assigned-clocks = <&clk IMX8QXP_SDHC2_DIV>; + assigned-clock-rates = <200000000>; + power-domains = <&pd_conn_sdhc2>; + status = "disabled"; + }; + + fec1: ethernet at 5b040000 { + compatible = "fsl,imx6sx-fec"; + reg = <0x5b040000 0x10000>; + interrupts = <GIC_SPI 258 IRQ_TYPE_LEVEL_HIGH>, + <GIC_SPI 256 IRQ_TYPE_LEVEL_HIGH>, + <GIC_SPI 257 IRQ_TYPE_LEVEL_HIGH>, + <GIC_SPI 259 IRQ_TYPE_LEVEL_HIGH>; + clocks = <&clk IMX8QXP_ENET0_IPG_CLK>, <&clk IMX8QXP_ENET0_AHB_CLK>, <&clk IMX8QXP_ENET0_TX_CLK>, + <&clk IMX8QXP_ENET0_PTP_CLK>; + clock-names = "ipg", "ahb", "enet_clk_ref", "ptp"; + assigned-clocks = <&clk IMX8QXP_ENET0_REF_DIV>, <&clk IMX8QXP_ENET0_PTP_CLK>; + assigned-clock-rates = <125000000>, <125000000>; + fsl,num-tx-queues=<3>; + fsl,num-rx-queues=<3>; + power-domains = <&pd_conn_enet0>; + status = "disabled"; + }; + + fec2: ethernet at 5b050000 { + compatible = "fsl,imx8qxp-fec"; + reg = <0x5b050000 0x10000>; + interrupts = <GIC_SPI 262 IRQ_TYPE_LEVEL_HIGH>, + <GIC_SPI 260 IRQ_TYPE_LEVEL_HIGH>, + <GIC_SPI 261 IRQ_TYPE_LEVEL_HIGH>, + <GIC_SPI 263 IRQ_TYPE_LEVEL_HIGH>; + clocks = <&clk IMX8QXP_ENET1_IPG_CLK>, <&clk IMX8QXP_ENET1_AHB_CLK>, <&clk IMX8QXP_ENET1_TX_CLK>, + <&clk IMX8QXP_ENET1_PTP_CLK>; + clock-names = "ipg", "ahb", "enet_clk_ref", "ptp"; + assigned-clocks = <&clk IMX8QXP_ENET1_REF_DIV>, <&clk IMX8QXP_ENET1_PTP_CLK>; + assigned-clock-rates = <125000000>, <125000000>; + fsl,num-tx-queues=<3>; + fsl,num-rx-queues=<3>; + power-domains = <&pd_conn_enet1>; + status = "disabled"; + }; + }; + + db_subsys: bus at 5c000000 { + compatible = "simple-bus"; + #address-cells = <1>; + #size-cells = <1>; + ranges = <0x5c000000 0x0 0x5c000000 0x1000000>; + + ddr_pmu0: pmu at 5c020000 { + compatible = "fsl,imx8-ddr-pmu"; + reg = <0x5c020000 0x10000>; + }; + }; + + lsio_subsys: bus at 5d000000 { + compatible = "simple-bus"; + #address-cells = <1>; + #size-cells = <1>; + ranges = <0x5d000000 0x0 0x5d000000 0x1000000>; + + lsio_mu0: mailbox at 5d1b0000 { + compatible = "fsl,imx8qxp-mu", "fsl,imx6sx-mu"; + reg = <0x5d1b0000 0x10000>; + interrupts = <GIC_SPI 176 IRQ_TYPE_LEVEL_HIGH>; + #mbox-cells = <0>; + status = "disabled"; + }; + + lsio_mu1: mailbox at 5d1c0000 { + compatible = "fsl,imx8qxp-mu", "fsl,imx6sx-mu"; + reg = <0x5d1c0000 0x10000>; + interrupts = <GIC_SPI 177 IRQ_TYPE_LEVEL_HIGH>; + #mbox-cells = <2>; + }; + + lsio_mu3: mailbox at 5d1e0000 { + compatible = "fsl,imx8qxp-mu", "fsl,imx6sx-mu"; + reg = <0x5d1e0000 0x10000>; + interrupts = <GIC_SPI 179 IRQ_TYPE_LEVEL_HIGH>; + #mbox-cells = <0>; + status = "disabled"; + }; + + lsio_mu4: mailbox at 5d1f0000 { + compatible = "fsl,imx8qxp-mu", "fsl,imx6sx-mu"; + reg = <0x5d1f0000 0x10000>; + interrupts = <GIC_SPI 179 IRQ_TYPE_LEVEL_HIGH>; + #mbox-cells = <0>; + status = "disabled"; + }; + + lsio_gpio0: gpio at 5d080000 { + compatible = "fsl,imx8qxp-gpio", "fsl,imx35-gpio"; + reg = <0x5d080000 0x10000>; + interrupts = <GIC_SPI 136 IRQ_TYPE_LEVEL_HIGH>; + gpio-controller; + #gpio-cells = <2>; + interrupt-controller; + #interrupt-cells = <2>; + power-domains = <&pd_lsio_gpio0>; + }; + + lsio_gpio1: gpio at 5d090000 { + compatible = "fsl,imx8qxp-gpio", "fsl,imx35-gpio"; + reg = <0x5d090000 0x10000>; + interrupts = <GIC_SPI 137 IRQ_TYPE_LEVEL_HIGH>; + gpio-controller; + #gpio-cells = <2>; + interrupt-controller; + #interrupt-cells = <2>; + power-domains = <&pd_lsio_gpio1>; + }; + + lsio_gpio2: gpio at 5d0a0000 { + compatible = "fsl,imx8qxp-gpio", "fsl,imx35-gpio"; + reg = <0x5d0a0000 0x10000>; + interrupts = <GIC_SPI 138 IRQ_TYPE_LEVEL_HIGH>; + gpio-controller; + #gpio-cells = <2>; + interrupt-controller; + #interrupt-cells = <2>; + power-domains = <&pd_lsio_gpio2>; + }; + + lsio_gpio3: gpio at 5d0b0000 { + compatible = "fsl,imx8qxp-gpio", "fsl,imx35-gpio"; + reg = <0x5d0b0000 0x10000>; + interrupts = <GIC_SPI 139 IRQ_TYPE_LEVEL_HIGH>; + gpio-controller; + #gpio-cells = <2>; + interrupt-controller; + #interrupt-cells = <2>; + power-domains = <&pd_lsio_gpio3>; + }; + + lsio_gpio4: gpio at 5d0c0000 { + compatible = "fsl,imx8qxp-gpio", "fsl,imx35-gpio"; + reg = <0x5d0c0000 0x10000>; + interrupts = <GIC_SPI 140 IRQ_TYPE_LEVEL_HIGH>; + gpio-controller; + #gpio-cells = <2>; + interrupt-controller; + #interrupt-cells = <2>; + power-domains = <&pd_lsio_gpio4>; + }; + + lsio_gpio5: gpio at 5d0d0000 { + compatible = "fsl,imx8qxp-gpio", "fsl,imx35-gpio"; + reg = <0x5d0d0000 0x10000>; + interrupts = <GIC_SPI 141 IRQ_TYPE_LEVEL_HIGH>; + gpio-controller; + #gpio-cells = <2>; + interrupt-controller; + #interrupt-cells = <2>; + power-domains = <&pd_lsio_gpio5>; + }; + + lsio_gpio6: gpio at 5d0e0000 { + compatible = "fsl,imx8qxp-gpio", "fsl,imx35-gpio"; + reg = <0x5d0e0000 0x10000>; + interrupts = <GIC_SPI 142 IRQ_TYPE_LEVEL_HIGH>; + gpio-controller; + #gpio-cells = <2>; + interrupt-controller; + #interrupt-cells = <2>; + power-domains = <&pd_lsio_gpio6>; + }; + + lsio_gpio7: gpio at 5d0f0000 { + compatible = "fsl,imx8qxp-gpio", "fsl,imx35-gpio"; + reg = <0x5d0f0000 0x10000>; + interrupts = <GIC_SPI 143 IRQ_TYPE_LEVEL_HIGH>; + gpio-controller; + #gpio-cells = <2>; + interrupt-controller; + #interrupt-cells = <2>; + power-domains = <&pd_lsio_gpio7>; + }; + }; + + hsio_subsys: bus at 5f000000 { + compatible = "simple-bus"; + #address-cells = <1>; + #size-cells = <1>; + ranges = <0x5f000000 0x0 0x5f000000 0x1000000>; + }; + +}; -- 2.7.4 ^ permalink raw reply related [flat|nested] 21+ messages in thread
* [PATCH V2 2/4] arm64: dts: imx: add imx8qxp support 2018-10-14 14:34 ` [PATCH V2 2/4] arm64: dts: " A.s. Dong @ 2018-10-14 23:13 ` Fabio Estevam 2018-10-15 6:27 ` Daniel Baluta ` (2 more replies) 2018-10-15 6:58 ` Sascha Hauer 1 sibling, 3 replies; 21+ messages in thread From: Fabio Estevam @ 2018-10-14 23:13 UTC (permalink / raw) To: linux-arm-kernel Hi Dong, On Sun, Oct 14, 2018 at 11:35 AM A.s. Dong <aisheng.dong@nxp.com> wrote: > > Add imx8qxp support You could probably expand the commit log by explaining a bit of what im8qxp means. > diff --git a/arch/arm64/boot/dts/freescale/imx8qxp.dtsi b/arch/arm64/boot/dts/freescale/imx8qxp.dtsi > new file mode 100644 > index 0000000..e1d2578 > --- /dev/null > +++ b/arch/arm64/boot/dts/freescale/imx8qxp.dtsi > @@ -0,0 +1,861 @@ > +// SPDX-License-Identifier: GPL-2.0+ > +/* > + * Copyright (C) 2016 Freescale Semiconductor, Inc. > + * Copyright 2017~2018 NXP I guess you meant "-" instead of "~". > + memory at 80000000 { > + device_type = "memory"; > + reg = <0x00000000 0x80000000 0 0x40000000>; > + }; This should go to the board dts file instead as the memory size may vary from board to board. > + imx8qx-pm { > + compatible = "fsl,scu-pd"; > + #address-cells = <1>; > + #size-cells = <0>; > + > + pd_lsio: lsio-power-domain { > + #power-domain-cells = <0>; > + #address-cells = <1>; > + #size-cells = <0>; > + > + pd_lsio_pwm0: lsio-pwm0 at 191 { > + reg = <191>; The number after @ is in hex, so the reg property should be 0x191. ^ permalink raw reply [flat|nested] 21+ messages in thread
* [PATCH V2 2/4] arm64: dts: imx: add imx8qxp support 2018-10-14 23:13 ` Fabio Estevam @ 2018-10-15 6:27 ` Daniel Baluta 2018-10-15 7:30 ` Leonard Crestez 2018-10-15 7:57 ` A.s. Dong 2 siblings, 0 replies; 21+ messages in thread From: Daniel Baluta @ 2018-10-15 6:27 UTC (permalink / raw) To: linux-arm-kernel On Du, 2018-10-14 at 20:13 -0300, Fabio Estevam wrote: > Hi Dong, > > On Sun, Oct 14, 2018 at 11:35 AM A.s. Dong <aisheng.dong@nxp.com> > wrote: > > > > > > Add imx8qxp support > You could probably expand the commit log by explaining a bit of what > im8qxp means. Also a link to documentation would be really helpful for reviewers. thanks, Daniel. ^ permalink raw reply [flat|nested] 21+ messages in thread
* [PATCH V2 2/4] arm64: dts: imx: add imx8qxp support 2018-10-14 23:13 ` Fabio Estevam 2018-10-15 6:27 ` Daniel Baluta @ 2018-10-15 7:30 ` Leonard Crestez 2018-10-15 9:29 ` A.s. Dong 2018-10-15 7:57 ` A.s. Dong 2 siblings, 1 reply; 21+ messages in thread From: Leonard Crestez @ 2018-10-15 7:30 UTC (permalink / raw) To: linux-arm-kernel On Sun, 2018-10-14 at 20:13 -0300, Fabio Estevam wrote: > > + imx8qx-pm { > > + compatible = "fsl,scu-pd"; > > + #address-cells = <1>; > > + #size-cells = <0>; > > + > > + pd_lsio: lsio-power-domain { > > + #power-domain-cells = <0>; > > + #address-cells = <1>; > > + #size-cells = <0>; > > + > > + pd_lsio_pwm0: lsio-pwm0 at 191 { > > + reg = <191>; > > The number after @ is in hex, so the reg property should be 0x191. These are SC_R_* resource ids from include/linux/firmware/imx/types.h and they are almost everywhere referenced as decimals. Is this really not acceptable for DT? -- Regards, Leonard ^ permalink raw reply [flat|nested] 21+ messages in thread
* [PATCH V2 2/4] arm64: dts: imx: add imx8qxp support 2018-10-15 7:30 ` Leonard Crestez @ 2018-10-15 9:29 ` A.s. Dong 0 siblings, 0 replies; 21+ messages in thread From: A.s. Dong @ 2018-10-15 9:29 UTC (permalink / raw) To: linux-arm-kernel > -----Original Message----- > From: Leonard Crestez > Sent: Monday, October 15, 2018 3:30 PM > On Sun, 2018-10-14 at 20:13 -0300, Fabio Estevam wrote: > > > + imx8qx-pm { > > > + compatible = "fsl,scu-pd"; > > > + #address-cells = <1>; > > > + #size-cells = <0>; > > > + > > > + pd_lsio: lsio-power-domain { > > > + #power-domain-cells = <0>; > > > + #address-cells = <1>; > > > + #size-cells = <0>; > > > + > > > + pd_lsio_pwm0: lsio-pwm0 at 191 { > > > + reg = <191>; > > > > The number after @ is in hex, so the reg property should be 0x191. > > These are SC_R_* resource ids from include/linux/firmware/imx/types.h > and they are almost everywhere referenced as decimals. > > Is this really not acceptable for DT? > I think the problem is mismatch as DT binding request the reg property value must be equal to the unit-address. See: https://github.com/devicetree-org/devicetree-specification/releases It seems like a common issue in the kernel as I see many similar users. Regards Dong Aisheng > -- > Regards, > Leonard ^ permalink raw reply [flat|nested] 21+ messages in thread
* [PATCH V2 2/4] arm64: dts: imx: add imx8qxp support 2018-10-14 23:13 ` Fabio Estevam 2018-10-15 6:27 ` Daniel Baluta 2018-10-15 7:30 ` Leonard Crestez @ 2018-10-15 7:57 ` A.s. Dong 2018-10-18 0:51 ` Rob Herring 2 siblings, 1 reply; 21+ messages in thread From: A.s. Dong @ 2018-10-15 7:57 UTC (permalink / raw) To: linux-arm-kernel > -----Original Message----- > From: Fabio Estevam [mailto:festevam at gmail.com] > Sent: Monday, October 15, 2018 7:14 AM > To: A.s. Dong <aisheng.dong@nxp.com> > Cc: moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE > <linux-arm-kernel@lists.infradead.org>; Dong Aisheng <dongas86@gmail.com>; > Sascha Hauer <kernel@pengutronix.de>; Shawn Guo <shawnguo@kernel.org>; > Fabio Estevam <fabio.estevam@nxp.com>; Rob Herring <robh+dt@kernel.org>; > Catalin Marinas <catalin.marinas@arm.com>; Will Deacon > <will.deacon@arm.com>; dl-linux-imx <linux-imx@nxp.com>; Mark Rutland > <mark.rutland@arm.com>; open list:OPEN FIRMWARE AND FLATTENED > DEVICE TREE BINDINGS <devicetree@vger.kernel.org> > Subject: Re: [PATCH V2 2/4] arm64: dts: imx: add imx8qxp support > > Hi Dong, > > On Sun, Oct 14, 2018 at 11:35 AM A.s. Dong <aisheng.dong@nxp.com> wrote: > > > > Add imx8qxp support > > You could probably expand the commit log by explaining a bit of what im8qxp > means. > Got it, thanks for the suggestion. > > diff --git a/arch/arm64/boot/dts/freescale/imx8qxp.dtsi > > b/arch/arm64/boot/dts/freescale/imx8qxp.dtsi > > new file mode 100644 > > index 0000000..e1d2578 > > --- /dev/null > > +++ b/arch/arm64/boot/dts/freescale/imx8qxp.dtsi > > @@ -0,0 +1,861 @@ > > +// SPDX-License-Identifier: GPL-2.0+ > > +/* > > + * Copyright (C) 2016 Freescale Semiconductor, Inc. > > + * Copyright 2017~2018 NXP > > I guess you meant "-" instead of "~". > > > + memory at 80000000 { > > + device_type = "memory"; > > + reg = <0x00000000 0x80000000 0 0x40000000>; > > + }; > > This should go to the board dts file instead as the memory size may vary from > board to board. > That's right. Will change it. > > + imx8qx-pm { > > + compatible = "fsl,scu-pd"; > > + #address-cells = <1>; > > + #size-cells = <0>; > > + > > + pd_lsio: lsio-power-domain { > > + #power-domain-cells = <0>; > > + #address-cells = <1>; > > + #size-cells = <0>; > > + > > + pd_lsio_pwm0: lsio-pwm0 at 191 { > > + reg = <191>; > > The number after @ is in hex, so the reg property should be 0x191. Thanks for the reminder. The PD ID is defined in DEC. So I will change them all into HEX later manually. BTW, this seems like error prone and checkpatch can't report it. And I notice many similar users in kernel with the same issue: arch/arm/boot/dts/tps65910.dtsi arch/arm/boot/dts/tegra124-nyan.dtsi arch/arm/boot/dts/rk3288.dtsi ... Regards Dong Aisheng ^ permalink raw reply [flat|nested] 21+ messages in thread
* [PATCH V2 2/4] arm64: dts: imx: add imx8qxp support 2018-10-15 7:57 ` A.s. Dong @ 2018-10-18 0:51 ` Rob Herring 2018-10-18 2:32 ` A.s. Dong 0 siblings, 1 reply; 21+ messages in thread From: Rob Herring @ 2018-10-18 0:51 UTC (permalink / raw) To: linux-arm-kernel On Mon, Oct 15, 2018 at 07:57:07AM +0000, A.s. Dong wrote: > > -----Original Message----- > > From: Fabio Estevam [mailto:festevam at gmail.com] > > Sent: Monday, October 15, 2018 7:14 AM > > To: A.s. Dong <aisheng.dong@nxp.com> > > Cc: moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE > > <linux-arm-kernel@lists.infradead.org>; Dong Aisheng <dongas86@gmail.com>; > > Sascha Hauer <kernel@pengutronix.de>; Shawn Guo <shawnguo@kernel.org>; > > Fabio Estevam <fabio.estevam@nxp.com>; Rob Herring <robh+dt@kernel.org>; > > Catalin Marinas <catalin.marinas@arm.com>; Will Deacon > > <will.deacon@arm.com>; dl-linux-imx <linux-imx@nxp.com>; Mark Rutland > > <mark.rutland@arm.com>; open list:OPEN FIRMWARE AND FLATTENED > > DEVICE TREE BINDINGS <devicetree@vger.kernel.org> > > Subject: Re: [PATCH V2 2/4] arm64: dts: imx: add imx8qxp support > > > > Hi Dong, > > > > On Sun, Oct 14, 2018 at 11:35 AM A.s. Dong <aisheng.dong@nxp.com> wrote: > > > > > > Add imx8qxp support > > > > You could probably expand the commit log by explaining a bit of what im8qxp > > means. > > > > Got it, thanks for the suggestion. > > > > diff --git a/arch/arm64/boot/dts/freescale/imx8qxp.dtsi > > > b/arch/arm64/boot/dts/freescale/imx8qxp.dtsi > > > new file mode 100644 > > > index 0000000..e1d2578 > > > --- /dev/null > > > +++ b/arch/arm64/boot/dts/freescale/imx8qxp.dtsi > > > @@ -0,0 +1,861 @@ > > > +// SPDX-License-Identifier: GPL-2.0+ > > > +/* > > > + * Copyright (C) 2016 Freescale Semiconductor, Inc. > > > + * Copyright 2017~2018 NXP > > > > I guess you meant "-" instead of "~". > > > > > + memory at 80000000 { > > > + device_type = "memory"; > > > + reg = <0x00000000 0x80000000 0 0x40000000>; > > > + }; > > > > This should go to the board dts file instead as the memory size may vary from > > board to board. > > > > That's right. Will change it. > > > > + imx8qx-pm { > > > + compatible = "fsl,scu-pd"; > > > + #address-cells = <1>; > > > + #size-cells = <0>; > > > + > > > + pd_lsio: lsio-power-domain { > > > + #power-domain-cells = <0>; > > > + #address-cells = <1>; > > > + #size-cells = <0>; > > > + > > > + pd_lsio_pwm0: lsio-pwm0 at 191 { > > > + reg = <191>; > > > > The number after @ is in hex, so the reg property should be 0x191. > > Thanks for the reminder. > The PD ID is defined in DEC. So I will change them all into HEX later manually. > > BTW, this seems like error prone and checkpatch can't report it. checkpatch doesn't really check dts files. But if it did would you have noticed? Because there is at least one checkpatch issue with your author name and S-o-b name not matching. > And I notice many similar users in kernel with the same issue: > arch/arm/boot/dts/tps65910.dtsi > arch/arm/boot/dts/tegra124-nyan.dtsi > arch/arm/boot/dts/rk3288.dtsi At least I2C and SPI are now checked by dtc. 'simple-bus' children were too, but silently broke and only recently got fixed in upstream dtc. I've not pulled that into the kernel yet, but you can build dtbs using an external copy of dtc. And guess what, there are *lots* of warnings. Rob ^ permalink raw reply [flat|nested] 21+ messages in thread
* [PATCH V2 2/4] arm64: dts: imx: add imx8qxp support 2018-10-18 0:51 ` Rob Herring @ 2018-10-18 2:32 ` A.s. Dong 0 siblings, 0 replies; 21+ messages in thread From: A.s. Dong @ 2018-10-18 2:32 UTC (permalink / raw) To: linux-arm-kernel [...] > > > > + imx8qx-pm { > > > > + compatible = "fsl,scu-pd"; > > > > + #address-cells = <1>; > > > > + #size-cells = <0>; > > > > + > > > > + pd_lsio: lsio-power-domain { > > > > + #power-domain-cells = <0>; > > > > + #address-cells = <1>; > > > > + #size-cells = <0>; > > > > + > > > > + pd_lsio_pwm0: lsio-pwm0 at 191 { > > > > + reg = <191>; > > > > > > The number after @ is in hex, so the reg property should be 0x191. > > > > Thanks for the reminder. > > The PD ID is defined in DEC. So I will change them all into HEX later manually. > > > > BTW, this seems like error prone and checkpatch can't report it. > > checkpatch doesn't really check dts files. > > But if it did would you have noticed? Because there is at least one checkpatch > issue with your author name and S-o-b name not matching. > > > And I notice many similar users in kernel with the same issue: > > arch/arm/boot/dts/tps65910.dtsi > > arch/arm/boot/dts/tegra124-nyan.dtsi > > arch/arm/boot/dts/rk3288.dtsi > > At least I2C and SPI are now checked by dtc. 'simple-bus' children were too, > but silently broke and only recently got fixed in upstream dtc. > I've not pulled that into the kernel yet, but you can build dtbs using an external > copy of dtc. And guess what, there are *lots* of warnings. > Thanks for the info. Will try it. Regards Dong Aisheng > Rob ^ permalink raw reply [flat|nested] 21+ messages in thread
* [PATCH V2 2/4] arm64: dts: imx: add imx8qxp support 2018-10-14 14:34 ` [PATCH V2 2/4] arm64: dts: " A.s. Dong 2018-10-14 23:13 ` Fabio Estevam @ 2018-10-15 6:58 ` Sascha Hauer 2018-10-15 8:08 ` A.s. Dong 1 sibling, 1 reply; 21+ messages in thread From: Sascha Hauer @ 2018-10-15 6:58 UTC (permalink / raw) To: linux-arm-kernel On Sun, Oct 14, 2018 at 02:34:52PM +0000, A.s. Dong wrote: > Add imx8qxp support > > Cc: Rob Herring <robh+dt@kernel.org> > Cc: Mark Rutland <mark.rutland@arm.com> > Cc: devicetree at vger.kernel.org > Cc: Shawn Guo <shawnguo@kernel.org> > Cc: Sascha Hauer <kernel@pengutronix.de> > Cc: Fabio Estevam <fabio.estevam@nxp.com> > Signed-off-by: Dong Aisheng <aisheng.dong@nxp.com> > --- > v1->v2: > * mu binding usage update > * no define for node address > * do not use '_' for node name > * drop 'fsl-' prefix for imx dtsi > * no defines for unit address > * generic node names > * range map for 32bit register > * separate board dts > --- > Documentation/devicetree/bindings/arm/fsl.txt | 4 + > arch/arm64/boot/dts/freescale/imx8-ca35.dtsi | 61 ++ > arch/arm64/boot/dts/freescale/imx8qxp.dtsi | 861 ++++++++++++++++++++++++++ > 3 files changed, 926 insertions(+) > create mode 100644 arch/arm64/boot/dts/freescale/imx8-ca35.dtsi > create mode 100644 arch/arm64/boot/dts/freescale/imx8qxp.dtsi > > diff --git a/Documentation/devicetree/bindings/arm/fsl.txt b/Documentation/devicetree/bindings/arm/fsl.txt > index 968f238..baeb1fc 100644 > --- a/Documentation/devicetree/bindings/arm/fsl.txt > +++ b/Documentation/devicetree/bindings/arm/fsl.txt > @@ -119,6 +119,10 @@ i.MX6q generic board > Required root node properties: > - compatible = "fsl,imx6q"; > > +i.MX8QXP generic board > +Required root node properties: > + - compatible = "fsl,imx8qxp"; > + > Freescale Vybrid Platform Device Tree Bindings > ---------------------------------------------- > > diff --git a/arch/arm64/boot/dts/freescale/imx8-ca35.dtsi b/arch/arm64/boot/dts/freescale/imx8-ca35.dtsi > new file mode 100644 > index 0000000..c79e97a > --- /dev/null > +++ b/arch/arm64/boot/dts/freescale/imx8-ca35.dtsi > @@ -0,0 +1,61 @@ > +// SPDX-License-Identifier: GPL-2.0+ > +/* > + * Copyright (C) 2016 Freescale Semiconductor, Inc. > + * Copyright 2017~2018 NXP > + */ > + > +#include <dt-bindings/interrupt-controller/arm-gic.h> > + > +/{ > + cpus { > + #address-cells = <2>; > + #size-cells = <0>; > + > + /* We have 1 clusters with 4 Cortex-A35 cores */ > + A35_0: cpu at 0 { > + device_type = "cpu"; > + compatible = "arm,cortex-a35"; > + reg = <0x0 0x0>; > + enable-method = "psci"; > + next-level-cache = <&A35_L2>; > + }; > + > + A35_1: cpu at 1 { > + device_type = "cpu"; > + compatible = "arm,cortex-a35"; > + reg = <0x0 0x1>; > + enable-method = "psci"; > + next-level-cache = <&A35_L2>; > + }; > + > + A35_2: cpu at 2 { > + device_type = "cpu"; > + compatible = "arm,cortex-a35"; > + reg = <0x0 0x2>; > + enable-method = "psci"; > + next-level-cache = <&A35_L2>; > + }; > + > + A35_3: cpu at 3 { > + device_type = "cpu"; > + compatible = "arm,cortex-a35"; > + reg = <0x0 0x3>; > + enable-method = "psci"; > + next-level-cache = <&A35_L2>; > + }; > + > + A35_L2: l2-cache0 { > + compatible = "cache"; > + }; > + }; > + > + pmu { > + compatible = "arm,armv8-pmuv3"; > + interrupts = <GIC_PPI 7 IRQ_TYPE_LEVEL_HIGH>; > + }; > + > + psci { > + compatible = "arm,psci-1.0"; > + method = "smc"; > + }; > +}; > diff --git a/arch/arm64/boot/dts/freescale/imx8qxp.dtsi b/arch/arm64/boot/dts/freescale/imx8qxp.dtsi > new file mode 100644 > index 0000000..e1d2578 > --- /dev/null > +++ b/arch/arm64/boot/dts/freescale/imx8qxp.dtsi > @@ -0,0 +1,861 @@ > +// SPDX-License-Identifier: GPL-2.0+ > +/* > + * Copyright (C) 2016 Freescale Semiconductor, Inc. > + * Copyright 2017~2018 NXP > + * Dong Aisheng <aisheng.dong@nxp.com> > + */ > + > +#include <dt-bindings/clock/imx8qxp-clock.h> > +#include <dt-bindings/gpio/gpio.h> > +#include <dt-bindings/pinctrl/pads-imx8qxp.h> > + > +#include "imx8-ca35.dtsi" > + > +/ { > + interrupt-parent = <&gic>; > + #address-cells = <2>; > + #size-cells = <2>; > + > + aliases { > + serial0 = &dma_lpuart0; > + mmc0 = &usdhc1; > + mmc1 = &usdhc2; > + mmc2 = &usdhc3; > + }; > + > + memory at 80000000 { > + device_type = "memory"; > + reg = <0x00000000 0x80000000 0 0x40000000>; > + }; > + > + gic: interrupt-controller at 51a00000 { > + compatible = "arm,gic-v3"; > + reg = <0x0 0x51a00000 0 0x10000>, /* GIC Dist */ > + <0x0 0x51b00000 0 0xc0000>; /* GICR (RD_base + SGI_base) */ > + #interrupt-cells = <3>; > + interrupt-controller; > + interrupts = <GIC_PPI 9 IRQ_TYPE_LEVEL_HIGH>; > + }; > + > + timer { > + compatible = "arm,armv8-timer"; > + interrupts = <GIC_PPI 13 IRQ_TYPE_LEVEL_LOW>, /* Physical Secure */ > + <GIC_PPI 14 IRQ_TYPE_LEVEL_LOW>, /* Physical Non-Secure */ > + <GIC_PPI 11 IRQ_TYPE_LEVEL_LOW>, /* Virtual */ > + <GIC_PPI 10 IRQ_TYPE_LEVEL_LOW>; /* Hypervisor */ > + }; > + > + scu { > + compatible = "fsl,imx-scu"; > + mbox-names = "tx0", "tx1", "tx2", "tx3", > + "rx0", "rx1", "rx2", "rx3"; > + mboxes = <&lsio_mu1 0 0 > + &lsio_mu1 0 1 > + &lsio_mu1 0 2 > + &lsio_mu1 0 3 > + &lsio_mu1 1 0 > + &lsio_mu1 1 1 > + &lsio_mu1 1 2 > + &lsio_mu1 1 3>; > + > + clk: clock-controller { > + compatible = "fsl,imx8qxp-clk"; > + #clock-cells = <1>; > + }; > + > + iomuxc: pinctrl { > + compatible = "fsl,imx8qxp-iomuxc"; > + }; > + > + imx8qx-pm { > + compatible = "fsl,scu-pd"; I missed this earlier, but there should be a i.MX8qp specific compatible as the SCU API might change for future SoCs. > + compatible = "fsl,imx7ulp-lpuart"; > + compatible = "fsl,imx7ulp-lpi2c"; > + compatible = "fsl,imx7d-usdhc"; All these lack the most specific imx8qp compatible. > + compatible = "fsl,imx6sx-fec"; > + compatible = "fsl,imx8qxp-fec"; BTW are there really two different FECs on the i.MX8qp? Sascha -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | ^ permalink raw reply [flat|nested] 21+ messages in thread
* [PATCH V2 2/4] arm64: dts: imx: add imx8qxp support 2018-10-15 6:58 ` Sascha Hauer @ 2018-10-15 8:08 ` A.s. Dong 2018-10-15 8:27 ` Sascha Hauer 0 siblings, 1 reply; 21+ messages in thread From: A.s. Dong @ 2018-10-15 8:08 UTC (permalink / raw) To: linux-arm-kernel > -----Original Message----- > From: Sascha Hauer [mailto:s.hauer at pengutronix.de] > Sent: Monday, October 15, 2018 2:59 PM > To: A.s. Dong <aisheng.dong@nxp.com> > Cc: linux-arm-kernel at lists.infradead.org; Mark Rutland > <mark.rutland@arm.com>; dongas86 at gmail.com; devicetree at vger.kernel.org; > catalin.marinas at arm.com; will.deacon at arm.com; robh+dt at kernel.org; > dl-linux-imx <linux-imx@nxp.com>; kernel at pengutronix.de; Fabio Estevam > <fabio.estevam@nxp.com>; shawnguo at kernel.org > Subject: Re: [PATCH V2 2/4] arm64: dts: imx: add imx8qxp support > > On Sun, Oct 14, 2018 at 02:34:52PM +0000, A.s. Dong wrote: > > Add imx8qxp support > > > > Cc: Rob Herring <robh+dt@kernel.org> > > Cc: Mark Rutland <mark.rutland@arm.com> > > Cc: devicetree at vger.kernel.org > > Cc: Shawn Guo <shawnguo@kernel.org> > > Cc: Sascha Hauer <kernel@pengutronix.de> > > Cc: Fabio Estevam <fabio.estevam@nxp.com> > > Signed-off-by: Dong Aisheng <aisheng.dong@nxp.com> > > --- > > v1->v2: > > * mu binding usage update > > * no define for node address > > * do not use '_' for node name > > * drop 'fsl-' prefix for imx dtsi > > * no defines for unit address > > * generic node names > > * range map for 32bit register > > * separate board dts > > --- > > Documentation/devicetree/bindings/arm/fsl.txt | 4 + > > arch/arm64/boot/dts/freescale/imx8-ca35.dtsi | 61 ++ > > arch/arm64/boot/dts/freescale/imx8qxp.dtsi | 861 > ++++++++++++++++++++++++++ > > 3 files changed, 926 insertions(+) > > create mode 100644 arch/arm64/boot/dts/freescale/imx8-ca35.dtsi > > create mode 100644 arch/arm64/boot/dts/freescale/imx8qxp.dtsi > > > > diff --git a/Documentation/devicetree/bindings/arm/fsl.txt > > b/Documentation/devicetree/bindings/arm/fsl.txt > > index 968f238..baeb1fc 100644 > > --- a/Documentation/devicetree/bindings/arm/fsl.txt > > +++ b/Documentation/devicetree/bindings/arm/fsl.txt > > @@ -119,6 +119,10 @@ i.MX6q generic board Required root node > > properties: > > - compatible = "fsl,imx6q"; > > > > +i.MX8QXP generic board > > +Required root node properties: > > + - compatible = "fsl,imx8qxp"; > > + > > Freescale Vybrid Platform Device Tree Bindings > > ---------------------------------------------- > > > > diff --git a/arch/arm64/boot/dts/freescale/imx8-ca35.dtsi > > b/arch/arm64/boot/dts/freescale/imx8-ca35.dtsi > > new file mode 100644 > > index 0000000..c79e97a > > --- /dev/null > > +++ b/arch/arm64/boot/dts/freescale/imx8-ca35.dtsi > > @@ -0,0 +1,61 @@ > > +// SPDX-License-Identifier: GPL-2.0+ > > +/* > > + * Copyright (C) 2016 Freescale Semiconductor, Inc. > > + * Copyright 2017~2018 NXP > > + */ > > + > > +#include <dt-bindings/interrupt-controller/arm-gic.h> > > + > > +/{ > > + cpus { > > + #address-cells = <2>; > > + #size-cells = <0>; > > + > > + /* We have 1 clusters with 4 Cortex-A35 cores */ > > + A35_0: cpu at 0 { > > + device_type = "cpu"; > > + compatible = "arm,cortex-a35"; > > + reg = <0x0 0x0>; > > + enable-method = "psci"; > > + next-level-cache = <&A35_L2>; > > + }; > > + > > + A35_1: cpu at 1 { > > + device_type = "cpu"; > > + compatible = "arm,cortex-a35"; > > + reg = <0x0 0x1>; > > + enable-method = "psci"; > > + next-level-cache = <&A35_L2>; > > + }; > > + > > + A35_2: cpu at 2 { > > + device_type = "cpu"; > > + compatible = "arm,cortex-a35"; > > + reg = <0x0 0x2>; > > + enable-method = "psci"; > > + next-level-cache = <&A35_L2>; > > + }; > > + > > + A35_3: cpu at 3 { > > + device_type = "cpu"; > > + compatible = "arm,cortex-a35"; > > + reg = <0x0 0x3>; > > + enable-method = "psci"; > > + next-level-cache = <&A35_L2>; > > + }; > > + > > + A35_L2: l2-cache0 { > > + compatible = "cache"; > > + }; > > + }; > > + > > + pmu { > > + compatible = "arm,armv8-pmuv3"; > > + interrupts = <GIC_PPI 7 IRQ_TYPE_LEVEL_HIGH>; > > + }; > > + > > + psci { > > + compatible = "arm,psci-1.0"; > > + method = "smc"; > > + }; > > +}; > > diff --git a/arch/arm64/boot/dts/freescale/imx8qxp.dtsi > > b/arch/arm64/boot/dts/freescale/imx8qxp.dtsi > > new file mode 100644 > > index 0000000..e1d2578 > > --- /dev/null > > +++ b/arch/arm64/boot/dts/freescale/imx8qxp.dtsi > > @@ -0,0 +1,861 @@ > > +// SPDX-License-Identifier: GPL-2.0+ > > +/* > > + * Copyright (C) 2016 Freescale Semiconductor, Inc. > > + * Copyright 2017~2018 NXP > > + * Dong Aisheng <aisheng.dong@nxp.com> > > + */ > > + > > +#include <dt-bindings/clock/imx8qxp-clock.h> > > +#include <dt-bindings/gpio/gpio.h> > > +#include <dt-bindings/pinctrl/pads-imx8qxp.h> > > + > > +#include "imx8-ca35.dtsi" > > + > > +/ { > > + interrupt-parent = <&gic>; > > + #address-cells = <2>; > > + #size-cells = <2>; > > + > > + aliases { > > + serial0 = &dma_lpuart0; > > + mmc0 = &usdhc1; > > + mmc1 = &usdhc2; > > + mmc2 = &usdhc3; > > + }; > > + > > + memory at 80000000 { > > + device_type = "memory"; > > + reg = <0x00000000 0x80000000 0 0x40000000>; > > + }; > > + > > + gic: interrupt-controller at 51a00000 { > > + compatible = "arm,gic-v3"; > > + reg = <0x0 0x51a00000 0 0x10000>, /* GIC Dist */ > > + <0x0 0x51b00000 0 0xc0000>; /* GICR (RD_base + SGI_base) > */ > > + #interrupt-cells = <3>; > > + interrupt-controller; > > + interrupts = <GIC_PPI 9 IRQ_TYPE_LEVEL_HIGH>; > > + }; > > + > > + timer { > > + compatible = "arm,armv8-timer"; > > + interrupts = <GIC_PPI 13 IRQ_TYPE_LEVEL_LOW>, /* Physical Secure > */ > > + <GIC_PPI 14 IRQ_TYPE_LEVEL_LOW>, /* Physical > Non-Secure */ > > + <GIC_PPI 11 IRQ_TYPE_LEVEL_LOW>, /* Virtual */ > > + <GIC_PPI 10 IRQ_TYPE_LEVEL_LOW>; /* Hypervisor */ > > + }; > > + > > + scu { > > + compatible = "fsl,imx-scu"; > > + mbox-names = "tx0", "tx1", "tx2", "tx3", > > + "rx0", "rx1", "rx2", "rx3"; > > + mboxes = <&lsio_mu1 0 0 > > + &lsio_mu1 0 1 > > + &lsio_mu1 0 2 > > + &lsio_mu1 0 3 > > + &lsio_mu1 1 0 > > + &lsio_mu1 1 1 > > + &lsio_mu1 1 2 > > + &lsio_mu1 1 3>; > > + > > + clk: clock-controller { > > + compatible = "fsl,imx8qxp-clk"; > > + #clock-cells = <1>; > > + }; > > + > > + iomuxc: pinctrl { > > + compatible = "fsl,imx8qxp-iomuxc"; > > + }; > > + > > + imx8qx-pm { > > + compatible = "fsl,scu-pd"; > > I missed this earlier, but there should be a i.MX8qp specific compatible as the > SCU API might change for future SoCs. > We still do not see that requirement up till now. Not sure if it would be possible in the future. I see low possibilities. SCU IPC is designed to be generic to all MX8 SCU firmwares. Even it changes, SCU firmware version control may helps. > > + compatible = "fsl,imx7ulp-lpuart"; > > + compatible = "fsl,imx7ulp-lpi2c"; > > + compatible = "fsl,imx7d-usdhc"; > > All these lack the most specific imx8qp compatible. > Adding them requires binding doc update as well. S I suppose they could be added later when the QXP specific features are really supported by the drivers. Do you think it's okay? > > + compatible = "fsl,imx6sx-fec"; > > + compatible = "fsl,imx8qxp-fec"; > > BTW are there really two different FECs on the i.MX8qp? Good catch, will alignment them all to fsl,imx6sx-fec. Regards Dong Aisheng > > > Sascha > > -- > Pengutronix e.K. | > | > Industrial Linux Solutions | > https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww. > pengutronix.de%2F&data=02%7C01%7Caisheng.dong%40nxp.com%7Cf1 > 897d4035174ffda74808d6326bb448%7C686ea1d3bc2b4c6fa92cd99c5c3016 > 35%7C0%7C0%7C636751835496320764&sdata=J0MO38TWN91LWL3W > 5SZk3y1v3PLyHzhNHl0L8jS1xcE%3D&reserved=0 | > Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 > | > Amtsgericht Hildesheim, HRA 2686 | Fax: > +49-5121-206917-5555 | ^ permalink raw reply [flat|nested] 21+ messages in thread
* [PATCH V2 2/4] arm64: dts: imx: add imx8qxp support 2018-10-15 8:08 ` A.s. Dong @ 2018-10-15 8:27 ` Sascha Hauer 2018-10-15 9:03 ` A.s. Dong 0 siblings, 1 reply; 21+ messages in thread From: Sascha Hauer @ 2018-10-15 8:27 UTC (permalink / raw) To: linux-arm-kernel On Mon, Oct 15, 2018 at 08:08:31AM +0000, A.s. Dong wrote: > > > + imx8qx-pm { > > > + compatible = "fsl,scu-pd"; > > > > I missed this earlier, but there should be a i.MX8qp specific compatible as the > > SCU API might change for future SoCs. > > > > We still do not see that requirement up till now. Not sure if it would be > possible in the future. I see low possibilities. > SCU IPC is designed to be generic to all MX8 SCU firmwares. And i.MX9? i.MX10? > Even it changes, SCU firmware version control may helps. It's not the first time that the position of the version field changes with a newer version. > > > > + compatible = "fsl,imx7ulp-lpuart"; > > > + compatible = "fsl,imx7ulp-lpi2c"; > > > + compatible = "fsl,imx7d-usdhc"; > > > > All these lack the most specific imx8qp compatible. > > > > Adding them requires binding doc update as well. > S I suppose they could be added later when the QXP specific features are > really supported by the drivers. > Do you think it's okay? Newer Kernels should work with older device trees, so once you roll out these compatibles it's too late already. Sascha -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | ^ permalink raw reply [flat|nested] 21+ messages in thread
* [PATCH V2 2/4] arm64: dts: imx: add imx8qxp support 2018-10-15 8:27 ` Sascha Hauer @ 2018-10-15 9:03 ` A.s. Dong 2018-10-15 9:40 ` Sascha Hauer 0 siblings, 1 reply; 21+ messages in thread From: A.s. Dong @ 2018-10-15 9:03 UTC (permalink / raw) To: linux-arm-kernel > -----Original Message----- > From: Sascha Hauer [mailto:s.hauer at pengutronix.de] > Sent: Monday, October 15, 2018 4:28 PM > To: A.s. Dong <aisheng.dong@nxp.com> > Cc: linux-arm-kernel at lists.infradead.org; Mark Rutland > <mark.rutland@arm.com>; dongas86 at gmail.com; devicetree at vger.kernel.org; > catalin.marinas at arm.com; will.deacon at arm.com; robh+dt at kernel.org; > dl-linux-imx <linux-imx@nxp.com>; kernel at pengutronix.de; Fabio Estevam > <fabio.estevam@nxp.com>; shawnguo at kernel.org > Subject: Re: [PATCH V2 2/4] arm64: dts: imx: add imx8qxp support > > On Mon, Oct 15, 2018 at 08:08:31AM +0000, A.s. Dong wrote: > > > > + imx8qx-pm { > > > > + compatible = "fsl,scu-pd"; > > > > > > I missed this earlier, but there should be a i.MX8qp specific > > > compatible as the SCU API might change for future SoCs. > > > > > > > We still do not see that requirement up till now. Not sure if it would > > be possible in the future. I see low possibilities. > > SCU IPC is designed to be generic to all MX8 SCU firmwares. > > And i.MX9? i.MX10? > MX8DM MX8DXP > > Even it changes, SCU firmware version control may helps. > > It's not the first time that the position of the version field changes with a > newer version. > I understand your worry. Up till now all SCU firmware based SoCs are all using one generic IPC driver internally. And I have not heard a possible changing in the future. I double checked the SCU firmware implementation that the IPC Is deigned to be platform independent. So it's less to be changed. So I wonder if this could be over worried. Even it is changed, (quite less probility), we still can user version To distinguish them, just like arm,scpi , arm,scmi. Right? > > > > > > + compatible = "fsl,imx7ulp-lpuart"; > > > > + compatible = "fsl,imx7ulp-lpi2c"; > > > > + compatible = "fsl,imx7d-usdhc"; > > > > > > All these lack the most specific imx8qp compatible. > > > > > > > Adding them requires binding doc update as well. > > S I suppose they could be added later when the QXP specific features > > are really supported by the drivers. > > Do you think it's okay? > > Newer Kernels should work with older device trees, so once you roll out these > compatibles it's too late already. > The backwards compatible string is used to guarantee a basic function. Even we add qxp specific compatible string later, it still can work with backwards function. So I'm not quite get what the real problem is. And this is the initial support that we don't expect the full features with such an early device tree, right? Regards Dong Aisheng > Sascha > > -- > Pengutronix e.K. | > | > Industrial Linux Solutions | > https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww. > pengutronix.de%2F&data=02%7C01%7Caisheng.dong%40nxp.com%7C33 > 7b52b64a9d4b1f2c5c08d632781dcf%7C686ea1d3bc2b4c6fa92cd99c5c30163 > 5%7C0%7C0%7C636751888819600237&sdata=rPKmWjR87ig5Q%2FFfTP > ZvXtPvLbqt6pZYkINKdhgVwE8%3D&reserved=0 | > Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 > | > Amtsgericht Hildesheim, HRA 2686 | Fax: > +49-5121-206917-5555 | ^ permalink raw reply [flat|nested] 21+ messages in thread
* [PATCH V2 2/4] arm64: dts: imx: add imx8qxp support 2018-10-15 9:03 ` A.s. Dong @ 2018-10-15 9:40 ` Sascha Hauer 2018-10-15 16:09 ` A.s. Dong 0 siblings, 1 reply; 21+ messages in thread From: Sascha Hauer @ 2018-10-15 9:40 UTC (permalink / raw) To: linux-arm-kernel On Mon, Oct 15, 2018 at 09:03:04AM +0000, A.s. Dong wrote: > > -----Original Message----- > > From: Sascha Hauer [mailto:s.hauer at pengutronix.de] > > Sent: Monday, October 15, 2018 4:28 PM > > To: A.s. Dong <aisheng.dong@nxp.com> > > Cc: linux-arm-kernel at lists.infradead.org; Mark Rutland > > <mark.rutland@arm.com>; dongas86 at gmail.com; devicetree at vger.kernel.org; > > catalin.marinas at arm.com; will.deacon at arm.com; robh+dt at kernel.org; > > dl-linux-imx <linux-imx@nxp.com>; kernel at pengutronix.de; Fabio Estevam > > <fabio.estevam@nxp.com>; shawnguo at kernel.org > > Subject: Re: [PATCH V2 2/4] arm64: dts: imx: add imx8qxp support > > > > On Mon, Oct 15, 2018 at 08:08:31AM +0000, A.s. Dong wrote: > > > > > + imx8qx-pm { > > > > > + compatible = "fsl,scu-pd"; > > > > > > > > I missed this earlier, but there should be a i.MX8qp specific > > > > compatible as the SCU API might change for future SoCs. > > > > > > > > > > We still do not see that requirement up till now. Not sure if it would > > > be possible in the future. I see low possibilities. > > > SCU IPC is designed to be generic to all MX8 SCU firmwares. > > > > And i.MX9? i.MX10? > > > > MX8DM MX8DXP I was not talking about existing SoCs, I was talking about future SoCs. > > > > Even it changes, SCU firmware version control may helps. > > > > It's not the first time that the position of the version field changes with a > > newer version. > > > > I understand your worry. > Up till now all SCU firmware based SoCs are all using one generic IPC driver internally. > And I have not heard a possible changing in the future. > I double checked the SCU firmware implementation that the IPC > Is deigned to be platform independent. So it's less to be changed. > So I wonder if this could be over worried. > Even it is changed, (quite less probility), we still can user version > To distinguish them, just like arm,scpi , arm,scmi. Right? You can still add and use a generic compatible, but does it hurt when you add a SoC specific one that you *can* use should you have to? > > > > > > > > > + compatible = "fsl,imx7ulp-lpuart"; > > > > > + compatible = "fsl,imx7ulp-lpi2c"; > > > > > + compatible = "fsl,imx7d-usdhc"; > > > > > > > > All these lack the most specific imx8qp compatible. > > > > > > > > > > Adding them requires binding doc update as well. > > > S I suppose they could be added later when the QXP specific features > > > are really supported by the drivers. > > > Do you think it's okay? > > > > Newer Kernels should work with older device trees, so once you roll out these > > compatibles it's too late already. > > > > The backwards compatible string is used to guarantee a basic function. > Even we add qxp specific compatible string later, it still can work with > backwards function. So I'm not quite get what the real problem is. > And this is the initial support that we don't expect the full features > with such an early device tree, right? By not adding a SoC compatible you lose the possibility to add a SoC specific fixup without changing the device tree or you have to work with quirks like: https://elixir.bootlin.com/linux/latest/source/drivers/clocksource/timer-imx-gpt.c#L521 or https://elixir.bootlin.com/linux/latest/source/drivers/spi/spi-imx.c#L1182 So far we have added new compatibles with each new SoC type for good reasons, so why should we change this? Sascha -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | ^ permalink raw reply [flat|nested] 21+ messages in thread
* [PATCH V2 2/4] arm64: dts: imx: add imx8qxp support 2018-10-15 9:40 ` Sascha Hauer @ 2018-10-15 16:09 ` A.s. Dong 2018-10-16 7:08 ` Sascha Hauer 0 siblings, 1 reply; 21+ messages in thread From: A.s. Dong @ 2018-10-15 16:09 UTC (permalink / raw) To: linux-arm-kernel > -----Original Message----- > From: Sascha Hauer [mailto:s.hauer at pengutronix.de] > Sent: Monday, October 15, 2018 5:41 PM > To: A.s. Dong <aisheng.dong@nxp.com> > Cc: linux-arm-kernel at lists.infradead.org; Mark Rutland > <mark.rutland@arm.com>; dongas86 at gmail.com; devicetree at vger.kernel.org; > catalin.marinas at arm.com; will.deacon at arm.com; robh+dt at kernel.org; > dl-linux-imx <linux-imx@nxp.com>; kernel at pengutronix.de; Fabio Estevam > <fabio.estevam@nxp.com>; shawnguo at kernel.org > Subject: Re: [PATCH V2 2/4] arm64: dts: imx: add imx8qxp support > > On Mon, Oct 15, 2018 at 09:03:04AM +0000, A.s. Dong wrote: > > > -----Original Message----- > > > From: Sascha Hauer [mailto:s.hauer at pengutronix.de] > > > Sent: Monday, October 15, 2018 4:28 PM > > > To: A.s. Dong <aisheng.dong@nxp.com> > > > Cc: linux-arm-kernel at lists.infradead.org; Mark Rutland > > > <mark.rutland@arm.com>; dongas86 at gmail.com; > > > devicetree at vger.kernel.org; catalin.marinas at arm.com; > > > will.deacon at arm.com; robh+dt at kernel.org; dl-linux-imx > > > <linux-imx@nxp.com>; kernel at pengutronix.de; Fabio Estevam > > > <fabio.estevam@nxp.com>; shawnguo at kernel.org > > > Subject: Re: [PATCH V2 2/4] arm64: dts: imx: add imx8qxp support > > > > > > On Mon, Oct 15, 2018 at 08:08:31AM +0000, A.s. Dong wrote: > > > > > > + imx8qx-pm { > > > > > > + compatible = "fsl,scu-pd"; > > > > > > > > > > I missed this earlier, but there should be a i.MX8qp specific > > > > > compatible as the SCU API might change for future SoCs. > > > > > > > > > > > > > We still do not see that requirement up till now. Not sure if it > > > > would be possible in the future. I see low possibilities. > > > > SCU IPC is designed to be generic to all MX8 SCU firmwares. > > > > > > And i.MX9? i.MX10? > > > > > > > MX8DM MX8DXP > > I was not talking about existing SoCs, I was talking about future SoCs. > > > > > > > Even it changes, SCU firmware version control may helps. > > > > > > It's not the first time that the position of the version field > > > changes with a newer version. > > > > > > > I understand your worry. > > Up till now all SCU firmware based SoCs are all using one generic IPC driver > internally. > > And I have not heard a possible changing in the future. > > I double checked the SCU firmware implementation that the IPC Is > > deigned to be platform independent. So it's less to be changed. > > So I wonder if this could be over worried. > > Even it is changed, (quite less probility), we still can user version > > To distinguish them, just like arm,scpi , arm,scmi. Right? > > You can still add and use a generic compatible, but does it hurt when you add > a SoC specific one that you *can* use should you have to? > Do you mean only change "fsl,scu-pd" to "fsl,imx8qxp-scu-pd"? And keep the "fsl,imx-scu" as it is, right? I guess I may be over-anxious, sorry for that if it's true. > > > > > > > > > > > > + compatible = "fsl,imx7ulp-lpuart"; > > > > > > + compatible = "fsl,imx7ulp-lpi2c"; > > > > > > + compatible = "fsl,imx7d-usdhc"; > > > > > > > > > > All these lack the most specific imx8qp compatible. > > > > > > > > > > > > > Adding them requires binding doc update as well. > > > > S I suppose they could be added later when the QXP specific > > > > features are really supported by the drivers. > > > > Do you think it's okay? > > > > > > Newer Kernels should work with older device trees, so once you roll > > > out these compatibles it's too late already. > > > > > > > The backwards compatible string is used to guarantee a basic function. > > Even we add qxp specific compatible string later, it still can work > > with backwards function. So I'm not quite get what the real problem is. > > And this is the initial support that we don't expect the full features > > with such an early device tree, right? > > By not adding a SoC compatible you lose the possibility to add a SoC specific > fixup without changing the device tree or you have to work with quirks like: > > https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Felixir. > bootlin.com%2Flinux%2Flatest%2Fsource%2Fdrivers%2Fclocksource%2Ftimer-i > mx-gpt.c%23L521&data=02%7C01%7Caisheng.dong%40nxp.com%7Ce0a > 58f79a6b24fd248c308d6328251f0%7C686ea1d3bc2b4c6fa92cd99c5c301635 > %7C0%7C0%7C636751932632219124&sdata=P9ncjvrhubRASh%2BOu7X > %2FNbAtch3aSqvqqSVLSdb%2BQ2c%3D&reserved=0 > > or > > https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Felixir. > bootlin.com%2Flinux%2Flatest%2Fsource%2Fdrivers%2Fspi%2Fspi-imx.c%23L1 > 182&data=02%7C01%7Caisheng.dong%40nxp.com%7Ce0a58f79a6b24fd > 248c308d6328251f0%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7 > C636751932632219124&sdata=blvN1%2FBbm7hZr7ddA7MAkIuqM5wk > 0%2Bv3DvifalAWV0w%3D&reserved=0 > > So far we have added new compatibles with each new SoC type for good > reasons, so why should we change this? > Yes, I fully understand. Just was wondering whether it can be done later. But I think there's no bad to do it right now. So I agree with it. Thanks for the suggestion. Regards Dong Aisheng > Sascha > > -- > Pengutronix e.K. | > | > Industrial Linux Solutions | > https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww. > pengutronix.de%2F&data=02%7C01%7Caisheng.dong%40nxp.com%7Ce0 > a58f79a6b24fd248c308d6328251f0%7C686ea1d3bc2b4c6fa92cd99c5c30163 > 5%7C0%7C0%7C636751932632219124&sdata=Qd1KhPokzveWzr%2BBo > HX%2F9jZSx3oiEkR47w4ABA1Deqg%3D&reserved=0 | > Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 > | > Amtsgericht Hildesheim, HRA 2686 | Fax: > +49-5121-206917-5555 | ^ permalink raw reply [flat|nested] 21+ messages in thread
* [PATCH V2 2/4] arm64: dts: imx: add imx8qxp support 2018-10-15 16:09 ` A.s. Dong @ 2018-10-16 7:08 ` Sascha Hauer 0 siblings, 0 replies; 21+ messages in thread From: Sascha Hauer @ 2018-10-16 7:08 UTC (permalink / raw) To: linux-arm-kernel On Mon, Oct 15, 2018 at 04:09:01PM +0000, A.s. Dong wrote: > > -----Original Message----- > > From: Sascha Hauer [mailto:s.hauer at pengutronix.de] > > Sent: Monday, October 15, 2018 5:41 PM > > To: A.s. Dong <aisheng.dong@nxp.com> > > Cc: linux-arm-kernel at lists.infradead.org; Mark Rutland > > <mark.rutland@arm.com>; dongas86 at gmail.com; devicetree at vger.kernel.org; > > catalin.marinas at arm.com; will.deacon at arm.com; robh+dt at kernel.org; > > dl-linux-imx <linux-imx@nxp.com>; kernel at pengutronix.de; Fabio Estevam > > <fabio.estevam@nxp.com>; shawnguo at kernel.org > > Subject: Re: [PATCH V2 2/4] arm64: dts: imx: add imx8qxp support > > > > On Mon, Oct 15, 2018 at 09:03:04AM +0000, A.s. Dong wrote: > > > > -----Original Message----- > > > > From: Sascha Hauer [mailto:s.hauer at pengutronix.de] > > > > Sent: Monday, October 15, 2018 4:28 PM > > > > To: A.s. Dong <aisheng.dong@nxp.com> > > > > Cc: linux-arm-kernel at lists.infradead.org; Mark Rutland > > > > <mark.rutland@arm.com>; dongas86 at gmail.com; > > > > devicetree at vger.kernel.org; catalin.marinas at arm.com; > > > > will.deacon at arm.com; robh+dt at kernel.org; dl-linux-imx > > > > <linux-imx@nxp.com>; kernel at pengutronix.de; Fabio Estevam > > > > <fabio.estevam@nxp.com>; shawnguo at kernel.org > > > > Subject: Re: [PATCH V2 2/4] arm64: dts: imx: add imx8qxp support > > > > > > > > On Mon, Oct 15, 2018 at 08:08:31AM +0000, A.s. Dong wrote: > > > > > > > + imx8qx-pm { > > > > > > > + compatible = "fsl,scu-pd"; > > > > > > > > > > > > I missed this earlier, but there should be a i.MX8qp specific > > > > > > compatible as the SCU API might change for future SoCs. > > > > > > > > > > > > > > > > We still do not see that requirement up till now. Not sure if it > > > > > would be possible in the future. I see low possibilities. > > > > > SCU IPC is designed to be generic to all MX8 SCU firmwares. > > > > > > > > And i.MX9? i.MX10? > > > > > > > > > > MX8DM MX8DXP > > > > I was not talking about existing SoCs, I was talking about future SoCs. > > > > > > > > > > Even it changes, SCU firmware version control may helps. > > > > > > > > It's not the first time that the position of the version field > > > > changes with a newer version. > > > > > > > > > > I understand your worry. > > > Up till now all SCU firmware based SoCs are all using one generic IPC driver > > internally. > > > And I have not heard a possible changing in the future. > > > I double checked the SCU firmware implementation that the IPC Is > > > deigned to be platform independent. So it's less to be changed. > > > So I wonder if this could be over worried. > > > Even it is changed, (quite less probility), we still can user version > > > To distinguish them, just like arm,scpi , arm,scmi. Right? > > > > You can still add and use a generic compatible, but does it hurt when you add > > a SoC specific one that you *can* use should you have to? > > > > Do you mean only change "fsl,scu-pd" to "fsl,imx8qxp-scu-pd"? > And keep the "fsl,imx-scu" as it is, right? Yes, that's what I meant. Sascha -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | ^ permalink raw reply [flat|nested] 21+ messages in thread
* [PATCH V2 3/4] arm64: dts: imx: add imx8qxp mek support 2018-10-14 14:34 [PATCH V2 0/4] arm64: imx: add imx8qxp support A.s. Dong 2018-10-14 14:34 ` [PATCH V2 1/4] " A.s. Dong 2018-10-14 14:34 ` [PATCH V2 2/4] arm64: dts: " A.s. Dong @ 2018-10-14 14:34 ` A.s. Dong 2018-10-15 7:01 ` Sascha Hauer 2018-10-14 14:35 ` [PATCH V2 4/4] defconfig: arm64: add imx8qxp support A.s. Dong 3 siblings, 1 reply; 21+ messages in thread From: A.s. Dong @ 2018-10-14 14:34 UTC (permalink / raw) To: linux-arm-kernel Add imx8qxp mek board support. Cc: Rob Herring <robh+dt@kernel.org> Cc: Mark Rutland <mark.rutland@arm.com> Cc: devicetree at vger.kernel.org Cc: Shawn Guo <shawnguo@kernel.org> Cc: Sascha Hauer <kernel@pengutronix.de> Cc: Fabio Estevam <fabio.estevam@nxp.com> Signed-off-by: Dong Aisheng <aisheng.dong@nxp.com> --- Documentation/devicetree/bindings/arm/fsl.txt | 4 + arch/arm64/boot/dts/freescale/Makefile | 1 + arch/arm64/boot/dts/freescale/imx8qxp-mek.dts | 134 ++++++++++++++++++++++++++ 3 files changed, 139 insertions(+) create mode 100644 arch/arm64/boot/dts/freescale/imx8qxp-mek.dts diff --git a/Documentation/devicetree/bindings/arm/fsl.txt b/Documentation/devicetree/bindings/arm/fsl.txt index baeb1fc..704472b 100644 --- a/Documentation/devicetree/bindings/arm/fsl.txt +++ b/Documentation/devicetree/bindings/arm/fsl.txt @@ -97,6 +97,10 @@ i.MX7 SabreSD Board Required root node properties: - compatible = "fsl,imx7d-sdb", "fsl,imx7d"; +i.MX8QXP MEK Board +Required root node properties: + - compatible = "fsl,imx8qxp-mek", "fsl,imx8qxp"; + Generic i.MX boards ------------------- diff --git a/arch/arm64/boot/dts/freescale/Makefile b/arch/arm64/boot/dts/freescale/Makefile index 86e18ad..cff87f3 100644 --- a/arch/arm64/boot/dts/freescale/Makefile +++ b/arch/arm64/boot/dts/freescale/Makefile @@ -13,3 +13,4 @@ dtb-$(CONFIG_ARCH_LAYERSCAPE) += fsl-ls2080a-rdb.dtb dtb-$(CONFIG_ARCH_LAYERSCAPE) += fsl-ls2080a-simu.dtb dtb-$(CONFIG_ARCH_LAYERSCAPE) += fsl-ls2088a-qds.dtb dtb-$(CONFIG_ARCH_LAYERSCAPE) += fsl-ls2088a-rdb.dtb +dtb-$(CONFIG_SOC_IMX8QXP) += imx8qxp-mek.dtb diff --git a/arch/arm64/boot/dts/freescale/imx8qxp-mek.dts b/arch/arm64/boot/dts/freescale/imx8qxp-mek.dts new file mode 100644 index 0000000..04e3a42 --- /dev/null +++ b/arch/arm64/boot/dts/freescale/imx8qxp-mek.dts @@ -0,0 +1,134 @@ +// SPDX-License-Identifier: GPL-2.0+ +/* + * Copyright 2017~2018 NXP + */ + +/dts-v1/; + +#include "imx8qxp.dtsi" + +/ { + model = "Freescale i.MX8QXP MEK"; + compatible = "fsl,imx8qxp-mek", "fsl,imx8qxp"; + + chosen { + stdout-path = &dma_lpuart0; + }; + + reg_usdhc2_vmmc: usdhc2-vmmc { + compatible = "regulator-fixed"; + regulator-name = "SD1_SPWR"; + regulator-min-microvolt = <3000000>; + regulator-max-microvolt = <3000000>; + gpio = <&lsio_gpio4 19 GPIO_ACTIVE_HIGH>; + enable-active-high; + }; +}; + +&dma_lpuart0 { + pinctrl-names = "default"; + pinctrl-0 = <&pinctrl_lpuart0>; + status = "okay"; +}; + +&fec1 { + pinctrl-names = "default"; + pinctrl-0 = <&pinctrl_fec1>; + phy-mode = "rgmii-id"; + phy-handle = <ðphy0>; + fsl,magic-packet; + status = "okay"; + + mdio { + #address-cells = <1>; + #size-cells = <0>; + + ethphy0: ethernet-phy at 0 { + compatible = "ethernet-phy-ieee802.3-c22"; + at803x,eee-disabled; + at803x,vddio-1p8v; + reg = <0>; + }; + + ethphy1: ethernet-phy at 1 { + compatible = "ethernet-phy-ieee802.3-c22"; + at803x,eee-disabled; + at803x,vddio-1p8v; + reg = <1>; + }; + }; +}; + +&usdhc1 { + pinctrl-names = "default"; + pinctrl-0 = <&pinctrl_usdhc1>; + bus-width = <8>; + non-removable; + status = "okay"; +}; + +&usdhc2 { + pinctrl-names = "default"; + pinctrl-0 = <&pinctrl_usdhc2>; + bus-width = <4>; + vmmc-supply = <®_usdhc2_vmmc>; + cd-gpios = <&lsio_gpio4 22 GPIO_ACTIVE_LOW>; + wp-gpios = <&lsio_gpio4 21 GPIO_ACTIVE_HIGH>; + status = "okay"; +}; + +&iomuxc { + pinctrl_fec1: fec1grp { + fsl,pins = < + SC_P_ENET0_MDC_CONN_ENET0_MDC 0x06000020 + SC_P_ENET0_MDIO_CONN_ENET0_MDIO 0x06000020 + SC_P_ENET0_RGMII_TX_CTL_CONN_ENET0_RGMII_TX_CTL 0x06000020 + SC_P_ENET0_RGMII_TXC_CONN_ENET0_RGMII_TXC 0x06000020 + SC_P_ENET0_RGMII_TXD0_CONN_ENET0_RGMII_TXD0 0x06000020 + SC_P_ENET0_RGMII_TXD1_CONN_ENET0_RGMII_TXD1 0x06000020 + SC_P_ENET0_RGMII_TXD2_CONN_ENET0_RGMII_TXD2 0x06000020 + SC_P_ENET0_RGMII_TXD3_CONN_ENET0_RGMII_TXD3 0x06000020 + SC_P_ENET0_RGMII_RXC_CONN_ENET0_RGMII_RXC 0x06000020 + SC_P_ENET0_RGMII_RX_CTL_CONN_ENET0_RGMII_RX_CTL 0x06000020 + SC_P_ENET0_RGMII_RXD0_CONN_ENET0_RGMII_RXD0 0x06000020 + SC_P_ENET0_RGMII_RXD1_CONN_ENET0_RGMII_RXD1 0x06000020 + SC_P_ENET0_RGMII_RXD2_CONN_ENET0_RGMII_RXD2 0x06000020 + SC_P_ENET0_RGMII_RXD3_CONN_ENET0_RGMII_RXD3 0x06000020 + >; + }; + + pinctrl_lpuart0: lpuart0grp { + fsl,pins = < + SC_P_UART0_RX_ADMA_UART0_RX 0x06000020 + SC_P_UART0_TX_ADMA_UART0_TX 0x06000020 + >; + }; + + pinctrl_usdhc1: usdhc1grp { + fsl,pins = < + SC_P_EMMC0_CLK_CONN_EMMC0_CLK 0x06000041 + SC_P_EMMC0_CMD_CONN_EMMC0_CMD 0x00000021 + SC_P_EMMC0_DATA0_CONN_EMMC0_DATA0 0x00000021 + SC_P_EMMC0_DATA1_CONN_EMMC0_DATA1 0x00000021 + SC_P_EMMC0_DATA2_CONN_EMMC0_DATA2 0x00000021 + SC_P_EMMC0_DATA3_CONN_EMMC0_DATA3 0x00000021 + SC_P_EMMC0_DATA4_CONN_EMMC0_DATA4 0x00000021 + SC_P_EMMC0_DATA5_CONN_EMMC0_DATA5 0x00000021 + SC_P_EMMC0_DATA6_CONN_EMMC0_DATA6 0x00000021 + SC_P_EMMC0_DATA7_CONN_EMMC0_DATA7 0x00000021 + SC_P_EMMC0_STROBE_CONN_EMMC0_STROBE 0x00000041 + >; + }; + + pinctrl_usdhc2: usdhc2grp { + fsl,pins = < + SC_P_USDHC1_CLK_CONN_USDHC1_CLK 0x06000041 + SC_P_USDHC1_CMD_CONN_USDHC1_CMD 0x00000021 + SC_P_USDHC1_DATA0_CONN_USDHC1_DATA0 0x00000021 + SC_P_USDHC1_DATA1_CONN_USDHC1_DATA1 0x00000021 + SC_P_USDHC1_DATA2_CONN_USDHC1_DATA2 0x00000021 + SC_P_USDHC1_DATA3_CONN_USDHC1_DATA3 0x00000021 + SC_P_USDHC1_VSELECT_CONN_USDHC1_VSELECT 0x00000021 + >; + }; +}; -- 2.7.4 ^ permalink raw reply related [flat|nested] 21+ messages in thread
* [PATCH V2 3/4] arm64: dts: imx: add imx8qxp mek support 2018-10-14 14:34 ` [PATCH V2 3/4] arm64: dts: imx: add imx8qxp mek support A.s. Dong @ 2018-10-15 7:01 ` Sascha Hauer 2018-10-15 8:40 ` A.s. Dong 0 siblings, 1 reply; 21+ messages in thread From: Sascha Hauer @ 2018-10-15 7:01 UTC (permalink / raw) To: linux-arm-kernel On Sun, Oct 14, 2018 at 02:34:56PM +0000, A.s. Dong wrote: > Add imx8qxp mek board support. > > Cc: Rob Herring <robh+dt@kernel.org> > Cc: Mark Rutland <mark.rutland@arm.com> > Cc: devicetree at vger.kernel.org > Cc: Shawn Guo <shawnguo@kernel.org> > Cc: Sascha Hauer <kernel@pengutronix.de> > Cc: Fabio Estevam <fabio.estevam@nxp.com> > Signed-off-by: Dong Aisheng <aisheng.dong@nxp.com> > --- > Documentation/devicetree/bindings/arm/fsl.txt | 4 + > arch/arm64/boot/dts/freescale/Makefile | 1 + > arch/arm64/boot/dts/freescale/imx8qxp-mek.dts | 134 ++++++++++++++++++++++++++ > 3 files changed, 139 insertions(+) > create mode 100644 arch/arm64/boot/dts/freescale/imx8qxp-mek.dts > > +&iomuxc { > + pinctrl_fec1: fec1grp { > + fsl,pins = < > + SC_P_ENET0_MDC_CONN_ENET0_MDC 0x06000020 > + SC_P_ENET0_MDIO_CONN_ENET0_MDIO 0x06000020 > + SC_P_ENET0_RGMII_TX_CTL_CONN_ENET0_RGMII_TX_CTL 0x06000020 > + SC_P_ENET0_RGMII_TXC_CONN_ENET0_RGMII_TXC 0x06000020 > + SC_P_ENET0_RGMII_TXD0_CONN_ENET0_RGMII_TXD0 0x06000020 > + SC_P_ENET0_RGMII_TXD1_CONN_ENET0_RGMII_TXD1 0x06000020 > + SC_P_ENET0_RGMII_TXD2_CONN_ENET0_RGMII_TXD2 0x06000020 > + SC_P_ENET0_RGMII_TXD3_CONN_ENET0_RGMII_TXD3 0x06000020 > + SC_P_ENET0_RGMII_RXC_CONN_ENET0_RGMII_RXC 0x06000020 > + SC_P_ENET0_RGMII_RX_CTL_CONN_ENET0_RGMII_RX_CTL 0x06000020 > + SC_P_ENET0_RGMII_RXD0_CONN_ENET0_RGMII_RXD0 0x06000020 > + SC_P_ENET0_RGMII_RXD1_CONN_ENET0_RGMII_RXD1 0x06000020 > + SC_P_ENET0_RGMII_RXD2_CONN_ENET0_RGMII_RXD2 0x06000020 > + SC_P_ENET0_RGMII_RXD3_CONN_ENET0_RGMII_RXD3 0x06000020 I doubt these names will be valid for future SoCs. They should have a IMX8QP_ prefix. -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | ^ permalink raw reply [flat|nested] 21+ messages in thread
* [PATCH V2 3/4] arm64: dts: imx: add imx8qxp mek support 2018-10-15 7:01 ` Sascha Hauer @ 2018-10-15 8:40 ` A.s. Dong 0 siblings, 0 replies; 21+ messages in thread From: A.s. Dong @ 2018-10-15 8:40 UTC (permalink / raw) To: linux-arm-kernel > -----Original Message----- > From: Sascha Hauer [mailto:s.hauer at pengutronix.de] > Sent: Monday, October 15, 2018 3:02 PM > To: A.s. Dong <aisheng.dong@nxp.com> > Cc: linux-arm-kernel at lists.infradead.org; dongas86 at gmail.com; > kernel at pengutronix.de; shawnguo at kernel.org; Fabio Estevam > <fabio.estevam@nxp.com>; robh+dt at kernel.org; catalin.marinas at arm.com; > will.deacon at arm.com; dl-linux-imx <linux-imx@nxp.com>; Mark Rutland > <mark.rutland@arm.com>; devicetree at vger.kernel.org > Subject: Re: [PATCH V2 3/4] arm64: dts: imx: add imx8qxp mek support > > On Sun, Oct 14, 2018 at 02:34:56PM +0000, A.s. Dong wrote: > > Add imx8qxp mek board support. > > > > Cc: Rob Herring <robh+dt@kernel.org> > > Cc: Mark Rutland <mark.rutland@arm.com> > > Cc: devicetree at vger.kernel.org > > Cc: Shawn Guo <shawnguo@kernel.org> > > Cc: Sascha Hauer <kernel@pengutronix.de> > > Cc: Fabio Estevam <fabio.estevam@nxp.com> > > Signed-off-by: Dong Aisheng <aisheng.dong@nxp.com> > > --- > > Documentation/devicetree/bindings/arm/fsl.txt | 4 + > > arch/arm64/boot/dts/freescale/Makefile | 1 + > > arch/arm64/boot/dts/freescale/imx8qxp-mek.dts | 134 > > ++++++++++++++++++++++++++ > > 3 files changed, 139 insertions(+) > > create mode 100644 arch/arm64/boot/dts/freescale/imx8qxp-mek.dts > > > > +&iomuxc { > > + pinctrl_fec1: fec1grp { > > + fsl,pins = < > > + SC_P_ENET0_MDC_CONN_ENET0_MDC > 0x06000020 > > + SC_P_ENET0_MDIO_CONN_ENET0_MDIO > 0x06000020 > > + SC_P_ENET0_RGMII_TX_CTL_CONN_ENET0_RGMII_TX_CTL > 0x06000020 > > + SC_P_ENET0_RGMII_TXC_CONN_ENET0_RGMII_TXC > 0x06000020 > > + SC_P_ENET0_RGMII_TXD0_CONN_ENET0_RGMII_TXD0 > 0x06000020 > > + SC_P_ENET0_RGMII_TXD1_CONN_ENET0_RGMII_TXD1 > 0x06000020 > > + SC_P_ENET0_RGMII_TXD2_CONN_ENET0_RGMII_TXD2 > 0x06000020 > > + SC_P_ENET0_RGMII_TXD3_CONN_ENET0_RGMII_TXD3 > 0x06000020 > > + SC_P_ENET0_RGMII_RXC_CONN_ENET0_RGMII_RXC > 0x06000020 > > + SC_P_ENET0_RGMII_RX_CTL_CONN_ENET0_RGMII_RX_CTL > 0x06000020 > > + SC_P_ENET0_RGMII_RXD0_CONN_ENET0_RGMII_RXD0 > 0x06000020 > > + SC_P_ENET0_RGMII_RXD1_CONN_ENET0_RGMII_RXD1 > 0x06000020 > > + SC_P_ENET0_RGMII_RXD2_CONN_ENET0_RGMII_RXD2 > 0x06000020 > > + SC_P_ENET0_RGMII_RXD3_CONN_ENET0_RGMII_RXD3 > 0x06000020 > > I doubt these names will be valid for future SoCs. They should have a IMX8QP_ > prefix. > I agree, will change them. Thanks for the suggestion. Regards Dong Aisheng > -- > Pengutronix e.K. | > | > Industrial Linux Solutions | > https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww. > pengutronix.de%2F&data=02%7C01%7Caisheng.dong%40nxp.com%7C86 > a3443c48ed4c7cd65008d6326c13b0%7C686ea1d3bc2b4c6fa92cd99c5c3016 > 35%7C0%7C0%7C636751837102721123&sdata=GBMxEXHoTYdhOl3ir9U > bwZDsVxDAlefbq74tkuZGalk%3D&reserved=0 | > Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 > | > Amtsgericht Hildesheim, HRA 2686 | Fax: > +49-5121-206917-5555 | ^ permalink raw reply [flat|nested] 21+ messages in thread
* [PATCH V2 4/4] defconfig: arm64: add imx8qxp support 2018-10-14 14:34 [PATCH V2 0/4] arm64: imx: add imx8qxp support A.s. Dong ` (2 preceding siblings ...) 2018-10-14 14:34 ` [PATCH V2 3/4] arm64: dts: imx: add imx8qxp mek support A.s. Dong @ 2018-10-14 14:35 ` A.s. Dong 3 siblings, 0 replies; 21+ messages in thread From: A.s. Dong @ 2018-10-14 14:35 UTC (permalink / raw) To: linux-arm-kernel Cc: Catalin Marinas <catalin.marinas@arm.com> Cc: Will Deacon <will.deacon@arm.com> Cc: Shawn Guo <shawnguo@kernel.org> Cc: Sascha Hauer <kernel@pengutronix.de> Cc: Fabio Estevam <fabio.estevam@nxp.com> Signed-off-by: Dong Aisheng <aisheng.dong@nxp.com> --- arch/arm64/configs/defconfig | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig index db8d364..7e07505 100644 --- a/arch/arm64/configs/defconfig +++ b/arch/arm64/configs/defconfig @@ -45,6 +45,8 @@ CONFIG_ARCH_HISI=y CONFIG_ARCH_MEDIATEK=y CONFIG_ARCH_MESON=y CONFIG_ARCH_MVEBU=y +CONFIG_ARCH_MXC=y +CONFIG_SOC_IMX8QXP=y CONFIG_ARCH_QCOM=y CONFIG_ARCH_ROCKCHIP=y CONFIG_ARCH_SEATTLE=y @@ -219,6 +221,7 @@ CONFIG_NET_XGENE=y CONFIG_ATL1C=m CONFIG_MACB=y CONFIG_THUNDER_NIC_PF=y +CONFIG_FEC=y CONFIG_HIX5HD2_GMAC=y CONFIG_HNS_DSAF=y CONFIG_HNS_ENET=y @@ -294,6 +297,8 @@ CONFIG_SERIAL_MSM=y CONFIG_SERIAL_MSM_CONSOLE=y CONFIG_SERIAL_XILINX_PS_UART=y CONFIG_SERIAL_XILINX_PS_UART_CONSOLE=y +CONFIG_SERIAL_FSL_LPUART=y +CONFIG_SERIAL_FSL_LPUART_CONSOLE=y CONFIG_SERIAL_MVEBU_UART=y CONFIG_SERIAL_DEV_BUS=y CONFIG_VIRTIO_CONSOLE=y @@ -514,6 +519,7 @@ CONFIG_MMC_SDHCI_PLTFM=y CONFIG_MMC_SDHCI_OF_ARASAN=y CONFIG_MMC_SDHCI_OF_ESDHC=y CONFIG_MMC_SDHCI_CADENCE=y +CONFIG_MMC_SDHCI_ESDHC_IMX=y CONFIG_MMC_SDHCI_TEGRA=y CONFIG_MMC_SDHCI_F_SDH30=y CONFIG_MMC_MESON_GX=y -- 2.7.4 ^ permalink raw reply related [flat|nested] 21+ messages in thread
end of thread, other threads:[~2018-10-18 2:32 UTC | newest] Thread overview: 21+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2018-10-14 14:34 [PATCH V2 0/4] arm64: imx: add imx8qxp support A.s. Dong 2018-10-14 14:34 ` [PATCH V2 1/4] " A.s. Dong 2018-10-14 14:34 ` [PATCH V2 2/4] arm64: dts: " A.s. Dong 2018-10-14 23:13 ` Fabio Estevam 2018-10-15 6:27 ` Daniel Baluta 2018-10-15 7:30 ` Leonard Crestez 2018-10-15 9:29 ` A.s. Dong 2018-10-15 7:57 ` A.s. Dong 2018-10-18 0:51 ` Rob Herring 2018-10-18 2:32 ` A.s. Dong 2018-10-15 6:58 ` Sascha Hauer 2018-10-15 8:08 ` A.s. Dong 2018-10-15 8:27 ` Sascha Hauer 2018-10-15 9:03 ` A.s. Dong 2018-10-15 9:40 ` Sascha Hauer 2018-10-15 16:09 ` A.s. Dong 2018-10-16 7:08 ` Sascha Hauer 2018-10-14 14:34 ` [PATCH V2 3/4] arm64: dts: imx: add imx8qxp mek support A.s. Dong 2018-10-15 7:01 ` Sascha Hauer 2018-10-15 8:40 ` A.s. Dong 2018-10-14 14:35 ` [PATCH V2 4/4] defconfig: arm64: add imx8qxp support A.s. Dong
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).