From: Jacky Bai <ping.bai@nxp.com>
To: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
shawnguo@kernel.org, s.hauer@pengutronix.de
Cc: kernel@pengutronix.de, festevam@gmail.com,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org, aisheng.dong@nxp.com,
peng.fan@nxp.com, frank.li@nxp.com
Subject: [PATCH v2 0/4] Add i.MX943 basic dts support
Date: Tue, 4 Mar 2025 17:31:23 +0800 [thread overview]
Message-ID: <20250304093127.1954549-1-ping.bai@nxp.com> (raw)
i.MX943 is the first SoC of the i.MX94 family, all the SoCs
of this family are pin to pin compatible with only several
peripherals differance.
For i.MX943 device tree support, we split the dtsi into two
part, one for the common dtsi that shared for the i.MX94 family,
and an i.MX943 specific part.
Jacky Bai (4):
dt-bindings: dma: fsl-edma: add interrupts-extended property
dt-bindings: arm: fsl: add i.MX943 EVK board
arm64: dts: freescale: Add basic dtsi for imx943
arm64: dts: freescale: Add minimal dts support for imx943 evk
.../devicetree/bindings/arm/fsl.yaml | 6 +
.../devicetree/bindings/dma/fsl,edma.yaml | 11 +-
arch/arm64/boot/dts/freescale/Makefile | 1 +
arch/arm64/boot/dts/freescale/imx94-clock.h | 195 +++
arch/arm64/boot/dts/freescale/imx94-pinfunc.h | 1542 +++++++++++++++++
arch/arm64/boot/dts/freescale/imx94-power.h | 41 +
arch/arm64/boot/dts/freescale/imx94.dtsi | 1141 ++++++++++++
arch/arm64/boot/dts/freescale/imx943-evk.dts | 196 +++
arch/arm64/boot/dts/freescale/imx943.dtsi | 148 ++
9 files changed, 3280 insertions(+), 1 deletion(-)
create mode 100644 arch/arm64/boot/dts/freescale/imx94-clock.h
create mode 100644 arch/arm64/boot/dts/freescale/imx94-pinfunc.h
create mode 100644 arch/arm64/boot/dts/freescale/imx94-power.h
create mode 100644 arch/arm64/boot/dts/freescale/imx94.dtsi
create mode 100644 arch/arm64/boot/dts/freescale/imx943-evk.dts
create mode 100644 arch/arm64/boot/dts/freescale/imx943.dtsi
--
2.34.1
next reply other threads:[~2025-03-04 9:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 9:31 Jacky Bai [this message]
2025-03-04 9:31 ` [PATCH v2 1/4] dt-bindings: dma: fsl-edma: add interrupts-extended property Jacky Bai
2025-03-04 10:57 ` Rob Herring (Arm)
2025-03-04 13:13 ` Rob Herring
2025-03-04 14:40 ` Jacky Bai
2025-03-04 14:50 ` Krzysztof Kozlowski
2025-03-04 14:53 ` Rob Herring
2025-03-04 15:38 ` Jacky Bai
2025-03-04 15:26 ` Frank Li
2025-03-04 15:41 ` Jacky Bai
2025-03-04 9:31 ` [PATCH v2 2/4] dt-bindings: arm: fsl: add i.MX943 EVK board Jacky Bai
2025-03-04 14:55 ` Krzysztof Kozlowski
2025-03-04 9:31 ` [PATCH v2 3/4] arm64: dts: freescale: Add basic dtsi for imx943 Jacky Bai
2025-03-04 14:54 ` Krzysztof Kozlowski
2025-03-04 15:16 ` Jacky Bai
2025-03-05 1:22 ` Jacky Bai
2025-03-04 15:30 ` Frank Li
2025-03-05 0:33 ` Jacky Bai
2025-03-04 15:35 ` Frank Li
2025-03-05 0:34 ` Jacky Bai
2025-03-04 9:31 ` [PATCH v2 4/4] arm64: dts: freescale: Add minimal dts support for imx943 evk Jacky Bai
2025-03-04 15:27 ` Frank Li
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250304093127.1954549-1-ping.bai@nxp.com \
--to=ping.bai@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=frank.li@nxp.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=peng.fan@nxp.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox