linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: sebastian.hesselbarth@gmail.com (Sebastian Hesselbarth)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Dove: activate GPIO interrupts in DT
Date: Tue, 22 Jan 2013 20:40:24 +0100	[thread overview]
Message-ID: <50FEEB28.8020000@gmail.com> (raw)
In-Reply-To: <20130122112845.4f7c0f38@armhf>

On 01/22/2013 11:28 AM, Jean-Francois Moine wrote:
> In a DT, the interrupts of an interrupt-controller are not usable when
> #interrupt-cells is missing.
>
> This patch activates the interrupts of the GPIOs 0 and 1 for the Marvell
> Dove SoC.
>
> Signed-off-by: Jean-Fran?ois Moine<moinejf@free.fr>
>
> diff --git a/arch/arm/boot/dts/dove.dtsi b/arch/arm/boot/dts/dove.dtsi
> index 42eac1f..287fb12 100644
> --- a/arch/arm/boot/dts/dove.dtsi
> +++ b/arch/arm/boot/dts/dove.dtsi
> @@ -93,6 +93,7 @@
>   			reg =<0xd0400 0x20>;
>   			ngpios =<32>;
>   			interrupt-controller;
> +			#interrupt-cells =<1>;
>   			interrupts =<12>,<13>,<14>,<60>;
>   		};
>
> @@ -103,6 +104,7 @@
>   			reg =<0xd0420 0x20>;
>   			ngpios =<32>;
>   			interrupt-controller;
> +			#interrupt-cells =<1>;
>   			interrupts =<61>;
>   		};
>

Jean-Francois,

first thanks for sending the patch!

I checked Documentation/devicetree/bindings/gpio/gpio-mvebu.txt and there
#interrupt-cells is specified to be set to two. Further, I checked kirkwood.dtsi
and it is also missing the #interrupt-cells.

Can you please update your patch to have #interrupt-cells set to two? When you
resend v2 of the patch please Cc at least all I added.

I will send another patch fixing kirkwood.dtsi.

Sebastian

      reply	other threads:[~2013-01-22 19:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-22 10:28 [PATCH] Dove: activate GPIO interrupts in DT Jean-Francois Moine
2013-01-22 19:40 ` Sebastian Hesselbarth [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50FEEB28.8020000@gmail.com \
    --to=sebastian.hesselbarth@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).