* [PATCH] dt-bindings: rcc: stm32: select the "secure" path for stm32mp13
@ 2022-06-13 9:38 ` Alexandre Torgue
0 siblings, 0 replies; 10+ messages in thread
From: Alexandre Torgue @ 2022-06-13 9:38 UTC (permalink / raw)
To: robh+dt, Krzysztof Kozlowski
Cc: linux-arm-kernel, devicetree, Alexandre Torgue, linux-stm32,
linux-kernel
Like for stm32mp15, when stm32 RCC node is used to interact with a secure
context (using clock SCMI protocol), a different path has to be used for
yaml verification.
Signed-off-by: Alexandre Torgue <alexandre.torgue@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
then:
properties:
clocks:
--
2.17.1
^ permalink raw reply related [flat|nested] 10+ messages in thread
* [PATCH] dt-bindings: rcc: stm32: select the "secure" path for stm32mp13
@ 2022-06-13 9:38 ` Alexandre Torgue
0 siblings, 0 replies; 10+ messages in thread
From: Alexandre Torgue @ 2022-06-13 9:38 UTC (permalink / raw)
To: robh+dt, Krzysztof Kozlowski
Cc: linux-arm-kernel, devicetree, Alexandre Torgue, linux-stm32,
linux-kernel
Like for stm32mp15, when stm32 RCC node is used to interact with a secure
context (using clock SCMI protocol), a different path has to be used for
yaml verification.
Signed-off-by: Alexandre Torgue <alexandre.torgue@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
then:
properties:
clocks:
--
2.17.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply related [flat|nested] 10+ messages in thread
* Re: [PATCH] dt-bindings: rcc: stm32: select the "secure" path for stm32mp13
2022-06-13 9:38 ` Alexandre Torgue
@ 2022-06-16 17:55 ` Rob Herring
-1 siblings, 0 replies; 10+ messages in thread
From: Rob Herring @ 2022-06-16 17:55 UTC (permalink / raw)
To: Alexandre Torgue
Cc: Krzysztof Kozlowski, linux-arm-kernel, devicetree, linux-stm32,
linux-kernel
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@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
>
>
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH] dt-bindings: rcc: stm32: select the "secure" path for stm32mp13
@ 2022-06-16 17:55 ` Rob Herring
0 siblings, 0 replies; 10+ messages in thread
From: Rob Herring @ 2022-06-16 17:55 UTC (permalink / raw)
To: Alexandre Torgue
Cc: Krzysztof Kozlowski, linux-arm-kernel, devicetree, linux-stm32,
linux-kernel
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@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
>
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH] dt-bindings: rcc: stm32: select the "secure" path for stm32mp13
2022-06-16 17:55 ` Rob Herring
@ 2022-06-17 7:21 ` Alexandre TORGUE
-1 siblings, 0 replies; 10+ messages in thread
From: Alexandre TORGUE @ 2022-06-17 7:21 UTC (permalink / raw)
To: Rob Herring
Cc: Krzysztof Kozlowski, linux-arm-kernel, devicetree, linux-stm32,
linux-kernel
Hi Rob
On 6/16/22 19:55, Rob Herring wrote:
> 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?
Yes "st,stm32mp1-rcc" is for the STM32MP15.
>
>> context (using clock SCMI protocol), a different path has to be used for
>> yaml verification.
>>
>> Signed-off-by: Alexandre Torgue <alexandre.torgue@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?
Yes. Compare to STM32MP15, the STM32MP13 is by default "secure". In our
case it is "mapped" to OPTEE, using SCMI protocols.
regards
Alex
>
>> then:
>> properties:
>> clocks:
>> --
>> 2.17.1
>>
>>
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH] dt-bindings: rcc: stm32: select the "secure" path for stm32mp13
@ 2022-06-17 7:21 ` Alexandre TORGUE
0 siblings, 0 replies; 10+ messages in thread
From: Alexandre TORGUE @ 2022-06-17 7:21 UTC (permalink / raw)
To: Rob Herring
Cc: Krzysztof Kozlowski, linux-arm-kernel, devicetree, linux-stm32,
linux-kernel
Hi Rob
On 6/16/22 19:55, Rob Herring wrote:
> 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?
Yes "st,stm32mp1-rcc" is for the STM32MP15.
>
>> context (using clock SCMI protocol), a different path has to be used for
>> yaml verification.
>>
>> Signed-off-by: Alexandre Torgue <alexandre.torgue@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?
Yes. Compare to STM32MP15, the STM32MP13 is by default "secure". In our
case it is "mapped" to OPTEE, using SCMI protocols.
regards
Alex
>
>> then:
>> properties:
>> clocks:
>> --
>> 2.17.1
>>
>>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH] dt-bindings: rcc: stm32: select the "secure" path for stm32mp13
2022-06-17 7:21 ` Alexandre TORGUE
@ 2022-06-17 20:38 ` Rob Herring
-1 siblings, 0 replies; 10+ messages in thread
From: Rob Herring @ 2022-06-17 20:38 UTC (permalink / raw)
To: Alexandre TORGUE
Cc: Krzysztof Kozlowski, linux-arm-kernel, devicetree, linux-stm32,
linux-kernel
On Fri, Jun 17, 2022 at 09:21:40AM +0200, Alexandre TORGUE wrote:
> Hi Rob
>
> On 6/16/22 19:55, Rob Herring wrote:
> > 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?
>
> Yes "st,stm32mp1-rcc" is for the STM32MP15.
>
> >
> > > context (using clock SCMI protocol), a different path has to be used for
> > > yaml verification.
> > >
> > > Signed-off-by: Alexandre Torgue <alexandre.torgue@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?
>
> Yes. Compare to STM32MP15, the STM32MP13 is by default "secure". In our case
> it is "mapped" to OPTEE, using SCMI protocols.
Okay,
Acked-by: Rob Herring <robh@kernel.org>
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH] dt-bindings: rcc: stm32: select the "secure" path for stm32mp13
@ 2022-06-17 20:38 ` Rob Herring
0 siblings, 0 replies; 10+ messages in thread
From: Rob Herring @ 2022-06-17 20:38 UTC (permalink / raw)
To: Alexandre TORGUE
Cc: Krzysztof Kozlowski, linux-arm-kernel, devicetree, linux-stm32,
linux-kernel
On Fri, Jun 17, 2022 at 09:21:40AM +0200, Alexandre TORGUE wrote:
> Hi Rob
>
> On 6/16/22 19:55, Rob Herring wrote:
> > 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?
>
> Yes "st,stm32mp1-rcc" is for the STM32MP15.
>
> >
> > > context (using clock SCMI protocol), a different path has to be used for
> > > yaml verification.
> > >
> > > Signed-off-by: Alexandre Torgue <alexandre.torgue@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?
>
> Yes. Compare to STM32MP15, the STM32MP13 is by default "secure". In our case
> it is "mapped" to OPTEE, using SCMI protocols.
Okay,
Acked-by: Rob Herring <robh@kernel.org>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH] dt-bindings: rcc: stm32: select the "secure" path for stm32mp13
2022-06-13 9:38 ` Alexandre Torgue
@ 2022-06-20 15:12 ` Alexandre TORGUE
-1 siblings, 0 replies; 10+ messages in thread
From: Alexandre TORGUE @ 2022-06-20 15:12 UTC (permalink / raw)
To: robh+dt, Krzysztof Kozlowski
Cc: linux-arm-kernel, devicetree, linux-stm32, linux-kernel
On 6/13/22 11:38, Alexandre Torgue wrote:
> Like for stm32mp15, when stm32 RCC node is used to interact with a secure
> context (using clock SCMI protocol), a different path has to be used for
> yaml verification.
>
> Signed-off-by: Alexandre Torgue <alexandre.torgue@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
> then:
> properties:
> clocks:
Applied on stm32-next.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [PATCH] dt-bindings: rcc: stm32: select the "secure" path for stm32mp13
@ 2022-06-20 15:12 ` Alexandre TORGUE
0 siblings, 0 replies; 10+ messages in thread
From: Alexandre TORGUE @ 2022-06-20 15:12 UTC (permalink / raw)
To: robh+dt, Krzysztof Kozlowski
Cc: linux-arm-kernel, devicetree, linux-stm32, linux-kernel
On 6/13/22 11:38, Alexandre Torgue wrote:
> Like for stm32mp15, when stm32 RCC node is used to interact with a secure
> context (using clock SCMI protocol), a different path has to be used for
> yaml verification.
>
> Signed-off-by: Alexandre Torgue <alexandre.torgue@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
> then:
> properties:
> clocks:
Applied on stm32-next.
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2022-06-20 15:19 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-06-13 9:38 [PATCH] dt-bindings: rcc: stm32: select the "secure" path for stm32mp13 Alexandre Torgue
2022-06-13 9:38 ` Alexandre Torgue
2022-06-16 17:55 ` Rob Herring
2022-06-16 17:55 ` Rob Herring
2022-06-17 7:21 ` Alexandre TORGUE
2022-06-17 7:21 ` Alexandre TORGUE
2022-06-17 20:38 ` Rob Herring
2022-06-17 20:38 ` Rob Herring
2022-06-20 15:12 ` Alexandre TORGUE
2022-06-20 15:12 ` Alexandre TORGUE
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.