U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Kumar, Udit" <u-kumar1@ti.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: <vigneshr@ti.com>, <nm@ti.com>, <trini@konsulko.com>,
	<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>,
	<bmeng.cn@gmail.com>, <mkorpershoek@baylibre.com>,
	<s-vadapalli@ti.com>, <u-boot@lists.denx.de>,
	<joao.goncalves@toradex.com>, <hnagalla@ti.com>
Subject: Re: [PATCH 0/4] Adding support to load secure firmware for HS devices
Date: Tue, 21 May 2024 20:59:17 +0530	[thread overview]
Message-ID: <37ba74bf-21ea-4551-8631-c07d8ff2c0ea@ti.com> (raw)
In-Reply-To: <ZkyvvWotyQJQyz9k@smile.fi.intel.com>


On 5/21/2024 7:59 PM, Andy Shevchenko wrote:
> On Tue, May 21, 2024 at 04:26:44PM +0530, Udit Kumar wrote:
>> Some use case needs rproc firmware to be loaded at u-boot stage,
>> using following commands at u-boot shell, firmware could be loaded
>>
>> => setenv dorprocboot 1
>> => run boot_rprocs
>>
>> For Secure devices, secure version of rproc firmware should be loaded,
>> which is appended by sec keyword[0].
>> but currently non-secure firmware is loaded even for secure devices.
>> So adding support for loading secure firmware on Secured devices.
> Are you Cc'ing random people with this?
> Please don't do it.

I used names names popped up while running get_maintainer.pl script of 
u-boot

your email id was there for patch-3 of this series

./scripts/get_maintainer.pl 
0003-include-env-ti-Add-support-for-secure-firmwares.patch
Joe Hershberger <joe.hershberger@ni.com> (maintainer:ENVIRONMENT)
Tom Rini <trini@konsulko.com> (maintainer:THE REST)
Udit Kumar <u-kumar1@ti.com> 
(commit_signer:1/2=50%,authored:1/2=50%,commit_signer:1/7=14%,authored:1/7=14%)
Simon Glass <sjg@chromium.org> 
(commit_signer:1/2=50%,authored:1/2=50%,authored:1/7=14%)
Andy Shevchenko <andriy.shevchenko@linux.intel.com> (commit_signer:1/2=50%)
Bin Meng <bmeng.cn@gmail.com> (commit_signer:1/2=50%)
Manorit Chawdhry <m-chawdhry@ti.com> 
(commit_signer:1/2=50%,commit_signer:5/7=71%,authored:4/7=57%)
Mattijs Korpershoek <mkorpershoek@baylibre.com> (commit_signer:4/7=57%)
Nishanth Menon <nm@ti.com> (commit_signer:1/7=14%,authored:1/7=14%)
Siddharth Vadapalli <s-vadapalli@ti.com> (commit_signer:1/7=14%)
u-boot@lists.denx.de (open list)


  reply	other threads:[~2024-05-21 15:29 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 ` [PATCH 4/4] mach-k3: common.c: add a flag for booting authenticated rproc binaries Udit Kumar
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 [this message]
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=37ba74bf-21ea-4551-8631-c07d8ff2c0ea@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