U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Udit Kumar <u-kumar1@ti.com>
To: <vigneshr@ti.com>, <nm@ti.com>, <trini@konsulko.com>
Cc: <joe.hershberger@ni.com>, <m-chawdhry@ti.com>, <afd@ti.com>,
	<devarsht@ti.com>, <sjg@chromium.org>,
	<emanuele.ghidoli@toradex.com>,
	<matthias.schiffer@ew.tq-group.com>, <a-bhatia1@ti.com>,
	<vitor.soares@toradex.com>, <danishanwar@ti.com>,
	<andriy.shevchenko@linux.intel.com>, <bmeng.cn@gmail.com>,
	<mkorpershoek@baylibre.com>, <s-vadapalli@ti.com>,
	<u-boot@lists.denx.de>, <joao.goncalves@toradex.com>,
	<hnagalla@ti.com>, Udit Kumar <u-kumar1@ti.com>
Subject: [PATCH 4/4] mach-k3: common.c: add a flag for booting authenticated rproc binaries
Date: Tue, 21 May 2024 16:26:48 +0530	[thread overview]
Message-ID: <20240521105648.3780072-5-u-kumar1@ti.com> (raw)
In-Reply-To: <20240521105648.3780072-1-u-kumar1@ti.com>

From: Manorit Chawdhry <m-chawdhry@ti.com>

The flag will be used for booting authenticated remote procs from hs-se
devices which can optionally be used in hs-fs devices also.

Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com>
Signed-off-by: Udit Kumar <u-kumar1@ti.com>
---
 arch/arm/mach-k3/common.c | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/arch/arm/mach-k3/common.c b/arch/arm/mach-k3/common.c
index 1a269d6934..eaa7d36176 100644
--- a/arch/arm/mach-k3/common.c
+++ b/arch/arm/mach-k3/common.c
@@ -283,8 +283,10 @@ int misc_init_r(void)
 	}
 
 	/* Default FIT boot on HS-SE devices */
-	if (get_device_type() == K3_DEVICE_TYPE_HS_SE)
+	if (get_device_type() == K3_DEVICE_TYPE_HS_SE) {
 		env_set("boot_fit", "1");
+		env_set("secure_rprocs", "1");
+	}
 
 	return 0;
 }
-- 
2.34.1


  parent reply	other threads:[~2024-05-21 10:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-21 10:56 [PATCH 0/4] Adding support to load secure firmware for HS devices Udit Kumar
2024-05-21 10:56 ` [PATCH 1/4] include: mach-k3: move k3 security functions to security.h Udit Kumar
2024-05-21 10:56 ` [PATCH 2/4] drivers: remoteproc: ti_k3 : enable secure booting with firmware images Udit Kumar
2024-05-21 10:56 ` [PATCH 3/4] include: env: ti: Add support for secure firmwares Udit Kumar
2024-05-21 10:56 ` Udit Kumar [this message]
2024-05-21 14:29 ` [PATCH 0/4] Adding support to load secure firmware for HS devices Andy Shevchenko
2024-05-21 15:29   ` Kumar, Udit
2024-05-21 16:12     ` Andy Shevchenko
2024-05-21 16:21       ` Tom Rini
2024-05-21 16:35         ` Andy Shevchenko
2024-05-21 16:45           ` Tom Rini
2024-05-21 17:48             ` Andy Shevchenko
2024-05-21 17:52               ` Tom Rini
2024-05-21 18:55                 ` Andy Shevchenko
2024-05-21 19:23                   ` Tom Rini
2024-06-07 22:03 ` 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=20240521105648.3780072-5-u-kumar1@ti.com \
    --to=u-kumar1@ti.com \
    --cc=a-bhatia1@ti.com \
    --cc=afd@ti.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=bmeng.cn@gmail.com \
    --cc=danishanwar@ti.com \
    --cc=devarsht@ti.com \
    --cc=emanuele.ghidoli@toradex.com \
    --cc=hnagalla@ti.com \
    --cc=joao.goncalves@toradex.com \
    --cc=joe.hershberger@ni.com \
    --cc=m-chawdhry@ti.com \
    --cc=matthias.schiffer@ew.tq-group.com \
    --cc=mkorpershoek@baylibre.com \
    --cc=nm@ti.com \
    --cc=s-vadapalli@ti.com \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=vigneshr@ti.com \
    --cc=vitor.soares@toradex.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