From: Aaron Lu <aaron.lu@intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Takashi Iwai <tiwai@suse.de>,
linux-acpi@vger.kernel.org, Len Brown <lenb@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Revert "ACPI / video: Add HP EliteBook Revolve 810 to the blacklist"
Date: Mon, 17 Feb 2014 13:52:46 +0800 [thread overview]
Message-ID: <5301A3AE.9030703@intel.com> (raw)
In-Reply-To: <5716481.SxKZLEy9L1@vostro.rjw.lan>
On 02/15/2014 06:21 AM, Rafael J. Wysocki wrote:
> On Friday, February 14, 2014 05:26:01 PM Mika Westerberg wrote:
>> On Fri, Feb 14, 2014 at 03:46:20PM +0100, Takashi Iwai wrote:
>>> The acpi_osi blacklist is just a workaround, and if we have better
>>> solutions, it should be removed. That's why I'm asking it.
>>>
>>> So, after removing acpi_osi blacklist, and keeping your video
>>> blacklist patch, the backlight works?
>>
>> Yes, the backlight works (there is only intel_backlight listed under
>> /sys/class/backlight).
>>
>>> If yes, as mentioned, we should think of rather extending this video
>>> blacklist to more EliteBook G1 and ProBook G1 machines, and remove
>>> acpi_osi blacklist instead.
>>
>> Makes sense to me. (Well, I'm fine as long as backlight on my machine works
>> ;-))
>>
>> Aaron, Rafael, any comments on this?
>
> I generally agree with Takashi, but I'm not sure what to do for 3.14.
I can re-base the previously sent patch titled:
[PATCH] ACPI / video: Add systems that should favor native backlight interface
And put Mika's system into the DMI table that will use native backlight
interface in video module and remove it from video_detect's DMI table at
the same time. Does this sound OK?
next prev parent reply other threads:[~2014-02-17 5:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 12:34 [PATCH] Revert "ACPI / video: Add HP EliteBook Revolve 810 to the blacklist" Mika Westerberg
2014-02-14 13:37 ` Takashi Iwai
2014-02-14 14:03 ` Mika Westerberg
2014-02-14 14:01 ` Takashi Iwai
2014-02-14 14:16 ` Mika Westerberg
2014-02-14 14:16 ` Takashi Iwai
2014-02-14 14:45 ` Mika Westerberg
2014-02-14 14:46 ` Takashi Iwai
2014-02-14 14:50 ` Aaron Lu
2014-02-14 14:54 ` Takashi Iwai
2014-02-14 15:26 ` Mika Westerberg
2014-02-14 22:21 ` Rafael J. Wysocki
2014-02-17 5:52 ` Aaron Lu [this message]
2014-02-17 9:56 ` Takashi Iwai
2014-02-17 13:07 ` Aaron Lu
2014-02-17 9:57 ` Mika Westerberg
2014-02-14 14:47 ` 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=5301A3AE.9030703@intel.com \
--to=aaron.lu@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rjw@rjwysocki.net \
--cc=tiwai@suse.de \
/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