linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] ARM: shmobile: r8a7791: use GIC_* defines
Date: Mon, 04 Jan 2016 08:56:43 +0000	[thread overview]
Message-ID: <CAMuHMdWH6Hi4yU0gYfxmyCDF3JNZiii00SwiNrZomQ_-pWbkdA@mail.gmail.com> (raw)
In-Reply-To: <1451856807-8081-3-git-send-email-horms+renesas@verge.net.au>

Hi Simon,

On Sun, Jan 3, 2016 at 10:33 PM, Simon Horman
<horms+renesas@verge.net.au> wrote:
> Use GIC_* defines for GIC interrupt cells in r8a7791 device tree.

Thanks for doing this!

> Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
> ---
>  arch/arm/boot/dts/r8a7791.dtsi | 370 ++++++++++++++++++++---------------------
>  1 file changed, 185 insertions(+), 185 deletions(-)
>
> diff --git a/arch/arm/boot/dts/r8a7791.dtsi b/arch/arm/boot/dts/r8a7791.dtsi
> index 2a369ddcb6fd..c24276375c53 100644
> --- a/arch/arm/boot/dts/r8a7791.dtsi
> +++ b/arch/arm/boot/dts/r8a7791.dtsi

> @@ -782,7 +782,7 @@
>         ether: ethernet@ee700000 {
>                 compatible = "renesas,ether-r8a7791";
>                 reg = <0 0xee700000 0 0x400>;
> -               interrupts = <0 162 IRQ_TYPE_LEVEL_HIGH>;
> +               interrupts = <GIC_SPI 162 IRQ_TYPE_LEVEL_HIGH>;
>                 clocks = <&mstp8_clks R8A7791_CLK_ETHER>;
>                 power-domains = <&cpg_clocks>;
>                 phy-mode = "rmii";
> @@ -806,7 +806,7 @@

You forgot to update the avb node in between these two chunks.

> @@ -1577,9 +1577,9 @@
>                 /* Map all possible DDR as inbound ranges */
>                 dma-ranges = <0x42000000 0 0x40000000 0 0x40000000 0 0x80000000
>                               0x43000000 2 0x00000000 2 0x00000000 1 0x00000000>;
> -               interrupts = <0 116 IRQ_TYPE_LEVEL_HIGH>,
> -                            <0 117 IRQ_TYPE_LEVEL_HIGH>,
> -                            <0 118 IRQ_TYPE_LEVEL_HIGH>;
> +               interrupts = <GIC_SPI 116 IRQ_TYPE_LEVEL_HIGH>,
> +                            <GIC_SPI 117 IRQ_TYPE_LEVEL_HIGH>,
> +                            <GIC_SPI 118 IRQ_TYPE_LEVEL_HIGH>;
>                 #interrupt-cells = <1>;
>                 interrupt-map-mask = <0 0 0 0>;
>                 interrupt-map = <0 0 0 0 &gic 0 116 IRQ_TYPE_LEVEL_HIGH>;

You forgot to update the "interrupt-map" properties in the various PCI nodes
(the "0" after the "&gic").

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

      reply	other threads:[~2016-01-04  8:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-03 21:33 [PATCH 0/2] ARM: shmobile: r8a779[01]: use GIC_* defines Simon Horman
2016-01-03 21:33 ` [PATCH 1/2] ARM: shmobile: r8a7790: " Simon Horman
2016-01-04  8:53   ` Geert Uytterhoeven
2016-01-03 21:33 ` [PATCH 2/2] ARM: shmobile: r8a7791: " Simon Horman
2016-01-04  8:56   ` Geert Uytterhoeven [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=CAMuHMdWH6Hi4yU0gYfxmyCDF3JNZiii00SwiNrZomQ_-pWbkdA@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --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).