[PATCH 1/7] dt-bindings: interrupt-controller: Add bcm2712 MSI-X DT bindings
Florian Fainelli
florian.fainelli at broadcom.com
Wed Jun 26 04:35:23 PDT 2024
On 26/06/2024 11:45, Stanimir Varbanov wrote:
> Adds DT bindings for bcm2712 MSI-X interrupt peripheral controller.
>
> Signed-off-by: Stanimir Varbanov <svarbanov at suse.de>
> ---
> .../brcm,bcm2712-msix.yaml | 74 +++++++++++++++++++
> 1 file changed, 74 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/interrupt-controller/brcm,bcm2712-msix.yaml
>
> diff --git a/Documentation/devicetree/bindings/interrupt-controller/brcm,bcm2712-msix.yaml b/Documentation/devicetree/bindings/interrupt-controller/brcm,bcm2712-msix.yaml
> new file mode 100644
> index 000000000000..ca610e4467d9
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/interrupt-controller/brcm,bcm2712-msix.yaml
> @@ -0,0 +1,74 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/interrupt-controller/brcm,bcm2712-msix.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Broadcom bcm2712 MSI-X Interrupt Peripheral support
> +
> +maintainers:
> + - Stanimir Varbanov <svarbanov at suse.de>
> +
> +description: >
> + This interrupt controller is used to provide intterupt vectors to the
> + generic interrupt controller (GIC) on bcm2712. It will be used as
> + external MSI-X controller for PCIe root complex.
> +
> +allOf:
> + - $ref: /schemas/interrupt-controller/msi-controller.yaml#
> +
> +properties:
> + compatible:
> + items:
> + - enum:
> + - "brcm,bcm2712-mip-intc"
> + reg:
> + maxItems: 1
> + description: >
> + Specifies the base physical address and size of the registers
> +
> + interrupt-controller: true
> +
> + "#interrupt-cells":
> + const: 2
Should we have some sort of an interrupt-map or interrupt-map-mask
property that defines the "linkage" between the inputs and the outputs?
This controller does not really sit at the top-level of the interrupt
tree as it feeds the ARM GIC, unfortunately this is not captured at all,
and it seems to require ad-hoc properties to establish the mapping, that
does not seem ideal.
--
Florian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4221 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20240626/016213d8/attachment.p7s>
More information about the linux-arm-kernel
mailing list