irqchip: armada-370-xp: Move the devicetree binding documentation
Subsystems (2)
PATCH 1/1 irqchip: armada-370-xp: Move the devicetree binding documentation
Move the devicetree binding documentation to the interrupt-controller directory, where it belongs.
--- .../devicetree/bindings/arm/armada-370-xp-mpic.txt | 38 ---------------------- .../marvell,armada-370-xp-mpic.txt | 38 ++++++++++++++++++++++ 2 files changed, 38 insertions(+), 38 deletions(-) delete mode 100644 Documentation/devicetree/bindings/arm/armada-370-xp-mpic.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/marvell,armada-370-xp-mpic.txt
Documentation/devicetree/bindings/arm/armada-370-xp-mpic.txt deleted +0 -38
@@ -1,38 +0,0 @@ -Marvell Armada 370, 375, 38x, XP Interrupt Controller ------------------------------------------------------ - -Required properties: -- compatible: Should be "marvell,mpic" -- interrupt-controller: Identifies the node as an interrupt controller. -- msi-controller: Identifies the node as an PCI Message Signaled - Interrupt controller. -- #interrupt-cells: The number of cells to define the interrupts. Should be 1. - The cell is the IRQ number - -- reg: Should contain PMIC registers location and length. First pair - for the main interrupt registers, second pair for the per-CPU - interrupt registers. For this last pair, to be compliant with SMP - support, the "virtual" must be use (For the record, these registers - automatically map to the interrupt controller registers of the - current CPU) - -Optional properties: - -- interrupts: If defined, then it indicates that this MPIC is - connected as a slave to another interrupt controller. This is - typically the case on Armada 375 and Armada 38x, where the MPIC is - connected as a slave to the Cortex-A9 GIC. The provided interrupt - indicate to which GIC interrupt the MPIC output is connected. - -Example: - - mpic: interrupt-controller at d0020000 { - compatible = "marvell,mpic"; - #interrupt-cells = <1>; - #address-cells = <1>; - #size-cells = <1>; - interrupt-controller; - msi-controller; - reg = <0xd0020a00 0x1d0>, - <0xd0021070 0x58>; - };
Documentation/devicetree/bindings/interrupt-controller/marvell,armada-370-xp-mpic.txt new file +38 -0
@@ -0,0 +1,38 @@ +Marvell Armada 370, 375, 38x, XP Interrupt Controller +----------------------------------------------------- + +Required properties: +- compatible: Should be "marvell,mpic" +- interrupt-controller: Identifies the node as an interrupt controller. +- msi-controller: Identifies the node as an PCI Message Signaled + Interrupt controller. +- #interrupt-cells: The number of cells to define the interrupts. Should be 1. + The cell is the IRQ number + +- reg: Should contain PMIC registers location and length. First pair + for the main interrupt registers, second pair for the per-CPU + interrupt registers. For this last pair, to be compliant with SMP + support, the "virtual" must be use (For the record, these registers + automatically map to the interrupt controller registers of the + current CPU) + +Optional properties: + +- interrupts: If defined, then it indicates that this MPIC is + connected as a slave to another interrupt controller. This is + typically the case on Armada 375 and Armada 38x, where the MPIC is + connected as a slave to the Cortex-A9 GIC. The provided interrupt + indicate to which GIC interrupt the MPIC output is connected. + +Example: + + mpic: interrupt-controller at d0020000 { + compatible = "marvell,mpic"; + #interrupt-cells = <1>; + #address-cells = <1>; + #size-cells = <1>; + interrupt-controller; + msi-controller; + reg = <0xd0020a00 0x1d0>, + <0xd0021070 0x58>; + };
Signature · 1 line
1.9.1
PATCH 1/1 irqchip: armada-370-xp: Move the devicetree binding documentation
Dear Ezequiel Garcia,
Quoted 10 lines · Ezequiel Garcia
Move the devicetree binding documentation to the interrupt-controller directory, where it belongs.
Signed-off-by Ezequiel Garcia <[email protected]>--- .../devicetree/bindings/arm/armada-370-xp-mpic.txt | 38 ---------------------- .../marvell,armada-370-xp-mpic.txt | 38 ++++++++++++++++++++++ 2 files changed, 38 insertions(+), 38 deletions(-) delete mode 100644 Documentation/devicetree/bindings/arm/armada-370-xp-mpic.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/marvell,armada-370-xp-mpic.txt
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
PATCH 1/1 irqchip: armada-370-xp: Move the devicetree binding documentation
Quoted 12 lines · Thomas Petazzoni
Quoted 10 lines · Ezequiel Garcia
Move the devicetree binding documentation to the interrupt-controller directory, where it belongs.
Signed-off-by Ezequiel Garcia <[email protected]>--- .../devicetree/bindings/arm/armada-370-xp-mpic.txt | 38 ---------------------- .../marvell,armada-370-xp-mpic.txt | 38 ++++++++++++++++++++++ 2 files changed, 38 insertions(+), 38 deletions(-) delete mode 100644 Documentation/devicetree/bindings/arm/armada-370-xp-mpic.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/marvell,armada-370-xp-mpic.txt
Quoted 1 line
Reviewed-by Thomas Petazzoni <[email protected]>
Thanks for reviewing!
Ouch, before anyone complains, I've just realised I forgot to create the patch with the rename detection flag :-(
Signature · 3 lines
Ezequiel Garc?a, Free Electrons Embedded Linux, Kernel and Android Engineering http://free-electrons.com
PATCH 1/1 irqchip: armada-370-xp: Move the devicetree binding documentation
Quoted 13 lines · Ezequiel Garcia
Quoted 12 lines · Thomas Petazzoni
Quoted 10 lines · Ezequiel Garcia
Move the devicetree binding documentation to the interrupt-controller directory, where it belongs.
Signed-off-by Ezequiel Garcia <[email protected]>--- .../devicetree/bindings/arm/armada-370-xp-mpic.txt | 38 ---------------------- .../marvell,armada-370-xp-mpic.txt | 38 ++++++++++++++++++++++ 2 files changed, 38 insertions(+), 38 deletions(-) delete mode 100644 Documentation/devicetree/bindings/arm/armada-370-xp-mpic.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/marvell,armada-370-xp-mpic.txt
Quoted 6 lines
Quoted 1 line
Reviewed-by Thomas Petazzoni <[email protected]>Thanks for reviewing!
Ouch, before anyone complains, I've just realised I forgot to create the patch with the rename detection flag :-(
Jason,
Would you take this?
Thanks,
Signature · 3 lines
Ezequiel Garc?a, Free Electrons Embedded Linux, Kernel and Android Engineering http://free-electrons.com
PATCH 1/1 irqchip: armada-370-xp: Move the devicetree binding documentation
Quoted 16 lines · Ezequiel Garcia
Quoted 15 lines · Ezequiel Garcia
Quoted 13 lines · Thomas Petazzoni
Quoted 10 lines · Ezequiel Garcia
Move the devicetree binding documentation to the interrupt-controller directory, where it belongs.
Signed-off-by Ezequiel Garcia <[email protected]>--- .../devicetree/bindings/arm/armada-370-xp-mpic.txt | 38 ---------------------- .../marvell,armada-370-xp-mpic.txt | 38 ++++++++++++++++++++++ 2 files changed, 38 insertions(+), 38 deletions(-) delete mode 100644 Documentation/devicetree/bindings/arm/armada-370-xp-mpic.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/marvell,armada-370-xp-mpic.txtReviewed-by Thomas Petazzoni <[email protected]>
Quoted 8 lines
Quoted 4 lines
Thanks for reviewing!
Ouch, before anyone complains, I've just realised I forgot to create the patch with the rename detection flag :-(
Jason,
Would you take this?
Sure, my quick read of the above self-reply led me to believe there was another version coming...
thx,
Jason.
PATCH 1/1 irqchip: armada-370-xp: Move the devicetree binding documentation
Quoted 22 lines · Jason Cooper
Quoted 21 lines · Ezequiel Garcia
Quoted 19 lines · Ezequiel Garcia
Quoted 12 lines · Thomas Petazzoni
Quoted 10 lines · Ezequiel Garcia
Move the devicetree binding documentation to the interrupt-controller directory, where it belongs.
Signed-off-by Ezequiel Garcia <[email protected]>--- .../devicetree/bindings/arm/armada-370-xp-mpic.txt | 38 ---------------------- .../marvell,armada-370-xp-mpic.txt | 38 ++++++++++++++++++++++ 2 files changed, 38 insertions(+), 38 deletions(-) delete mode 100644 Documentation/devicetree/bindings/arm/armada-370-xp-mpic.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/marvell,armada-370-xp-mpic.txtQuoted 1 line
Reviewed-by Thomas Petazzoni <[email protected]>Thanks for reviewing!
Ouch, before anyone complains, I've just realised I forgot to create the patch with the rename detection flag :-(
Quoted 7 lines
Quoted 3 lines
Jason,
Would you take this?
Sure, my quick read of the above self-reply led me to believe there was another version coming...
Actually, there was... and then thought maybe you didn't need it.
Want me send it? I can do that real quick.
Signature · 3 lines
Ezequiel Garc?a, Free Electrons Embedded Linux, Kernel and Android Engineering http://free-electrons.com
PATCH 1/1 irqchip: armada-370-xp: Move the devicetree binding documentation
Quoted 27 lines · Ezequiel Garcia
Quoted 26 lines · Jason Cooper
Quoted 24 lines · Ezequiel Garcia
Quoted 13 lines · Ezequiel Garcia
Quoted 12 lines · Thomas Petazzoni
Quoted 10 lines · Ezequiel Garcia
Move the devicetree binding documentation to the interrupt-controller directory, where it belongs.
Signed-off-by Ezequiel Garcia <[email protected]>--- .../devicetree/bindings/arm/armada-370-xp-mpic.txt | 38 ---------------------- .../marvell,armada-370-xp-mpic.txt | 38 ++++++++++++++++++++++ 2 files changed, 38 insertions(+), 38 deletions(-) delete mode 100644 Documentation/devicetree/bindings/arm/armada-370-xp-mpic.txt create mode 100644 Documentation/devicetree/bindings/interrupt-controller/marvell,armada-370-xp-mpic.txtQuoted 6 lines
Quoted 1 line
Reviewed-by Thomas Petazzoni <[email protected]>Thanks for reviewing!
Ouch, before anyone complains, I've just realised I forgot to create the patch with the rename detection flag :-(
Jason,
Would you take this?
Quoted 7 lines
Quoted 3 lines
Sure, my quick read of the above self-reply led me to believe there was another version coming...
Actually, there was... and then thought maybe you didn't need it.
Want me send it? I can do that real quick.
Please do.
thx,
Jason.