From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Patrick DELAUNAY <patrick.delaunay@foss.st.com>,
Alexandre TORGUE <alexandre.torgue@foss.st.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>
Cc: Etienne CARRIERE <etienne.carriere@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
Fabrice Gasnier <fabrice.gasnier@foss.st.com>
Subject: Re: [PATCH 3/3] nvmem: stm32: add OP-TEE support for STM32MP13x
Date: Wed, 9 Nov 2022 18:02:58 +0000 [thread overview]
Message-ID: <52fa1899-6eb9-389f-2ff1-22164356df66@linaro.org> (raw)
In-Reply-To: <6df7b823-463b-d6fa-9662-54f39463a894@foss.st.com>
On 09/11/2022 17:35, Patrick DELAUNAY wrote:
>>>
>>>
>>>>
>>>> Why not add TEE client based new driver instead of ifdefing around
>>>> this driver? Also I see there is not much common across both drivers
>>>> anyway.
>>>
>>>
>>> I hesitate between the 2 solutions. I choose this update to handle
>>> the STM32MP15 support with OP-TEE.
>>
>> How are you to handing this?
>>
>>>
>>> For backward compatibility reason the same driver STM32 ROMEM
>>> associated to compatible "st,stm32mp15-bsec" should be kept.
>>>
>>> - the lower OTP can directly accessible by Linux (the IP is not
>>> secured) => boot with SPL
>>
>> Can we determine this at runtime?
>
>
> Not directly with IP register, but we detect the OP-TEE support at runtime.
>
You mean using CONFIG_OP_TEE ?
>
>>
>>>
>>> - the upper OTP and the write operation are requested by
>>> STMicroelectronics SMCs
>>>
>>> => boot with TF-A SPMIN and old OP-TEE (before migration to STM32
>>> BSEC PTA)
>>>
>>>
>>> But in the future OP-TEE the access to OTP should be also done with
>>> STM32 BSEC PTA...
>>
>> Given that we have only one compatible for these two type of
>> combinations how are you planning to deal with both the cases and
>> still be backward compatible?
next prev parent reply other threads:[~2022-11-09 18:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 14:52 [PATCH 0/3] nvmem: stm32: add OP-TEE support for STM32MP13x Patrick Delaunay
2022-10-28 14:52 ` [PATCH 1/3] dt-bindings: nvmem: add new stm32mp13 compatible for stm32-romem Patrick Delaunay
2022-10-28 15:39 ` Fabrice Gasnier
2022-10-28 14:52 ` [PATCH 2/3] ARM: dts: stm32mp13: fix compatible for BSEC Patrick Delaunay
2022-10-28 14:52 ` [PATCH 3/3] nvmem: stm32: add OP-TEE support for STM32MP13x Patrick Delaunay
2022-11-01 7:26 ` Srinivas Kandagatla
2022-11-02 10:59 ` Patrick DELAUNAY
2022-11-08 10:03 ` Srinivas Kandagatla
2022-11-09 17:35 ` Patrick DELAUNAY
2022-11-09 18:02 ` Srinivas Kandagatla [this message]
2022-11-03 13:18 ` [Linux-stm32] " Fabrice Gasnier
2022-11-07 10:18 ` Patrick DELAUNAY
2022-10-31 17:42 ` [PATCH 0/3] " Srinivas Kandagatla
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=52fa1899-6eb9-389f-2ff1-22164356df66@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=alexandre.torgue@foss.st.com \
--cc=etienne.carriere@linaro.org \
--cc=fabrice.gasnier@foss.st.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=patrick.delaunay@foss.st.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;
as well as URLs for NNTP newsgroup(s).