[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220616175531.GA3716982-robh@kernel.org>
Date: Thu, 16 Jun 2022 11:55:31 -0600
From: Rob Herring <robh@...nel.org>
To: Alexandre Torgue <alexandre.torgue@...s.st.com>
Cc: Krzysztof Kozlowski <krzk+dt@...nel.org>,
linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
linux-stm32@...md-mailman.stormreply.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] dt-bindings: rcc: stm32: select the "secure" path for
stm32mp13
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@...s.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
>
>
Powered by blists - more mailing lists