From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Jean Delvare <jdelvare@suse.de>, Alex Hung <alex.hung@canonical.com>
Cc: rjw@rjwysocki.net, lenb@kernel.org, gregkh@linuxfoundation.org,
davem@davemloft.net, mika.westerberg@linux.intel.com,
f.fainelli@gmail.com, dmitry.torokhov@gmail.com, kishon@ti.com,
karniksayli1995@gmail.com, linux-acpi@vger.kernel.org,
Mario.Limonciello@dell.com
Subject: Re: [PATCH 2/2] ACPI / osi: add DMI quirk for Dell systems
Date: Mon, 05 Feb 2018 16:15:00 +0200 [thread overview]
Message-ID: <1517840100.22495.25.camel@linux.intel.com> (raw)
In-Reply-To: <20180205141447.6e1442ac@endymion>
On Mon, 2018-02-05 at 14:14 +0100, Jean Delvare wrote:
> On Wed, 31 Jan 2018 00:40:05 -0800, Alex Hung wrote:
> > A number of Dell systems require an OEM _OSI string "Linux-Dell-
> > Video" as
> > a BIOS workaround for a system hang bug caused by discrete VGA. The
> > form of
> > the OEM _OSI string is discussed in Documentation/acpi/osi.txt and
> > is
> > defined by each OEM.
>
> I admit I don't understand how it is the operating system's job to
> carry the information from the BIOS to the BIOS.
> > + for (i = 0; i < OSI_STRING_ENTRIES_MAX; i++) {
> > + osi = &osi_setup_entries[i];
> > + if (!strcmp(osi->string, str)) {
>
> This can only happen if the user passes acpi_osi=Linux-Dell-Video or
> acpi_osi=!Linux-Dell-Video on the boot command line, right?
>
> > + osi->enable = true;
>
> Does this not prevent the user from explicitly disabling it with
> acpi_osi=!Linux-Dell-Video ?
Playing with OSI string is a bad idea. I wouldn't do anything while
Rafael, or even Len can confirm that is the right thing to do.
For me, AFAIK we need to be bug-to-bug compatible with Windows (at least
on ACPICA side), so, what Windows exactly does on such laptops?
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2018-02-05 14:15 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 8:40 [PATCH 1/2] firmware: dmi_scan: add DMI_OEM_STRING support to dmi_matches Alex Hung
2018-01-31 8:40 ` [PATCH 2/2] ACPI / osi: add DMI quirk for Dell systems Alex Hung
2018-02-05 13:14 ` Jean Delvare
2018-02-05 14:15 ` Andy Shevchenko [this message]
2018-02-05 17:36 ` Mario.Limonciello
2018-02-05 22:45 ` Dmitry Torokhov
2018-02-06 0:45 ` Mario.Limonciello
2018-02-06 13:45 ` Andy Shevchenko
2018-02-06 16:24 ` Mario.Limonciello
2018-02-07 20:38 ` Alex Hung
2018-02-07 20:49 ` Mario.Limonciello
2018-02-11 9:29 ` Rafael J. Wysocki
2018-02-11 13:45 ` Lukas Wunner
2018-02-12 9:49 ` Rafael J. Wysocki
2018-02-12 20:29 ` Mario.Limonciello
2018-02-12 22:57 ` Rafael J. Wysocki
2018-02-12 23:14 ` Mario.Limonciello
2018-02-13 5:25 ` Alex Hung
2018-02-13 7:32 ` Mika Westerberg
2018-02-14 9:06 ` Rafael J. Wysocki
2018-02-14 9:50 ` Mika Westerberg
2018-02-13 9:18 ` Rafael J. Wysocki
2018-02-13 9:55 ` Lukas Wunner
2018-02-14 9:10 ` Rafael J. Wysocki
2018-02-14 18:47 ` Mario.Limonciello
2018-02-15 9:44 ` Rafael J. Wysocki
2018-02-05 17:24 ` Mario.Limonciello
2018-02-05 21:55 ` Jean Delvare
2018-02-07 20:05 ` Alex Hung
2018-02-05 10:26 ` [PATCH 1/2] firmware: dmi_scan: add DMI_OEM_STRING support to dmi_matches Jean Delvare
2018-02-07 5:25 ` Alex Hung
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=1517840100.22495.25.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=Mario.Limonciello@dell.com \
--cc=alex.hung@canonical.com \
--cc=davem@davemloft.net \
--cc=dmitry.torokhov@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jdelvare@suse.de \
--cc=karniksayli1995@gmail.com \
--cc=kishon@ti.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rjw@rjwysocki.net \
/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).