From: Marc Zyngier <maz@kernel.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Thomas Gleixner <tglx@linutronix.de>,
Rob Herring <robh+dt@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Philipp Zabel <p.zabel@pengutronix.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
devicetree <devicetree@vger.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Prabhakar <prabhakar.csengg@gmail.com>,
Biju Das <biju.das.jz@bp.renesas.com>
Subject: Re: [RFC PATCH v4 0/5] Renesas RZ/G2L IRQC support
Date: Thu, 17 Mar 2022 09:23:08 +0000 [thread overview]
Message-ID: <87wngtx79f.wl-maz@kernel.org> (raw)
In-Reply-To: <CAHp75Vc+uSNF4L0WCfCyadOqJ6szXS3Ct5BmEUbeQ_aKg1zjWg@mail.gmail.com>
On Thu, 17 Mar 2022 08:46:14 +0000,
Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
>
> On Thu, Mar 17, 2022 at 5:43 AM Lad Prabhakar
> <prabhakar.mahadev-lad.rj@bp.renesas.com> wrote:
> >
> > Hi All,
> >
> > The RZ/G2L Interrupt Controller is a front-end for the GIC found on
> > Renesas RZ/G2L SoC's with below pins:
> > - IRQ sense select for 8 external interrupts, mapped to 8 GIC SPI interrupts
> > - GPIO pins used as external interrupt input pins out of GPIOINT0-122 a
> > maximum of only 32 can be mapped to 32 GIC SPI interrupts,
> > - NMI edge select.
> >
> What I want to know now is whether it is going to collide with Marc's
> series about GPIO IRQ chip constification?
Probably, but the current scheme will still be alive for some time
(you'll need a couple of cycles to sort out all the drivers).
Worse case, this can be fixed at merge time.
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2022-03-17 9:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 1:23 [RFC PATCH v4 0/5] Renesas RZ/G2L IRQC support Lad Prabhakar
2022-03-17 1:24 ` [RFC PATCH v4 1/5] dt-bindings: interrupt-controller: Add Renesas RZ/G2L Interrupt Controller Lad Prabhakar
2022-03-17 9:44 ` Krzysztof Kozlowski
2022-03-17 11:55 ` Lad, Prabhakar
2022-03-17 13:34 ` Krzysztof Kozlowski
2022-03-17 1:24 ` [RFC PATCH v4 2/5] irqchip: Add RZ/G2L IA55 Interrupt Controller driver Lad Prabhakar
2022-03-17 16:13 ` Marc Zyngier
2022-03-18 14:59 ` Lad, Prabhakar
2022-03-18 17:44 ` Marc Zyngier
2022-03-17 1:24 ` [RFC PATCH v4 3/5] gpio: gpiolib: Allow free() callback to be overridden Lad Prabhakar
2022-03-18 15:15 ` Lad, Prabhakar
2022-03-17 1:24 ` [RFC PATCH v4 4/5] gpio: gpiolib: Add ngirq member to struct gpio_irq_chip Lad Prabhakar
2022-03-17 1:24 ` [RFC PATCH v4 5/5] pinctrl: renesas: pinctrl-rzg2l: Add IRQ domain to handle GPIO interrupt Lad Prabhakar
2022-03-17 8:46 ` [RFC PATCH v4 0/5] Renesas RZ/G2L IRQC support Andy Shevchenko
2022-03-17 9:23 ` Marc Zyngier [this message]
2022-03-17 11:59 ` Lad, Prabhakar
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=87wngtx79f.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=brgl@bgdev.pl \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=prabhakar.csengg@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh+dt@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.