From: Takashi Iwai <tiwai@suse.de>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: Takashi Iwai <tiwai@suse.de>,
Shreeya Patel <shreeya.patel@collabora.com>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
regressions@lists.linux.dev,
Mario Limonciello <mario.limonciello@amd.com>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>
Subject: Re: [REGRESSION] Missing IRQ via amd_gpio
Date: Fri, 22 Apr 2022 16:33:15 +0200 [thread overview]
Message-ID: <s5hy1zxrxw4.wl-tiwai@suse.de> (raw)
In-Reply-To: <e4c9bb60-210d-243a-e225-6b3546c0b42b@leemhuis.info>
On Fri, 22 Apr 2022 16:17:36 +0200,
Thorsten Leemhuis wrote:
>
> Hi Takashi! Thx for CCing the regression list.
>
> On 22.04.22 15:03, Takashi Iwai wrote:
> > Hi,
> >
> > we received a bug report for 5.17.3 kernel showing a new error:
> >
> > amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x003D to IRQ, err -517
> >
> > Not only an error message but in practice this leads to a missing IRQ
> > assignment; the IRQ 27 is no longer assigned to amd_gpio driver.
> >
> > As the error number (EPROBE_DEFER) indicates, this seems to be the
> > side-effect of the recent fix, the upstream commit 5467801f1fcb
> > ("gpio: Restrict usage of GPIO chip irq members before
> > initialization"). As far as I understand, the problem is in
> > acpi_gpiochip_request_interrupts() call that is called from
> > gpiochip_add_irqchip() itself. Since it's called before the
> > initialized flag set, it always fails now.
> >
> > Below is a temporary quick fix and it seems working. But I'm not sure
> > whether I overlooked something obvious...
>
> A patch that afaics will fix this hopefully should get merged really
> soon now:
>
> https://lore.kernel.org/all/20220422131452.20757-1-mario.limonciello@amd.com/
>
> See also v1:
>
> https://lore.kernel.org/all/20220414025705.598-1-mario.limonciello@amd.com/
Thanks, good to know that we reached to the very same fix :)
So, feel free to take my tags to Mario's patch, if any:
Reviewed-by: Takashi Iwai <tiwai@suse.de>
Tested-by: Takashi Iwai <tiwai@suse.de>
Takashi
prev parent reply other threads:[~2022-04-22 14:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 13:03 Takashi Iwai
2022-04-22 14:17 ` Thorsten Leemhuis
2022-04-22 14:29 ` Thorsten Leemhuis
2022-04-22 14:33 ` Takashi Iwai [this message]
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=s5hy1zxrxw4.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=shreeya.patel@collabora.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®