From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
Len Brown <lenb@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [REGRESSION/PATCH] acpi: blacklist win8 OSI for ASUS Zenbok Prime UX31A
Date: Mon, 29 Jul 2013 22:17:54 +0200 [thread overview]
Message-ID: <7981076.SojlpLkL71@vostro.rjw.lan> (raw)
In-Reply-To: <1375125658-1223-1-git-send-email-felipe.contreras@gmail.com>
On Monday, July 29, 2013 02:20:58 PM Felipe Contreras wrote:
> Since v3.7 the acpi backlight driver doesn't work at all on this machine
> because presumably the ACPI code contains stub code when Windows 8 OSI is
> reported.
>
> The commit ea45ea7 (in v3.11-rc2) tried to fix this problem by using the intel
> backlight driver, however, on this machine it turns the backlight completely
> off when it reaches level 0%, after which the user might have a lot trouble
> trying to bring it back.
>
> This patch fixes both regressions by blacklisting the win8 OSI, so we are back
> to v3.6 behavior, and it should remain that way until the intel backlight
> driver is fixed.
Well, it really is a workaround, so perhaps it would be fair to call it this
way?
> Since v3.7, users have been forced to fix the initial regression by modifying
> the boot arguments [1].
>
> [1] https://wiki.archlinux.org/index.php/ASUS_Zenbook_Prime_UX31A
>
> Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
I don't really feel this is the right approach, but then I don't care enough
to fight with you. :-)
I'll queue up this patch for 3.12.
Thanks,
Rafael
> ---
> drivers/acpi/blacklist.c | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/drivers/acpi/blacklist.c b/drivers/acpi/blacklist.c
> index cb96296..a404127 100644
> --- a/drivers/acpi/blacklist.c
> +++ b/drivers/acpi/blacklist.c
> @@ -192,6 +192,12 @@ static int __init dmi_disable_osi_win7(const struct dmi_system_id *d)
> acpi_osi_setup("!Windows 2009");
> return 0;
> }
> +static int __init dmi_disable_osi_win8(const struct dmi_system_id *d)
> +{
> + printk(KERN_NOTICE PREFIX "DMI detected: %s\n", d->ident);
> + acpi_osi_setup("!Windows 2012");
> + return 0;
> +}
>
> static struct dmi_system_id acpi_osi_dmi_table[] __initdata = {
> {
> @@ -267,6 +273,14 @@ static struct dmi_system_id acpi_osi_dmi_table[] __initdata = {
> DMI_MATCH(DMI_PRODUCT_NAME, "Satellite P305D"),
> },
> },
> + {
> + .callback = dmi_disable_osi_win8,
> + .ident = "ASUS Zenbook Prime UX31A",
> + .matches = {
> + DMI_MATCH(DMI_SYS_VENDOR, "ASUSTeK COMPUTER INC."),
> + DMI_MATCH(DMI_PRODUCT_NAME, "UX31A"),
> + },
> + },
>
> /*
> * BIOS invocation of _OSI(Linux) is almost always a BIOS bug.
>
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2013-07-29 20:07 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 19:20 Felipe Contreras
2013-07-29 20:17 ` Rafael J. Wysocki [this message]
2013-07-29 20:22 ` Felipe Contreras
2013-07-29 20:47 ` Rafael J. Wysocki
2013-07-29 21:04 ` Felipe Contreras
2013-07-30 3:11 ` Aaron Lu
2013-07-30 3:44 ` Felipe Contreras
2013-07-30 5:51 ` Aaron Lu
2013-07-30 5:57 ` Aaron Lu
2013-07-30 13:42 ` Rafael J. Wysocki
2013-07-30 20:59 ` Felipe Contreras
2013-07-30 23:13 ` Rafael J. Wysocki
2013-07-31 0:11 ` Felipe Contreras
2013-07-31 1:36 ` Aaron Lu
2013-07-31 2:07 ` Felipe Contreras
2013-07-31 2:22 ` Aaron Lu
2013-08-01 18:50 ` Felipe Contreras
2013-07-31 5:14 ` Matthew Garrett
2013-07-31 11:32 ` Felipe Contreras
2013-07-31 14:00 ` Matthew Garrett
2013-07-31 17:46 ` Felipe Contreras
2013-07-31 17:52 ` Matthew Garrett
2013-07-31 18:07 ` Felipe Contreras
2013-07-31 18:47 ` Matthew Garrett
2013-08-01 17:37 ` Felipe Contreras
2013-08-01 17:42 ` Matthew Garrett
2013-08-01 17:50 ` Felipe Contreras
2013-08-01 18:01 ` Matthew Garrett
2013-08-01 18:11 ` Felipe Contreras
2013-08-01 23:40 ` Felipe Contreras
2013-07-31 1:59 ` Aaron Lu
2013-07-31 2:09 ` Felipe Contreras
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=7981076.SojlpLkL71@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=felipe.contreras@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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®