From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: "Gatien Chevallier" <gatien.chevallier@foss.st.com>,
"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>,
cristian.marussi@arm.com, jens.wiklander@linaro.org,
etienne.carriere@foss.st.com,
"Sudeep Holla" <sudeep.holla@kernel.org>
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>,
Antonio Borneo <antonio.borneo@foss.st.com>
Subject: Re: [PATCH v6 00/12] bus: add stm32 debug bus and coresight support for stm32mp1x platforms
Date: Tue, 10 Mar 2026 10:07:24 +0100 [thread overview]
Message-ID: <ed019efc-d1e0-4e77-bf9c-79da40f0c707@foss.st.com> (raw)
In-Reply-To: <20260226-debug_bus-v6-0-5d794697798d@foss.st.com>
Hi
On 2/26/26 11:30, Gatien Chevallier wrote:
> 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>
> ---
> Changes in v6:
> - Fix use of platform_driver_register() in probe of the stm32 debug bus
> (unusable since dc23806a7c47 ("driver core: enforce device_lock for driver_match_device()"))
> - Added all review tags
> - Link to v5: https://lore.kernel.org/r/20260123-debug_bus-v5-0-90b670844241@foss.st.com
>
...
>
> ---
> Gatien Chevallier (12):
> 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
> bus: stm32_firewall: add stm32_firewall_get_grant_all_access() API
> 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
>
Patch 1 to 11 applied on stm32-next. Linus, let me know if I take the
pinctrl one or you prefer to take it.
regards
Alex
next prev parent reply other threads:[~2026-03-10 9:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 10:30 [PATCH v6 00/12] bus: add stm32 debug bus and coresight support for stm32mp1x platforms Gatien Chevallier
2026-02-26 10:30 ` [PATCH v6 01/12] dt-bindings: document access-controllers property for coresight peripherals Gatien Chevallier
2026-02-26 10:46 ` Suzuki K Poulose
2026-02-26 10:54 ` Gatien CHEVALLIER
2026-02-26 11:05 ` Suzuki K Poulose
2026-02-26 10:30 ` [PATCH v6 02/12] dt-bindings: pinctrl: document access-controllers property for stm32 HDP Gatien Chevallier
2026-02-26 10:30 ` [PATCH v6 03/12] dt-bindings: bus: document the stm32 debug bus Gatien Chevallier
2026-02-26 10:30 ` [PATCH v6 04/12] bus: stm32_firewall: allow check on different firewall controllers Gatien Chevallier
2026-02-26 10:30 ` [PATCH v6 05/12] bus: stm32_firewall: add stm32_firewall_get_grant_all_access() API Gatien Chevallier
2026-02-26 10:30 ` [PATCH v6 06/12] drivers: bus: add the stm32 debug bus driver Gatien Chevallier
2026-02-26 10:30 ` [PATCH v6 07/12] arm: dts: stm32: introduce the debug bus for stm32mp1x platforms Gatien Chevallier
2026-02-26 10:30 ` [PATCH v6 08/12] arm: dts: stm32: enable the debug bus on stm32mp1x boards Gatien Chevallier
2026-02-26 10:30 ` [PATCH v6 09/12] arm: dts: stm32: enable CoreSight on stm32mp15xx-dkx boards Gatien Chevallier
2026-02-26 10:30 ` [PATCH v6 10/12] arm: dts: stm32: enable CoreSight on the stm32mp157c-ev1 board Gatien Chevallier
2026-02-26 10:30 ` [PATCH v6 11/12] arm: dts: stm32: enable CoreSight on the stm32mp135f-dk board Gatien Chevallier
2026-02-26 10:30 ` [PATCH v6 12/12] pinctrl: stm32: add firewall checks before probing the HDP driver Gatien Chevallier
2026-03-06 10:33 ` [PATCH v6 00/12] bus: add stm32 debug bus and coresight support for stm32mp1x platforms Alexandre TORGUE
2026-03-10 9:07 ` Alexandre TORGUE [this message]
2026-03-11 9:28 ` Linus Walleij
2026-03-12 12:10 ` Alexandre TORGUE
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=ed019efc-d1e0-4e77-bf9c-79da40f0c707@foss.st.com \
--to=alexandre.torgue@foss.st.com \
--cc=antonio.borneo@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=coresight@lists.linaro.org \
--cc=cristian.marussi@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=etienne.carriere@foss.st.com \
--cc=gatien.chevallier@foss.st.com \
--cc=james.clark@linaro.org \
--cc=jens.wiklander@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=sudeep.holla@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