From: Marek Vasut <marex@denx.de>
To: gabriel.fernandez@foss.st.com,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@st.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Etienne Carriere <etienne.carriere@st.com>
Cc: linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Etienne Carriere <etienne.carriere@foss.st.com>
Subject: Re: [PATCH v3 10/11] dt-bindings: clock: stm32mp1 new compatible for secure rcc
Date: Tue, 20 Apr 2021 20:30:20 +0200 [thread overview]
Message-ID: <36aafe68-d313-692a-a551-4ff4147e584c@denx.de> (raw)
In-Reply-To: <20210419093852.14978-11-gabriel.fernandez@foss.st.com>
On 4/19/21 11:38 AM, gabriel.fernandez@foss.st.com wrote:
> From: Gabriel Fernandez <gabriel.fernandez@foss.st.com>
>
> Introduce new compatible string "st,stm32mp1-rcc-secure" for
> stm32mp1 clock driver when the device is configured with RCC
> security support hardened.
>
> Signed-off-by: Etienne Carriere <etienne.carriere@foss.st.com>
> Signed-off-by: Gabriel Fernandez <gabriel.fernandez@foss.st.com>
> ---
> .../devicetree/bindings/clock/st,stm32mp1-rcc.yaml | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/clock/st,stm32mp1-rcc.yaml b/Documentation/devicetree/bindings/clock/st,stm32mp1-rcc.yaml
> index 4e385508f516..8b1ecb2ecdd5 100644
> --- a/Documentation/devicetree/bindings/clock/st,stm32mp1-rcc.yaml
> +++ b/Documentation/devicetree/bindings/clock/st,stm32mp1-rcc.yaml
> @@ -54,7 +54,9 @@ properties:
>
> compatible:
> items:
> - - const: st,stm32mp1-rcc
> + - enum:
> + - st,stm32mp1-rcc-secure
> + - st,stm32mp1-rcc
It is still the same IP and same SoC silicon, so shouldn't the
configuration be discerned via DT property instead of compatible string ?
WARNING: multiple messages have this Message-ID (diff)
From: Marek Vasut <marex@denx.de>
To: gabriel.fernandez@foss.st.com,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@st.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Etienne Carriere <etienne.carriere@st.com>
Cc: linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Etienne Carriere <etienne.carriere@foss.st.com>
Subject: Re: [PATCH v3 10/11] dt-bindings: clock: stm32mp1 new compatible for secure rcc
Date: Tue, 20 Apr 2021 20:30:20 +0200 [thread overview]
Message-ID: <36aafe68-d313-692a-a551-4ff4147e584c@denx.de> (raw)
In-Reply-To: <20210419093852.14978-11-gabriel.fernandez@foss.st.com>
On 4/19/21 11:38 AM, gabriel.fernandez@foss.st.com wrote:
> From: Gabriel Fernandez <gabriel.fernandez@foss.st.com>
>
> Introduce new compatible string "st,stm32mp1-rcc-secure" for
> stm32mp1 clock driver when the device is configured with RCC
> security support hardened.
>
> Signed-off-by: Etienne Carriere <etienne.carriere@foss.st.com>
> Signed-off-by: Gabriel Fernandez <gabriel.fernandez@foss.st.com>
> ---
> .../devicetree/bindings/clock/st,stm32mp1-rcc.yaml | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/clock/st,stm32mp1-rcc.yaml b/Documentation/devicetree/bindings/clock/st,stm32mp1-rcc.yaml
> index 4e385508f516..8b1ecb2ecdd5 100644
> --- a/Documentation/devicetree/bindings/clock/st,stm32mp1-rcc.yaml
> +++ b/Documentation/devicetree/bindings/clock/st,stm32mp1-rcc.yaml
> @@ -54,7 +54,9 @@ properties:
>
> compatible:
> items:
> - - const: st,stm32mp1-rcc
> + - enum:
> + - st,stm32mp1-rcc-secure
> + - st,stm32mp1-rcc
It is still the same IP and same SoC silicon, so shouldn't the
configuration be discerned via DT property instead of compatible string ?
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-04-20 18:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-19 9:38 [PATCH v3 00/11] Introduce STM32MP1 RCC in secured mode gabriel.fernandez
2021-04-19 9:38 ` gabriel.fernandez
2021-04-19 9:38 ` [PATCH v3 01/11] clk: stm32mp1: merge 'clk-hsi-div' and 'ck_hsi' into one clock gabriel.fernandez
2021-04-19 9:38 ` gabriel.fernandez
2021-04-19 9:38 ` [PATCH v3 02/11] clk: stm32mp1: merge 'ck_hse_rtc' and 'ck_rtc' " gabriel.fernandez
2021-04-19 9:38 ` gabriel.fernandez
2021-04-19 9:38 ` [PATCH v3 03/11] clk: stm32mp1: remove intermediate pll clocks gabriel.fernandez
2021-04-19 9:38 ` gabriel.fernandez
2021-04-19 9:38 ` [PATCH v3 04/11] clk: stm32mp1: convert to module driver gabriel.fernandez
2021-04-19 9:38 ` gabriel.fernandez
2021-04-19 9:38 ` [PATCH v3 05/11] clk: stm32mp1: move RCC reset controller into RCC clock driver gabriel.fernandez
2021-04-19 9:38 ` gabriel.fernandez
2021-04-19 9:38 ` [PATCH v3 06/11] reset: stm32mp1: remove stm32mp1 reset gabriel.fernandez
2021-04-19 9:38 ` gabriel.fernandez
2021-04-19 9:38 ` [PATCH v3 07/11] dt-bindings: clock: add IDs for SCMI clocks on stm32mp15 gabriel.fernandez
2021-04-19 9:38 ` gabriel.fernandez
2021-04-19 9:38 ` [PATCH v3 08/11] dt-bindings: reset: add IDs for SCMI reset domains " gabriel.fernandez
2021-04-19 9:38 ` gabriel.fernandez
2021-04-19 9:38 ` [PATCH v3 09/11] dt-bindings: reset: add MCU HOLD BOOT ID " gabriel.fernandez
2021-04-19 9:38 ` gabriel.fernandez
2021-04-19 9:38 ` [PATCH v3 10/11] dt-bindings: clock: stm32mp1 new compatible for secure rcc gabriel.fernandez
2021-04-19 9:38 ` gabriel.fernandez
2021-04-20 16:25 ` Rob Herring
2021-04-20 16:25 ` Rob Herring
2021-04-20 18:30 ` Marek Vasut [this message]
2021-04-20 18:30 ` Marek Vasut
2021-04-19 9:38 ` [PATCH v3 11/11] clk: stm32mp1: new compatible for secure RCC support gabriel.fernandez
2021-04-19 9:38 ` gabriel.fernandez
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=36aafe68-d313-692a-a551-4ff4147e584c@denx.de \
--to=marex@denx.de \
--cc=alexandre.torgue@st.com \
--cc=devicetree@vger.kernel.org \
--cc=etienne.carriere@foss.st.com \
--cc=etienne.carriere@st.com \
--cc=gabriel.fernandez@foss.st.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=mturquette@baylibre.com \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
/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 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.