From: Patrick Delaunay <patrick.delaunay@foss.st.com>
To: Alexandre TORGUE <alexandre.torgue@foss.st.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: Fabrice GASNIER <fabrice.gasnier@foss.st.com>,
Patrick Delaunay <patrick.delaunay@foss.st.com>,
Etienne CARRIERE <etienne.carriere@linaro.org>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>
Subject: [PATCH v2 0/3] nvmem: stm32: add OP-TEE support for STM32MP13x
Date: Thu, 10 Nov 2022 16:45:46 +0100 [thread overview]
Message-ID: <20221110154550.3220800-1-patrick.delaunay@foss.st.com> (raw)
This serie update the NVMEM BSEC driver to be compatible with STM32MP13x
SoC and the trusted application STM32MP BSEC in OP-TEE
This serie solve issue in initial support of STM32MP131
(using BSEC STM32MP15 compatible) and so it break the STM32MP13x DTS
compatible.
I create this serie for more efficient review, including support for
STM32MP15x.
The first patches of the V1 series is already merged:
"dt-bindings: nvmem: add new stm32mp13 compatible for stm32-romem"
This STM32MP13x DTS break is acceptable as
- the STM32MP13x SoC is not yet available outside STMicroelectronics
(not official)
- the same patch is already integrated or modifications are in progress in
the other users (arm-trusted-firmware/TF-A, OP-TEE and U-Boot) of
stm32mp131 device tree.
It is the good time to correct this issue before the real availability of
the SoC and before full support of STM32MP13x SoC in Linux kernel.
Regards
Patrick
Changes in v2:
- rebase series on linux-next/master
- minor update after V1 revue
Changes in v1:
- update commit message to indicate DTS break reason.
Patrick Delaunay (3):
ARM: dts: stm32mp13: fix compatible for BSEC
nvmem: stm32: add OP-TEE support for STM32MP13x
nvmem: stm32: detect bsec pta presence for STM32MP15x
arch/arm/boot/dts/stm32mp131.dtsi | 2 +-
drivers/nvmem/stm32-romem.c | 474 +++++++++++++++++++++++++++++-
2 files changed, 471 insertions(+), 5 deletions(-)
--
2.25.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-11-10 15:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 15:45 Patrick Delaunay [this message]
2022-11-10 15:45 ` [PATCH v2 1/3] ARM: dts: stm32mp13: fix compatible for BSEC Patrick Delaunay
2022-11-10 15:45 ` [PATCH v2 2/3] nvmem: stm32: add OP-TEE support for STM32MP13x Patrick Delaunay
2022-11-11 17:18 ` Srinivas Kandagatla
2022-11-14 14:20 ` Patrick DELAUNAY
2022-11-10 15:45 ` [PATCH v2 3/3] nvmem: stm32: detect bsec pta presence for STM32MP15x Patrick Delaunay
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=20221110154550.3220800-1-patrick.delaunay@foss.st.com \
--to=patrick.delaunay@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=devicetree@vger.kernel.org \
--cc=etienne.carriere@linaro.org \
--cc=fabrice.gasnier@foss.st.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--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=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
/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).