mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Xogium <contact@xogium.me>, Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH master] nvmem: bsec: make OP-TEE TA interaction optional
Date: Fri, 24 May 2024 12:35:14 +0200	[thread overview]
Message-ID: <20240524103514.2217258-1-a.fatoum@pengutronix.de> (raw)

When targeting older OP-TEE versions, a PTA for BSEC access may not be
available. Allow disabling STM32_BSEC_OPTEE_TA in this case, so the
driver falls back to the secure monitor call silicon provider service.

Reported-by: Xogium <contact@xogium.me>
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
 drivers/nvmem/Kconfig | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/drivers/nvmem/Kconfig b/drivers/nvmem/Kconfig
index 255198b2ad81..349471ce3932 100644
--- a/drivers/nvmem/Kconfig
+++ b/drivers/nvmem/Kconfig
@@ -91,10 +91,13 @@ config STM32_BSEC_WRITE
 	    mw -l -d /dev/stm32-bsec 0x000000e8+4 0x0000bc9a
 
 config STM32_BSEC_OPTEE_TA
-	def_bool STM32_BSEC && OPTEE
+	bool "Support BSEC access over OP-TEE TA"
+	depends on STM32_BSEC && OPTEE
+	default y
 	help
 	  Say y here to enable the accesses to STM32MP SoC OTPs by the OP-TEE
-	  trusted application STM32MP BSEC.
+	  trusted application STM32MP BSEC in addition to the older SMC SiP
+	  service.
 
 config KVX_OTP_NV
 	tristate "kalray KVX OTP Non volatile regs Support"
-- 
2.39.2




             reply	other threads:[~2024-05-24 10:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-24 10:35 Ahmad Fatoum [this message]
2024-05-24 11:41 ` Sascha Hauer

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=20240524103514.2217258-1-a.fatoum@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=contact@xogium.me \
    /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