From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Patrick Delaunay <patrick.delaunay@foss.st.com>,
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>,
Fabrice Gasnier <fabrice.gasnier@foss.st.com>
Cc: 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: Re: [PATCH 0/3] nvmem: stm32: add OP-TEE support for STM32MP13x
Date: Mon, 31 Oct 2022 17:42:39 +0000 [thread overview]
Message-ID: <4cec819c-abd9-a9f8-5874-8394b6902bdb@linaro.org> (raw)
In-Reply-To: <20221028145252.2115933-1-patrick.delaunay@foss.st.com>
On 28/10/2022 15:52, Patrick Delaunay wrote:
>
> 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 DTS compatible.
>
> I create this serie for more efficient review.
>
> The 2 first patches of this series are re-sent of patches already sent
>
> 1- "dt-bindings: nvmem: add new stm32mp13 compatible for stm32-romem"
> https://lore.kernel.org/all/20221014172324.1.Ifc1812116ff63f5501f3edd155d3cf5c0ecc846c@changeid/
> https://patchwork.kernel.org/project/linux-arm-kernel/list/?series=685403
>
> 2- "ARM: dts: stm32mp13: fix compatible for BSEC"
> https://lore.kernel.org/all/20221017134437.1.I167a5efc1f8777cce14518c6fa38400ac684de3e@changeid/
> https://patchwork.kernel.org/project/linux-arm-kernel/list/?series=685815
>
> This 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 SoC in Linux kernel.
>
> This last patch on NVMEM STM32 ROMEM driver in depend on the preliminary
> patch for the driver:
>
> "nvmem: stm32: move STM32MP15_BSEC_NUM_LOWER in config"
> https://lore.kernel.org/all/20221017174953.v2.1.I95e71328dd654723bd4c57206bd008ff81c726bb@changeid/
>
> present in the serie
>
> "nvmem: stm32: several minor improvements"
> https://patchwork.kernel.org/project/linux-arm-kernel/list/?series=685886
>
> Regards
>
> Patrick
>
> Changes in v1:
> - update commit message to indicate DTS break reason.
>
> Patrick Delaunay (3):
> dt-bindings: nvmem: add new stm32mp13 compatible for stm32-romem
> ARM: dts: stm32mp13: fix compatible for BSEC
> nvmem: stm32: add OP-TEE support for STM32MP13x
Applied 1/3 and 3/3 thanks,
dts changes need to go via the dts maintainer..
--srini
>
> .../bindings/nvmem/st,stm32-romem.yaml | 1 +
> arch/arm/boot/dts/stm32mp131.dtsi | 2 +-
> drivers/nvmem/stm32-romem.c | 450 +++++++++++++++++-
> 3 files changed, 448 insertions(+), 5 deletions(-)
>
prev parent reply other threads:[~2022-10-31 17:42 UTC|newest]
Thread overview: 5+ 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-31 17:42 ` Srinivas Kandagatla [this message]
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=4cec819c-abd9-a9f8-5874-8394b6902bdb@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--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=patrick.delaunay@foss.st.com \
--cc=robh+dt@kernel.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).