From: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
Peng Fan <peng.fan@nxp.com>,
Conor Dooley <conor.dooley@microchip.com>
Subject: [PATCH v3 0/3] arm64: dts: add i.MX95 and EVK board
Date: Sun, 28 Apr 2024 20:22:18 +0800 [thread overview]
Message-ID: <20240428-imx95-dts-v3-v3-0-765395f88b9f@nxp.com> (raw)
Add a minimal i.MX95 dtsi and EVK board dts.
i.MX95 has a M33 running SCMI firmware, but as of now, the scmi pinctrl
driver still not ready for i.MX95, so we count on bootloader to
configure the pinctrl for lpuart and sdhc and it boots well. After pinctrl
driver ready, we could move to use scmi pinctrl.
Signed-off-by: Peng Fan <peng.fan@nxp.com>
---
Changes in v3:
- Drop irqsteer node because binding not accepted
- Pass dtbs_check
- Link to v2: https://lore.kernel.org/r/20240226-imx95-dts-v2-0-00e36637b07e@nxp.com
Changes in v2:
- Addressed Rob and Krzysztof's comments, and fix dts_check issue
To pass the dtbs_check, need apply:
https://lore.kernel.org/all/20240226070910.3379108-1-peng.fan@oss.nxp.com/
https://lore.kernel.org/all/20240226130243.3820915-1-peng.fan@oss.nxp.com/
https://lore.kernel.org/all/20240226130516.3821803-1-peng.fan@oss.nxp.com/
https://lore.kernel.org/all/20240226130826.3824251-1-peng.fan@oss.nxp.com/
https://lore.kernel.org/all/20240219-imx-mailbox-v8-1-75535a87794e@nxp.com/
- Link to v1: https://lore.kernel.org/r/20240218-imx95-dts-v1-0-2959f89f2018@nxp.com
---
Peng Fan (3):
dt-bindings: arm: fsl: add i.MX95 19x19 EVK board
arm64: dts: freescale: add i.MX95 basic dtsi
arm64: dts: freescale: add i.MX95 19x19 EVK minimal board dts
Documentation/devicetree/bindings/arm/fsl.yaml | 6 +
arch/arm64/boot/dts/freescale/Makefile | 1 +
arch/arm64/boot/dts/freescale/imx95-19x19-evk.dts | 111 ++
arch/arm64/boot/dts/freescale/imx95-clock.h | 187 ++++
arch/arm64/boot/dts/freescale/imx95-power.h | 55 +
arch/arm64/boot/dts/freescale/imx95.dtsi | 1152 +++++++++++++++++++++
6 files changed, 1512 insertions(+)
---
base-commit: bb7a2467e6beef44a80a17d45ebf2931e7631083
change-id: 20240428-imx95-dts-v3-bee59f0e559b
Best regards,
--
Peng Fan <peng.fan@nxp.com>
next reply other threads:[~2024-04-28 12:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-28 12:22 Peng Fan (OSS) [this message]
2024-04-28 12:22 ` [PATCH v3 1/3] dt-bindings: arm: fsl: add i.MX95 19x19 EVK board Peng Fan (OSS)
2024-04-28 12:22 ` [PATCH v3 2/3] arm64: dts: freescale: add i.MX95 basic dtsi Peng Fan (OSS)
2024-04-29 7:57 ` Alexander Stein
2024-05-03 0:15 ` Peng Fan
2024-04-28 12:22 ` [PATCH v3 3/3] arm64: dts: freescale: add i.MX95 19x19 EVK minimal board dts Peng Fan (OSS)
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=20240428-imx95-dts-v3-v3-0-765395f88b9f@nxp.com \
--to=peng.fan@oss.nxp.com \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).