From: Stephen Boyd <sboyd@kernel.org>
To: Alexandre Torgue <alexandre.torgue@foss.st.com>,
Conor Dooley <conor+dt@kernel.org>,
Dan Carpenter <dan.carpenter@linaro.or6g>,
Gabriel Fernandez <gabriel.fernandez@foss.st.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Maxime Ripard <mripard@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Rob Herring <robh@kernel.org>
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: Re: [RESEND PATCH v2 1/3] clk: stm32mp2: use of STM32 access controller
Date: Mon, 03 Jun 2024 14:36:41 -0700 [thread overview]
Message-ID: <c776960ca7b285626366dd7ecba04018.sboyd@kernel.org> (raw)
In-Reply-To: <20240529131310.260954-2-gabriel.fernandez@foss.st.com>
Quoting gabriel.fernandez@foss.st.com (2024-05-29 06:13:08)
> From: Gabriel Fernandez <gabriel.fernandez@foss.st.com>
>
> Use an STM32 access controller to filter the registration of clocks.
> If a clock is used by the security world, then it must not registered.
>
> Signed-off-by: Gabriel Fernandez <gabriel.fernandez@foss.st.com>
> ---
Applied to clk-next
next prev parent reply other threads:[~2024-06-03 21:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 13:13 [RESEND PATCH v2 0/3] Use STM32 access controller for STM32MP25 clocks gabriel.fernandez
2024-05-29 13:13 ` [RESEND PATCH v2 1/3] clk: stm32mp2: use of STM32 access controller gabriel.fernandez
2024-06-03 21:36 ` Stephen Boyd [this message]
2024-05-29 13:13 ` [RESEND PATCH v2 2/3] clk: stm32mp25: add security clocks gabriel.fernandez
2024-06-03 21:36 ` Stephen Boyd
2024-05-29 13:13 ` [PATCH v2 3/3] arm64: dts: st: enable STM32 access controller for RCC gabriel.fernandez
2024-06-05 7:32 ` 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=c776960ca7b285626366dd7ecba04018.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=dan.carpenter@linaro.or6g \
--cc=devicetree@vger.kernel.org \
--cc=gabriel.fernandez@foss.st.com \
--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 \
/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).