linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Aaron Lu <aaron.lu@intel.com>
To: Matthew Garrett <matthew.garrett@nebula.com>
Cc: "james@albanarts.com" <james@albanarts.com>,
	"bitbucket@online.de" <bitbucket@online.de>,
	"felipe.contreras@gmail.com" <felipe.contreras@gmail.com>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"platform-driver-x86@vger.kernel.org"
	<platform-driver-x86@vger.kernel.org>,
	"hmh@hmh.eng.br" <hmh@hmh.eng.br>,
	"kvalo@adurom.com" <kvalo@adurom.com>,
	"corsac@debian.org" <corsac@debian.org>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	"joeyli.kernel@gmail.com" <joeyli.kernel@gmail.com>,
	"ben@bjencks.net" <ben@bjencks.net>,
	"jrg.otte@gmail.com" <jrg.otte@gmail.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"Martin@lichtvoll.de" <Martin@lichtvoll.de>,
	"thirdwiggin@gmail.com" <thirdwiggin@gmail.com>,
	"bugs@ttyhoney.com" <bugs@ttyhoney.com>,
	"jplatte@naasa.net" <jplatte@naasa.net>,
	"seth.forshee@canonical.com" <se>
Subject: Re: [PATCH v3] ACPI / video: Add systems that should favor native backlight interface
Date: Tue, 21 Jan 2014 13:32:42 +0800	[thread overview]
Message-ID: <52DE067A.60400@intel.com> (raw)
In-Reply-To: <1390274270.5320.2.camel@x230>

On 01/21/2014 11:17 AM, Matthew Garrett wrote:
> On Tue, 2014-01-21 at 10:24 +0800, Aaron Lu wrote:
>> On 01/20/2014 09:34 PM, Matthew Garrett wrote:
>>> On Mon, 2014-01-20 at 16:12 +0800, Aaron Lu wrote:
>>>
>>>> 1 remove the win8 OSI check, I've seen win7 laptops that also needs to
>>>>   have only the GPU interface left and checking win8 doesn't make much
>>>>   sense now;
>>>
>>> Are we sure that those aren't simply some other bug?
>>
>> Well, the firmware on that laptop makes use of EC to do backlight
>> control and the fact that the firmware interface doesn't work while the
>> GPU's work seems to indicate that the backlight control circuit is not
>> routed to EC. I think this is the same case as Win8 laptops.
> 
> We know that Windows 8 graphics drivers don't use the ACPI interface,
> and that systems change their behaviour as a result, in some cases with
> absolutely no way for the ACPI interface could possibly work. I haven't
> seen any cases where that's obviously true for any non-Windows 8

Perhaps I'm not clear, I didn't mean non-Windows 8 systems will all favor
GPU's interface, I just meant for one specific win7 laptop I could re-use
the existing code to make the GPU's interface as the only one left. And to
achieve this, the Win8 OSI check in acpi_video_verify_backlight_support
has to be gone.

BTW, I actually think use_native_backlight param should mean "the native
backlight control interface will be the only one available on the system",
it doesn't need to go side by side with Win8 OSI check.

> systems. EC interfaces that don't work are often due to Linux leaving
> the hardware in a state other than the one expected by the firmware. We

Good to know this, thanks.

> shouldn't assume that it's the same issue until we've investigated
> further.

OK, but I honestly don't have any idea how to proceed, in case you have
some time, the bug is:
https://bugzilla.kernel.org/show_bug.cgi?id=66501

  reply	other threads:[~2014-01-21  5:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-18 13:54 [PATCH v3] ACPI / video: Add systems that should favor native backlight interface Igor Gnatenko
2014-01-20  8:12 ` Aaron Lu
2014-01-20 13:34   ` Matthew Garrett
2014-01-21  2:24     ` Aaron Lu
2014-01-21  3:17       ` Matthew Garrett
2014-01-21  5:32         ` Aaron Lu [this message]
2014-01-21 12:11           ` Matthew Garrett
2014-01-22  1:58             ` 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=52DE067A.60400@intel.com \
    --to=aaron.lu@intel.com \
    --cc=Martin@lichtvoll.de \
    --cc=ben@bjencks.net \
    --cc=bitbucket@online.de \
    --cc=bugs@ttyhoney.com \
    --cc=corsac@debian.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=felipe.contreras@gmail.com \
    --cc=hmh@hmh.eng.br \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=james@albanarts.com \
    --cc=joeyli.kernel@gmail.com \
    --cc=jplatte@naasa.net \
    --cc=jrg.otte@gmail.com \
    --cc=kvalo@adurom.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=matthew.garrett@nebula.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=thirdwiggin@gmail.com \
    /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).