devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: <gabriel.fernandez@foss.st.com>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	Maxime Ripard <mripard@kernel.org>,
	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: Re: [PATCH v2 3/3] arm64: dts: st: enable STM32 access controller for RCC
Date: Wed, 5 Jun 2024 09:32:35 +0200	[thread overview]
Message-ID: <314f1f33-7f6b-4b10-a05e-f9e0d5456e31@foss.st.com> (raw)
In-Reply-To: <20240529131310.260954-4-gabriel.fernandez@foss.st.com>

Hi Gabriel

On 5/29/24 15:13, gabriel.fernandez@foss.st.com wrote:
> From: Gabriel Fernandez <gabriel.fernandez@foss.st.com>
> 
> Use an STM32 access controller to filter the registration of clocks.
> 
> Signed-off-by: Gabriel Fernandez <gabriel.fernandez@foss.st.com>
> ---
>   arch/arm64/boot/dts/st/stm32mp251.dtsi | 1 +
>   1 file changed, 1 insertion(+)
> 
> diff --git a/arch/arm64/boot/dts/st/stm32mp251.dtsi b/arch/arm64/boot/dts/st/stm32mp251.dtsi
> index dcd0656d67a8..602d02efc202 100644
> --- a/arch/arm64/boot/dts/st/stm32mp251.dtsi
> +++ b/arch/arm64/boot/dts/st/stm32mp251.dtsi
> @@ -441,6 +441,7 @@ rcc: clock-controller@44200000 {
>   				<&scmi_clk CK_SCMI_TIMG2>,
>   				<&scmi_clk CK_SCMI_PLL3>,
>   				<&clk_dsi_txbyte>;
> +				access-controllers = <&rifsc 156>;
>   		};
>   
>   		exti1: interrupt-controller@44220000 {

Applied on stm32-next.

cheers
Alex

  reply	other threads:[~2024-06-05  7:33 UTC|newest]

Thread overview: 8+ 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
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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-16 15:24 [PATCH v2 0/3] Use STM32 access controller for STM32MP25 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=314f1f33-7f6b-4b10-a05e-f9e0d5456e31@foss.st.com \
    --to=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 \
    --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 NNTP newsgroup(s).