From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
SH-Linux <linux-sh@vger.kernel.org>,
"Simon Horman [Horms]" <horms@verge.net.au>,
Thomas Gleixner <tglx@linutronix.de>,
Jason Cooper <jason@lakedaemon.net>
Subject: Re: [PATCH] irqchip: renesas-intc-irqpin: r8a7779 IRLM setup support
Date: Thu, 18 Dec 2014 04:39:51 +0200 [thread overview]
Message-ID: <1533637.nrBHixev6I@avalon> (raw)
In-Reply-To: <CANqRtoS34Jf+ztJYpt1faCkNQk-V0vihgxjWj2Sn61YWKZepJQ@mail.gmail.com>
Hi Magnus,
On Thursday 18 December 2014 10:26:27 Magnus Damm wrote:
> On Thu, Dec 18, 2014 at 6:41 AM, Laurent Pinchart wrote:
> > On Monday 15 December 2014 14:09:20 Magnus Damm wrote:
> >> From: Magnus Damm <damm+renesas@opensource.se>
> >>
> >> Add r8a7779 specific support for IRLM bit configuration
> >> in the INTC-IRQPIN driver. Without this code we need
> >> special workaround code in arch/arm/mach-shmobile.
> >>
> >> The IRLM bit for the INTC hardware exists on various
> >> older SH-based SoCs and is used to select between two
> >> modes for the external interrupt pins IRQ0 to IRQ3:
> >>
> >> IRLM = 0: (default from reset on r8a7779)
> >> In this mode the pins IRQ0 to IRQ3 are used together
> >> to give a value between 0 and 15 to the SoC. External
> >> logic is required for masking. This mode is not
> >> supported by the INTC-IRQPIN driver.
> >>
> >> IRLM = 1: (needs this patch or configuration elsewhere)
> >> In this mode IRQ0 to IRQ3 operate as 4 individual
> >> external interrupt pins. In this mode the SMSC ethernet
> >> chip can be used via IRQ1 on r8a7779 Marzen. This mode
> >> is the only supported mode by the INTC-IRQPIN driver.
> >>
> >> For this patch to work the r8a7779 DTS needs to pass
> >> the ICR0 register as the last register bank.
> >>
> >> Signed-off-by: Magnus Damm <damm+renesas@opensource.se>
> >> ---
> >>
> >> Same version as sent on December 3rd.
> >>
> >> Written against renesas-devel-20141202-v3.18-rc7 which is
> >> basically v3.18-rc7 plus latest arch/arm/mach-shmobile code.
> >>
> >> Documentation/devicetree/bindings/interrupt-controller/renesas,intc-irqp
> >> in.txt | 5 +
> >> drivers/irqchip/irq-renesas-intc-irqpi | 50 ++++++++--
> >> 2 files changed, 46 insertions(+), 9 deletions(-)
> >>
> >> ---
> >> 0001/Documentation/devicetree/bindings/interrupt-controller/renesas,intc-
> >> ir qpin.txt +++
> >> work/Documentation/devicetree/bindings/interrupt-controller/renesas,intc-
> >> irqpin.txt 2014-12-03 20:25:13.000000000 +0900
> >> @@ -9,6 +9,11 @@
> >> Required properties:
> >> - "renesas,intc-irqpin-r8a7778" (R-Car M1A)
> >> - "renesas,intc-irqpin-r8a7779" (R-Car H1)
> >> - "renesas,intc-irqpin-sh73a0" (SH-Mobile AG5)
> >> +
> >> +- reg: Base address and length of each register bank used by the
> >> external
> >> + IRQ pins driven by the interrupt controller hardware module. The base
> >> + addresses, length and number of required register banks varies with
> >> soctype.
> >
> > Ouch. Ouch. Multiple times. Very much :-/
> >
> > I suppose it's too late to fix the DT bindings ?
>
> I don't think it is ever too late, but the question is just how urgent
> it is to get rid of the Marzen C board code. With the code in this
> patch queue up we can get rid of the board code. If someone decides to
> rework the INTC IRQPIN bits then we will have to live with the Marzen
> code for longer. And if we should do it right and describe the actual
> hardware, then perhaps we should consider the non-IRQ-pin interrupts
> included in INTC for some SoCs. So it rapidly gets more complex...
I don't think there's a need to delay getting rid of Marzen legacy code, my
comment wasn't an attempt to delay your efforts :-)
Looking at the hardware we should have a single INTC DT node, not four. What
I'm wondering is whether we could still fix the DT bindings, or if the
backward compatibility requirements would make it too painful, especially
given that R-Car Gen2 doesn't use INTC.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-12-18 2:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 5:09 [PATCH] irqchip: renesas-intc-irqpin: r8a7779 IRLM setup support Magnus Damm
2014-12-17 21:41 ` Laurent Pinchart
2014-12-18 1:26 ` Magnus Damm
2014-12-18 2:39 ` Laurent Pinchart [this message]
2014-12-18 3:14 ` Magnus Damm
2015-01-07 17:15 ` Jason Cooper
2015-01-07 22:19 ` Laurent Pinchart
2015-01-07 17:20 ` Jason Cooper
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=1533637.nrBHixev6I@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=horms@verge.net.au \
--cc=jason@lakedaemon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=tglx@linutronix.de \
/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