stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Aaron Lu <aaron.lu@intel.com>
To: Josh Boyer <jwboyer@fedoraproject.org>,
	Dmitry Tunin <hanipouspilot@gmail.com>
Cc: "linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	Matthew Garrett <mjg59@srcf.ucam.org>,
	Jani Nikula <jani.nikula@linux.intel.com>
Subject: Re: [PATCH v3 1/2] acpi: Add "acpi_osi=" for ASUS X200MA to enable, brightness keys
Date: Fri, 19 Dec 2014 09:46:08 +0800	[thread overview]
Message-ID: <54938360.4000804@intel.com> (raw)
In-Reply-To: <CA+5PVA43jLUp4K9=56nwgQJEyLB9EkEynb2PqfEhBWD8q-m-DQ@mail.gmail.com>

CC Jani, who is working on the patchset to enable 8+ output devices and
may have some comments on this.

Regards,
Aaron

On 12/18/2014 09:25 PM, Josh Boyer wrote:
> On Thu, Dec 18, 2014 at 7:16 AM, Dmitry Tunin <hanipouspilot@gmail.com> wrote:
>> Add "acpi_osi=" quirk for ASUS X200MA
>> More information can be found in UX302LA bugreport
>> https://bugzilla.kernel.org/show_bug.cgi?id=70241
>>
>> X200MA is affected by th e same bug and the solution has been tested
>>
>> I reported it to launchpad too
>> https://bugs.launchpad.net/ubuntu/bug/1400068
>>
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Dmitry Tunin <hanipouspilot@gmail.com>
>>
> 
> The UX301LA models have the same setup, with 16 devices instead of 8.
> I discussed this with Matthew Garrett a bit and a more ideal approach
> is to actually enumerate all 16 devices between the firmware and i915
> driver.  The problem we have is that the intel opregion spec that
> hasn't been updated since 2008 doesn't cover the additional 8 devices.
> Anyway, that is being tracked here:
> 
> https://bugs.freedesktop.org/show_bug.cgi?id=81762
> 
>> ---
>>  drivers/acpi/blacklist.c | 20 ++++++++++++++++++++
>>  1 file changed, 20 insertions(+)
>>
>> diff --git a/drivers/acpi/blacklist.c b/drivers/acpi/blacklist.c
>> index 7556e7c..f78ed08 100644
>> --- a/drivers/acpi/blacklist.c
>> +++ b/drivers/acpi/blacklist.c
>> @@ -162,6 +162,17 @@ static int __init dmi_disable_osi_win8(const struct
>> dmi_system_id *d)
>>         acpi_osi_setup("!Windows 2012");
>>         return 0;
>>  }
>> +/*
>> + * Some ASUS models firmware declares 16 devices instead of 8
>> + * 'acpi_osi=' kernel parameter fixes it
>> + * Without this parameters brightness keys Fn+F5 and F6 do not work
>> + */
>> +static int __init dmi_disable_osi_all(const struct dmi_system_id *d)
>> +{
>> +       printk(KERN_NOTICE PREFIX "DMI detected: %s\n", d->ident);
>> +       acpi_osi_setup("");
>> +       return 0;
>> +}
> 
> What does this do to the rest of the function keys?  Does everything
> else still work as expected, including suspend and resume?
> 
>>   static struct dmi_system_id acpi_osi_dmi_table[] __initdata = {
>>         {
>> @@ -371,6 +382,15 @@ static struct dmi_system_id acpi_osi_dmi_table[]
>> __initdata = {
>>                      DMI_MATCH(DMI_PRODUCT_NAME, "1015PX"),
>>                 },
>>         },
>> +       /* Without this brightness keys do not work */
>> +       {
>> +       .callback = dmi_disable_osi_all,
>> +       .ident = "ASUSTeK COMPUTER INC. X200MA",
>> +       .matches = {
>> +                    DMI_MATCH(DMI_SYS_VENDOR, "ASUSTeK COMPUTER INC."),
>> +                    DMI_MATCH(DMI_PRODUCT_NAME, "X200MA"),
>> +               },
>> +       },
>>         {}
>>  };
>>
>> --
>> 1.9.1
>> --
>> To unsubscribe from this list: send the line "unsubscribe stable" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  parent reply	other threads:[~2014-12-19  1:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-18 12:16 [PATCH v3 1/2] acpi: Add "acpi_osi=" for ASUS X200MA to enable, brightness keys Dmitry Tunin
2014-12-18 12:19 ` [PATCH 2/2] acpi: Add "acpi_osi=" for ASUS UX302LA " Dmitry Tunin
2014-12-18 13:25 ` [PATCH v3 1/2] acpi: Add "acpi_osi=" for ASUS X200MA " Josh Boyer
2014-12-18 13:27   ` Matthew Garrett
2014-12-18 13:28   ` Dmitry Tunin
2014-12-18 13:40   ` Dmitry Tunin
2014-12-18 13:57     ` Matthew Garrett
2014-12-18 14:03       ` Dmitry Tunin
2014-12-18 14:04       ` Dmitry Tunin
2014-12-18 14:09         ` Matthew Garrett
2014-12-18 14:22           ` Dmitry Tunin
2014-12-18 14:26             ` Matthew Garrett
2014-12-18 14:34               ` Dmitry Tunin
2014-12-18 14:36                 ` Matthew Garrett
2014-12-18 14:40                   ` Dmitry Tunin
2014-12-18 14:43                     ` Matthew Garrett
2014-12-18 14:50                       ` Matthew Garrett
2014-12-18 18:09                         ` Len Brown
2014-12-18 18:20                           ` Dmitry Tunin
2014-12-18 20:04                         ` Matthew Garrett
2014-12-18 21:20                           ` Dmitry Tunin
2014-12-18 14:06       ` Dmitry Tunin
2014-12-19  1:46   ` Aaron Lu [this message]
2014-12-19  3:23     ` Aaron Lu

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=54938360.4000804@intel.com \
    --to=aaron.lu@intel.com \
    --cc=hanipouspilot@gmail.com \
    --cc=jani.nikula@linux.intel.com \
    --cc=jwboyer@fedoraproject.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=stable@vger.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).