diff options
| author | Florian Fainelli <f.fainelli@gmail.com> | 2019-10-24 13:14:12 -0700 |
|---|---|---|
| committer | Marc Zyngier <maz@kernel.org> | 2019-11-10 18:47:46 +0000 |
| commit | b94f9008f2ad551f4d6a9537b10238847cb81e5d (patch) | |
| tree | 2951b728a5112436e74ddd00b7fb0178e7ca7e42 /Documentation/devicetree/bindings/interrupt-controller/brcm,bcm7038-l1-intc.txt | |
| parent | 6468fc18b00685c82408f40e9569c0d3527862b8 (diff) | |
dt-bindings: Document brcm, irq-can-wake for brcm, bcm7038-l1-intc.txt
The BCM7038 L1 interrupt controller can be used as a wake-up interrupt
controller on MIPS and ARM-based systems, document the brcm,irq-can-wake
which has been "standardized" across Broadcom interrupt controllers.
Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
Signed-off-by: Marc Zyngier <maz@kernel.org>
Acked-by: Rob Herring <robh@kernel.org>
Link: https://lore.kernel.org/r/20191024201415.23454-3-f.fainelli@gmail.com
Diffstat (limited to 'Documentation/devicetree/bindings/interrupt-controller/brcm,bcm7038-l1-intc.txt')
| -rw-r--r-- | Documentation/devicetree/bindings/interrupt-controller/brcm,bcm7038-l1-intc.txt | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/Documentation/devicetree/bindings/interrupt-controller/brcm,bcm7038-l1-intc.txt b/Documentation/devicetree/bindings/interrupt-controller/brcm,bcm7038-l1-intc.txt index 2117d4ac1ae5..4eb043270f5b 100644 --- a/Documentation/devicetree/bindings/interrupt-controller/brcm,bcm7038-l1-intc.txt +++ b/Documentation/devicetree/bindings/interrupt-controller/brcm,bcm7038-l1-intc.txt @@ -31,6 +31,11 @@ Required properties: - interrupts: specifies the interrupt line(s) in the interrupt-parent controller node; valid values depend on the type of parent interrupt controller +Optional properties: + +- brcm,irq-can-wake: If present, this means the L1 controller can be used as a + wakeup source for system suspend/resume. + If multiple reg ranges and interrupt-parent entries are present on an SMP system, the driver will allow IRQ SMP affinity to be set up through the /proc/irq/ interface. In the simplest possible configuration, only one |