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,
aisheng.dong@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 V2 0/6] arm64: dts: imx8ulp: several updates
Date: Wed, 31 Aug 2022 22:25:46 +0800 [thread overview]
Message-ID: <20220831142552.43393-1-peng.fan@oss.nxp.com> (raw)
From: Peng Fan <peng.fan@nxp.com>
V2:
Drop 'status = "okay"' and blank line in patch 5
Update cgc/sram/pcc node to match binding doc
Add pmu/mailbox node
Increase lpspi clock
Clark Wang (1):
arm64: dts: imx8ulp: increase the clock speed of LPSPI
Peng Fan (5):
arm64: dts: imx8ulp: drop undocumented property in cgc
arm64: dts: imx8ulp: correct the scmi sram node name
arm64: dts: imx8ulp: add #reset-cells for pcc
arm64: dts: imx8ulp: add pmu node
arm64: dts: imx8ulp: add mailbox node
arch/arm64/boot/dts/freescale/imx8ulp.dtsi | 57 +++++++++++++++++-----
1 file changed, 44 insertions(+), 13 deletions(-)
--
2.37.1
next reply other threads:[~2022-08-31 14:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 14:25 Peng Fan (OSS) [this message]
2022-08-31 14:25 ` [PATCH V2 1/6] arm64: dts: imx8ulp: drop undocumented property in cgc Peng Fan (OSS)
2022-08-31 14:25 ` [PATCH V2 2/6] arm64: dts: imx8ulp: correct the scmi sram node name Peng Fan (OSS)
2022-09-05 3:20 ` Shawn Guo
2022-09-05 3:32 ` Peng Fan
2022-08-31 14:25 ` [PATCH V2 3/6] arm64: dts: imx8ulp: add #reset-cells for pcc Peng Fan (OSS)
2022-08-31 14:25 ` [PATCH V2 4/6] arm64: dts: imx8ulp: add pmu node Peng Fan (OSS)
2022-08-31 14:25 ` [PATCH V2 5/6] arm64: dts: imx8ulp: add mailbox node Peng Fan (OSS)
2022-08-31 14:25 ` [PATCH V2 6/6] arm64: dts: imx8ulp: increase the clock speed of LPSPI Peng Fan (OSS)
2022-09-05 3:39 ` [PATCH V2 0/6] arm64: dts: imx8ulp: several updates 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=20220831142552.43393-1-peng.fan@oss.nxp.com \
--to=peng.fan@oss.nxp.com \
--cc=aisheng.dong@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).