From: Nishanth Menon <nm@ti.com>
To: Tom Rini <trini@konsulko.com>
Cc: Heinrich Schuchardt <xypron.glpk@gmx.de>,
Sinthu Raja <sinthu.raja@ti.com>,
Manorit Chawdhry <m-chawdhry@ti.com>, Reid Tonking <reidt@ti.com>,
Neha Malcom Francis <n-francis@ti.com>, Andrew Davis <afd@ti.com>,
Simon Glass <sjg@chromium.org>,
Robert Nelson <robertcnelson@gmail.com>,
Jason Kridner <jkridner@beagleboard.org>,
Nishanth Menon <nm@ti.com>, <u-boot@lists.denx.de>
Subject: [PATCH V2 0/4] board: ti: Add support for BeagleBone AI-64
Date: Sat, 4 Nov 2023 03:10:59 -0500 [thread overview]
Message-ID: <20231104081103.10607-1-nm@ti.com> (raw)
Hi,
Refactored series purely focussed on introducing BeagleBone AI-64
Cleanups are isolated off into their own series.
What works:
* emmc, sd, dhcp, basic i2c gpio etc..
* DDR looks stable as well.
TODO:
* PMIC support will need to be added for AVS to be active - something to
do once upstream kernel gets that support
* USB boot is broken (or was just noticed in v1) - some sort of regression with
serdes is my best guess.
* We could potentially enable something like nvme boot as well if we can
make PCIe work
BootLogs:
AI64 (SD): https://gist.github.com/nmenon/0de3149737c517083443ab7077e6a9e4
AI64 (emmc boot with SD): https://gist.github.com/nmenon/71f978c0ad02e0977564c4fd6ecf751f
AI64 (emmc boot without SD): https://gist.github.com/nmenon/469c2ff3b7af0a568764896fd9aafd18
The complete series including dependencies can be found at:
https://github.com/nmenon/u-boot/commits/beagleboneai64-v2
CI loop (for complete series): https://github.com/u-boot/u-boot/pull/445
Dependencies (in order):
(keys and yaml)
1. https://lore.kernel.org/all/20231101183329.65091-1-afd@ti.com/
2. https://lore.kernel.org/u-boot/20231104024511.3597476-1-nm@ti.com/
(docs prompt cleanup - gets in the way of moving things)
3. https://lore.kernel.org/u-boot/20231103000915.2413501-1-nm@ti.com/
(j7200/J721e cleanups):
4. https://lore.kernel.org/u-boot/20231104072150.3339-1-nm@ti.com/
(Beagle - move products to beagle vendor folder):
5. https://lore.kernel.org/u-boot/20231104080137.9628-1-nm@ti.com/
Changes since V1:
* Major refactoring to put BeagleBone AI-64 under beagle vendor folder.
* Split into additional series
V1: https://lore.kernel.org/u-boot/20231103003805.2420005-1-nm@ti.com/
Nishanth Menon (3):
board: beagle: Add BeagleBone AI-64 support
configs: Add j721e_beagleboneai64_* configs
doc: board: beagle: Add BeagleBone AI-64 documentation
Robert Nelson (1):
arm: dts: Add k3-j721e-beagleboneai64
arch/arm/dts/Makefile | 5 +-
.../dts/k3-j721e-beagleboneai64-u-boot.dtsi | 358 ++
arch/arm/dts/k3-j721e-beagleboneai64.dts | 993 ++++++
.../k3-j721e-ddr-beagleboneai64-lp4-3200.dtsi | 2200 ++++++++++++
arch/arm/dts/k3-j721e-r5-beagleboneai64.dts | 185 +
arch/arm/mach-k3/Kconfig | 1 +
board/beagle/beagleboneai64/Kconfig | 59 +
board/beagle/beagleboneai64/MAINTAINERS | 6 +
board/beagle/beagleboneai64/Makefile | 10 +
board/beagle/beagleboneai64/beagleboneai64.c | 30 +
.../beagle/beagleboneai64/beagleboneai64.env | 19 +
board/beagle/beagleboneai64/board-cfg.yaml | 36 +
board/beagle/beagleboneai64/pm-cfg.yaml | 12 +
board/beagle/beagleboneai64/rm-cfg.yaml | 3174 +++++++++++++++++
board/beagle/beagleboneai64/sec-cfg.yaml | 380 ++
configs/j721e_beagleboneai64_a72_defconfig | 171 +
configs/j721e_beagleboneai64_r5_defconfig | 131 +
doc/board/beagle/index.rst | 1 +
doc/board/beagle/j721e_beagleboneai64.rst | 327 ++
doc/board/ti/k3.rst | 1 +
20 files changed, 8098 insertions(+), 1 deletion(-)
create mode 100644 arch/arm/dts/k3-j721e-beagleboneai64-u-boot.dtsi
create mode 100644 arch/arm/dts/k3-j721e-beagleboneai64.dts
create mode 100644 arch/arm/dts/k3-j721e-ddr-beagleboneai64-lp4-3200.dtsi
create mode 100644 arch/arm/dts/k3-j721e-r5-beagleboneai64.dts
create mode 100644 board/beagle/beagleboneai64/Kconfig
create mode 100644 board/beagle/beagleboneai64/MAINTAINERS
create mode 100644 board/beagle/beagleboneai64/Makefile
create mode 100644 board/beagle/beagleboneai64/beagleboneai64.c
create mode 100644 board/beagle/beagleboneai64/beagleboneai64.env
create mode 100644 board/beagle/beagleboneai64/board-cfg.yaml
create mode 100644 board/beagle/beagleboneai64/pm-cfg.yaml
create mode 100644 board/beagle/beagleboneai64/rm-cfg.yaml
create mode 100644 board/beagle/beagleboneai64/sec-cfg.yaml
create mode 100644 configs/j721e_beagleboneai64_a72_defconfig
create mode 100644 configs/j721e_beagleboneai64_r5_defconfig
create mode 100644 doc/board/beagle/j721e_beagleboneai64.rst
--
2.37.2
next reply other threads:[~2023-11-04 8:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-04 8:10 Nishanth Menon [this message]
2023-11-04 8:11 ` [PATCH V2 1/4] arm: dts: Add k3-j721e-beagleboneai64 Nishanth Menon
2023-11-22 20:49 ` Tom Rini
2023-11-04 8:11 ` [PATCH V2 2/4] board: beagle: Add BeagleBone AI-64 support Nishanth Menon
2023-11-06 17:04 ` Andrew Davis
2023-11-07 6:12 ` Neha Malcom Francis
2023-11-04 8:11 ` [PATCH V2 3/4] configs: Add j721e_beagleboneai64_* configs Nishanth Menon
2023-11-04 8:11 ` [PATCH V2 4/4] doc: board: beagle: Add BeagleBone AI-64 documentation 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=20231104081103.10607-1-nm@ti.com \
--to=nm@ti.com \
--cc=afd@ti.com \
--cc=jkridner@beagleboard.org \
--cc=m-chawdhry@ti.com \
--cc=n-francis@ti.com \
--cc=reidt@ti.com \
--cc=robertcnelson@gmail.com \
--cc=sinthu.raja@ti.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.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