[PATCH] dt-bindings: rcc: stm32: select the "secure" path for stm32mp13
Rob Herring
robh at kernel.org
Thu Jun 16 10:55:31 PDT 2022
On Mon, Jun 13, 2022 at 11:38:15AM +0200, Alexandre Torgue wrote:
> Like for stm32mp15, when stm32 RCC node is used to interact with a secure
'st,stm32mp1' is stm32mp15?
> context (using clock SCMI protocol), a different path has to be used for
> yaml verification.
>
> Signed-off-by: Alexandre Torgue <alexandre.torgue at foss.st.com>
>
> ---
>
> Hi Rob, Krzysztof,
>
> If you agree with this patch, I'll apply it directly in my STM32 tree.
>
> Thanks
> Alex
>
> diff --git a/Documentation/devicetree/bindings/clock/st,stm32mp1-rcc.yaml b/Documentation/devicetree/bindings/clock/st,stm32mp1-rcc.yaml
> index f8c474227807..242fe922b035 100644
> --- a/Documentation/devicetree/bindings/clock/st,stm32mp1-rcc.yaml
> +++ b/Documentation/devicetree/bindings/clock/st,stm32mp1-rcc.yaml
> @@ -78,6 +78,7 @@ if:
> contains:
> enum:
> - st,stm32mp1-rcc-secure
> + - st,stm32mp13-rcc
You don't need '-secure' because it's always secure?
> then:
> properties:
> clocks:
> --
> 2.17.1
>
>
More information about the linux-arm-kernel
mailing list