From: Nishanth Menon <nm@ti.com>
To: Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>, Vignesh <vigneshr@ti.com>
Cc: <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Tero Kristo <kristo@kernel.org>, Nishanth Menon <nm@ti.com>,
Tom Rini <trini@konsulko.com>, Bryan <bb@ti.com>,
Praneeth <praneeth@ti.com>,
Robert Nelson <robertcnelson@gmail.com>
Subject: [PATCH 0/3] arm64: dts: ti: k3-am625: Add boot phase marking
Date: Mon, 11 Sep 2023 11:25:32 -0500 [thread overview]
Message-ID: <20230911162535.1044560-1-nm@ti.com> (raw)
bootph-all as phase tag was added to dt-schema
(dtschema/schemas/bootph.yaml) to describe various node usage during
boot phases with DT.
Based on next-20230911
Nishanth Menon (3):
arm64: dts: ti: k3-am625: Add boot phase tags marking
arm64: dts: ti: k3-am625-beagleplay: Add boot phase tags marking
arm64: dts: ti: k3-am625-sk: Add boot phase tags marking
arch/arm64/boot/dts/ti/k3-am62-main.dtsi | 10 +++++++
arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi | 2 ++
arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi | 2 ++
arch/arm64/boot/dts/ti/k3-am62.dtsi | 3 +++
.../arm64/boot/dts/ti/k3-am625-beagleplay.dts | 26 ++++++++++++++++++
arch/arm64/boot/dts/ti/k3-am625-sk.dts | 27 +++++++++++++++++++
.../arm64/boot/dts/ti/k3-am62x-sk-common.dtsi | 16 +++++++++++
7 files changed, 86 insertions(+)
--
2.40.0
next reply other threads:[~2023-09-11 22:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 16:25 Nishanth Menon [this message]
2023-09-11 16:25 ` [PATCH 1/3] arm64: dts: ti: k3-am625: Add boot phase tags marking Nishanth Menon
2023-09-11 16:25 ` [PATCH 2/3] arm64: dts: ti: k3-am625-beagleplay: " Nishanth Menon
2023-09-11 16:25 ` [PATCH 3/3] arm64: dts: ti: k3-am625-sk: " Nishanth Menon
2023-10-03 11:00 ` [PATCH 0/3] arm64: dts: ti: k3-am625: Add boot phase marking Vignesh Raghavendra
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=20230911162535.1044560-1-nm@ti.com \
--to=nm@ti.com \
--cc=bb@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=praneeth@ti.com \
--cc=robertcnelson@gmail.com \
--cc=robh+dt@kernel.org \
--cc=trini@konsulko.com \
--cc=vigneshr@ti.com \
/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®