From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Aaron Lu <aaron.lu@intel.com>
Cc: linux-acpi@vger.kernel.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ACPI / video: Add HP EliteBook Revolve 810 to the blacklist
Date: Wed, 12 Feb 2014 11:34:30 +0200 [thread overview]
Message-ID: <20140212093430.GB5018@intel.com> (raw)
In-Reply-To: <52FADD1F.90209@intel.com>
On Wed, Feb 12, 2014 at 10:31:59AM +0800, Aaron Lu wrote:
> On 02/07/2014 06:25 PM, Mika Westerberg wrote:
> > On Fri, Feb 07, 2014 at 09:29:58AM +0800, Aaron Lu wrote:
> >> On 02/03/2014 06:59 PM, Mika Westerberg wrote:
> >>> On HP EliteBook Revolve 810 the ACPI backlight device doesn't work as
> >>> expected. For example when resuming from system sleep, it seems to lose
> >>> backlight settings.
> >>>
> >>> Forcing Intel driver fixes the problem so add this machine the ACPI
> >>> video detect blacklist.
> >>
> >> For reference's purpose, can you please file a bug to kernel bugzilla
> >> under the ACPI/Power-Video category and attach the acpidump and dmesg
> >> there? Thanks.
> >
> > Done, the bug is here:
> >
> > https://bugzilla.kernel.org/show_bug.cgi?id=70231
> >
> > I noticed that using only the acpi_video0 for tuning backlight works but if
> > I use intel_backlight directly, on resume I get values from acpi_video0
> > instead. I'm not really familiar how this is supposed to work, though so
> > please let me know if I'm missing something.
>
> Thanks for the report, as communicated on the bug page, your system is
> already blacklisted for win8 by commit:
>
> commit 2d4054d8422462cb2771fdb4eb1925df55d2b320
> Author: Takashi Iwai <tiwai@suse.de> Fri Dec 20 00:09:12 2013
> Committer: Rafael J. Wysocki <rafael.j.wysocki@intel.com> Fri Dec 20 22:50:56 2013
>
> ACPI: Blacklist Win8 OSI for some HP laptop 2013 models
>
> And the fact that acpi_video interface works made it not appropriate to
> add your system into the video_detect_dmi_table. You can just use acpi_video
> interface and everything should work fine.
OK, thanks for the investigation Aaron.
I have few questions, though.
1) Is it always right thing to do to use acpi_video0 over anything else?
In my case that device first disapeared and then reappeared so I got kind
of confused about that. I'm going to tune my scripts to use acpi_video0 as
you suggested.
2) What should we do with this commit? It is already in mainline so I
guess revert is the sane thing to do.
I should have asked/investigated this more before submitting the patch.
Sorry about that.
next prev parent reply other threads:[~2014-02-12 9:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-03 10:59 Mika Westerberg
2014-02-07 1:29 ` Aaron Lu
2014-02-07 10:25 ` Mika Westerberg
2014-02-12 2:31 ` Aaron Lu
2014-02-12 9:34 ` Mika Westerberg [this message]
2014-02-13 1:09 ` 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=20140212093430.GB5018@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 \
/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
Powered by JetHome