On Wednesday 07 August 2013 at 16:53:09, Mark Rutland wrote: > On Wed, Aug 07, 2013 at 12:06:32PM +0100, Lars Poeschel wrote: > > From: Lars Poeschel <poeschel@xxxxxxxxxxx> > > > > Following commit ff5c9059 and therefore other omap platforms using > > the gpio-omap driver correct the #interrupt-cells property on am33xx > > too. The omap gpio binding documentaion also states that > > the #interrupt-cells property should be 2. > > I take it there are no device nodes for which any of these nodes are an > interrupt parent (which would need to be updated)? As far as I know: No. Lars > If so: > > Acked-by: Mark Rutland <mark.rutland@xxxxxxx> > > Thanks, > Mark. > > > Signed-off-by: Lars Poeschel <poeschel@xxxxxxxxxxx> > > --- > > > > arch/arm/boot/dts/am33xx.dtsi | 8 ++++---- > > 1 file changed, 4 insertions(+), 4 deletions(-) > > > > diff --git a/arch/arm/boot/dts/am33xx.dtsi > > b/arch/arm/boot/dts/am33xx.dtsi index 38b446b..033c5dd 100644 > > --- a/arch/arm/boot/dts/am33xx.dtsi > > +++ b/arch/arm/boot/dts/am33xx.dtsi > > @@ -102,7 +102,7 @@ > > > > gpio-controller; > > #gpio-cells = <2>; > > interrupt-controller; > > > > - #interrupt-cells = <1>; > > + #interrupt-cells = <2>; > > > > reg = <0x44e07000 0x1000>; > > interrupts = <96>; > > > > }; > > > > @@ -113,7 +113,7 @@ > > > > gpio-controller; > > #gpio-cells = <2>; > > interrupt-controller; > > > > - #interrupt-cells = <1>; > > + #interrupt-cells = <2>; > > > > reg = <0x4804c000 0x1000>; > > interrupts = <98>; > > > > }; > > > > @@ -124,7 +124,7 @@ > > > > gpio-controller; > > #gpio-cells = <2>; > > interrupt-controller; > > > > - #interrupt-cells = <1>; > > + #interrupt-cells = <2>; > > > > reg = <0x481ac000 0x1000>; > > interrupts = <32>; > > > > }; > > > > @@ -135,7 +135,7 @@ > > > > gpio-controller; > > #gpio-cells = <2>; > > interrupt-controller; > > > > - #interrupt-cells = <1>; > > + #interrupt-cells = <2>; > > > > reg = <0x481ae000 0x1000>; > > interrupts = <62>; > > > > }; -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
