From: Chintan Vankar <c-vankar@ti.com>
To: Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>, Tero Kristo <kristo@kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>, Nishanth Menon <nm@ti.com>
Cc: <srk@ti.com>, <s-vadapalli@ti.com>, <danishanwar@ti.com>,
<c-vankar@ti.com>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: [PATCH v4 0/2] Add bootph-all property to necessary nodes to enable ethernet boot for AM68-SK, J722s and AM62p-SK
Date: Tue, 29 Apr 2025 12:56:42 +0530 [thread overview]
Message-ID: <20250429072644.2400295-1-c-vankar@ti.com> (raw)
This series adds bootph-all property to necessary nodes to enable
ethernet boot support for AM68-SK, J722s and AM62p-SK.
This series is based on linux-next tagged next-20250428.
Link to v3:
https://lore.kernel.org/r/20250425051055.2393301-1-c-vankar@ti.com/
Changes from v3 to v4:
- As per Nishanth's suggestion, moved nodes which require "bootph-all"
property into board specific file for AM68-SK.
Chintan Vankar (2):
arm64: dts: ti: k3-am68-sk-base-board: Add bootph-all property to
enable Ethernet boot
arm64: dts: ti: k3-am62p*/k3-j722s: Add bootph-all property to enable
Ethernet boot
.../boot/dts/ti/k3-am62p-j722s-common-main.dtsi | 3 +++
arch/arm64/boot/dts/ti/k3-am62p5-sk.dts | 2 ++
arch/arm64/boot/dts/ti/k3-am68-sk-base-board.dts | 12 ++++++++++++
arch/arm64/boot/dts/ti/k3-j722s-evm.dts | 3 +++
4 files changed, 20 insertions(+)
--
2.34.1
next reply other threads:[~2025-04-29 7:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 7:26 Chintan Vankar [this message]
2025-04-29 7:26 ` [PATCH v4 1/2] arm64: dts: ti: k3-am68-sk-base-board: Add bootph-all property to enable Ethernet boot Chintan Vankar
2025-04-29 7:26 ` [PATCH v4 2/2] arm64: dts: ti: k3-am62p*/k3-j722s: " Chintan Vankar
2025-04-29 11:27 ` Nishanth Menon
2025-04-30 5:48 ` Vankar, Chintan
2025-05-02 12:00 ` Nishanth Menon
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=20250429072644.2400295-1-c-vankar@ti.com \
--to=c-vankar@ti.com \
--cc=conor+dt@kernel.org \
--cc=danishanwar@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=s-vadapalli@ti.com \
--cc=srk@ti.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