From: Krzysztof Kozlowski <krzk@kernel.org>
To: Gatien Chevallier <gatien.chevallier@foss.st.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>
Cc: devicetree@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/7] arm64: dts: st: add RISAB1/2/3/4/5/6 nodes to stm32mp251.dtsi
Date: Tue, 10 Feb 2026 08:51:13 +0100 [thread overview]
Message-ID: <c4212679-9e39-47d0-8a53-62427e2ef7aa@kernel.org> (raw)
In-Reply-To: <20260209-stm32_risab-v1-3-ef0b2b6a7e0a@foss.st.com>
On 09/02/2026 15:59, Gatien Chevallier wrote:
> Add RISAB1/2/3/4/5/6 nodes to the stm32mp251.dtsi device tree SoC
> file.
And what is RISAB?
>
> Signed-off-by: Gatien Chevallier <gatien.chevallier@foss.st.com>
> ---
> arch/arm64/boot/dts/st/stm32mp251.dtsi | 48 ++++++++++++++++++++++++++++++++++
> 1 file changed, 48 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/st/stm32mp251.dtsi b/arch/arm64/boot/dts/st/stm32mp251.dtsi
> index a8e6e0f77b83..e9d8338b2017 100644
> --- a/arch/arm64/boot/dts/st/stm32mp251.dtsi
> +++ b/arch/arm64/boot/dts/st/stm32mp251.dtsi
> @@ -1733,6 +1733,54 @@ pcie@0,0 {
> };
> };
>
> + risab1: risab@420f0000 {
It appears here as node name as well, so it must be a generic name, but
I do not recall it in DT spec or my knowledge.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-02-10 7:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 14:59 [PATCH 0/7] soc: st: add RISAB dump debug driver Gatien Chevallier
2026-02-09 14:59 ` [PATCH 1/7] dt-bindings: soc: st: document the RISAB firewall peripheral Gatien Chevallier
2026-02-10 7:57 ` Krzysztof Kozlowski
2026-02-10 9:55 ` Gatien CHEVALLIER
2026-02-13 15:06 ` Krzysztof Kozlowski
2026-02-17 13:12 ` Gatien CHEVALLIER
2026-02-17 20:06 ` Krzysztof Kozlowski
2026-02-18 10:38 ` Gatien CHEVALLIER
2026-02-18 20:03 ` Krzysztof Kozlowski
2026-02-19 14:02 ` Gatien CHEVALLIER
2026-02-26 18:13 ` Krzysztof Kozlowski
2026-03-02 15:09 ` Gatien CHEVALLIER
2026-03-06 8:33 ` Gatien CHEVALLIER
2026-02-09 14:59 ` [PATCH 2/7] soc: st: add RISAB dump debug driver Gatien Chevallier
2026-02-10 7:50 ` Krzysztof Kozlowski
2026-02-10 9:57 ` Gatien CHEVALLIER
2026-02-09 14:59 ` [PATCH 3/7] arm64: dts: st: add RISAB1/2/3/4/5/6 nodes to stm32mp251.dtsi Gatien Chevallier
2026-02-10 7:51 ` Krzysztof Kozlowski [this message]
2026-02-10 9:58 ` Gatien CHEVALLIER
2026-02-09 14:59 ` [PATCH 4/7] arm64: dts: st: add RISAB1/2/3/4/5/6 nodes to stm32mp231.dtsi Gatien Chevallier
2026-02-09 14:59 ` [PATCH 5/7] arm64: dts: st: enable all RISAB instances on the stm32mp257f-ev1 board Gatien Chevallier
2026-02-09 14:59 ` [PATCH 6/7] arm64: dts: st: enable all RISAB instances on the stm32mp257f-dk board Gatien Chevallier
2026-02-09 14:59 ` [PATCH 7/7] arm64: dts: st: enable all RISAB instances on the stm32mp235f-dk board Gatien Chevallier
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=c4212679-9e39-47d0-8a53-62427e2ef7aa@kernel.org \
--to=krzk@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gatien.chevallier@foss.st.com \
--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 \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox