From: Daniel Schultz <d.schultz@phytec.de>
To: <w.egorov@phytec.de>, <trini@konsulko.com>, <u-boot@lists.denx.de>
Cc: <mkorpershoek@baylibre.com>, <B.Hahn@phytec.de>,
<upstream@lists.phytec.de>, Daniel Schultz <d.schultz@phytec.de>
Subject: [PATCH 2/3] configs: phycore_am62x_a53_defconfig: Enable remoteproc cmd
Date: Thu, 27 Mar 2025 22:58:23 -0700 [thread overview]
Message-ID: <20250328055824.3849523-2-d.schultz@phytec.de> (raw)
In-Reply-To: <20250328055824.3849523-1-d.schultz@phytec.de>
This enables the 'rproc' command, allowing users to
start, stop, and manage co-processors as well as load firmware
images.
Useful for systems with auxiliary cores, such as the M4 core
in the AM62x soc.
Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
---
configs/phycore_am62x_a53_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/configs/phycore_am62x_a53_defconfig b/configs/phycore_am62x_a53_defconfig
index 03d4618df38..c1a46bc40a9 100644
--- a/configs/phycore_am62x_a53_defconfig
+++ b/configs/phycore_am62x_a53_defconfig
@@ -76,6 +76,7 @@ CONFIG_CMD_DFU=y
CONFIG_CMD_I2C=y
CONFIG_CMD_MMC=y
CONFIG_CMD_MTD=y
+CONFIG_CMD_REMOTEPROC=y
CONFIG_CMD_USB=y
CONFIG_CMD_CACHE=y
CONFIG_CMD_EFIDEBUG=y
--
2.25.1
next prev parent reply other threads:[~2025-03-28 5:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 5:58 [PATCH 1/3] configs: phycore_am64x_a53_defconfig: Enable remoteproc cmd Daniel Schultz
2025-03-28 5:58 ` Daniel Schultz [this message]
2025-03-31 8:52 ` [PATCH 2/3] configs: phycore_am62x_a53_defconfig: " Mattijs Korpershoek
2025-03-28 5:58 ` [PATCH 3/3] configs: phycore_am62x_a53_defconfig: Enable gpio Daniel Schultz
2025-03-31 8:53 ` Mattijs Korpershoek
2025-03-31 8:52 ` [PATCH 1/3] configs: phycore_am64x_a53_defconfig: Enable remoteproc cmd Mattijs Korpershoek
2025-04-11 19:16 ` 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=20250328055824.3849523-2-d.schultz@phytec.de \
--to=d.schultz@phytec.de \
--cc=B.Hahn@phytec.de \
--cc=mkorpershoek@baylibre.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=upstream@lists.phytec.de \
--cc=w.egorov@phytec.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