From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: linux-acpi@vger.kernel.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>, Aaron Lu <aaron.lu@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Revert "ACPI / video: Add HP EliteBook Revolve 810 to the blacklist"
Date: Fri, 14 Feb 2014 17:26:01 +0200 [thread overview]
Message-ID: <20140214152601.GL5018@intel.com> (raw)
In-Reply-To: <s5hy51dzr9f.wl%tiwai@suse.de>
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?
next prev parent reply other threads:[~2014-02-14 15:18 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 [this message]
2014-02-14 22:21 ` Rafael J. Wysocki
2014-02-17 5:52 ` Aaron Lu
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=20140214152601.GL5018@intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=aaron.lu@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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