From: Andrew Davis <afd@ti.com>
To: Neha Malcom Francis <n-francis@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>, Nishanth Menon <nm@ti.com>,
Simon Glass <sjg@chromium.org>, Tom Rini <trini@konsulko.com>
Cc: <u-boot@lists.denx.de>, Andrew Davis <afd@ti.com>
Subject: [PATCH 0/6] Move DRAM address of ATF
Date: Wed, 14 Feb 2024 10:30:03 -0600 [thread overview]
Message-ID: <20240214163009.983034-1-afd@ti.com> (raw)
Hello all,
Explanation for this series is mostly in [4/6]. First 3
patches should be safe to take independent of the last 3.
Thanks,
Andrew
Andrew Davis (6):
arm: mach-k3: Add default ATF location for AM62/AM62a
arm: mach-k3: Add config option for setting OP-TEE address
arm: mach-k3: am62: Enable OF_SYSTEM_SETUP for all boards
arm: mach-k3: am62: Fixup TF-A/OP-TEE reserved-memory node in FDT
arm: mach-k3: am62a: Fixup TF-A/OP-TEE reserved-memory node in FDT
arm: mach-k3: Move DRAM address of ATF for AM62/AM62a
arch/arm/dts/k3-am625-beagleplay-u-boot.dtsi | 4 +-
arch/arm/dts/k3-am65-iot2050-boot-image.dtsi | 4 +-
arch/arm/dts/k3-binman.dtsi | 8 +--
.../dts/k3-j721e-beagleboneai64-u-boot.dtsi | 4 +-
arch/arm/mach-k3/Kconfig | 10 +++-
arch/arm/mach-k3/Makefile | 1 +
arch/arm/mach-k3/am625_fdt.c | 2 +
arch/arm/mach-k3/am62a7_fdt.c | 16 ++++++
arch/arm/mach-k3/am62ax/Kconfig | 1 +
arch/arm/mach-k3/am62x/Kconfig | 3 ++
arch/arm/mach-k3/common_fdt.c | 52 +++++++++++++++++++
arch/arm/mach-k3/common_fdt.h | 2 +
configs/am62ax_evm_a53_defconfig | 1 -
configs/am62x_beagleplay_a53_defconfig | 1 -
configs/am62x_evm_a53_defconfig | 1 -
configs/phycore_am62x_a53_defconfig | 1 -
configs/verdin-am62_a53_defconfig | 2 -
17 files changed, 96 insertions(+), 17 deletions(-)
create mode 100644 arch/arm/mach-k3/am62a7_fdt.c
--
2.39.2
next reply other threads:[~2024-02-14 16:31 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 16:30 Andrew Davis [this message]
2024-02-14 16:30 ` [PATCH 1/6] arm: mach-k3: Add default ATF location for AM62/AM62a Andrew Davis
2024-02-16 4:55 ` Neha Malcom Francis
2024-03-06 13:27 ` Bryan Brattlof
2024-06-19 11:49 ` Dhruva Gole
2024-06-19 18:20 ` Nishanth Menon
2024-06-19 20:02 ` Andrew Davis
2024-06-20 5:30 ` Wadim Egorov
2024-06-21 13:49 ` Bryan Brattlof
2024-02-14 16:30 ` [PATCH 2/6] arm: mach-k3: Add config option for setting OP-TEE address Andrew Davis
2024-02-16 4:59 ` Neha Malcom Francis
2024-02-28 6:21 ` Manorit Chawdhry
2024-03-06 13:49 ` Andrew Davis
2024-03-06 13:28 ` Bryan Brattlof
2024-02-14 16:30 ` [PATCH 3/6] arm: mach-k3: am62: Enable OF_SYSTEM_SETUP for all boards Andrew Davis
2024-02-14 16:30 ` [PATCH 4/6] arm: mach-k3: am62: Fixup TF-A/OP-TEE reserved-memory node in FDT Andrew Davis
2024-02-16 5:26 ` Neha Malcom Francis
2024-02-28 6:24 ` Manorit Chawdhry
2024-03-06 13:52 ` Andrew Davis
2024-03-06 13:35 ` Bryan Brattlof
2024-03-06 14:03 ` Andrew Davis
2024-03-06 15:38 ` Bryan Brattlof
2024-02-14 16:30 ` [PATCH 5/6] arm: mach-k3: am62a: " Andrew Davis
2024-03-06 13:35 ` Bryan Brattlof
2024-02-14 16:30 ` [PATCH 6/6] arm: mach-k3: Move DRAM address of ATF for AM62/AM62a Andrew Davis
2024-02-15 8:06 ` Francesco Dolcini
2024-02-15 20:44 ` Andrew Davis
2024-03-06 13:37 ` Bryan Brattlof
2024-03-06 16:53 ` [PATCH 0/6] Move DRAM address of ATF Tom Rini
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=20240214163009.983034-1-afd@ti.com \
--to=afd@ti.com \
--cc=n-francis@ti.com \
--cc=nm@ti.com \
--cc=sjg@chromium.org \
--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