Re: [PATCH 13/13] [RFC] irqchip: renesas-irqc: Add binding docs for new R-Car Gen2 SoCs
From: Simon Horman <horms@verge.net.au>
Date: 2014-07-11 14:18:52
Also in:
linux-sh, lkml
On Wed, Jul 09, 2014 at 02:23:43PM +0200, Geert Uytterhoeven wrote:
- r8a7792 (R-Car V2H) - r8a7793 (R-Car M2-N) - r8a7794 (R-Car E2) r8a7791 is now called "R-Car M2-W".
As per my comments on patches in this series:
I don't feel strongly about this either way. But it seems to me
that if we want to start using "M2-W" then we should make some
effort, though not necessarily immediately, to update all instances
of "M2" that already exist in the tree.
This seems to be in keeping with the approach we ave taken for
these SoCs for other drivers. And from that point of view it is
fine by me. But I wonder how sure are we that the hardware on the
SoCs will work with this approach.
quoted hunk ↗ jump to hunk
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be> --- .../devicetree/bindings/interrupt-controller/renesas,irqc.txt | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)diff --git a/Documentation/devicetree/bindings/interrupt-controller/renesas,irqc.txt b/Documentation/devicetree/bindings/interrupt-controller/renesas,irqc.txt index f819e2a5907c..cd9d92708c21 100644 --- a/Documentation/devicetree/bindings/interrupt-controller/renesas,irqc.txt +++ b/Documentation/devicetree/bindings/interrupt-controller/renesas,irqc.txt@@ -6,7 +6,10 @@ Required properties: Examples with soctypes are: - "renesas,irqc-r8a73a4" (R-Mobile AP6) - "renesas,irqc-r8a7790" (R-Car H2) - - "renesas,irqc-r8a7791" (R-Car M2) + - "renesas,irqc-r8a7791" (R-Car M2-W) + - "renesas,irqc-r8a7792" (R-Car V2H) + - "renesas,irqc-r8a7793" (R-Car M2-N) + - "renesas,irqc-r8a7794" (R-Car E2) - #interrupt-cells: has to be <2>: an interrupt index and flags, as defined in interrupts.txt in this directory-- 1.9.1