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>,
Arnd Bergmann <arnd@arndb.de>
Cc: Etienne CARRIERE <etienne.carriere@linaro.org>,
Fabrice GASNIER <fabrice.gasnier@foss.st.com>,
Amelie DELAUNAY <amelie.delaunay@foss.st.com>,
Lionel DEBIEVE <lionel.debieve@foss.st.com>,
Patrick Delaunay <patrick.delaunay@foss.st.com>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>
Subject: [PATCH v6 0/3] nvmem: stm32: add OP-TEE support for STM32MP13x
Date: Wed, 18 Jan 2023 18:29:36 +0100 [thread overview]
Message-ID: <20230118172940.841094-1-patrick.delaunay@foss.st.com> (raw)
The v5 patchset is rebased on next-20221226.
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 v6:
- Add reviewed by Etienne Carierre review
- added reviewed by Etienne Carriere
Changes in v5:
- minor changes after Etienne Carierre review (comments,
change %x to %#x, remove goto to out_tee_session)
- update the BSEC SMC detection logic in stm32_romem_probe()
after Etienne Carierre review to support NVMEM probe after OP-TEE probe
Changes in v4:
- fixe warning reported by kernel test robot for 64 bits support in
drivers/nvmem/stm32-bsec-optee-ta.c:260:18:
warning: format '%d' expects argument of type 'int',
but argument 4 has type 'size_t'
Changes in v3:
- add a separate file stm32-bsec-optee-ta.c with STM32MP BSEC TA
communication functions to avoid #if in romem driver.
- use of_find_compatible_node in optee_presence_check function
instead of of_find_node_by_path("/firmware/optee")
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/Kconfig | 11 +
drivers/nvmem/Makefile | 1 +
drivers/nvmem/stm32-bsec-optee-ta.c | 298 ++++++++++++++++++++++++++++
drivers/nvmem/stm32-bsec-optee-ta.h | 80 ++++++++
drivers/nvmem/stm32-romem.c | 84 +++++++-
6 files changed, 472 insertions(+), 4 deletions(-)
create mode 100644 drivers/nvmem/stm32-bsec-optee-ta.c
create mode 100644 drivers/nvmem/stm32-bsec-optee-ta.h
base-commit: c76083fac3bae1a87ae3d005b5cb1cbc761e31d5
prerequisite-patch-id: 5aaa8fffbdd16871143808180b3932d80f4045d0
prerequisite-patch-id: ae711dc528e191e4751cbb7402041fc5f185d6b3
--
2.25.1
next reply other threads:[~2023-01-18 17:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 17:29 Patrick Delaunay [this message]
2023-01-18 17:29 ` [PATCH v6 1/3] ARM: dts: stm32mp13: fix compatible for BSEC Patrick Delaunay
2023-01-19 12:06 ` [Linux-stm32] " Ahmad Fatoum
2023-02-02 12:31 ` Alexandre TORGUE
2023-01-26 21:02 ` [PATCH v6 0/3] nvmem: stm32: add OP-TEE support for STM32MP13x Arnd Bergmann
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=20230118172940.841094-1-patrick.delaunay@foss.st.com \
--to=patrick.delaunay@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=amelie.delaunay@foss.st.com \
--cc=arnd@arndb.de \
--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=lionel.debieve@foss.st.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).