* Re: [PATCH v3 02/11] dt-bindings: treewide: add feature-domains description
[not found] ` <20230726083810.232100-3-gatien.chevallier@foss.st.com>
@ 2023-07-29 11:16 ` Jonathan Cameron
0 siblings, 0 replies; 2+ messages in thread
From: Jonathan Cameron @ 2023-07-29 11:16 UTC (permalink / raw)
To: Gatien Chevallier
Cc: Oleksii_Moisieiev, gregkh, herbert, davem, robh+dt,
krzysztof.kozlowski+dt, conor+dt, alexandre.torgue, vkoul,
olivier.moysan, arnaud.pouliquen, mchehab, fabrice.gasnier,
andi.shyti, ulf.hansson, edumazet, kuba, pabeni, hugues.fruchet,
lee, will, catalin.marinas, arnd, richardcochran, Frank Rowand,
linux-crypto, devicetree, linux-stm32, linux-arm-kernel,
linux-kernel, dmaengine, linux-i2c, linux-iio, alsa-devel,
linux-media, linux-mmc, netdev, linux-phy, linux-serial,
linux-spi, linux-usb
On Wed, 26 Jul 2023 10:38:01 +0200
Gatien Chevallier <gatien.chevallier@foss.st.com> wrote:
> feature-domains is an optional property that allows a peripheral to
> refer to one or more feature domain controller(s).
>
> Description of this property is added to all peripheral binding files of
> the peripheral under the STM32 firewall controllers. It allows an accurate
> representation of the hardware, where various peripherals are connected
> to this firewall bus. The firewall can then check the peripheral accesses
> before allowing it to probe.
>
> Signed-off-by: Gatien Chevallier <gatien.chevallier@foss.st.com>
Acked-by: Jonathan Cameron <Jonathan.Cameron@huawei.com> #for IIO
> ---
>
> Changes in V2:
> - Add missing "feature-domains" property declaration
> in bosch,m_can.yaml and st,stm32-cryp.yaml files
>
> Documentation/devicetree/bindings/crypto/st,stm32-cryp.yaml | 4 ++++
> Documentation/devicetree/bindings/crypto/st,stm32-hash.yaml | 4 ++++
> Documentation/devicetree/bindings/dma/st,stm32-dma.yaml | 4 ++++
> Documentation/devicetree/bindings/dma/st,stm32-dmamux.yaml | 4 ++++
> Documentation/devicetree/bindings/i2c/st,stm32-i2c.yaml | 4 ++++
> Documentation/devicetree/bindings/iio/adc/st,stm32-adc.yaml | 4 ++++
> .../devicetree/bindings/iio/adc/st,stm32-dfsdm-adc.yaml | 4 ++++
> Documentation/devicetree/bindings/iio/dac/st,stm32-dac.yaml | 4 ++++
> .../devicetree/bindings/media/cec/st,stm32-cec.yaml | 4 ++++
> Documentation/devicetree/bindings/media/st,stm32-dcmi.yaml | 4 ++++
> .../bindings/memory-controllers/st,stm32-fmc2-ebi.yaml | 4 ++++
> Documentation/devicetree/bindings/mfd/st,stm32-lptimer.yaml | 4 ++++
> Documentation/devicetree/bindings/mfd/st,stm32-timers.yaml | 5 +++++
> Documentation/devicetree/bindings/mmc/arm,pl18x.yaml | 4 ++++
> Documentation/devicetree/bindings/net/can/bosch,m_can.yaml | 4 ++++
> Documentation/devicetree/bindings/net/stm32-dwmac.yaml | 4 ++++
> Documentation/devicetree/bindings/phy/phy-stm32-usbphyc.yaml | 4 ++++
> .../devicetree/bindings/regulator/st,stm32-vrefbuf.yaml | 4 ++++
> Documentation/devicetree/bindings/rng/st,stm32-rng.yaml | 4 ++++
> Documentation/devicetree/bindings/serial/st,stm32-uart.yaml | 4 ++++
> Documentation/devicetree/bindings/sound/st,stm32-i2s.yaml | 4 ++++
> Documentation/devicetree/bindings/sound/st,stm32-sai.yaml | 4 ++++
> .../devicetree/bindings/sound/st,stm32-spdifrx.yaml | 4 ++++
> Documentation/devicetree/bindings/spi/st,stm32-qspi.yaml | 4 ++++
> Documentation/devicetree/bindings/spi/st,stm32-spi.yaml | 4 ++++
> Documentation/devicetree/bindings/usb/dwc2.yaml | 4 ++++
> 26 files changed, 105 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/crypto/st,stm32-cryp.yaml b/Documentation/devicetree/bindings/crypto/st,stm32-cryp.yaml
> index 0ddeb8a9a7a0..87a578327fc0 100644
> --- a/Documentation/devicetree/bindings/crypto/st,stm32-cryp.yaml
> +++ b/Documentation/devicetree/bindings/crypto/st,stm32-cryp.yaml
> @@ -46,6 +46,10 @@ properties:
> power-domains:
> maxItems: 1
>
> + feature-domains:
> + minItems: 1
> + maxItems: 2
> +
> required:
> - compatible
> - reg
> diff --git a/Documentation/devicetree/bindings/crypto/st,stm32-hash.yaml b/Documentation/devicetree/bindings/crypto/st,stm32-hash.yaml
> index b767ec72a999..042a1e005ab2 100644
> --- a/Documentation/devicetree/bindings/crypto/st,stm32-hash.yaml
> +++ b/Documentation/devicetree/bindings/crypto/st,stm32-hash.yaml
> @@ -50,6 +50,10 @@ properties:
> power-domains:
> maxItems: 1
>
> + feature-domains:
> + minItems: 1
> + maxItems: 2
> +
> required:
> - compatible
> - reg
> diff --git a/Documentation/devicetree/bindings/dma/st,stm32-dma.yaml b/Documentation/devicetree/bindings/dma/st,stm32-dma.yaml
> index 329847ef096a..9f60915e6130 100644
> --- a/Documentation/devicetree/bindings/dma/st,stm32-dma.yaml
> +++ b/Documentation/devicetree/bindings/dma/st,stm32-dma.yaml
> @@ -82,6 +82,10 @@ properties:
> description: if defined, it indicates that the controller
> supports memory-to-memory transfer
>
> + feature-domains:
> + minItems: 1
> + maxItems: 2
> +
> required:
> - compatible
> - reg
> diff --git a/Documentation/devicetree/bindings/dma/st,stm32-dmamux.yaml b/Documentation/devicetree/bindings/dma/st,stm32-dmamux.yaml
> index e722fbcd8a5f..15d33d41098f 100644
> --- a/Documentation/devicetree/bindings/dma/st,stm32-dmamux.yaml
> +++ b/Documentation/devicetree/bindings/dma/st,stm32-dmamux.yaml
> @@ -28,6 +28,10 @@ properties:
> resets:
> maxItems: 1
>
> + feature-domains:
> + minItems: 1
> + maxItems: 2
> +
> required:
> - compatible
> - reg
> diff --git a/Documentation/devicetree/bindings/i2c/st,stm32-i2c.yaml b/Documentation/devicetree/bindings/i2c/st,stm32-i2c.yaml
> index 94b75d9f66cd..8a1a21faab8c 100644
> --- a/Documentation/devicetree/bindings/i2c/st,stm32-i2c.yaml
> +++ b/Documentation/devicetree/bindings/i2c/st,stm32-i2c.yaml
> @@ -99,6 +99,10 @@ properties:
>
> wakeup-source: true
>
> + feature-domains:
> + minItems: 1
> + maxItems: 2
> +
> required:
> - compatible
> - reg
> diff --git a/Documentation/devicetree/bindings/iio/adc/st,stm32-adc.yaml b/Documentation/devicetree/bindings/iio/adc/st,stm32-adc.yaml
> index 995cbf8cefc6..d59ac9282a28 100644
> --- a/Documentation/devicetree/bindings/iio/adc/st,stm32-adc.yaml
> +++ b/Documentation/devicetree/bindings/iio/adc/st,stm32-adc.yaml
> @@ -93,6 +93,10 @@ properties:
> '#size-cells':
> const: 0
>
> + feature-domains:
> + minItems: 1
> + maxItems: 2
> +
> allOf:
> - if:
> properties:
> diff --git a/Documentation/devicetree/bindings/iio/adc/st,stm32-dfsdm-adc.yaml b/Documentation/devicetree/bindings/iio/adc/st,stm32-dfsdm-adc.yaml
> index 1970503389aa..39ee55aa4dd8 100644
> --- a/Documentation/devicetree/bindings/iio/adc/st,stm32-dfsdm-adc.yaml
> +++ b/Documentation/devicetree/bindings/iio/adc/st,stm32-dfsdm-adc.yaml
> @@ -59,6 +59,10 @@ properties:
> If not, SPI CLKOUT frequency will not be accurate.
> maximum: 20000000
>
> + feature-domains:
> + minItems: 1
> + maxItems: 2
> +
> required:
> - compatible
> - reg
> diff --git a/Documentation/devicetree/bindings/iio/dac/st,stm32-dac.yaml b/Documentation/devicetree/bindings/iio/dac/st,stm32-dac.yaml
> index 04045b932bd2..184d0a44d1de 100644
> --- a/Documentation/devicetree/bindings/iio/dac/st,stm32-dac.yaml
> +++ b/Documentation/devicetree/bindings/iio/dac/st,stm32-dac.yaml
> @@ -45,6 +45,10 @@ properties:
> '#size-cells':
> const: 0
>
> + feature-domains:
> + minItems: 1
> + maxItems: 2
> +
> additionalProperties: false
>
> required:
> diff --git a/Documentation/devicetree/bindings/media/cec/st,stm32-cec.yaml b/Documentation/devicetree/bindings/media/cec/st,stm32-cec.yaml
> index 2314a9a14650..41db21373301 100644
> --- a/Documentation/devicetree/bindings/media/cec/st,stm32-cec.yaml
> +++ b/Documentation/devicetree/bindings/media/cec/st,stm32-cec.yaml
> @@ -29,6 +29,10 @@ properties:
> - const: cec
> - const: hdmi-cec
>
> + feature-domains:
> + minItems: 1
> + maxItems: 2
> +
> required:
> - compatible
> - reg
> diff --git a/Documentation/devicetree/bindings/media/st,stm32-dcmi.yaml b/Documentation/devicetree/bindings/media/st,stm32-dcmi.yaml
> index 6b3e413cedb2..81e1cd5e30cc 100644
> --- a/Documentation/devicetree/bindings/media/st,stm32-dcmi.yaml
> +++ b/Documentation/devicetree/bindings/media/st,stm32-dcmi.yaml
> @@ -36,6 +36,10 @@ properties:
> resets:
> maxItems: 1
>
> + feature-domains:
> + minItems: 1
> + maxItems: 2
> +
> port:
> $ref: /schemas/graph.yaml#/$defs/port-base
> unevaluatedProperties: false
> diff --git a/Documentation/devicetree/bindings/memory-controllers/st,stm32-fmc2-ebi.yaml b/Documentation/devicetree/bindings/memory-controllers/st,stm32-fmc2-ebi.yaml
> index 14f1833d37c9..4ef01ee4a5e5 100644
> --- a/Documentation/devicetree/bindings/memory-controllers/st,stm32-fmc2-ebi.yaml
> +++ b/Documentation/devicetree/bindings/memory-controllers/st,stm32-fmc2-ebi.yaml
> @@ -45,6 +45,10 @@ properties:
> Reflects the memory layout with four integer values per bank. Format:
> <bank-number> 0 <address of the bank> <size>
>
> + feature-domains:
> + minItems: 1
> + maxItems: 2
> +
> patternProperties:
> "^.*@[0-4],[a-f0-9]+$":
> additionalProperties: true
> diff --git a/Documentation/devicetree/bindings/mfd/st,stm32-lptimer.yaml b/Documentation/devicetree/bindings/mfd/st,stm32-lptimer.yaml
> index 27329c5dc38e..156aed282fb8 100644
> --- a/Documentation/devicetree/bindings/mfd/st,stm32-lptimer.yaml
> +++ b/Documentation/devicetree/bindings/mfd/st,stm32-lptimer.yaml
> @@ -44,6 +44,10 @@ properties:
>
> wakeup-source: true
>
> + feature-domains:
> + minItems: 1
> + maxItems: 2
> +
> pwm:
> type: object
> additionalProperties: false
> diff --git a/Documentation/devicetree/bindings/mfd/st,stm32-timers.yaml b/Documentation/devicetree/bindings/mfd/st,stm32-timers.yaml
> index f84e09a5743b..d19981ef3fce 100644
> --- a/Documentation/devicetree/bindings/mfd/st,stm32-timers.yaml
> +++ b/Documentation/devicetree/bindings/mfd/st,stm32-timers.yaml
> @@ -67,6 +67,11 @@ properties:
> "#size-cells":
> const: 0
>
> + feature-domains:
> + minItems: 1
> + maxItems: 2
> +
> +
> pwm:
> type: object
> additionalProperties: false
> diff --git a/Documentation/devicetree/bindings/mmc/arm,pl18x.yaml b/Documentation/devicetree/bindings/mmc/arm,pl18x.yaml
> index 2459a55ed540..5a8b53d5c35f 100644
> --- a/Documentation/devicetree/bindings/mmc/arm,pl18x.yaml
> +++ b/Documentation/devicetree/bindings/mmc/arm,pl18x.yaml
> @@ -79,6 +79,10 @@ properties:
> - const: rx
> - const: tx
>
> + feature-domains:
> + minItems: 1
> + maxItems: 2
> +
> power-domains: true
>
> resets:
> diff --git a/Documentation/devicetree/bindings/net/can/bosch,m_can.yaml b/Documentation/devicetree/bindings/net/can/bosch,m_can.yaml
> index 67879aab623b..144cbcbefa37 100644
> --- a/Documentation/devicetree/bindings/net/can/bosch,m_can.yaml
> +++ b/Documentation/devicetree/bindings/net/can/bosch,m_can.yaml
> @@ -118,6 +118,10 @@ properties:
> phys:
> maxItems: 1
>
> + feature-domains:
> + minItems: 1
> + maxItems: 2
> +
> required:
> - compatible
> - reg
> diff --git a/Documentation/devicetree/bindings/net/stm32-dwmac.yaml b/Documentation/devicetree/bindings/net/stm32-dwmac.yaml
> index fc8c96b08d7d..133e1edbd561 100644
> --- a/Documentation/devicetree/bindings/net/stm32-dwmac.yaml
> +++ b/Documentation/devicetree/bindings/net/stm32-dwmac.yaml
> @@ -93,6 +93,10 @@ properties:
> select RCC clock instead of ETH_REF_CLK.
> type: boolean
>
> + feature-domains:
> + minItems: 1
> + maxItems: 2
> +
> required:
> - compatible
> - clocks
> diff --git a/Documentation/devicetree/bindings/phy/phy-stm32-usbphyc.yaml b/Documentation/devicetree/bindings/phy/phy-stm32-usbphyc.yaml
> index 24a3dbde223b..89fa65f31d20 100644
> --- a/Documentation/devicetree/bindings/phy/phy-stm32-usbphyc.yaml
> +++ b/Documentation/devicetree/bindings/phy/phy-stm32-usbphyc.yaml
> @@ -55,6 +55,10 @@ properties:
> description: number of clock cells for ck_usbo_48m consumer
> const: 0
>
> + feature-domains:
> + minItems: 1
> + maxItems: 2
> +
> # Required child nodes:
>
> patternProperties:
> diff --git a/Documentation/devicetree/bindings/regulator/st,stm32-vrefbuf.yaml b/Documentation/devicetree/bindings/regulator/st,stm32-vrefbuf.yaml
> index 05f4ad2c7d3a..b73a97f89fe4 100644
> --- a/Documentation/devicetree/bindings/regulator/st,stm32-vrefbuf.yaml
> +++ b/Documentation/devicetree/bindings/regulator/st,stm32-vrefbuf.yaml
> @@ -30,6 +30,10 @@ properties:
> vdda-supply:
> description: phandle to the vdda input analog voltage.
>
> + feature-domains:
> + minItems: 1
> + maxItems: 2
> +
> required:
> - compatible
> - reg
> diff --git a/Documentation/devicetree/bindings/rng/st,stm32-rng.yaml b/Documentation/devicetree/bindings/rng/st,stm32-rng.yaml
> index 187b172d0cca..c45e6285653c 100644
> --- a/Documentation/devicetree/bindings/rng/st,stm32-rng.yaml
> +++ b/Documentation/devicetree/bindings/rng/st,stm32-rng.yaml
> @@ -30,6 +30,10 @@ properties:
> type: boolean
> description: If set enable the clock detection management
>
> + feature-domains:
> + minItems: 1
> + maxItems: 2
> +
> required:
> - compatible
> - reg
> diff --git a/Documentation/devicetree/bindings/serial/st,stm32-uart.yaml b/Documentation/devicetree/bindings/serial/st,stm32-uart.yaml
> index 1df8ffe95fc6..b80d5a8ff4e8 100644
> --- a/Documentation/devicetree/bindings/serial/st,stm32-uart.yaml
> +++ b/Documentation/devicetree/bindings/serial/st,stm32-uart.yaml
> @@ -70,6 +70,10 @@ properties:
> enum: [1, 2, 4, 8, 12, 14, 16]
> default: 8
>
> + feature-domains:
> + minItems: 1
> + maxItems: 2
> +
> allOf:
> - $ref: rs485.yaml#
> - $ref: serial.yaml#
> diff --git a/Documentation/devicetree/bindings/sound/st,stm32-i2s.yaml b/Documentation/devicetree/bindings/sound/st,stm32-i2s.yaml
> index b9111d375b93..30339447cc24 100644
> --- a/Documentation/devicetree/bindings/sound/st,stm32-i2s.yaml
> +++ b/Documentation/devicetree/bindings/sound/st,stm32-i2s.yaml
> @@ -65,6 +65,10 @@ properties:
> $ref: audio-graph-port.yaml#
> unevaluatedProperties: false
>
> + feature-domains:
> + minItems: 1
> + maxItems: 2
> +
> required:
> - compatible
> - "#sound-dai-cells"
> diff --git a/Documentation/devicetree/bindings/sound/st,stm32-sai.yaml b/Documentation/devicetree/bindings/sound/st,stm32-sai.yaml
> index 56d206f97a96..f59770ead3e3 100644
> --- a/Documentation/devicetree/bindings/sound/st,stm32-sai.yaml
> +++ b/Documentation/devicetree/bindings/sound/st,stm32-sai.yaml
> @@ -48,6 +48,10 @@ properties:
> clock-names:
> maxItems: 3
>
> + feature-domains:
> + minItems: 1
> + maxItems: 2
> +
> required:
> - compatible
> - reg
> diff --git a/Documentation/devicetree/bindings/sound/st,stm32-spdifrx.yaml b/Documentation/devicetree/bindings/sound/st,stm32-spdifrx.yaml
> index bc48151b9adb..480ce8704fda 100644
> --- a/Documentation/devicetree/bindings/sound/st,stm32-spdifrx.yaml
> +++ b/Documentation/devicetree/bindings/sound/st,stm32-spdifrx.yaml
> @@ -50,6 +50,10 @@ properties:
> resets:
> maxItems: 1
>
> + feature-domains:
> + minItems: 1
> + maxItems: 2
> +
> required:
> - compatible
> - "#sound-dai-cells"
> diff --git a/Documentation/devicetree/bindings/spi/st,stm32-qspi.yaml b/Documentation/devicetree/bindings/spi/st,stm32-qspi.yaml
> index 8bba965a9ae6..3331f6cd1b75 100644
> --- a/Documentation/devicetree/bindings/spi/st,stm32-qspi.yaml
> +++ b/Documentation/devicetree/bindings/spi/st,stm32-qspi.yaml
> @@ -46,6 +46,10 @@ properties:
> - const: tx
> - const: rx
>
> + feature-domains:
> + minItems: 1
> + maxItems: 2
> +
> required:
> - compatible
> - reg
> diff --git a/Documentation/devicetree/bindings/spi/st,stm32-spi.yaml b/Documentation/devicetree/bindings/spi/st,stm32-spi.yaml
> index 9ca1a843c820..a0664a0fcabf 100644
> --- a/Documentation/devicetree/bindings/spi/st,stm32-spi.yaml
> +++ b/Documentation/devicetree/bindings/spi/st,stm32-spi.yaml
> @@ -59,6 +59,10 @@ properties:
> - const: rx
> - const: tx
>
> + feature-domains:
> + minItems: 1
> + maxItems: 2
> +
> patternProperties:
> "^[a-zA-Z][a-zA-Z0-9,+\\-._]{0,63}@[0-9a-f]+$":
> type: object
> diff --git a/Documentation/devicetree/bindings/usb/dwc2.yaml b/Documentation/devicetree/bindings/usb/dwc2.yaml
> index 0a5c98ea711d..95b615ee3a07 100644
> --- a/Documentation/devicetree/bindings/usb/dwc2.yaml
> +++ b/Documentation/devicetree/bindings/usb/dwc2.yaml
> @@ -172,6 +172,10 @@ properties:
>
> tpl-support: true
>
> + feature-domains:
> + minItems: 1
> + maxItems: 2
> +
> dependencies:
> port: [ usb-role-switch ]
> role-switch-default-mode: [ usb-role-switch ]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH v3 00/11] Introduce STM32 Firewall framework
[not found] <20230726083810.232100-1-gatien.chevallier@foss.st.com>
[not found] ` <20230726083810.232100-3-gatien.chevallier@foss.st.com>
@ 2023-09-25 15:39 ` Gatien CHEVALLIER
1 sibling, 0 replies; 2+ messages in thread
From: Gatien CHEVALLIER @ 2023-09-25 15:39 UTC (permalink / raw)
To: Oleksii_Moisieiev, gregkh, herbert, davem, robh+dt,
krzysztof.kozlowski+dt, conor+dt, alexandre.torgue, vkoul, jic23,
olivier.moysan, arnaud.pouliquen, mchehab, fabrice.gasnier,
andi.shyti, ulf.hansson, edumazet, kuba, pabeni, hugues.fruchet,
lee, will, catalin.marinas, arnd, richardcochran, Frank Rowand
Cc: linux-crypto, devicetree, linux-stm32, linux-arm-kernel,
linux-kernel, dmaengine, linux-i2c, linux-iio, alsa-devel,
linux-media, linux-mmc, netdev, linux-phy, linux-serial,
linux-spi, linux-usb
Hello all,
Since the "feature-domains" bindings lacks precision (maybe some
renaming for better clarity on its purpose), I will send v4 with a
vendor binding so the generic one better discussed and enriched with
other contributor examples.
This will avoid mixing several patch set.
Best regards,
Gatien
On 7/26/23 10:37, Gatien Chevallier wrote:
> Introduce STM32 Firewall framework for STM32MP1x and STM32MP2x
> platforms. STM32MP1x(ETZPC) and STM32MP2x(RIFSC) Firewall controllers
> register to the framework to offer firewall services such as access
> granting.
>
> This series of patches is a new approach on the previous STM32 system
> bus, history is available here:
> https://lore.kernel.org/lkml/20230127164040.1047583/
>
> The need for such framework arises from the fact that there are now
> multiple hardware firewalls implemented across multiple products.
> Drivers are shared between different products, using the same code.
> When it comes to firewalls, the purpose mostly stays the same: Protect
> hardware resources. But the implementation differs, and there are
> multiple types of firewalls: peripheral, memory, ...
>
> Some hardware firewall controllers such as the RIFSC implemented on
> STM32MP2x platforms may require to take ownership of a resource before
> being able to use it, hence the requirement for firewall services to
> take/release the ownership of such resources.
>
> On the other hand, hardware firewall configurations are becoming
> more and more complex. These mecanisms prevent platform crashes
> or other firewall-related incoveniences by denying access to some
> resources.
>
> The stm32 firewall framework offers an API that is defined in
> firewall controllers drivers to best fit the specificity of each
> firewall.
>
> For every peripherals protected by either the ETZPC or the RIFSC, the
> firewall framework checks the firewall controlelr registers to see if
> the peripheral's access is granted to the Linux kernel. If not, the
> peripheral is configured as secure, the node is marked populated,
> so that the driver is not probed for that device.
>
> The firewall framework relies on the feature-domain-controller device
> tree bindings: https://lore.kernel.org/lkml/0c0a82bb-18ae-d057-562b.
> It is used by peripherals to reference a domain controller, in this
> case a 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.
>
> The STM32 ETZPC device is responsible for filtering accesses based on
> security level, or co-processor isolation for any resource connected
> to it.
>
> The RIFSC is responsible for filtering accesses based on Compartment
> ID / security level / privilege level for any resource connected to
> it.
>
> STM32MP13/15/25 SoC device tree files are updated in this series to
> implement this mecanism.
>
> Changes in V2:
>
> generic:
> - Add fw_devlink dependency for "feature-domains"
> property.
>
> bindings:
> - Corrected YAMLS errors highlighted by Rob's robot
> - Firewall controllers YAMLs no longer define the
> maxItems for the "feature-domains" property
> - Renamed st,stm32-rifsc.yaml to
> st,stm32mp25-rifsc.yaml
> - Fix examples in YAML files
> - Change feature-domains maxItems to 2 in firewall
> consumer files as there should not be more than
> 2 entries for now
> - Declare "feature-domain-names" as an optional
> property for firewall controllers child nodes.
> - Add missing "feature-domains" property declaration
> in bosch,m_can.yaml and st,stm32-cryp.yaml files
>
> firewall framework:
> - Support multiple entries for "feature-domains"
> property
> - Better handle the device-tree parsing using
> phandle+args APIs
> - Remove "resource firewall" type
> - Add a field for the name of the firewall entry
> - Fix licenses
>
> RIFSC:
> - Add controller name
> - Driver is now a module_platform_driver
> - Fix license
>
> ETZPC:
> - Add controller name
> - Driver is now a module_platform_driver
> - Fix license
>
> Device trees:
> - Fix rifsc node name
> - Move the "ranges" property under the
> "feature-domains" one
>
> Changes in V3:
>
> Change incorrect ordering for bindings commits leading
> to an error while running
> "make DT_CHECKER_FLAGS=-m dt_binding_check"
>
> Oleksii Moisieiev (1):
> dt-bindings: Document common device controller bindings
>
> Gatien Chevallier (10):
> dt-bindings: treewide: add feature-domains description
> dt-bindings: bus: document RIFSC
> dt-bindings: bus: document ETZPC
> firewall: introduce stm32_firewall framework
> of: property: fw_devlink: Add support for "feature-domains"
> bus: rifsc: introduce RIFSC firewall controller driver
> arm64: dts: st: add RIFSC as a domain controller for STM32MP25x boards
> bus: etzpc: introduce ETZPC firewall controller driver
> ARM: dts: stm32: add ETZPC as a system bus for STM32MP15x boards
> ARM: dts: stm32: add ETZPC as a system bus for STM32MP13x boards
>
> .../bindings/bus/st,stm32-etzpc.yaml | 96 +
> .../bindings/bus/st,stm32mp25-rifsc.yaml | 105 +
> .../bindings/crypto/st,stm32-cryp.yaml | 4 +
> .../bindings/crypto/st,stm32-hash.yaml | 4 +
> .../devicetree/bindings/dma/st,stm32-dma.yaml | 4 +
> .../bindings/dma/st,stm32-dmamux.yaml | 4 +
> .../feature-domain-controller.yaml | 84 +
> .../devicetree/bindings/i2c/st,stm32-i2c.yaml | 4 +
> .../bindings/iio/adc/st,stm32-adc.yaml | 4 +
> .../bindings/iio/adc/st,stm32-dfsdm-adc.yaml | 4 +
> .../bindings/iio/dac/st,stm32-dac.yaml | 4 +
> .../bindings/media/cec/st,stm32-cec.yaml | 4 +
> .../bindings/media/st,stm32-dcmi.yaml | 4 +
> .../memory-controllers/st,stm32-fmc2-ebi.yaml | 4 +
> .../bindings/mfd/st,stm32-lptimer.yaml | 4 +
> .../bindings/mfd/st,stm32-timers.yaml | 5 +
> .../devicetree/bindings/mmc/arm,pl18x.yaml | 4 +
> .../bindings/net/can/bosch,m_can.yaml | 4 +
> .../devicetree/bindings/net/stm32-dwmac.yaml | 4 +
> .../bindings/phy/phy-stm32-usbphyc.yaml | 4 +
> .../bindings/regulator/st,stm32-vrefbuf.yaml | 4 +
> .../devicetree/bindings/rng/st,stm32-rng.yaml | 4 +
> .../bindings/serial/st,stm32-uart.yaml | 4 +
> .../bindings/sound/st,stm32-i2s.yaml | 4 +
> .../bindings/sound/st,stm32-sai.yaml | 4 +
> .../bindings/sound/st,stm32-spdifrx.yaml | 4 +
> .../bindings/spi/st,stm32-qspi.yaml | 4 +
> .../devicetree/bindings/spi/st,stm32-spi.yaml | 4 +
> .../devicetree/bindings/usb/dwc2.yaml | 4 +
> MAINTAINERS | 7 +
> arch/arm/boot/dts/st/stm32mp131.dtsi | 1027 +++---
> arch/arm/boot/dts/st/stm32mp133.dtsi | 51 +-
> arch/arm/boot/dts/st/stm32mp13xc.dtsi | 19 +-
> arch/arm/boot/dts/st/stm32mp13xf.dtsi | 19 +-
> arch/arm/boot/dts/st/stm32mp151.dtsi | 2757 +++++++++--------
> arch/arm/boot/dts/st/stm32mp153.dtsi | 52 +-
> arch/arm/boot/dts/st/stm32mp15xc.dtsi | 19 +-
> arch/arm64/Kconfig.platforms | 1 +
> arch/arm64/boot/dts/st/stm32mp251.dtsi | 7 +-
> drivers/bus/Kconfig | 9 +
> drivers/bus/Makefile | 1 +
> drivers/bus/stm32_etzpc.c | 141 +
> drivers/bus/stm32_firewall.c | 288 ++
> drivers/bus/stm32_firewall.h | 83 +
> drivers/bus/stm32_rifsc.c | 252 ++
> drivers/of/property.c | 2 +
> include/linux/bus/stm32_firewall_device.h | 140 +
> 47 files changed, 3346 insertions(+), 1919 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/bus/st,stm32-etzpc.yaml
> create mode 100644 Documentation/devicetree/bindings/bus/st,stm32mp25-rifsc.yaml
> create mode 100644 Documentation/devicetree/bindings/feature-controllers/feature-domain-controller.yaml
> create mode 100644 drivers/bus/stm32_etzpc.c
> create mode 100644 drivers/bus/stm32_firewall.c
> create mode 100644 drivers/bus/stm32_firewall.h
> create mode 100644 drivers/bus/stm32_rifsc.c
> create mode 100644 include/linux/bus/stm32_firewall_device.h
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2023-09-25 15:40 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20230726083810.232100-1-gatien.chevallier@foss.st.com>
[not found] ` <20230726083810.232100-3-gatien.chevallier@foss.st.com>
2023-07-29 11:16 ` [PATCH v3 02/11] dt-bindings: treewide: add feature-domains description Jonathan Cameron
2023-09-25 15:39 ` [PATCH v3 00/11] Introduce STM32 Firewall framework Gatien CHEVALLIER
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).