From: Krzysztof Kozlowski <krzk@kernel.org>
To: Christophe Leroy <christophe.leroy@csgroup.eu>,
Rob Herring <robh@kernel.org>
Cc: Qiang Zhao <qiang.zhao@nxp.com>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3 5/6] dt-bindings: soc: fsl: qe: Add support of IRQ in QE GPIO
Date: Fri, 29 Aug 2025 09:47:48 +0200 [thread overview]
Message-ID: <0f716362-07f4-4c79-bb0a-e71d2630a797@kernel.org> (raw)
In-Reply-To: <f21e27da-de26-4835-9660-b39e99695281@csgroup.eu>
On 28/08/2025 16:12, Christophe Leroy wrote:
>
>
> Le 28/08/2025 à 15:28, Rob Herring a écrit :
>> On Mon, Aug 25, 2025 at 2:20 AM Christophe Leroy
>> <christophe.leroy@csgroup.eu> wrote:
>>>
>>> In the QE, a few GPIOs are IRQ capable. Similarly to
>>> commit 726bd223105c ("powerpc/8xx: Adding support of IRQ in MPC8xx
>>> GPIO"), add IRQ support to QE GPIO.
>>>
>>> Add property 'fsl,qe-gpio-irq-mask' similar to
>>> 'fsl,cpm1-gpio-irq-mask' that define which of the GPIOs have IRQs.
>>
>> Why do you need to know this? The ones that have interrupts will be
>> referenced by an 'interrupts' property somewhere.
>
> I don't follow you. The ones that have interrupts need to be reported by
> gc->qe_gpio_to_irq[] so that gpiod_to_irq() return the IRQ number, for
> instance to gpio_sysfs_request_irq() so that it can install an irq
> handler. I can't see where they would be referenced by an "interrupts"
> property.
They would be referenced by every consumer of these interrupts. IOW,
this property is completely redundant, because DT holds this information
already in other place.
>
>>
>>> Here is an exemple for port B of mpc8323 which has IRQs for
>>
>> typo
>>
>>> GPIOs PB7, PB9, PB25 and PB27.
>>>
>>> qe_pio_b: gpio-controller@1418 {
>>> compatible = "fsl,mpc8323-qe-pario-bank";
>>> reg = <0x1418 0x18>;
>>> interrupts = <4 5 6 7>;
>>> interrupt-parent = <&qepic>;
>>> gpio-controller;
>>> #gpio-cells = <2>;
>>> fsl,qe-gpio-irq-mask = <0x01400050>;
>>> };
>>
>> You are missing #interrupt-cells and interrupt-controller properties.
>
> The gpio controller is not an interrupt controller. The GPIO controller
> is brought by patch 1/6 and documented in patch 6/6.
Then the IRQ mask property is not right here. If you say "this GPIOs
have IRQs" it means this is an interrupt controller.
If you say this is not an interrupt controller, then you cannot have
here interrupts per some GPIOs, obviously.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-08-29 7:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-25 6:53 [PATCH v3 0/6] Add support of IRQs to QUICC ENGINE GPIOs Christophe Leroy
2025-08-25 6:53 ` [PATCH v3 1/6] soc: fsl: qe: Add an interrupt controller for QUICC Engine Ports Christophe Leroy
2025-08-25 6:53 ` [PATCH v3 2/6] soc: fsl: qe: Change GPIO driver to a proper platform driver Christophe Leroy
2025-08-25 12:56 ` Bartosz Golaszewski
2025-08-25 13:01 ` Bartosz Golaszewski
2025-08-26 8:40 ` [PATCH v4] " Christophe Leroy
2025-08-25 6:53 ` [PATCH v3 3/6] soc: fsl: qe: Drop legacy-of-mm-gpiochip.h header from GPIO driver Christophe Leroy
2025-08-25 6:53 ` [PATCH v3 4/6] soc: fsl: qe: Add support of IRQ in QE GPIO Christophe Leroy
2025-08-25 13:02 ` Bartosz Golaszewski
2025-08-26 8:41 ` [PATCH v4] " Christophe Leroy
2025-08-26 9:57 ` Bartosz Golaszewski
2025-08-25 6:53 ` [PATCH v3 5/6] dt-bindings: " Christophe Leroy
2025-08-28 13:28 ` Rob Herring
2025-08-28 14:12 ` Christophe Leroy
2025-08-29 7:47 ` Krzysztof Kozlowski [this message]
2025-08-29 8:35 ` Christophe Leroy
2025-08-29 9:16 ` Krzysztof Kozlowski
2025-08-29 9:41 ` Christophe Leroy
2025-08-29 10:51 ` Krzysztof Kozlowski
2025-08-29 7:48 ` Krzysztof Kozlowski
2025-08-25 6:53 ` [PATCH v3 6/6] dt-bindings: soc: fsl: qe: Add an interrupt controller for QUICC Engine Ports Christophe Leroy
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=0f716362-07f4-4c79-bb0a-e71d2630a797@kernel.org \
--to=krzk@kernel.org \
--cc=brgl@bgdev.pl \
--cc=christophe.leroy@csgroup.eu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=qiang.zhao@nxp.com \
--cc=robh@kernel.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).