From: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
To: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
shawnguo@kernel.org, s.hauer@pengutronix.de
Cc: kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, Peng Fan <peng.fan@nxp.com>
Subject: [PATCH 0/3] arm64: add i.MX93 support
Date: Mon, 25 Apr 2022 19:03:27 +0800 [thread overview]
Message-ID: <20220425110330.1630984-1-peng.fan@oss.nxp.com> (raw)
From: Peng Fan <peng.fan@nxp.com>
Add i.MX93 dtsi and 11x11 evk board support
The required bindings and drivers has already been in tree.
There arem checkpatch error for the pin header files as other i.MX pin
pin header files.
Peng Fan (3):
arm64: dts: freescale: Add i.MX93 dtsi support
arm64: dts: freescale: add i.MX93 11x11 EVK basic support
arm64: defconfig: enable i.MX93 clk & pinctrl
arch/arm64/boot/dts/freescale/Makefile | 1 +
.../boot/dts/freescale/imx93-11x11-evk.dts | 130 ++++
arch/arm64/boot/dts/freescale/imx93-pinfunc.h | 623 ++++++++++++++++++
arch/arm64/boot/dts/freescale/imx93.dtsi | 337 ++++++++++
arch/arm64/configs/defconfig | 2 +
5 files changed, 1093 insertions(+)
create mode 100644 arch/arm64/boot/dts/freescale/imx93-11x11-evk.dts
create mode 100755 arch/arm64/boot/dts/freescale/imx93-pinfunc.h
create mode 100644 arch/arm64/boot/dts/freescale/imx93.dtsi
--
2.25.1
next reply other threads:[~2022-04-25 11:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 11:03 Peng Fan (OSS) [this message]
2022-04-25 11:03 ` [PATCH 1/3] arm64: dts: freescale: Add i.MX93 dtsi support Peng Fan (OSS)
2022-05-02 23:02 ` Rob Herring
2022-04-25 11:03 ` [PATCH 2/3] arm64: dts: freescale: add i.MX93 11x11 EVK basic support Peng Fan (OSS)
2022-06-05 20:39 ` Tommaso Merciai
2022-06-05 20:53 ` Tommaso Merciai
2022-04-25 11:03 ` [PATCH 3/3] arm64: defconfig: enable i.MX93 clk & pinctrl Peng Fan (OSS)
2022-06-05 19:52 ` Tommaso Merciai
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=20220425110330.1630984-1-peng.fan@oss.nxp.com \
--to=peng.fan@oss.nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=robh+dt@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 NNTP newsgroup(s).