From: sashiko-bot@kernel.org
To: "Maulik Shah" <maulik.shah@oss.qualcomm.com>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH v3 6/8] pinctrl: qcom: Acknowledge IRQs for PDC interrupt controller
Date: Tue, 16 Jun 2026 09:45:19 +0000 [thread overview]
Message-ID: <20260616094520.376531F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260616-hamoa_pdc_v3-v3-6-4d8e1504ea75@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The patch adds `IRQCHIP_EOI_THREADED` to `msm_gpio_irq_chip.flags`, which alters the EOI timing for all threaded interrupts, but this functional change is completely undocumented in the commit message.
--
commit c69ba699fb1e70baa301113c62200fca65540992
Author: Stephan Gerhold <stephan.gerhold@linaro.org>
pinctrl: qcom: Acknowledge IRQs for PDC interrupt controller
This commit updates the MSM GPIO driver to properly acknowledge incoming
GPIO interrupts for the PDC interrupt controller. For edge-triggered IRQs,
it uses handle_fasteoi_ack_irq() as the IRQ handler and forwards the
irq_ack() callback to the parent IRQ chip.
> diff --git a/drivers/pinctrl/qcom/pinctrl-msm.c b/drivers/pinctrl/qcom/pinctrl-msm.c
> index 11db6564c44df..17665e1a9dbcb 100644
> --- a/drivers/pinctrl/qcom/pinctrl-msm.c
> +++ b/drivers/pinctrl/qcom/pinctrl-msm.c
[ ... ]
> @@ -1395,6 +1408,7 @@ static const struct irq_chip msm_gpio_irq_chip = {
> .flags = (IRQCHIP_MASK_ON_SUSPEND |
> IRQCHIP_SET_TYPE_MASKED |
> IRQCHIP_ENABLE_WAKEUP_ON_SUSPEND |
> + IRQCHIP_EOI_THREADED |
> IRQCHIP_IMMUTABLE),
> };
[Severity: Medium]
The commit message does not mention the addition of IRQCHIP_EOI_THREADED.
Does this change belong in a separate patch, or should the commit message
be updated to explain why it is needed?
Adding this flag alters the EOI timing for oneshot threaded interrupts
handled by this chip, deferring the irq_eoi() callback until after the
threaded handler completes.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260616-hamoa_pdc_v3-v3-0-4d8e1504ea75@oss.qualcomm.com?part=6
next prev parent reply other threads:[~2026-06-16 9:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-16 9:25 [PATCH v3 0/8] x1e80100: Enable PDC wake GPIOs and deepest idle state Maulik Shah
2026-06-16 9:25 ` [PATCH v3 1/8] irqchip/qcom-pdc: restructure version support Maulik Shah
2026-06-16 9:25 ` [PATCH v3 2/8] irqchip/qcom-pdc: Move all statics to struct pdc_desc Maulik Shah
2026-06-16 9:25 ` [PATCH v3 3/8] irqchip/qcom-pdc: Remove pdc_enable_intr() wrapper Maulik Shah
2026-06-16 9:36 ` sashiko-bot
2026-06-16 9:25 ` [PATCH v3 4/8] irqchip/qcom-pdc: Differentiate between direct SPI and GPIO as SPI Maulik Shah
2026-06-16 9:25 ` [PATCH v3 5/8] irqchip/qcom-pdc: Configure PDC to pass through mode Maulik Shah
2026-06-16 9:43 ` sashiko-bot
2026-06-16 9:25 ` [PATCH v3 6/8] pinctrl: qcom: Acknowledge IRQs for PDC interrupt controller Maulik Shah
2026-06-16 9:45 ` sashiko-bot [this message]
2026-06-16 9:25 ` [PATCH v3 7/8] Revert "pinctrl: qcom: x1e80100: Bypass PDC wakeup parent for now" Maulik Shah
2026-06-16 9:25 ` [PATCH v3 8/8] arm64: dts: qcom: x1e80100: Add deepest idle state Maulik Shah
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=20260616094520.376531F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=maulik.shah@oss.qualcomm.com \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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