[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4e9e5ec1-e040-49e0-84a4-9f86c0fcec1b@leemhuis.info>
Date: Wed, 7 Feb 2024 09:07:09 +0100
From: "Linux regression tracking (Thorsten Leemhuis)"
<regressions@...mhuis.info>
To: Linus Walleij <linus.walleij@...aro.org>,
Mario Limonciello <mario.limonciello@....com>
Cc: Basavaraj Natikar <Basavaraj.Natikar@....com>,
Shyam Sundar S K <Shyam-sundar.S-k@....com>,
"Rafael J . Wysocki" <rafael.j.wysocki@...el.com>,
"open list:PIN CONTROL SUBSYSTEM" <linux-gpio@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>,
"Rafael J . Wysocki" <rafael@...nel.org>,
Christian Heusel <christian@...sel.eu>,
Linux kernel regressions list <regressions@...ts.linux.dev>
Subject: Re: [PATCH] pinctrl: amd: Add IRQF_ONESHOT to the interrupt request
On 31.01.24 10:06, Linus Walleij wrote:
> On Tue, Jan 23, 2024 at 7:08 PM Mario Limonciello
> <mario.limonciello@....com> wrote:
>
>> On some systems the interrupt is shared between GPIO controller
>> and ACPI SCI. When the interrupt is shared with the ACPI SCI the
>> flags need to be identical.
>>
>> This should fix the GPIO controller failing to work after commit
>> 7a36b901a6eb ("ACPI: OSL: Use a threaded interrupt handler for SCI").
>> ```
>> [ 0.417335] genirq: Flags mismatch irq 9. 00000088 (pinctrl_amd) vs. 00002080 (acpi)
>> [ 0.420073] amd_gpio: probe of AMDI0030:00 failed with error -16
>> ```
>>
>> Cc: Rafael J. Wysocki <rafael@...nel.org>
>> Reported-by: Christian Heusel <christian@...sel.eu>
>> Closes: https://bugzilla.kernel.org/show_bug.cgi?id=218407
>> Fixes: 7a36b901a6eb ("ACPI: OSL: Use a threaded interrupt handler for SCI")
>> Link: https://lore.kernel.org/linux-acpi/CAJZ5v0iRqUXeuKmC_+dAJtDBLWQ3x15n4gRH48y7MEaLoXF+UA@mail.gmail.com/T/#mc5506014141b61e472b24e095889535a04458083
>> Signed-off-by: Mario Limonciello <mario.limonciello@....com>
>
> Patch applied for fixes!
Hmm, Linus, that was a week ago and I still can't spot the fix in -next
or
https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git
; am I missing something or did something come up?
Furthermore Christian seems to grow impatient -- and I do as well, as I
recently couldn't wake up my laptop due to this while on the road. :-/
As at least one of the affected machines is quite popular in Linux
community, I'd prefer if we can fix this rather sooner than later.
Linus, if you are busy, I could ask the other Linus to pick this up
straight from the list if that's okay for you.
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.
Powered by blists - more mailing lists