From: <gabriel.fernandez@foss.st.com>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Maxime Ripard <mripard@kernel.org>,
Gabriel Fernandez <gabriel.fernandez@foss.st.com>,
Dan Carpenter <dan.carpenter@linaro.or6g>
Cc: <devicetree@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-clk@vger.kernel.org>
Subject: [PATCH v2 0/3] Use STM32 access controller for STM32MP25 clocks
Date: Thu, 16 May 2024 17:24:24 +0200 [thread overview]
Message-ID: <20240516152427.692374-1-gabriel.fernandez@foss.st.com> (raw)
From: Gabriel Fernandez <gabriel.fernandez@foss.st.com>
Use an STM32 access controller to filter the registration of clocks.
Don't register a clock if this clock is secured or declared as shared (this
clock is generally managed by the security world).
This series depends on the stm32_firewall framework (merged since
next-20240419) notably for the include file 'linux/bus/stm32_firewall_device.h'.
Changes in v2:
- rebased on next-20240514
- YAML patch was apllied on next
- use appropriate include
- manage the case if 'access-contoller' property is not present in the DT
- rename DT patch (RCC support part was merged)
Gabriel Fernandez (3):
clk: stm32mp2: use of STM32 access controller
clk: stm32mp25: add security clocks
arm64: dts: st: enable STM32 access controller for RCC
arch/arm64/boot/dts/st/stm32mp251.dtsi | 1 +
drivers/clk/stm32/clk-stm32-core.c | 2 +-
drivers/clk/stm32/clk-stm32-core.h | 2 +-
drivers/clk/stm32/clk-stm32mp13.c | 2 +-
drivers/clk/stm32/clk-stm32mp25.c | 516 +++++++++++++++----------
5 files changed, 325 insertions(+), 198 deletions(-)
--
2.25.1
next reply other threads:[~2024-05-16 15:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 15:24 gabriel.fernandez [this message]
2024-05-16 15:24 ` [PATCH v2 1/3] clk: stm32mp2: use of STM32 access controller gabriel.fernandez
2024-05-16 15:24 ` [PATCH v2 2/3] clk: stm32mp25: add security clocks gabriel.fernandez
2024-05-16 15:24 ` [PATCH v2 3/3] arm64: dts: st: enable STM32 access controller for RCC gabriel.fernandez
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=20240516152427.692374-1-gabriel.fernandez@foss.st.com \
--to=gabriel.fernandez@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=dan.carpenter@linaro.or6g \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=mripard@kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh@kernel.org \
--cc=sboyd@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 read-only IMAP folder(s) and NNTP newsgroup(s).