linux-kernel - Re: [PATCH] backlight: add support for disabling backlights via sysfs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 29 Jun 2012 15:18:49 +0800
From:	joeyli <jlee@...e.com>
To:	Matthew Garrett <mjg59@...f.ucam.org>
Cc:	seth.forshee@...onical.com, Richard Purdie <rpurdie@...ys.net>,
	linux-kernel@...r.kernel.org, platform-driver-x86@...r.kernel.org,
	Corentin Chary <corentin.chary@...il.com>
Subject: Re: [PATCH] backlight: add support for disabling backlights via
 sysfs

於 五，2012-06-29 於 03:57 +0100，Matthew Garrett 提到：
> On Fri, Jun 29, 2012 at 10:43:59AM +0800, joeyli wrote:
> 
> > 	http://msdn.microsoft.com/en-us/windows/hardware/gg487382.aspx
> >
> > In WDDM architecture, in spec p.5, there have a "Monitor" driver to
> > check the WDDM driver support brightness DDI, if not, then it will use
> > standard acpi method to control brightness.
> 
> What's the interaction between GPU drivers and platform drivers? For 
> instance, on acer systems that have backlight control via WMI, does 
> Windows use WMI, the GPU driver or ACPI?
>  

I think GPU driver.

Because there have no wmi method support backlight control on modern
Acer machine and _BCM also broken on some machines.

On old machines that have 6AF4F258 wmi method, it supported to set
brightness level through wmi. But 6AF4F258 is really old now and almost
broken or not provide by new acer BIOS.

So, it is clear for modern Acer machines do NOT use wmi to control
backlight. It must control brightness through acpi or GPU driver.
(For very very new machine maybe changed again, need to check.)

Have a a period of time, acer BIOS provide healthful _BCM
implementation, in _BCM, they changed brightness through OPregion or
write EC register.

But now, some machines have broken _BCM and they are also not control
brightness through WMI, that means the brightness control is through GPU
driver.

Per WDDM spec, if WDDM driver support DDI, the NORMAL code path of
brightness control is:
	Mobility Center(userland) -> Monitor Driver -> WDDM Driver -> Graphics Adapter

Reviewed DSDT from Acer machines, I believe Acer didn't force ODM fully implement
Acer's WMI space. So, also need to check with Acer for how many ODM really follow WDDM spec.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/