From: Nishanth Menon <nm@ti.com>
To: <n-francis@ti.com>, <trini@konsulko.com>
Cc: <bb@ti.com>, <praneeth@ti.com>, <afd@ti.com>,
Robert Nelson <robertcnelson@gmail.com>, <vigneshr@ti.com>,
<u-boot@lists.denx.de>, Nishanth Menon <nm@ti.com>
Subject: [PATCH V3 0/4] board: ti: Add support for BeaglePlay
Date: Tue, 15 Aug 2023 11:44:36 -0500 [thread overview]
Message-ID: <20230815164440.2713726-1-nm@ti.com> (raw)
Add support for BeaglePlay - rev 3
Boot log: https://gist.github.com/nmenon/3e99b44380873263e39ba4d84788db89
Full series(including dependencies) can be found at:
https://github.com/nmenon/fix-k3-dt-u-boot/commits/beagleplay-v3
Caveats:
* I have kept networking out of picture for now as it is still in debug
(See
https://github.com/nmenon/fix-k3-dt-u-boot/commits/beagleplay-v3-enet-debug
if anyone is interested)
Changes since V2:
* I have rebased to latest next branch
bdc682437a67 (origin/next) Merge branch '2023-08-14-assorted-general-updates' into next
* Uses config fragments by default.
* Updated MAINTAINER file as well
V2: https://lore.kernel.org/u-boot/20230727234446.3651836-1-nm@ti.com/
V1: https://lore.kernel.org/all/20230725185253.2123433-1-nm@ti.com/
Nishanth Menon (3):
arm: dts: k3-am625-sk-binman: Add labels for unsigned binary
board: ti: am62x: Add am62x_beagleplay_* defconfigs
doc: board: ti: Add BeaglePlay documentation
Robert Nelson (1):
arm: dts: Add k3-am625-beagleplay
arch/arm/dts/Makefile | 2 +
.../dts/k3-am625-beagleplay-ddr4-1600MTs.dtsi | 2195 +++++++++++++++++
arch/arm/dts/k3-am625-beagleplay-u-boot.dtsi | 172 ++
arch/arm/dts/k3-am625-beagleplay.dts | 758 ++++++
arch/arm/dts/k3-am625-r5-beagleplay.dts | 87 +
arch/arm/dts/k3-am625-sk-binman.dtsi | 4 +-
board/ti/am62x/MAINTAINERS | 7 +
board/ti/am62x/beagleplay_a53.config | 20 +
board/ti/am62x/beagleplay_r5.config | 11 +
doc/board/ti/am62x_beagleplay.rst | 121 +
doc/board/ti/k3.rst | 1 +
11 files changed, 3376 insertions(+), 2 deletions(-)
create mode 100644 arch/arm/dts/k3-am625-beagleplay-ddr4-1600MTs.dtsi
create mode 100644 arch/arm/dts/k3-am625-beagleplay-u-boot.dtsi
create mode 100644 arch/arm/dts/k3-am625-beagleplay.dts
create mode 100644 arch/arm/dts/k3-am625-r5-beagleplay.dts
create mode 100644 board/ti/am62x/beagleplay_a53.config
create mode 100644 board/ti/am62x/beagleplay_r5.config
create mode 100644 doc/board/ti/am62x_beagleplay.rst
--
2.40.0
next reply other threads:[~2023-08-15 16:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 16:44 Nishanth Menon [this message]
2023-08-15 16:44 ` [PATCH V3 1/4] arm: dts: k3-am625-sk-binman: Add labels for unsigned binary Nishanth Menon
2023-08-15 16:44 ` [PATCH V3 2/4] arm: dts: Add k3-am625-beagleplay Nishanth Menon
2023-08-15 16:44 ` [PATCH V3 3/4] board: ti: am62x: Add am62x_beagleplay_* defconfigs Nishanth Menon
2023-08-15 16:44 ` [PATCH V3 4/4] doc: board: ti: Add BeaglePlay documentation Nishanth Menon
2023-08-22 15:33 ` [PATCH V3 0/4] board: ti: Add support for BeaglePlay Mattijs Korpershoek
2023-08-22 15:40 ` Nishanth Menon
2023-08-22 15:55 ` Mattijs Korpershoek
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=20230815164440.2713726-1-nm@ti.com \
--to=nm@ti.com \
--cc=afd@ti.com \
--cc=bb@ti.com \
--cc=n-francis@ti.com \
--cc=praneeth@ti.com \
--cc=robertcnelson@gmail.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--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