From: Armin Wolf <W_Armin@gmx.de>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: lenb@kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] ACPI: bus: _OSC fixes
Date: Wed, 13 Mar 2024 23:28:55 +0100 [thread overview]
Message-ID: <2e8100b0-d87c-413e-bcb1-b91c3ce41633@gmx.de> (raw)
In-Reply-To: <CAJZ5v0hKwThcAO4jMOzi7ySqSv_jHvs_+paBB212qVsaf7LZng@mail.gmail.com>
Am 12.03.24 um 21:10 schrieb Rafael J. Wysocki:
> On Sat, Mar 9, 2024 at 9:13 PM Armin Wolf <W_Armin@gmx.de> wrote:
>> This patch series fixes the handling of various ACPI features bits
>> when evaluating _OSC.
>>
>> The first three patches fix the reporting of various features supported
>> by the kernel, while the fourth patch corrects the feature bit used to
>> indicate support for the "Generic Initiator Affinity" in SRAT.
>>
>> The last patch fixes the reporting of IRQ ResourceSource support. Unlike
>> the other feature bits, the ACPI specification states that this feature
>> bit might be used by the ACPI firmware to indicate whether or not it
>> supports the usage of IRQ ResourceSource:
>>
>> "If not set, the OS may choose to ignore the ResourceSource
>> parameter in the extended interrupt descriptor."
>>
>> Since the code responsible for parsing IRQ ResourceSource already checks
>> if ResourceSource is present, i assumed that we can omit taking this
>> into account.
>>
>> All patches where tested on a Asus Prime B650-Plus and a Dell Inspiron
>> 3505.
>>
>> Armin Wolf (5):
>> ACPI: bus: Indicate support for _TFP thru _OSC
>> ACPI: bus: Indicate support for more than 16 p-states thru _OSC
>> ACPI: bus: Indicate support for the Generic Event Device thru _OSC
>> ACPI: Fix Generic Initiator Affinity _OSC bit
>> ACPI: bus: Indicate support for IRQ ResourceSource thru _OSC
>>
>> drivers/acpi/bus.c | 5 +++++
>> include/linux/acpi.h | 6 +++++-
>> 2 files changed, 10 insertions(+), 1 deletion(-)
>>
>> --
> All of that looks reasonable to me, but do you know about systems in
> the field where any of these patches actually fix functionality?
>
> If not, I'd prefer to queue them up for 6.10 as they are likely to
> change behavior, at least in corner cases.
>
> Thanks!
Hi,
i know no system which even queries those feature bits, so i am fine with
this landing in 6.10.
Thanks,
Armin Wolf
next prev parent reply other threads:[~2024-03-13 22:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-09 20:13 [PATCH 0/5] ACPI: bus: _OSC fixes Armin Wolf
2024-03-09 20:13 ` [PATCH 1/5] ACPI: bus: Indicate support for _TFP thru _OSC Armin Wolf
2024-03-09 20:13 ` [PATCH 2/5] ACPI: bus: Indicate support for more than 16 p-states " Armin Wolf
2024-03-09 20:13 ` [PATCH 3/5] ACPI: bus: Indicate support for the Generic Event Device " Armin Wolf
2024-03-09 20:13 ` [PATCH 4/5] ACPI: Fix Generic Initiator Affinity _OSC bit Armin Wolf
2024-03-09 20:13 ` [PATCH 5/5] ACPI: bus: Indicate support for IRQ ResourceSource thru _OSC Armin Wolf
2024-03-12 20:10 ` [PATCH 0/5] ACPI: bus: _OSC fixes Rafael J. Wysocki
2024-03-13 22:28 ` Armin Wolf [this message]
2024-03-27 15:41 ` Rafael J. Wysocki
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=2e8100b0-d87c-413e-bcb1-b91c3ce41633@gmx.de \
--to=w_armin@gmx.de \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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