From: "Lad, Prabhakar" <prabhakar.csengg@gmail.com>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Marc Zyngier <maz@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Thomas Gleixner <tglx@linutronix.de>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Andy Gross <agross@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
linux-tegra <linux-tegra@vger.kernel.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
devicetree <devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Phil Edworthy <phil.edworthy@renesas.com>
Subject: Re: [PATCH v4 0/7] Renesas RZ/G2L IRQC support
Date: Mon, 23 May 2022 18:28:04 +0100 [thread overview]
Message-ID: <CA+V-a8vKNBf78mLzu_RJjj-vWMvw7fAdZ=oA1V--UYYcL2FdnA@mail.gmail.com> (raw)
In-Reply-To: <OS0PR01MB5922A0C8F58C5A4221A57F1F86D09@OS0PR01MB5922.jpnprd01.prod.outlook.com>
Hi Biju,
On Thu, May 19, 2022 at 7:58 AM Biju Das <biju.das.jz@bp.renesas.com> wrote:
>
> Hi Prabhakar,
>
> > Subject: Re: [PATCH v4 0/7] Renesas RZ/G2L IRQC support
> >
> > On Wed, May 18, 2022 at 10:10 PM Andy Shevchenko
> > <andy.shevchenko@gmail.com> wrote:
> > >
> > > On Wed, May 18, 2022 at 9:29 PM 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.
> > > >
> > > >
> > _____________
> > > > | GIC
> > |
> > > > |
> > ________ |
> > > > ____________ | |
> > | |
> > > > NMI --------------------------------->| | SPI0-479 | | GIC-
> > 600| |
> > > > _______ | |------------>|
> > | |
> > > > | | | | PPI16-31 | |
> > | |
> > > > | | IRQ0-IRQ7 | IRQC |------------>|
> > | |
> > > > P0_P48_4 --->| GPIO |---------------->| | |
> > |________| |
> > > > | |GPIOINT0-122 | | |
> > |
> > > > | |---------------->| TINT0-31 | |
> > |
> > > > |______| |__________|
> > |____________|
> > > >
> > > > The proposed patches add hierarchical IRQ domain, one in IRQC driver
> > > > and another in pinctrl driver. Upon interrupt requests map the
> > > > interrupt to GIC. Out of GPIOINT0-122 only 32 can be mapped to GIC
> > > > SPI, this mapping is handled by the pinctrl and IRQC driver.
> > >
> > > Where is the explanation on why valid_mask can't be used instead?
> > >
> > The .valid_mask option is one time setting
>
> One question, if it is one time setting, Is it possible to use .valid mask to invalidate
> invalid gpio lines?(ie, currently gpio range is 392, but there is only 123 GPIOs
> present in the SoC, not sure this call back can be used to invalidate the non-supported GPIOS??).
>
Yes can be added, I will include it in the next version.
Cheers,
Prabhakar
next prev parent reply other threads:[~2022-05-23 17:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 19:29 [PATCH v4 0/7] Renesas RZ/G2L IRQC support Lad Prabhakar
2022-05-18 19:29 ` [PATCH v4 1/7] dt-bindings: interrupt-controller: Add Renesas RZ/G2L Interrupt Controller Lad Prabhakar
2022-05-18 19:29 ` [PATCH v4 2/7] irqchip: Add RZ/G2L IA55 Interrupt Controller driver Lad Prabhakar
2022-05-18 19:29 ` [PATCH v4 3/7] gpio: gpiolib: Add ngirq member to struct gpio_irq_chip Lad Prabhakar
2022-05-19 13:26 ` Linus Walleij
2022-05-23 17:27 ` Lad, Prabhakar
2022-05-18 19:29 ` [PATCH v4 4/7] gpio: gpiolib: Dont assume child_offset_to_irq callback always succeeds Lad Prabhakar
2022-05-19 13:30 ` Linus Walleij
2022-05-18 19:29 ` [PATCH v4 5/7] gpio: gpiolib: Add a check to validate GPIO hwirq Lad Prabhakar
2022-05-18 21:08 ` Andy Shevchenko
2022-05-19 4:11 ` Lad, Prabhakar
2022-05-18 19:29 ` [PATCH v4 6/7] dt-bindings: pinctrl: renesas,rzg2l-pinctrl: Document the properties to handle GPIO IRQ Lad Prabhakar
2022-05-19 12:01 ` Geert Uytterhoeven
2022-05-23 17:29 ` Lad, Prabhakar
2022-05-18 19:29 ` [PATCH v4 7/7] pinctrl: renesas: pinctrl-rzg2l: Add IRQ domain to handle GPIO interrupt Lad Prabhakar
2022-05-18 21:09 ` [PATCH v4 0/7] Renesas RZ/G2L IRQC support Andy Shevchenko
2022-05-19 4:07 ` Lad, Prabhakar
2022-05-19 6:58 ` Biju Das
2022-05-23 17:28 ` Lad, Prabhakar [this message]
2022-05-19 10:07 ` Andy Shevchenko
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='CA+V-a8vKNBf78mLzu_RJjj-vWMvw7fAdZ=oA1V--UYYcL2FdnA@mail.gmail.com' \
--to=prabhakar.csengg@gmail.com \
--cc=agross@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=bjorn.andersson@linaro.org \
--cc=brgl@bgdev.pl \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=maz@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=phil.edworthy@renesas.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
--cc=thierry.reding@gmail.com \
/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).