From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Michael Walle <mwalle@kernel.org>
Cc: longzhao@ambarella.com, Bartosz Golaszewski <brgl@kernel.org>,
linux-gpio@vger.kernel.org, Linus Walleij <linusw@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
Conor Dooley <conor+dt@kernel.org>,
Mika Westerberg <westeri@kernel.org>,
linux-acpi@vger.kernel.org, devicetree@vger.kernel.org,
Long Zhao <zl020895@163.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v13 08/13] gpio: regmap: remove gpiochip before tearing down irqchip
Date: Tue, 3 Nov 2026 19:50:02 +0200 [thread overview]
Message-ID: <auoeysEHqGemmuhO@ashevche-desk.local> (raw)
In-Reply-To: <DMKL43ZCOSQ3.3TAJL8BRQ6ZTH@kernel.org>
On Mon, Nov 02, 2026 at 09:33:20AM +0100, Michael Walle wrote:
> On Mon Nov 2, 2026 at 7:46 AM CET, Long Zhao via B4 Relay wrote:
> >
> > gpio_regmap_unregister() currently calls regmap_del_irq_chip() before
> > gpiochip_remove(). That disposes the mapped virtual IRQs and frees the
> > irq_domain while ACPI GPIO-signaled events may still be requested and
> > while gpiod_free_irqs() still needs gc->irq.domain.
>
> Maybe Andy have an opinion here. But that deviated from the usual
> cleanup in the reverse order and at least deserves a comment in the
> code.
Yeah, this is unfortunate. I think to make it work as proposed the IRQ domain
handling in GPIOLIB should be revisited. So, at least a good comment is a must,
indeed.
> > Remove the gpio_chip first so ACPI teardown and USED_AS_IRQ cleanup run
> > against a live domain, then delete the regmap irqchip. Use the same
> > order on the registration error path, which previously leaked the
> > irqchip when gpiochip_irqchip_add_domain() failed after
> > regmap_add_irq_chip_fwnode().
>
> This should be split into a seperate patch with a Fixes: tag.
Not sure if we need a separate change here as two are coupled.
I leave it to Bart to decide.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-11-03 17:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 6:45 [PATCH v13 00/13] gpio: add Ambarella CV75 PL061 support Long Zhao via B4 Relay
2026-11-02 6:45 ` [PATCH v13 01/13] dt-bindings: gpio: pl061: add Ambarella CV75 variant Long Zhao via B4 Relay
2026-11-02 6:45 ` [PATCH v13 02/13] gpiolib: regmap: add GPIO_REGMAP_QUIRK_SET_AFTER_DIR Long Zhao via B4 Relay
2026-11-02 8:35 ` Michael Walle
2026-11-02 6:45 ` [PATCH v13 03/13] gpio: pl061: drop redundant pending check in the IRQ handler Long Zhao via B4 Relay
2026-11-02 6:45 ` [PATCH v13 04/13] gpio: pl061: convert register access to regmap Long Zhao via B4 Relay
2026-11-02 6:45 ` [PATCH v13 05/13] gpio: pl061: use IRQ_TYPE_LEVEL_MASK and IRQ_TYPE_EDGE_BOTH Long Zhao via B4 Relay
2026-11-02 6:45 ` [PATCH v13 06/13] gpio: pl061: use cleanup helpers for locks Long Zhao via B4 Relay
2026-11-02 6:46 ` [PATCH v13 07/13] gpio: pl061: keep the parent device in a local Long Zhao via B4 Relay
2026-11-02 6:46 ` [PATCH v13 08/13] gpio: regmap: remove gpiochip before tearing down irqchip Long Zhao via B4 Relay
2026-11-02 8:33 ` Michael Walle
2026-11-03 17:50 ` Andy Shevchenko [this message]
2026-11-03 17:46 ` Andy Shevchenko
2026-11-02 6:46 ` [PATCH v13 09/13] gpiolib: request ACPI GPIO events for external IRQ domains Long Zhao via B4 Relay
2026-11-03 11:58 ` Andy Shevchenko
2026-11-02 6:46 ` [PATCH v13 10/13] gpio: pl061: switch data path to gpio-regmap Long Zhao via B4 Relay
2026-11-02 6:46 ` [PATCH v13 11/13] gpio: pl061: add Ambarella register-layout variant Long Zhao via B4 Relay
2026-11-02 6:46 ` [PATCH v13 12/13] gpio: pl061: tidy up IRQ trigger logging Long Zhao via B4 Relay
2026-11-03 16:53 ` Andy Shevchenko
2026-11-02 6:46 ` [PATCH v13 13/13] gpio: pl061: use string_choices helpers for " Long Zhao via B4 Relay
2026-11-03 16:54 ` 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=auoeysEHqGemmuhO@ashevche-desk.local \
--to=andriy.shevchenko@linux.intel.com \
--cc=brgl@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linusw@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longzhao@ambarella.com \
--cc=mwalle@kernel.org \
--cc=robh@kernel.org \
--cc=westeri@kernel.org \
--cc=zl020895@163.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
all inboxes | Powered by JetHome®