From: Gatien Chevallier <gatien.chevallier@foss.st.com>
To: "Suzuki K Poulose" <suzuki.poulose@arm.com>,
"Mike Leach" <mike.leach@linaro.org>,
"James Clark" <james.clark@linaro.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Mathieu Poirier" <mathieu.poirier@linaro.org>,
"Leo Yan" <leo.yan@linux.dev>,
"Clément Le Goffic" <legoffic.clement@gmail.com>,
"Linus Walleij" <linusw@kernel.org>,
"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
"Alexandre Torgue" <alexandre.torgue@foss.st.com>
Cc: <coresight@lists.linaro.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-gpio@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
Gatien Chevallier <gatien.chevallier@foss.st.com>,
Antonio Borneo <antonio.borneo@foss.st.com>
Subject: [PATCH 00/11] bus: add stm32 debug bus and coresight support for stm32mp1x platforms
Date: Fri, 9 Jan 2026 11:55:00 +0100 [thread overview]
Message-ID: <20260109-debug_bus-v1-0-8f2142b5a738@foss.st.com> (raw)
Stm32 SoCs embed debug peripherals such as Coresight. These peripherals
can monitor the activity of the cores. Because of that, they can be
used only if some features in the debug configuration are enabled.
Else, errors or firewall exceptions can be observed. Similarly to
the ETZPC(on stm32mp1x platforms) or the RIFSC(on stm32mp2x platforms),
debug-related peripherals access can be assessed at bus level to
prevent these issues from happening.
The debug configuration can only be accessed by the secure world.
That means that a service must be implemented in the secure world for
the kernel to check the firewall configuration. On OpenSTLinux, it is
done through a Debug access PTA in OP-TEE [1].
To represent the debug peripherals present on a dedicated debug bus,
create a debug bus node in the device tree and the associated driver
that will interact with this PTA.
[1]: https://github.com/OP-TEE/optee_os/pull/7673
Signed-off-by: Gatien Chevallier <gatien.chevallier@foss.st.com>
---
Gatien Chevallier (11):
dt-bindings: document access-controllers property for coresight peripherals
dt-bindings: pinctrl: document access-controllers property for stm32 HDP
dt-bindings: bus: document the stm32 debug bus
bus: stm32_firewall: allow check on different firewall controllers
drivers: bus: add the stm32 debug bus driver
arm: dts: stm32: introduce the debug bus for stm32mp1x platforms
arm: dts: stm32: enable the debug bus on stm32mp1x boards
arm: dts: stm32: enable CoreSight on stm32mp15xx-dkx boards
arm: dts: stm32: enable CoreSight on the stm32mp157c-ev1 board
arm: dts: stm32: enable CoreSight on the stm32mp135f-dk board
pinctrl: stm32: add firewall checks before probing the HDP driver
.../devicetree/bindings/arm/arm,coresight-cti.yaml | 3 +
.../devicetree/bindings/arm/arm,coresight-etm.yaml | 3 +
.../devicetree/bindings/arm/arm,coresight-tmc.yaml | 3 +
.../bindings/arm/arm,coresight-tpiu.yaml | 3 +
.../bindings/bus/st,stm32mp131-dbg-bus.yaml | 86 +++++++
.../devicetree/bindings/pinctrl/st,stm32-hdp.yaml | 4 +
MAINTAINERS | 1 +
arch/arm/boot/dts/st/stm32mp131.dtsi | 119 +++++++++
arch/arm/boot/dts/st/stm32mp135f-dk.dts | 24 ++
arch/arm/boot/dts/st/stm32mp151.dtsi | 173 +++++++++++++
arch/arm/boot/dts/st/stm32mp153.dtsi | 68 +++++
arch/arm/boot/dts/st/stm32mp157c-ev1.dts | 40 +++
arch/arm/boot/dts/st/stm32mp15xx-dkx.dtsi | 40 +++
drivers/bus/Kconfig | 10 +
drivers/bus/Makefile | 1 +
drivers/bus/stm32_dbg_bus.c | 285 +++++++++++++++++++++
drivers/bus/stm32_firewall.c | 2 +-
drivers/pinctrl/stm32/pinctrl-stm32-hdp.c | 41 +++
18 files changed, 905 insertions(+), 1 deletion(-)
---
base-commit: 9ace4753a5202b02191d54e9fdf7f9e3d02b85eb
change-id: 20260108-debug_bus-392666c7a3aa
Best regards,
--
Gatien Chevallier <gatien.chevallier@foss.st.com>
next reply other threads:[~2026-01-09 10:56 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 10:55 Gatien Chevallier [this message]
2026-01-09 10:55 ` [PATCH 01/11] dt-bindings: document access-controllers property for coresight peripherals Gatien Chevallier
2026-01-09 10:55 ` [PATCH 02/11] dt-bindings: pinctrl: document access-controllers property for stm32 HDP Gatien Chevallier
2026-01-11 11:27 ` Krzysztof Kozlowski
2026-01-12 8:24 ` Gatien CHEVALLIER
2026-01-12 16:10 ` Krzysztof Kozlowski
2026-01-09 10:55 ` [PATCH 03/11] dt-bindings: bus: document the stm32 debug bus Gatien Chevallier
2026-01-11 11:27 ` Krzysztof Kozlowski
2026-01-12 9:06 ` Gatien CHEVALLIER
2026-01-09 10:55 ` [PATCH 04/11] bus: stm32_firewall: allow check on different firewall controllers Gatien Chevallier
2026-01-09 10:55 ` [PATCH 05/11] drivers: bus: add the stm32 debug bus driver Gatien Chevallier
2026-01-11 11:27 ` Krzysztof Kozlowski
2026-01-12 9:13 ` Gatien CHEVALLIER
2026-01-13 14:45 ` Jens Wiklander
2026-01-13 16:09 ` Gatien CHEVALLIER
2026-01-14 6:53 ` Jens Wiklander
2026-01-09 10:55 ` [PATCH 06/11] arm: dts: stm32: introduce the debug bus for stm32mp1x platforms Gatien Chevallier
2026-01-09 10:55 ` [PATCH 07/11] arm: dts: stm32: enable the debug bus on stm32mp1x boards Gatien Chevallier
2026-01-09 10:55 ` [PATCH 08/11] arm: dts: stm32: enable CoreSight on stm32mp15xx-dkx boards Gatien Chevallier
2026-01-09 10:55 ` [PATCH 09/11] arm: dts: stm32: enable CoreSight on the stm32mp157c-ev1 board Gatien Chevallier
2026-01-09 10:55 ` [PATCH 10/11] arm: dts: stm32: enable CoreSight on the stm32mp135f-dk board Gatien Chevallier
2026-01-09 10:55 ` [PATCH 11/11] pinctrl: stm32: add firewall checks before probing the HDP driver Gatien Chevallier
2026-01-09 23:10 ` [PATCH 00/11] bus: add stm32 debug bus and coresight support for stm32mp1x platforms Linus Walleij
2026-01-12 15:56 ` Gatien CHEVALLIER
2026-01-12 15:17 ` Rob Herring
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=20260109-debug_bus-v1-0-8f2142b5a738@foss.st.com \
--to=gatien.chevallier@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=antonio.borneo@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=coresight@lists.linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=james.clark@linaro.org \
--cc=krzk+dt@kernel.org \
--cc=legoffic.clement@gmail.com \
--cc=leo.yan@linux.dev \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mathieu.poirier@linaro.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=mike.leach@linaro.org \
--cc=robh@kernel.org \
--cc=suzuki.poulose@arm.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®