From: Gatien CHEVALLIER <gatien.chevallier@foss.st.com>
To: <Oleksii_Moisieiev@epam.com>, <gregkh@linuxfoundation.org>,
<herbert@gondor.apana.org.au>, <davem@davemloft.net>,
<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<alexandre.torgue@foss.st.com>, <vkoul@kernel.org>,
<jic23@kernel.org>, <olivier.moysan@foss.st.com>,
<arnaud.pouliquen@foss.st.com>, <mchehab@kernel.org>,
<fabrice.gasnier@foss.st.com>, <ulf.hansson@linaro.org>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>
Cc: <linux-crypto@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <dmaengine@vger.kernel.org>,
<linux-i2c@vger.kernel.org>, <linux-iio@vger.kernel.org>,
<alsa-devel@alsa-project.org>, <linux-media@vger.kernel.org>,
<linux-mmc@vger.kernel.org>, <netdev@vger.kernel.org>,
<linux-phy@lists.infradead.org>, <linux-serial@vger.kernel.org>,
<linux-spi@vger.kernel.org>, <linux-usb@vger.kernel.org>
Subject: Re: [PATCH v3 0/6] Introduce STM32 system bus
Date: Wed, 5 Jul 2023 19:35:07 +0200 [thread overview]
Message-ID: <f8c6e86d-af6a-b61f-c642-c23cb3cfb015@foss.st.com> (raw)
In-Reply-To: <20230127164040.1047583-1-gatien.chevallier@foss.st.com>
Hello all,
I'm abandoning this series for:
https://lore.kernel.org/lkml/20230705172759.1610753
Sorry for the noise.
Best regards,
Gatien
On 1/27/23 17:40, Gatien Chevallier wrote:
> Document STM32 System Bus. This bus is intended to control firewall
> access for the peripherals connected to it.
>
> For every peripheral, the bus checks the firewall registers to see
> if the peripheral is configured as non-secure. If the peripheral
> is configured as secure, the node is marked populated, so the
> device won't be probed.
>
> This is useful as a firewall configuration sanity check and avoid
> platform crashes in case peripherals are incorrectly configured.
>
> The STM32 System Bus implements the feature-domain-controller
> bindings. It is used by peripherals to reference a domain
> controller, in this case the firewall feature domain.
> The bus uses the ID referenced by the feature-domains property to
> know where to look in the firewall to get the security configuration
> for the peripheral. This allows a device tree description rather
> than a hardcoded peripheral table in the bus driver.
>
> On STM32MP13/15 platforms, the firewall bus is represented by the
> ETZPC node, which is responsible for the securing / MCU isolating
> the capable peripherals.
>
> STM32MP13/15 device trees are updated in this series to implement
> the bus. All peripherals that are securable or MCU isolation capable
> by the ETZPC are connected to the bus.
>
> Changes in V2:
> - Corrected YAMLS errors highlighted by Rob's robot
> - Re-ordered Signed-off-by tags in two patches
>
> Changes in V3:
> - Document feature-domains property in YAML documentation for
> concerned periperals under the System Bus
> - Fix STM32 System Bus YAML documentation
> - Remove STM32 System bus bindings that were currently used
> as helpers for device tree
> - Correct few errors in driver
> - Add missing peripherals under the System Bus that were in
> SoC variation device tree files
> - Fix node names
>
> Gatien Chevallier (5):
> dt-bindings: treewide: add feature-domains description in binding
> files
> dt-bindings: bus: add STM32 System Bus
> bus: stm32_sys_bus: add support for STM32MP15 and STM32MP13 system bus
> ARM: dts: stm32: add ETZPC as a system bus for STM32MP15x boards
> ARM: dts: stm32: add ETZPC as a system bus for STM32MP13x boards
>
> Oleksii Moisieiev (1):
> dt-bindings: Document common device controller bindings
>
> .../devicetree/bindings/bus/st,sys-bus.yaml | 127 +
> .../bindings/crypto/st,stm32-hash.yaml | 5 +
> .../devicetree/bindings/dma/st,stm32-dma.yaml | 5 +
> .../bindings/dma/st,stm32-dmamux.yaml | 5 +
> .../feature-domain-controller.yaml | 84 +
> .../devicetree/bindings/i2c/st,stm32-i2c.yaml | 5 +
> .../bindings/iio/adc/st,stm32-adc.yaml | 5 +
> .../bindings/iio/adc/st,stm32-dfsdm-adc.yaml | 5 +
> .../bindings/iio/dac/st,stm32-dac.yaml | 5 +
> .../bindings/media/st,stm32-cec.yaml | 5 +
> .../bindings/media/st,stm32-dcmi.yaml | 5 +
> .../memory-controllers/st,stm32-fmc2-ebi.yaml | 5 +
> .../bindings/mfd/st,stm32-lptimer.yaml | 5 +
> .../bindings/mfd/st,stm32-timers.yaml | 6 +
> .../devicetree/bindings/mmc/arm,pl18x.yaml | 5 +
> .../devicetree/bindings/net/stm32-dwmac.yaml | 5 +
> .../bindings/phy/phy-stm32-usbphyc.yaml | 5 +
> .../bindings/regulator/st,stm32-vrefbuf.yaml | 5 +
> .../devicetree/bindings/rng/st,stm32-rng.yaml | 5 +
> .../bindings/serial/st,stm32-uart.yaml | 5 +
> .../bindings/sound/st,stm32-i2s.yaml | 5 +
> .../bindings/sound/st,stm32-sai.yaml | 5 +
> .../bindings/sound/st,stm32-spdifrx.yaml | 5 +
> .../bindings/spi/st,stm32-qspi.yaml | 5 +
> .../devicetree/bindings/spi/st,stm32-spi.yaml | 5 +
> .../devicetree/bindings/usb/dwc2.yaml | 5 +
> MAINTAINERS | 6 +
> arch/arm/boot/dts/stm32mp131.dtsi | 407 +--
> arch/arm/boot/dts/stm32mp133.dtsi | 51 +-
> arch/arm/boot/dts/stm32mp13xc.dtsi | 19 +-
> arch/arm/boot/dts/stm32mp13xf.dtsi | 18 +-
> arch/arm/boot/dts/stm32mp151.dtsi | 2722 +++++++++--------
> arch/arm/boot/dts/stm32mp153.dtsi | 52 +-
> arch/arm/boot/dts/stm32mp15xc.dtsi | 19 +-
> drivers/bus/Kconfig | 9 +
> drivers/bus/Makefile | 1 +
> drivers/bus/stm32_sys_bus.c | 168 +
> 37 files changed, 2208 insertions(+), 1596 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/bus/st,sys-bus.yaml
> create mode 100644 Documentation/devicetree/bindings/feature-controllers/feature-domain-controller.yaml
> create mode 100644 drivers/bus/stm32_sys_bus.c
>
prev parent reply other threads:[~2023-07-05 17:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 16:40 [PATCH v3 0/6] Introduce STM32 system bus Gatien Chevallier
2023-01-27 16:40 ` [PATCH v3 1/6] dt-bindings: Document common device controller bindings Gatien Chevallier
2023-01-27 16:49 ` Krzysztof Kozlowski
2023-01-27 17:00 ` Gatien CHEVALLIER
2023-01-27 16:40 ` [PATCH v3 2/6] dt-bindings: treewide: add feature-domains description in binding files Gatien Chevallier
2023-01-28 15:46 ` Jonathan Cameron
2023-02-03 20:57 ` Rob Herring
2023-01-27 16:40 ` [PATCH v3 3/6] dt-bindings: bus: add STM32 System Bus Gatien Chevallier
2023-01-28 15:48 ` Jonathan Cameron
2023-02-07 13:31 ` Gatien CHEVALLIER
2023-01-27 16:40 ` [PATCH v3 4/6] bus: stm32_sys_bus: add support for STM32MP15 and STM32MP13 system bus Gatien Chevallier
2023-01-28 16:12 ` Jonathan Cameron
2023-02-07 14:12 ` Gatien CHEVALLIER
2023-02-08 19:08 ` Jonathan Cameron
2023-01-27 16:40 ` [PATCH v3 5/6] ARM: dts: stm32: add ETZPC as a system bus for STM32MP15x boards Gatien Chevallier
2023-02-09 7:51 ` Uwe Kleine-König
2023-01-27 16:40 ` [PATCH v3 6/6] ARM: dts: stm32: add ETZPC as a system bus for STM32MP13x boards Gatien Chevallier
2023-02-09 7:46 ` [Linux-stm32] " Ahmad Fatoum
2023-02-09 8:10 ` Ahmad Fatoum
2023-02-13 10:54 ` Gatien CHEVALLIER
2023-02-13 11:27 ` Ahmad Fatoum
2023-02-27 11:26 ` Gatien CHEVALLIER
2023-04-21 10:19 ` Oleksii Moisieiev
2023-04-25 7:56 ` Gatien CHEVALLIER
2023-07-05 17:35 ` Gatien CHEVALLIER [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=f8c6e86d-af6a-b61f-c642-c23cb3cfb015@foss.st.com \
--to=gatien.chevallier@foss.st.com \
--cc=Oleksii_Moisieiev@epam.com \
--cc=alexandre.torgue@foss.st.com \
--cc=alsa-devel@alsa-project.org \
--cc=arnaud.pouliquen@foss.st.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=edumazet@google.com \
--cc=fabrice.gasnier@foss.st.com \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=jic23@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-usb@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olivier.moysan@foss.st.com \
--cc=pabeni@redhat.com \
--cc=robh+dt@kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=vkoul@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;
as well as URLs for NNTP newsgroup(s).