Hello,
On 2/10/26 8:32 PM, 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.
>
> Changes in v9:
> - Rebase on v6.19.0
> - Add Gabriel Fernandez's Reviewed-by
> - Link to v8: https://lore.kernel.org/r/20250924-b4-rcc-upstream-v8-0-b32d46f71a38@gmail.com
>
> Changes in v8:
> - Use uppercase for peripheral name in commit message
> - Add the '#access-controller-cells' property to the RCC in
> stm32mp231.dtsi
> - Link to v7: https://lore.kernel.org/r/20250922-b4-rcc-upstream-v7-0-2dfc4e018f40@gmail.com
>
> The 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/stm32mp231.dtsi | 1 +
> arch/arm64/boot/dts/st/stm32mp251.dtsi | 1 +
> drivers/clk/stm32/clk-stm32mp25.c | 40 +++++++++++++++++++++-
> 4 files changed, 48 insertions(+), 1 deletion(-)
> ---
> base-commit: 05f7e89ab9731565d8a62e3b5d1ec206485eeb0b
> change-id: 20250916-b4-rcc-upstream-8a8ea3af6a0d
> prerequisite-change-id: 20250916-b4-firewall-upstream-dfe8588a21f8:v8
> prerequisite-patch-id: e4a708d9c6df5725c9598fbd2169636e4e7dc46b
>
> Best regards,
> --
> Clément Le Goffic <legoffic.clement@gmail.com>
>
Everything seems fine here, does anyone is able to take it ?
Best regards,
Clément