On Wed, May 29, 2024 at 10:28:57AM +0200, Niklas Cassel wrote:
> The DWC core has four interrupt signals: tx_inta, tx_intb, tx_intc, tx_intd
> that are triggered when the PCIe controller (when running in Endpoint mode)
> has sent an Assert_INTA Message to the upstream device.
>
> Some DWC controllers have these interrupt in a combined interrupt signal.
>
> Add the description of these interrupts to the device tree binding.
>
> Signed-off-by: Niklas Cassel <cassel@xxxxxxxxxx>
Nit: We recently changed the driver instances of 'LEGACY' to 'INTX'. But the
binding it still using 'legacy'. Considering that the 'legacy' IRQ added to the
RC binding recently (ebce9f6623a7), should we rename it?
This will force the driver to support both 'legacy' and 'intx' for backwards
compatibility.
But irrespective of that,
Reviewed-by: Manivannan Sadhasivam <manivannan.sadhasivam@xxxxxxxxxx>
- Mani
> Reviewed-by: Rob Herring (Arm) <robh@xxxxxxxxxx>
> ---
> Documentation/devicetree/bindings/pci/snps,dw-pcie-ep.yaml | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/pci/snps,dw-pcie-ep.yaml b/Documentation/devicetree/bindings/pci/snps,dw-pcie-ep.yaml
> index f5f12cbc2cb3..f474b9e3fc7e 100644
> --- a/Documentation/devicetree/bindings/pci/snps,dw-pcie-ep.yaml
> +++ b/Documentation/devicetree/bindings/pci/snps,dw-pcie-ep.yaml
> @@ -151,6 +151,15 @@ properties:
> Application-specific IRQ raised depending on the vendor-specific
> events basis.
> const: app
> + - description:
> + Interrupts triggered when the controller itself (in Endpoint mode)
> + has sent an Assert_INT{A,B,C,D}/Desassert_INT{A,B,C,D} message to
> + the upstream device.
> + pattern: "^tx_int(a|b|c|d)$"
> + - description:
> + Combined interrupt signal raised when the controller has sent an
> + Assert_INT{A,B,C,D} message. See "^tx_int(a|b|c|d)$" for details.
> + const: legacy
> - description:
> Vendor-specific IRQ names. Consider using the generic names above
> for new bindings.
>
> --
> 2.45.1
>
--
மணிவண்ணன் சதாசிவம்
