From: Mario Limonciello <mario.limonciello@amd.com>
To: <linux-kernel@vger.kernel.org>, <linux-acpi@vger.kernel.org>,
<rafael@kernel.org>, Len Brown <lenb@kernel.org>
Cc: <kherbst@redhat.com>, <nouveau@lists.freedesktop.org>,
<hdegoede@redhat.com>, <ddadap@nvidia.com>,
<kai.heng.feng@canonical.com>, <Dell.Client.Kernel@dell.com>,
Mario Limonciello <mario.limonciello@amd.com>
Subject: [RFC 0/2] Stop the abuse of Linux-* _OSI strings
Date: Fri, 19 Aug 2022 09:25:17 -0500 [thread overview]
Message-ID: <20220819142519.5684-1-mario.limonciello@amd.com> (raw)
3 _OSI strings were introduced in recent years that were intended
to workaround very specific problems found on specific systems.
The idea was supposed to be that these quirks were only used on
those systems, but this proved to be a bad assumption. I've found
at least one system in the wild where the vendor using the _OSI
string doesn't match the _OSI string and the neither does the use.
So this brings a good time to review keeping those strings in the kernel.
There are 3 strings that were introduced:
Linux-Dell-Video
-> Intended for systems with NVIDIA cards that didn't support RTD3
Linux-Lenovo-NV-HDMI-Audio
-> Intended for powering on NVIDIA HDMI device
Linux-HPI-Hybrid-Graphics
-> Intended for changing dGPU output
AFAIK the first string is no longer relevant as nouveau now supports
RTD3. If that's wrong, this can be changed for the series.
The second two strings appear to be non-scalable workarounds. For
accomplishing these tasks, registers can be written from kernel drivers
or custom ASL can be put behind a _DSM. By forcing either of these two
solutions it will better let the Linux kernel control the behavior.
Based on the above this series drops the first string and marks the second
two strings to only apply to older systems.
Link: https://lore.kernel.org/all/54add026bb6f45fd94a2dc2bae4adf9f@AUSX13MPC101.AMER.DELL.COM/T/
Mario Limonciello (2):
ACPI: OSI: Remove Linux-Dell-Video _OSI string
ACPI: OSI: Deprecate some abused _OSI strings
Documentation/firmware-guide/acpi/osi.rst | 24 ++++++++----------
drivers/acpi/osi.c | 31 ++++++++++++-----------
2 files changed, 26 insertions(+), 29 deletions(-)
--
2.34.1
next reply other threads:[~2022-08-19 14:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 14:25 Mario Limonciello [this message]
2022-08-19 14:25 ` [RFC 1/2] ACPI: OSI: Remove Linux-Dell-Video _OSI string Mario Limonciello
2022-08-19 14:25 ` [RFC 2/2] ACPI: OSI: Deprecate some abused _OSI strings Mario Limonciello
2022-08-19 22:02 ` Daniel Dadap
2022-08-19 15:44 ` [RFC 0/2] Stop the abuse of Linux-* " Karol Herbst
2022-08-19 16:00 ` Limonciello, Mario
2022-08-19 16:37 ` Karol Herbst
2022-08-19 16:43 ` Limonciello, Mario
2022-08-19 16:47 ` Karol Herbst
2022-08-22 21:18 ` Lyude Paul
2022-08-23 3:47 ` Kai-Heng Feng
2022-08-23 17:05 ` Lyude Paul
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=20220819142519.5684-1-mario.limonciello@amd.com \
--to=mario.limonciello@amd.com \
--cc=Dell.Client.Kernel@dell.com \
--cc=ddadap@nvidia.com \
--cc=hdegoede@redhat.com \
--cc=kai.heng.feng@canonical.com \
--cc=kherbst@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nouveau@lists.freedesktop.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
all inboxes | Powered by JetHome®