public inbox for linux-clk@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rob Herring (Arm)" <robh@kernel.org>
To: "Clément Le Goffic" <legoffic.clement@gmail.com>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
	linux-arm-kernel@lists.infradead.org,
	"Gabriel Fernandez" <gabriel.fernandez@foss.st.com>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-clk@vger.kernel.org,
	"Michael Turquette" <mturquette@baylibre.com>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Alexandre Torgue" <alexandre.torgue@foss.st.com>,
	"Clément Le Goffic" <clement.legoffic@foss.st.com>,
	"Stephen Boyd" <sboyd@kernel.org>
Subject: Re: [PATCH v7 0/3] Register the STM32MP25 RCC driver as an access controller.
Date: Mon, 22 Sep 2025 12:27:50 -0500	[thread overview]
Message-ID: <175856184058.499994.8575309202132748563.robh@kernel.org> (raw)
In-Reply-To: <20250922-b4-rcc-upstream-v7-0-2dfc4e018f40@gmail.com>


On Mon, 22 Sep 2025 10:12:17 +0200, Clément Le Goffic wrote:
> The STM32MP25 RCC peripheral as an access controller is allowed to know
> whether the clocks are secured or not.
> The STM32MP25 RCC peripheral knows about the clock secure configuration
> of all non RIF-aware peripheral.
> In parallel all the RIF-aware peripheral configuration information
> are known by the RIFSC peripheral which is already an access
> controller.
> 
> This v7 is a subset of the v6 and other prior versions, split to simplify
> the review and merging process.
> 
> Changes in v7:
> - None
> - Link to v6: https://lore.kernel.org/all/20250909-b4-ddrperfm-upstream-v6-2-ce082cc801b5@gmail.com/
> 
> Signed-off-by: Clément Le Goffic <legoffic.clement@gmail.com>
> ---
> Clément Le Goffic (3):
>       dt-bindings: stm32: stm32mp25: add `#access-controller-cells` property
>       clk: stm32mp25: add firewall grant_access ops
>       arm64: dts: st: set rcc as an access-controller
> 
>  .../bindings/clock/st,stm32mp25-rcc.yaml           |  7 ++++
>  arch/arm64/boot/dts/st/stm32mp251.dtsi             |  1 +
>  drivers/clk/stm32/clk-stm32mp25.c                  | 40 +++++++++++++++++++++-
>  3 files changed, 47 insertions(+), 1 deletion(-)
> ---
> base-commit: 07e27ad16399afcd693be20211b0dfae63e0615f
> change-id: 20250916-b4-rcc-upstream-8a8ea3af6a0d
> prerequisite-change-id: 20250916-b4-firewall-upstream-dfe8588a21f8:v7
> prerequisite-patch-id: 1ead960f405c7a2dcc9111acd0bb4c95ed33954f
> 
> Best regards,
> --
> Clément Le Goffic <legoffic.clement@gmail.com>
> 
> 
> 


My bot found new DTB warnings on the .dts files added or changed in this
series.

Some warnings may be from an existing SoC .dtsi. Or perhaps the warnings
are fixed by another series. Ultimately, it is up to the platform
maintainer whether these warnings are acceptable or not. No need to reply
unless the platform maintainer has comments.

If you already ran DT checks and didn't see these error(s), then
make sure dt-schema is up to date:

  pip3 install dtschema --upgrade


This patch series was applied (using b4) to base:
 Base: using specified base-commit 07e27ad16399afcd693be20211b0dfae63e0615f
 Deps: looking for dependencies matching 1 patch-ids
 Deps: Applying prerequisite patch: [PATCH v7] bus: firewall: move stm32_firewall header file in include folder

If this is not the correct base, please add 'base-commit' tag
(or use b4 which does this automatically)

New warnings running 'make CHECK_DTBS=y for arch/arm64/boot/dts/st/' for 20250922-b4-rcc-upstream-v7-0-2dfc4e018f40@gmail.com:

arch/arm64/boot/dts/st/stm32mp235f-dk.dtb: clock-controller@44200000 (st,stm32mp25-rcc): '#access-controller-cells' is a required property
	from schema $id: http://devicetree.org/schemas/clock/st,stm32mp25-rcc.yaml#






      parent reply	other threads:[~2025-09-22 17:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-22  8:12 [PATCH v7 0/3] Register the STM32MP25 RCC driver as an access controller Clément Le Goffic
2025-09-22  8:12 ` [PATCH v7 1/3] dt-bindings: stm32: stm32mp25: add `#access-controller-cells` property Clément Le Goffic
2025-09-22  8:12 ` [PATCH v7 2/3] clk: stm32mp25: add firewall grant_access ops Clément Le Goffic
2025-09-22  8:12 ` [PATCH v7 3/3] arm64: dts: st: set rcc as an access-controller Clément Le Goffic
2025-09-22 17:27 ` Rob Herring (Arm) [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=175856184058.499994.8575309202132748563.robh@kernel.org \
    --to=robh@kernel.org \
    --cc=alexandre.torgue@foss.st.com \
    --cc=clement.legoffic@foss.st.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gabriel.fernandez@foss.st.com \
    --cc=krzk+dt@kernel.org \
    --cc=legoffic.clement@gmail.com \
    --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=mturquette@baylibre.com \
    --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