From: Judith Mendez <jm@ti.com>
To: Tom Rini <trini@konsulko.com>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
Hari Nagalla <hnagalla@ti.com>, Andrew Davis <afd@ti.com>,
<u-boot@lists.denx.de>
Subject: [PATCH 3/4] env: ti: am64x: set rproc_fw_binaries
Date: Wed, 22 Jan 2025 19:07:58 -0600 [thread overview]
Message-ID: <20250123010759.810799-4-jm@ti.com> (raw)
In-Reply-To: <20250123010759.810799-1-jm@ti.com>
From: Hari Nagalla <hnagalla@ti.com>
Set remote proc FW binaries for u-boot loading of remote cores.
Signed-off-by: Hari Nagalla <hnagalla@ti.com>
---
board/ti/am64x/am64x.env | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/board/ti/am64x/am64x.env b/board/ti/am64x/am64x.env
index 8ad805a613c..43e557b8ec7 100644
--- a/board/ti/am64x/am64x.env
+++ b/board/ti/am64x/am64x.env
@@ -2,6 +2,10 @@
#include <env/ti/mmc.env>
#include <env/ti/k3_dfu.env>
+#if CONFIG_CMD_REMOTEPROC
+#include <env/ti/k3_rproc.env>
+#endif
+
name_kern=Image
console=ttyS2,115200n8
args_all=setenv optargs earlycon=ns16550a,mmio32,0x02800000 ${mtdparts}
@@ -14,6 +18,8 @@ bootpart=1:2
bootdir=/boot
rd_spec=-
+rproc_fw_binaries= 0 /lib/firmware/am64-mcu-m4f0_0-fw 1 /lib/firmware/am64-main-r5f0_0-fw 2 /lib/firmware/am64-main-r5f0_1-fw 3 /lib/firmware/am64-main-r5f1_0-fw 4 /lib/firmware/am64-main-r5f1_1-fw
+
args_usb=run finduuid;setenv bootargs console=${console}
${optargs}
root=PARTUUID=${uuid} rw
--
2.48.0
next prev parent reply other threads:[~2025-01-23 1:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 1:07 [PATCH 0/4] Introduce K3 remoteproc driver for M4 subsystem Judith Mendez
2025-01-23 1:07 ` [PATCH 1/4] remoteproc: k3-m4: Introduce K3 remote proc " Judith Mendez
2025-01-29 13:24 ` Daniel Schultz
2025-01-29 22:27 ` Judith Mendez
2025-01-23 1:07 ` [PATCH 2/4] remoteproc: k3-r5: Add support for R5F cores on AM64x SoCs Judith Mendez
2025-01-29 13:10 ` Daniel Schultz
2025-01-23 1:07 ` Judith Mendez [this message]
2025-01-23 1:07 ` [PATCH 4/4] configs: am64x_evm_a53_defconfig: Enable R5F and M4 remote proc support Judith Mendez
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=20250123010759.810799-4-jm@ti.com \
--to=jm@ti.com \
--cc=afd@ti.com \
--cc=hnagalla@ti.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