mvebu error interrupt is triggered by any non-intx event, which is mainly
some pcie error.
Signed-off-by: Pali Rohár <[email protected]>
---
Documentation/devicetree/bindings/pci/mvebu-pci.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/pci/mvebu-pci.txt b/Documentation/devicetree/bindings/pci/mvebu-pci.txt
index 6d022a9d36ee..8f0bca42113f 100644
--- a/Documentation/devicetree/bindings/pci/mvebu-pci.txt
+++ b/Documentation/devicetree/bindings/pci/mvebu-pci.txt
@@ -83,6 +83,7 @@ and the following optional properties:
specified will default to 100ms, as required by the PCIe specification.
- interrupt-names: list of interrupt names, supported are:
- "intx" - interrupt line triggered by one of the legacy interrupt
+ - "error" - interrupt line triggered by any other event (non-intx)
- interrupts or interrupts-extended: List of the interrupt sources which
corresponding to the "interrupt-names". If non-empty then also additional
'interrupt-controller' subnode must be defined.
--
2.20.1
On Thu, Aug 18, 2022 at 01:00:33AM +0200, Pali Roh?r wrote:
> mvebu error interrupt is triggered by any non-intx event, which is mainly
> some pcie error.
>
> Signed-off-by: Pali Roh?r <[email protected]>
> ---
> Documentation/devicetree/bindings/pci/mvebu-pci.txt | 1 +
> 1 file changed, 1 insertion(+)
Acked-by: Rob Herring <[email protected]>
On Thu, Aug 18, 2022 at 01:00:33AM +0200, Pali Roh?r wrote:
> mvebu error interrupt is triggered by any non-intx event, which is mainly
> some pcie error.
>
> Signed-off-by: Pali Roh?r <[email protected]>
Reviewed-by: Andrew Lunn <[email protected]>
Andrew