From: Rob Herring <robh@kernel.org>
To: Alexandre Torgue <alexandre.torgue@foss.st.com>
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: rcc: stm32: select the "secure" path for stm32mp13
Date: Thu, 16 Jun 2022 11:55:31 -0600 [thread overview]
Message-ID: <20220616175531.GA3716982-robh@kernel.org> (raw)
In-Reply-To: <20220613093815.18334-1-alexandre.torgue@foss.st.com>
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
>
>
next prev parent reply other threads:[~2022-06-16 17:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 9:38 [PATCH] dt-bindings: rcc: stm32: select the "secure" path for stm32mp13 Alexandre Torgue
2022-06-16 17:55 ` Rob Herring [this message]
2022-06-17 7:21 ` Alexandre TORGUE
2022-06-17 20:38 ` Rob Herring
2022-06-20 15:12 ` Alexandre TORGUE
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=20220616175531.GA3716982-robh@kernel.org \
--to=robh@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
/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;
as well as URLs for NNTP newsgroup(s).