From: "Arnd Bergmann" <arnd@arndb.de>
To: "Thorsten Leemhuis" <regressions@leemhuis.info>,
"Daniel Mack" <daniel@zonque.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
manikanta.guntupalli@amd.com
Cc: linux-kernel@vger.kernel.org, stable@kernel.org,
"Bartosz Golaszewski" <bartosz.golaszewski@linaro.org>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Linux kernel regressions list" <regressions@lists.linux.dev>
Subject: Re: [PATCH] gpio: zynq: restore zynq_gpio_irq_reqres/zynq_gpio_irq_relres callbacks
Date: Wed, 06 Sep 2023 16:12:43 -0400 [thread overview]
Message-ID: <93e5e75d-3cfc-485b-9f81-54c82c58e24e@app.fastmail.com> (raw)
In-Reply-To: <6406fb2e-afb2-461d-9bac-aa157cf6d16f@leemhuis.info>
On Wed, Sep 6, 2023, at 09:49, Thorsten Leemhuis wrote:
> CCing Arnd (wrote the culprit), Linus (reviewed it), Bartosz (applied
> it), and the regressions mailing list
Thanks
> On 01.09.23 14:24, Daniel Mack wrote:
>> Commit f56914393537 ("gpio: zynq: fix zynqmp_gpio not an immutable chip
>> warning") ditched the open-coded resource allocation handlers in favor
>> of the generic ones. These generic handlers don't maintain the PM
>> runtime anymore, which causes a regression in that level IRQs are no
>> longer reported.
>>
>> Restore the original handlers to fix this.
>>
>> Signed-off-by: Daniel Mack <daniel@zonque.org>
>> Fixes: f56914393537 ("gpio: zynq: fix zynqmp_gpio not an immutable chip warning")
>> Cc: stable@kernel.org
>
> This seems to be a regression report that comes straight with a fix, but
> there wasn't a single reply yet afaics. :-/ Maybe the extended list of
> recipients will get things moving. But to ensure this doesn't fall
> through the cracks, I'll add it to the list of tracked regressions.
I don't understand what the GPIOCHIP_IRQ_RESOURCE_HELPERS change
intended to do in the first place: Manikanta's patch changed the behavior
here with the addition of GPIOCHIP_IRQ_RESOURCE_HELPERS, while my patch
was a cleanup that removed the dead code.
Daniel's fix reverts both my cleanup patch and part of the original
change, which may or may not be what we want here.
Arnd
next prev parent reply other threads:[~2023-09-06 20:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 12:24 Daniel Mack
2023-09-06 13:49 ` Thorsten Leemhuis
2023-09-06 20:12 ` Arnd Bergmann [this message]
2023-09-06 20:50 ` Daniel Mack
2023-09-06 15:08 ` Bartosz Golaszewski
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=93e5e75d-3cfc-485b-9f81-54c82c58e24e@app.fastmail.com \
--to=arnd@arndb.de \
--cc=bartosz.golaszewski@linaro.org \
--cc=daniel@zonque.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manikanta.guntupalli@amd.com \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=stable@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
all inboxes | Powered by JetHome®