From: Hui Wang <hui.wang@canonical.com>
To: Manuel Krause <manuelkrause@netscape.net>,
"Rafael J. Wysocki" <rafael@kernel.org>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Rafael Wysocki <rafael.j.wysocki@intel.com>
Subject: Re: [PATCH v3] ACPI: resources: add legacy irq override exception by DMI info
Date: Thu, 16 Sep 2021 07:04:46 +0800 [thread overview]
Message-ID: <6609e8a2-1f05-3c0b-8067-8ada8f5742a7@canonical.com> (raw)
In-Reply-To: <8e93e2ee-b403-c938-d730-7deacbfd759e@netscape.net>
On 9/16/21 3:05 AM, Manuel Krause wrote:
> On 15/09/2021 20:13, Rafael J. Wysocki wrote:
>>
[...]
>>> + if (check_override &&
>>> + acpi_dev_irq_override(gsi, triggering, polarity,
>>> shareable) &&
>>> + !acpi_get_override_irq(gsi, &t, &p)) {
>>> u8 trig = t ? ACPI_LEVEL_SENSITIVE :
>>> ACPI_EDGE_SENSITIVE;
>>> u8 pol = p ? ACPI_ACTIVE_LOW : ACPI_ACTIVE_HIGH;
>>>
>>> --
>>
>> Applied as 5.16 material under the subject "ACPI: resources: Add
>> DMI-based legacy IRQ override quirk" with some changelog edits.
>>
>> Thanks!
>>
>
Thanks Rafael.
> We have to thank you, Rafael, for investing your time and covering
> this issue + fix again!
>
> I just want to add now, that also PATCH v3 works fine on here (with
> kernel v5.14.4 now).
>
> I'm still not familiar with the kernel patch queueing mechanisms, so
> forgive my possibly bothering question:
> Would it be possible (e.g. for you) to get that fix into earlier
> kernel versions? Simple reason to ask for it: Some people thinking
> over to return their newly bought machine of this type without proper
> out-of-the-box Linux support.
> It shouldn't be my business, but I understand those folks' concerns.
>
>
Hi Manuel,
After the patch is in the linux-next, at least I will backport the patch
to ubuntu 20.04, 20.10 and 21.04 kernels.
Regards,
Hui.
> TIA and best regards,
>
> Manuel
prev parent reply other threads:[~2021-09-15 23:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 13:09 [PATCH v3] ACPI: resources: add legacy irq override exception by DMI info Hui Wang
2021-09-15 18:13 ` Rafael J. Wysocki
2021-09-15 19:05 ` Manuel Krause
2021-09-15 23:04 ` Hui Wang [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=6609e8a2-1f05-3c0b-8067-8ada8f5742a7@canonical.com \
--to=hui.wang@canonical.com \
--cc=linux-acpi@vger.kernel.org \
--cc=manuelkrause@netscape.net \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@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;
as well as URLs for NNTP newsgroup(s).