From: Yashwanth Varakala <y.varakala@phytec.de>
To: <shawnguo@kernel.org>, <s.hauer@pengutronix.de>,
<kernel@pengutronix.de>, <festevam@gmail.com>, <robh@kernel.org>,
<krzk+dt@kernel.org>, <conor+dt@kernel.org>
Cc: <imx@lists.linux.dev>, <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<upstream@lists.phytec.de>, <y.varakala@phytec.de>
Subject: [PATCH 0/3] arm64: dts: freescale: imx8mp-phycore: Add devicetree overlays
Date: Thu, 25 Jul 2024 11:44:54 +0200 [thread overview]
Message-ID: <20240725094457.37739-1-y.varakala@phytec.de> (raw)
Adding overlays for the phyboard imx8mp and updating them in
the Makefile.
Yashwanth Varakala (3):
arm64: dts: freescale: imx8mp-phycore: Add no-rtc overlay
arm64: boot: dts: freescale: Add no-spiflash overlay
arm64: dts: Add phyBOARD-Pollux dts for rpmsg
arch/arm64/boot/dts/freescale/Makefile | 6 ++
.../dts/freescale/imx8mp-phycore-no-rtc.dtso | 12 ++++
.../freescale/imx8mp-phycore-no-spiflash.dtso | 16 ++++++
.../dts/freescale/imx8mp-phycore-rpmsg.dtso | 57 +++++++++++++++++++
4 files changed, 91 insertions(+)
create mode 100644 arch/arm64/boot/dts/freescale/imx8mp-phycore-no-rtc.dtso
create mode 100644 arch/arm64/boot/dts/freescale/imx8mp-phycore-no-spiflash.dtso
create mode 100644 arch/arm64/boot/dts/freescale/imx8mp-phycore-rpmsg.dtso
--
2.34.1
next reply other threads:[~2024-07-25 9:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-25 9:44 Yashwanth Varakala [this message]
2024-07-25 9:44 ` [PATCH 1/3] arm64: dts: freescale: imx8mp-phycore: Add no-rtc overlay Yashwanth Varakala
2024-07-25 9:44 ` [PATCH 2/3] arm64: boot: dts: freescale: Add no-spiflash overlay Yashwanth Varakala
2024-07-25 9:44 ` [PATCH 3/3] arm64: dts: Add phyBOARD-Pollux dts for rpmsg Yashwanth Varakala
2024-07-26 9:19 ` Krzysztof Kozlowski
2024-08-01 2:27 ` Peng Fan
2024-08-07 10:34 ` Yashwanth Varakala
2024-08-08 3:13 ` Peng Fan
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=20240725094457.37739-1-y.varakala@phytec.de \
--to=y.varakala@phytec.de \
--cc=conor+dt@kernel.org \
--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=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=upstream@lists.phytec.de \
/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®