mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marek Vasut <marex@nabladev.com>
To: mateusz.nowicki@posteo.net, Arnd Bergmann <arnd@arndb.de>
Cc: Alexandre Torgue <alexandre.torgue@foss.st.com>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	Thomas BOURGOIN <thomas.bourgoin@st.com>,
	Rob Herring <robh@kernel.org>,
	krzk+dt@kernel.org, Conor Dooley <conor+dt@kernel.org>,
	Lionel DEBIEVE <lionel.debieve@foss.st.com>,
	Amelie DELAUNAY <amelie.delaunay@foss.st.com>,
	Patrice Chotard <patrice.chotard@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, kernel <kernel@dh-electronics.com>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	"laurent.pinchart" <laurent.pinchart@ideasonboard.com>,
	Fabrice GASNIER <fabrice.gasnier@foss.st.com>,
	Stefano Babic <sbabic@nabladev.com>,
	Etienne Carriere <etienne.carriere@foss.st.com>
Subject: Re: [PATCH] arm64: dts: st: fix arm,smc-id of the SMC watchdog on stm32mp2
Date: Sat, 31 Oct 2026 14:35:11 +0100	[thread overview]
Message-ID: <7ff5f937-144b-41fc-ab0d-82271a01dde1@nabladev.com> (raw)
In-Reply-To: <f7010f07fdcdb4ff04a0dbfac1cc5421@posteo.net>

On 10/31/26 1:00 PM, mateusz.nowicki@posteo.net wrote:

Hello Mateusz,

> Marek, would that work for the DHCOS boards? I can send the patch if
> you tell me which of them ship the old OP-TEE. Your OP-TEE change to
> accept both IDs is a good mitigation on top of it for anybody who
> updates the firmware.

I do not think revert of this patch is the right approach here. I also 
do not think patching the arm,smc-id in board DT is the right approach. 
Both of those, because we do not know which SMC ID is the correct one 
(we do not know which firmware is running and how it is configured, see 
the OP-TEE OS CFG_WDT_SM_HANDLER_ID which is user configurable, and as 
far as I can tell, the SMC ID is not discoverable, or is it?).

But maybe there is some way to probe for the correct ARM SMC WDT ID ? (I 
do not think we can infer the ID from e.g. OP-TEE OS version, because of 
the CFG_WDT_SM_HANDLER_ID user configuration).

In case of this SoC, we can mostly assume that the SMC IDs will be one 
of the two, 0xb200005a or 0xbc000000, so maybe we can extend the SMC WDT 
driver to support some sort of fallback -- if the primary SMC ID fails 
as not supported, try the secondary one ?

As for the DHCOS boards, those are evalboards, their bootloader can be 
easily updated, and they are running recent software more often than 
not, there this topic is mostly a non-issue. There is however hardware 
which does have downstream DTs which pull in upstream DTSIs .

      reply	other threads:[~2026-10-31 13:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-07  9:14 Mateusz Nowicki
2026-09-08  8:52 ` [Linux-stm32] [PATCH] arm64: dts: st: fix arm, smc-id " Antonio Borneo
2026-09-23 11:52 ` [PATCH] arm64: dts: st: fix arm,smc-id " Mateusz Nowicki
2026-09-28  8:45 ` Alexandre TORGUE
2026-10-31  5:59   ` Marek Vasut
2026-10-31  8:45     ` Arnd Bergmann
2026-10-31 12:00       ` mateusz.nowicki
2026-10-31 13:35         ` Marek Vasut [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=7ff5f937-144b-41fc-ab0d-82271a01dde1@nabladev.com \
    --to=marex@nabladev.com \
    --cc=alexandre.torgue@foss.st.com \
    --cc=amelie.delaunay@foss.st.com \
    --cc=arnd@arndb.de \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=etienne.carriere@foss.st.com \
    --cc=fabrice.gasnier@foss.st.com \
    --cc=geert+renesas@glider.be \
    --cc=kernel@dh-electronics.com \
    --cc=krzk+dt@kernel.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=lionel.debieve@foss.st.com \
    --cc=mateusz.nowicki@posteo.net \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=patrice.chotard@foss.st.com \
    --cc=robh@kernel.org \
    --cc=sbabic@nabladev.com \
    --cc=thomas.bourgoin@st.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

all inboxes | Powered by JetHome®