public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 16:03:16 +0200	[thread overview]
Message-ID: <20140214140316.GI5018@intel.com> (raw)
In-Reply-To: <s5hmwht24ub.wl%tiwai@suse.de>

On Fri, Feb 14, 2014 at 02:37:00PM +0100, Takashi Iwai wrote:
> At Fri, 14 Feb 2014 14:34:07 +0200,
> Mika Westerberg wrote:
> > 
> > This reverts commit e18ac62fa4b3f16234bab0d5a6627c57dbae9e7e.
> > 
> > The referenced commit added HP EliteBook Revolve 810 to the ACPI video
> > detected blacklist so that only the native Intel backlight interface was
> > exported.
> > 
> > However, this turned to be wrong solution after all. The ACPI video
> > interface works and as long as we only use that there are no problems. So
> > we can revert this commit and stick to use the backlight interface provided
> > by the ACPI video driver.
> > 
> > (Using Intel native interface will not work after resume since the ACPI
> > video driver will restore it's state which takes control over the native
> > one. That's a separate thing and should be addressed in the ACPI video
> > driver, I suppose.)
> > 
> > References: https://bugzilla.kernel.org/show_bug.cgi?id=70231
> > Cc: Aaron Lu <aaron.lu@intel.com>
> > Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
> > ---
> > Rafael, 
> > 
> > This turned out to be misunderstanding from my side. I should have
> > investigated this further before submitting the original patch. Sorry about
> > that.
> > 
> > Aaron,
> > 
> > Thanks for the investigation and pointing me to the right direction (e.g to
> > use acpi_video0 over the native one).
> 
> Could you check whether the ACPI video still really works even if you
> remove the recent acpi_osi blacklist entry below?  It might be that
> BIOS changed its mind to behave more kindly as if handling for Win7.
> 
> 
> Takashi
> 
> ---
> diff --git a/drivers/acpi/blacklist.c b/drivers/acpi/blacklist.c
> index 10e4964d051a..64d14406465d 100644
> --- a/drivers/acpi/blacklist.c
> +++ b/drivers/acpi/blacklist.c
> @@ -322,6 +322,7 @@ static struct dmi_system_id acpi_osi_dmi_table[] __initdata = {
>  		     DMI_MATCH(DMI_PRODUCT_VERSION, "2349D15"),
>  		},
>  	},
> +#if 0
>  	{
>  	.callback = dmi_disable_osi_win8,
>  	.ident = "HP ProBook 2013 models",
> @@ -372,6 +373,7 @@ static struct dmi_system_id acpi_osi_dmi_table[] __initdata = {
>  		     DMI_MATCH(DMI_PRODUCT_NAME, "HP EliteBook 8780w"),
>  		},
>  	},
> +#endif
>  
>  	/*
>  	 * BIOS invocation of _OSI(Linux) is almost always a BIOS bug.

After this patch is applied, the ACPI backlight doesn't work anymore. The
brightness stays the same, no matter what I do.

  reply	other threads:[~2014-02-14 13:56 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 [this message]
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
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=20140214140316.GI5018@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