From: Patrick DELAUNAY <patrick.delaunay@foss.st.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
<p.paillet@foss.st.com>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Russell King <linux@armlinux.org.uk>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Claudiu Beznea <claudiu.beznea@microchip.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Fabrice Gasnier <fabrice.gasnier@foss.st.com>,
Alexander Stein <alexander.stein@ew.tq-group.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
<devicetree@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Cc: Etienne Carriere <etienne.carriere@foss.st.com>
Subject: Re: [PATCH 4/4] ARM: multi_v7_defconfig: Add SCMI regulator support
Date: Wed, 26 Jul 2023 11:33:15 +0200 [thread overview]
Message-ID: <a442c999-4120-c945-c671-d5fe2c21522c@foss.st.com> (raw)
In-Reply-To: <aa05bcd6-140d-d951-2c7f-c09abf7f49f7@linaro.org>
Hi,
On 7/12/23 21:25, Krzysztof Kozlowski wrote:
> On 12/07/2023 16:24, p.paillet@foss.st.com wrote:
>> From: Pascal Paillet <p.paillet@foss.st.com>
>>
>> Enable ARM SCMI regulator support.
>>
> This we see from the diff. Please explain why, e.g. which boards use it.
>
> Best regards,
> Krzysztof
The STM32MP platforms rely on OP-TEE to boot: Clocks and regulators are
handled in
the secure world by OP-TEE and exported to the non secure world (LINUX)
thanks to ARM SCMI protocol.
Today it is used in the ARMv7 STMicrolectronics stm32mp boards:
- for STM32MP13: stm32mp135f-dk
- the STM32MP15 boards with SCMI variant, introduced by commit 5b7e58313a77
("ARM: dts: stm32: Add SCMI version of STM32 boards (DK1/DK2/ED1/EV1)")
* stm32mp157c-ev1-scmi
* stm32mp157c-ed1-scmi
* stm32mp157c-dk2-scmi
* stm32mp157a-dk1-scmi
This SCMI server provide access to "secured" resources protected in SoC
(for example with RCC_SECFGR); the resources need to be available early
for these board and the SCMI server is associated with OP-TEE, already
activated by the commit 24c159793238 ("ARM: multi_v7_defconfig: Add
OPTEE support").
Regards
Patrick
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
next prev parent reply other threads:[~2023-07-26 9:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 14:24 [PATCH 0/4] STM32MP13x expose SCMI regulators p.paillet
2023-07-12 14:24 ` [PATCH 1/4] dt-bindings: rcc: stm32: add STM32MP13 SCMI regulators IDs p.paillet
2023-07-12 18:08 ` Conor Dooley
2023-07-12 14:24 ` [PATCH 2/4] ARM: dts: stm32: STM32MP13x SoC exposes SCMI regulators p.paillet
2023-07-12 14:24 ` [PATCH 3/4] ARM: dts: stm32: add SCMI PMIC regulators on stm32mp135f-dk board p.paillet
2023-07-12 14:24 ` [PATCH 4/4] ARM: multi_v7_defconfig: Add SCMI regulator support p.paillet
2023-07-12 19:25 ` Krzysztof Kozlowski
2023-07-26 9:33 ` Patrick DELAUNAY [this message]
2023-08-10 16:13 ` Alexandre TORGUE
2023-08-16 11:39 ` [PATCH 0/4] STM32MP13x expose SCMI regulators Alexandre TORGUE
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=a442c999-4120-c945-c671-d5fe2c21522c@foss.st.com \
--to=patrick.delaunay@foss.st.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=alexandre.torgue@foss.st.com \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=claudiu.beznea@microchip.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=etienne.carriere@foss.st.com \
--cc=fabrice.gasnier@foss.st.com \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux@armlinux.org.uk \
--cc=mcoquelin.stm32@gmail.com \
--cc=p.paillet@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).