linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 03/04] ARM: shmobile: r8a73a4 IRQC support
Date: Thu, 14 Mar 2013 13:43:04 +0000	[thread overview]
Message-ID: <201303141343.04328.arnd@arndb.de> (raw)
In-Reply-To: <CANqRtoSok=0CuLyMGD8-SoKezX54WfacnNnx8FhxCJzs_ggcXg@mail.gmail.com>

On Thursday 14 March 2013, Magnus Damm wrote:
> Hi Arnd,
> 
> Thanks for your feedback, please see below for my reply.
> 
> On Tue, Mar 12, 2013 at 9:31 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> > On Tuesday 12 March 2013, Magnus Damm wrote:
> >> From: Magnus Damm <damm@opensource.se>
> >>
> >> Add IRQC interrupt controller support to r8a73a4 by
> >> hooking up two IRQC instances to handle 58 external
> >> IRQ signals. There IRQC controllers are tied to SPIs
> >> of the GIC. On r8a73a4 exact IRQ pin routing is handled
> >> by the PFC which is excluded from this patch.
> >>
> >> Both platform devices and DT devices are added in this
> >> patch. The platform device versions are used to provide
> >> a static interrupt map configuration for board code
> >> written in C.
> >>
> >> Signed-off-by: Magnus Damm <damm@opensource.se>
> >
> > What is the status of the IRQC DT support? I remember that I wasn't
> > happy with a prior version, but I did not follow up on some of the
> > questions that came up, sorry about that.
> 
> Uhm, perhaps I misunderstand, but I wonder if you refer to INTC instead of IRQC?

Yes, you are right.

> This particular driver is for the IRQC hardware block. It is not
> compatible with INTC. A while ago I posted an incremental DT support
> patch for IRQC -  "[PATCH] irqchip: irqc: Add DT support", please see
> https://lkml.org/lkml/2013/3/6/50

Ok, I had missed that, but the driver certainly looks good to me.

> > Did the patches end up getting merged anyway, or should we resume the
> > discussion about those patches? I understand that lack of INTC bindings
> > would make new SoC support particularly hard, and I don't want to
> > be responsible for holding you up here.
> 
> Thanks. I don't think the INTC patches went anywhere.
> 
> To zoom out a bit let me list different interrupt controllers:
> 
> A) INTC (drivers/sh/intc) [no DT yet]
> B) GIC (drivers/irqchip/irq-gic.c) [DT]
> C) INTC External IRQ Pin (drivers/irqchip/irq-renesas-intc-irqpin.c) [DT]
> D) IRQC (drivers/irqchip/irq-renesas-irqc.c) [DT]
> 
> Simple use cases are:
> - Legacy SH SoCs or ARM SoCs with Cortex-A8 or older make use of A).
> - More recent ARM SoCs with Cortex-A9 or newer use B) and C) or B) and D).

Ok. And I guess the EMMA EV2 uses only GIC but not IRQC or INTC, right?

> On top of this we now and then have GPIO controllers that have
> built-in interrupt controllers.

Yes, obviously.

Coming back to INTC, are you planning to use the same binding for A and C?
Which of them the binding you posted earlier for?

When I looked at the existing code, I had the impression that doing a
binding for just the SH-Mobile SoCs that have an ARM core in them 
(including those that also have an SH core) would be much easier than
doing a binding that also covers the older SH SoCs, since those are
much less uniform.

	Arnd

  reply	other threads:[~2013-03-14 13:43 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-12  4:55 [PATCH 00/04] ARM: shmobile: r8a73a4 SoC and APE6EVM board support Magnus Damm
2013-03-12  4:56 ` [PATCH 01/04] ARM: shmobile: Initial r8a73a4 SoC support Magnus Damm
2013-03-12 12:25   ` Arnd Bergmann
2013-03-14  7:44     ` Magnus Damm
2013-03-14  9:06       ` Arnd Bergmann
2013-03-19  3:22         ` Magnus Damm
2013-03-22 16:03           ` Arnd Bergmann
2013-03-12  4:56 ` [PATCH 02/04] ARM: shmobile: r8a73a4 SCIF support Magnus Damm
2013-03-12  4:56 ` [PATCH 03/04] ARM: shmobile: r8a73a4 IRQC support Magnus Damm
2013-03-12 12:31   ` Arnd Bergmann
2013-03-14  6:59     ` Magnus Damm
2013-03-14 13:43       ` Arnd Bergmann [this message]
2013-03-15  5:32         ` Magnus Damm
2013-03-22 16:00           ` Arnd Bergmann
2013-03-12  4:56 ` [PATCH 04/04] ARM: shmobile: APE6EVM support Magnus Damm
2013-03-12  7:51   ` Kuninori Morimoto
2013-03-12  7:57     ` Magnus Damm
2013-03-12 12:16   ` Arnd Bergmann
2013-03-14  7:01     ` Magnus Damm
2013-03-12  5:19 ` [PATCH 00/04] ARM: shmobile: r8a73a4 SoC and APE6EVM board support Kuninori Morimoto
2013-03-12 12:28 ` Arnd Bergmann
2013-03-14  7:28   ` Magnus Damm
2013-03-14  8:59     ` Arnd Bergmann

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=201303141343.04328.arnd@arndb.de \
    --to=arnd@arndb.de \
    --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).