diff mbox

irqchip: armada-370-xp: Move the devicetree binding documentation

Message ID 1399904860-937-1-git-send-email-ezequiel.garcia@free-electrons.com
State Superseded, archived
Headers show

Commit Message

Ezequiel Garcia May 12, 2014, 2:27 p.m. UTC
Move the devicetree binding documentation to the interrupt-controller
directory, where it belongs.

Signed-off-by: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
---
 .../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

Comments

Thomas Petazzoni May 12, 2014, 2:36 p.m. UTC | #1
Dear Ezequiel Garcia,

On Mon, 12 May 2014 11:27:40 -0300, Ezequiel Garcia wrote:
> Move the devicetree binding documentation to the interrupt-controller
> directory, where it belongs.
> 
> Signed-off-by: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
> ---
>  .../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

Reviewed-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Ezequiel Garcia May 12, 2014, 2:48 p.m. UTC | #2
On 12 May 04:36 PM, Thomas Petazzoni wrote:
> On Mon, 12 May 2014 11:27:40 -0300, Ezequiel Garcia wrote:
> > Move the devicetree binding documentation to the interrupt-controller
> > directory, where it belongs.
> > 
> > Signed-off-by: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
> > ---
> >  .../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
> 
> Reviewed-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>

Thanks for reviewing!

Ouch, before anyone complains, I've just realised I forgot to create the patch
with the rename detection flag :-(
Ezequiel Garcia May 18, 2014, 11:37 p.m. UTC | #3
On 12 May 11:48 AM, Ezequiel Garcia wrote:
> On 12 May 04:36 PM, Thomas Petazzoni wrote:
> > On Mon, 12 May 2014 11:27:40 -0300, Ezequiel Garcia wrote:
> > > Move the devicetree binding documentation to the interrupt-controller
> > > directory, where it belongs.
> > > 
> > > Signed-off-by: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
> > > ---
> > >  .../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
> > 
> > Reviewed-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> 
> 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,
Jason Cooper May 18, 2014, 11:40 p.m. UTC | #4
On Sun, May 18, 2014 at 08:37:58PM -0300, Ezequiel Garcia wrote:
> On 12 May 11:48 AM, Ezequiel Garcia wrote:
> > On 12 May 04:36 PM, Thomas Petazzoni wrote:
> > > On Mon, 12 May 2014 11:27:40 -0300, Ezequiel Garcia wrote:
> > > > Move the devicetree binding documentation to the interrupt-controller
> > > > directory, where it belongs.
> > > > 
> > > > Signed-off-by: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
> > > > ---
> > > >  .../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
> > > 
> > > Reviewed-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> > 
> > 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.
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Ezequiel Garcia May 18, 2014, 11:51 p.m. UTC | #5
On 18 May 07:40 PM, Jason Cooper wrote:
> On Sun, May 18, 2014 at 08:37:58PM -0300, Ezequiel Garcia wrote:
> > On 12 May 11:48 AM, Ezequiel Garcia wrote:
> > > On 12 May 04:36 PM, Thomas Petazzoni wrote:
> > > > On Mon, 12 May 2014 11:27:40 -0300, Ezequiel Garcia wrote:
> > > > > Move the devicetree binding documentation to the interrupt-controller
> > > > > directory, where it belongs.
> > > > > 
> > > > > Signed-off-by: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
> > > > > ---
> > > > >  .../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
> > > > 
> > > > Reviewed-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> > > 
> > > 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...
> 

Actually, there was... and then thought maybe you didn't need it.

Want me send it? I can do that real quick.
Jason Cooper May 18, 2014, 11:54 p.m. UTC | #6
On Sun, May 18, 2014 at 08:51:48PM -0300, Ezequiel Garcia wrote:
> On 18 May 07:40 PM, Jason Cooper wrote:
> > On Sun, May 18, 2014 at 08:37:58PM -0300, Ezequiel Garcia wrote:
> > > On 12 May 11:48 AM, Ezequiel Garcia wrote:
> > > > On 12 May 04:36 PM, Thomas Petazzoni wrote:
> > > > > On Mon, 12 May 2014 11:27:40 -0300, Ezequiel Garcia wrote:
> > > > > > Move the devicetree binding documentation to the interrupt-controller
> > > > > > directory, where it belongs.
> > > > > > 
> > > > > > Signed-off-by: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
> > > > > > ---
> > > > > >  .../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
> > > > > 
> > > > > Reviewed-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> > > > 
> > > > 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...
> > 
> 
> 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.
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
diff mbox

Patch

diff --git a/Documentation/devicetree/bindings/arm/armada-370-xp-mpic.txt b/Documentation/devicetree/bindings/arm/armada-370-xp-mpic.txt
deleted file mode 100644
index 5fc0313..0000000
--- a/Documentation/devicetree/bindings/arm/armada-370-xp-mpic.txt
+++ /dev/null
@@ -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@d0020000 {
-              compatible = "marvell,mpic";
-              #interrupt-cells = <1>;
-              #address-cells = <1>;
-              #size-cells = <1>;
-              interrupt-controller;
-              msi-controller;
-              reg = <0xd0020a00 0x1d0>,
-                    <0xd0021070 0x58>;
-        };
diff --git a/Documentation/devicetree/bindings/interrupt-controller/marvell,armada-370-xp-mpic.txt b/Documentation/devicetree/bindings/interrupt-controller/marvell,armada-370-xp-mpic.txt
new file mode 100644
index 0000000..5fc0313
--- /dev/null
+++ b/Documentation/devicetree/bindings/interrupt-controller/marvell,armada-370-xp-mpic.txt
@@ -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@d0020000 {
+              compatible = "marvell,mpic";
+              #interrupt-cells = <1>;
+              #address-cells = <1>;
+              #size-cells = <1>;
+              interrupt-controller;
+              msi-controller;
+              reg = <0xd0020a00 0x1d0>,
+                    <0xd0021070 0x58>;
+        };