From: Antonio Borneo <antonio.borneo@foss.st.com>
To: 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>,
<devicetree@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Cc: Amelie Delaunay <amelie.delaunay@foss.st.com>
Subject: Re: [PATCH 0/3] ARM/arm64: dts: stm32: align watchdog DT support accross STM32MP15 platforms
Date: Fri, 9 Oct 2026 11:22:50 +0200 [thread overview]
Message-ID: <a40c8b88f6da867f5c5411f9a4ca7ec5326cc364.camel@foss.st.com> (raw)
In-Reply-To: <20261007151358.1166329-1-antonio.borneo@foss.st.com>
On Wed, 2026-10-07 at 17:13 +0200, Antonio Borneo wrote:
> This series updates STM32MP watchdog DT descriptions to keep them aligned
> with the actual secure/non-secure watchdog integration used on each
> platform family.
>
> Two watchdog access models are used:
> - On ST STM32MP15 non-SCMI boards, IWDG1 is exposed as a non-secure
> watchdog. In that case Linux must register the watchdog device and keep
> it pinged once it has been started by the boot chain.
> - On ST SCMI-based STM32MP15 boards, the watchdog is handled through
> secure world services and exposed to Linux through the ARM SMC watchdog
> interface.
>
>
> Amelie Delaunay (2):
> ARM: dts: stm32: enable iwdg1 on STM32MP15 ST boards
> ARM: dts: stm32: enable ARM SMC watchdog on STM32MP15 SCMI boards
>
> Antonio Borneo (1):
> ARM: dts: stm32: move ARM SMC watchdog to STM32MP151 SoC
>
> arch/arm/boot/dts/st/stm32mp15-scmi.dtsi | 4 ++++
> arch/arm/boot/dts/st/stm32mp151.dtsi | 15 +++++++++++++++
> arch/arm/boot/dts/st/stm32mp157a-dk1-scmi.dts | 5 +++++
> arch/arm/boot/dts/st/stm32mp157c-dk2-scmi.dts | 5 +++++
> arch/arm/boot/dts/st/stm32mp157c-ed1-scmi.dts | 5 +++++
> arch/arm/boot/dts/st/stm32mp157c-ed1.dts | 5 +++++
> arch/arm/boot/dts/st/stm32mp157c-ev1-scmi.dts | 5 +++++
> arch/arm/boot/dts/st/stm32mp157f-dk2-scmi.dtsi | 7 -------
> arch/arm/boot/dts/st/stm32mp15xx-dkx.dtsi | 5 +++++
> 9 files changed, 49 insertions(+), 7 deletions(-)
>
>
> base-commit: f831584128ac2a36fb4fa62fe106793d08c2dbf1
Please discard this series. I will send a V2 asap.
Sorry for the noise!
Antonio Borneo
prev parent reply other threads:[~2026-10-09 9:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 15:13 [PATCH 0/3] ARM/arm64: dts: stm32: align watchdog DT support accross STM32MP15 platforms Antonio Borneo
2026-10-07 15:13 ` [PATCH 1/3] ARM: dts: stm32: enable iwdg1 on STM32MP15 ST boards Antonio Borneo
2026-10-07 15:13 ` [PATCH 2/3] ARM: dts: stm32: move ARM SMC watchdog to STM32MP151 SoC Antonio Borneo
2026-10-07 15:13 ` [PATCH 3/3] ARM: dts: stm32: enable ARM SMC watchdog on STM32MP15 SCMI boards Antonio Borneo
2026-10-09 9:22 ` Antonio Borneo [this message]
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=a40c8b88f6da867f5c5411f9a4ca7ec5326cc364.camel@foss.st.com \
--to=antonio.borneo@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=amelie.delaunay@foss.st.com \
--cc=conor+dt@kernel.org \
--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 \
--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