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-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Peng Fan <peng.fan@nxp.com>
Subject: [PATCH 0/5] arm64: dts: imx93: add nodes and minor update
Date: Wed, 10 May 2023 16:31:48 +0800 [thread overview]
Message-ID: <20230510083153.3769140-1-peng.fan@oss.nxp.com> (raw)
From: Peng Fan <peng.fan@nxp.com>
Add watchdog/ocotp/cpuidle for i.MX93
Reorder nodes
Enable WDOG3 for i.MX93-11x11-EVK
The OCOTP yaml has got reviewed by DT maitainers:
https://lore.kernel.org/all/01be24b3-aaf2-e27b-d00e-f8649a497463@linaro.org/
Peng Fan (5):
arm64: dts: imx93: add watchdog node
arm64: dts: imx93: add ocotp node
arm64: dts: imx93: reorder device nodes
arm64: dts: imx93: add cpuidle node
arm64: dts: imx93-11x11-evk: enable wdog3
.../boot/dts/freescale/imx93-11x11-evk.dts | 4 +
arch/arm64/boot/dts/freescale/imx93.dtsi | 128 ++++++++++++++----
2 files changed, 102 insertions(+), 30 deletions(-)
--
2.37.1
next reply other threads:[~2023-05-10 8:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 8:31 Peng Fan (OSS) [this message]
2023-05-10 8:31 ` [PATCH 1/5] arm64: dts: imx93: add watchdog node Peng Fan (OSS)
2023-05-10 8:31 ` [PATCH 2/5] arm64: dts: imx93: add ocotp node Peng Fan (OSS)
2023-05-10 8:31 ` [PATCH 3/5] arm64: dts: imx93: reorder device nodes Peng Fan (OSS)
2023-05-10 8:31 ` [PATCH 4/5] arm64: dts: imx93: add cpuidle node Peng Fan (OSS)
2023-05-10 8:31 ` [PATCH 5/5] arm64: dts: imx93-11x11-evk: enable wdog3 Peng Fan (OSS)
2023-05-15 3:23 ` [PATCH 0/5] arm64: dts: imx93: add nodes and minor update Shawn Guo
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=20230510083153.3769140-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
all inboxes | Powered by JetHome®