From: Tom Rini <trini@konsulko.com>
To: Andrew Davis <afd@ti.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>, Nishanth Menon <nm@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Manorit Chawdhry <m-chawdhry@ti.com>,
u-boot@lists.denx.de
Subject: Re: [PATCH 2/2] configs: Make TI_SECURE_DEVICE default for K3
Date: Thu, 3 Aug 2023 15:31:41 -0400 [thread overview]
Message-ID: <20230803193141.GY3630934@bill-the-cat> (raw)
In-Reply-To: <20230803145441.315515-2-afd@ti.com>
[-- Attachment #1: Type: text/plain, Size: 492 bytes --]
On Thu, Aug 03, 2023 at 09:54:41AM -0500, Andrew Davis wrote:
> All K3 boards now are secure by default, instead of setting this in each
> defconfig, make it implied by the ARCH config.
>
> The only exception is IOT2050, which I do not believe will have any
> problems with being a TI_SECURE_DEVICE, but for now turn it off to keep
> its config the same.
>
> Signed-off-by: Andrew Davis <afd@ti.com>
On my J721E GP EVM:
Tested-by: Tom Rini <trini@konsulko.com>
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2023-08-03 19:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 14:54 [PATCH 1/2] configs: am65x: Merge the HS and non-HS defconfigs Andrew Davis
2023-08-03 14:54 ` [PATCH 2/2] configs: Make TI_SECURE_DEVICE default for K3 Andrew Davis
2023-08-03 19:31 ` Tom Rini [this message]
2023-08-09 6:08 ` Jan Kiszka
2023-10-11 18:36 ` Tom Rini
2023-08-03 19:31 ` [PATCH 1/2] configs: am65x: Merge the HS and non-HS defconfigs Tom Rini
2023-08-04 5:05 ` Manorit Chawdhry
2023-09-28 7:54 ` Manorit Chawdhry
2023-10-11 18:36 ` 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=20230803193141.GY3630934@bill-the-cat \
--to=trini@konsulko.com \
--cc=afd@ti.com \
--cc=jan.kiszka@siemens.com \
--cc=m-chawdhry@ti.com \
--cc=nm@ti.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