From: Matthew Garrett <hidden> Date: 2012-03-13 13:35:08
On Tue, Mar 13, 2012 at 06:56:16PM +0530, Pradeep Subrahmanion wrote:
I tried giving acpi_backlight = vendor . In that case hot key for
brightness control is working. But i think , it is not calculating the
correct value for brightness because increasing brightness after maximum
level gives blank screen .
Which backlight device appears then?
By ' ACPI interface' , I mean 'acpi_video0' inside the
/sys/class/backlight. I havn't tried the /sys/class/backlight interface
directly . I will try that also.
So writing values into /sys/class/backlight/acpi_video0/brightness does
nothing?
--
Matthew Garrett | mjg59@srcf.ucam.org
On Tue, 2012-03-13 at 13:34 +0000, Matthew Garrett wrote:
On Tue, Mar 13, 2012 at 06:56:16PM +0530, Pradeep Subrahmanion wrote:
quoted
I tried giving acpi_backlight = vendor . In that case hot key for
brightness control is working. But i think , it is not calculating the
correct value for brightness because increasing brightness after maximum
level gives blank screen .
Which backlight device appears then?
'intel_backlight' appears when i gave option acpi_backlight = vendor. Writing to /sys/class/backlight/intel_backlight/brightness
does not cause any change in brightness.
quoted
By ' ACPI interface' , I mean 'acpi_video0' inside the
/sys/class/backlight. I havn't tried the /sys/class/backlight interface
directly . I will try that also.
So writing values into /sys/class/backlight/acpi_video0/brightness does
nothing?
No change in value when writing
to /sys/class/backlight/acpi_video0/brightness.
Another thing is that when i did boot with acpi_backlight = 'acer_wmi' ,
in new kernel (3.3.0-rc7) , it shows following messages ,
[ 8.350825] wmi: Mapper loaded
[ 10.363975] acer_wmi: Acer Laptop ACPI-WMI Extras
[ 10.396186] acer_wmi: Function bitmap for Communication Device: 0x91
[ 10.396385] acer_wmi: Brightness must be controlled by generic video
driver
Also there was no interface inside /sys/class/backlight for acer_wmi.
I also tried writing directly to Embedded controller register .But no
change.
----
Thanks ,
Pradeep Subrahmanion
Hi Pradeep,
於 二,2012-03-13 於 21:24 -0400,Pradeep Subrahmanion 提到:
On Tue, 2012-03-13 at 13:34 +0000, Matthew Garrett wrote:
quoted
On Tue, Mar 13, 2012 at 06:56:16PM +0530, Pradeep Subrahmanion wrote:
quoted
I tried giving acpi_backlight = vendor . In that case hot key for
brightness control is working. But i think , it is not calculating the
correct value for brightness because increasing brightness after maximum
level gives blank screen .
Which backlight device appears then?
'intel_backlight' appears when i gave option acpi_backlight = vendor. Writing to /sys/class/backlight/intel_backlight/brightness
does not cause any change in brightness.
The above command not work, that means EC didn't change backlight
value:
Method (_BCM, 1, NotSerialized)
{
Divide (Arg0, 0x0A, Local0, Local1)
Decrement (Local1)
Store (Local1, ^^^^LPC.EC0.BRTS) <== write backlight value to EC
register
}
Per my understood, EC firmware should change brightness but didn't do
that, another
way is touch i915 register in _BCM.
Acer machine provide a broken _BCM implementation and they didn't test
it.
quoted
quoted
By ' ACPI interface' , I mean 'acpi_video0' inside the
/sys/class/backlight. I havn't tried the /sys/class/backlight interface
directly . I will try that also.
So writing values into /sys/class/backlight/acpi_video0/brightness does
nothing?
No change in value when writing
to /sys/class/backlight/acpi_video0/brightness.
Another thing is that when i did boot with acpi_backlight = 'acer_wmi' ,
in new kernel (3.3.0-rc7) , it shows following messages ,
[ 8.350825] wmi: Mapper loaded
[ 10.363975] acer_wmi: Acer Laptop ACPI-WMI Extras
[ 10.396186] acer_wmi: Function bitmap for Communication Device: 0x91
[ 10.396385] acer_wmi: Brightness must be controlled by generic video
driver
Also there was no interface inside /sys/class/backlight for acer_wmi.
Yes, acer_wmi support backlight control with AMW0 interface, your
machine didn't have AMW0 interface.
Normally, backlight should control by standard acpi interface.
I also tried writing directly to Embedded controller register .But no
change.
The machine has broken _BCM method, because EC should do something after
_BCM changed EC register.
Per my understood, EC firmware should change brightness but didn't do
that, another
way is touch i915 register in _BCM.
how do we do this ? you mean change the _BCM implementation ?
Acer machine provide a broken _BCM implementation and they didn't test
it.
quoted
quoted
quoted
By ' ACPI interface' , I mean 'acpi_video0' inside the
/sys/class/backlight. I havn't tried the /sys/class/backlight interface
directly . I will try that also.
So writing values into /sys/class/backlight/acpi_video0/brightness does
nothing?
No change in value when writing
to /sys/class/backlight/acpi_video0/brightness.
Another thing is that when i did boot with acpi_backlight = 'acer_wmi' ,
in new kernel (3.3.0-rc7) , it shows following messages ,
[ 8.350825] wmi: Mapper loaded
[ 10.363975] acer_wmi: Acer Laptop ACPI-WMI Extras
[ 10.396186] acer_wmi: Function bitmap for Communication Device: 0x91
[ 10.396385] acer_wmi: Brightness must be controlled by generic video
driver
Also there was no interface inside /sys/class/backlight for acer_wmi.
Yes, acer_wmi support backlight control with AMW0 interface, your
machine didn't have AMW0 interface.
Normally, backlight should control by standard acpi interface.
quoted
I also tried writing directly to Embedded controller register .But no
change.
The machine has broken _BCM method, because EC should do something after
_BCM changed EC register.
Per my understood, EC firmware should change brightness but didn't do
that, another
way is touch i915 register in _BCM.
how do we do this ? you mean change the _BCM implementation ?
"BIOS guy" should do something like this:
Method (AINT, 2, NotSerialized)
{
...
If (LEqual (Arg0, One))
{
Store (Divide (Multiply (Arg1, 0xFF), 0x64, ), BCLP)
Or (BCLP, 0x80000000, BCLP) <== touch BCLP register
Store (0x02, ASLC)
}
Method (_BCM, 1, NotSerialized)
{
If (LAnd (LGreaterEqual (Arg0, Zero), LLessEqual (Arg0, 0x64)))
{
AINT (One, Arg0) <== call AINT method
Store (Arg0, BRTL)
}
}
Just for reference, they should do that when EC didn't wire to
backlight.
quoted
Acer machine provide a broken _BCM implementation and they didn't test
it.
quoted
quoted
quoted
By ' ACPI interface' , I mean 'acpi_video0' inside the
/sys/class/backlight. I havn't tried the /sys/class/backlight interface
directly . I will try that also.
So writing values into /sys/class/backlight/acpi_video0/brightness does
nothing?
No change in value when writing
to /sys/class/backlight/acpi_video0/brightness.
Another thing is that when i did boot with acpi_backlight = 'acer_wmi' ,
in new kernel (3.3.0-rc7) , it shows following messages ,
[ 8.350825] wmi: Mapper loaded
[ 10.363975] acer_wmi: Acer Laptop ACPI-WMI Extras
[ 10.396186] acer_wmi: Function bitmap for Communication Device: 0x91
[ 10.396385] acer_wmi: Brightness must be controlled by generic video
driver
Also there was no interface inside /sys/class/backlight for acer_wmi.
Yes, acer_wmi support backlight control with AMW0 interface, your
machine didn't have AMW0 interface.
Normally, backlight should control by standard acpi interface.
quoted
I also tried writing directly to Embedded controller register .But no
change.
The machine has broken _BCM method, because EC should do something after
_BCM changed EC register.
Thanks ,
Pradeep Subrahmanion
Why they didn't find _BCM not work?
My guess is:
Because the backlight control is through WDDM driver on Windows platform
but not through standard ACPI method _BCM. They only test Windows
platform, so, they didn't find _BCM broken.
And, they also didn't really follow Microsoft WDDM spec:
http://msdn.microsoft.com/en-us/windows/hardware/gg487382.aspx
Per spec,
ODM should keep _BCM works fine for any other OS didn't support WDDM
driver, but they didn't.
At last year, I told Acer PM one time for this issue, they said will
check but finally didn't response me.
Thanks
Joey Lee
Per my understood, EC firmware should change brightness but didn't do
that, another
way is touch i915 register in _BCM.
how do we do this ? you mean change the _BCM implementation ?
"BIOS guy" should do something like this:
Method (AINT, 2, NotSerialized)
{
...
If (LEqual (Arg0, One))
{
Store (Divide (Multiply (Arg1, 0xFF), 0x64, ), BCLP)
Or (BCLP, 0x80000000, BCLP) <== touch BCLP register
Store (0x02, ASLC)
}
Method (_BCM, 1, NotSerialized)
{
If (LAnd (LGreaterEqual (Arg0, Zero), LLessEqual (Arg0, 0x64)))
{
AINT (One, Arg0) <== call AINT method
Store (Arg0, BRTL)
}
}
Just for reference, they should do that when EC didn't wire to
backlight.
quoted
quoted
Acer machine provide a broken _BCM implementation and they didn't test
it.
quoted
quoted
quoted
By ' ACPI interface' , I mean 'acpi_video0' inside the
/sys/class/backlight. I havn't tried the /sys/class/backlight interface
directly . I will try that also.
So writing values into /sys/class/backlight/acpi_video0/brightness does
nothing?
No change in value when writing
to /sys/class/backlight/acpi_video0/brightness.
Another thing is that when i did boot with acpi_backlight = 'acer_wmi' ,
in new kernel (3.3.0-rc7) , it shows following messages ,
[ 8.350825] wmi: Mapper loaded
[ 10.363975] acer_wmi: Acer Laptop ACPI-WMI Extras
[ 10.396186] acer_wmi: Function bitmap for Communication Device: 0x91
[ 10.396385] acer_wmi: Brightness must be controlled by generic video
driver
Also there was no interface inside /sys/class/backlight for acer_wmi.
Yes, acer_wmi support backlight control with AMW0 interface, your
machine didn't have AMW0 interface.
Normally, backlight should control by standard acpi interface.
quoted
I also tried writing directly to Embedded controller register .But no
change.
The machine has broken _BCM method, because EC should do something after
_BCM changed EC register.
Thanks ,
Pradeep Subrahmanion
Why they didn't find _BCM not work?
My guess is:
Because the backlight control is through WDDM driver on Windows platform
but not through standard ACPI method _BCM. They only test Windows
platform, so, they didn't find _BCM broken.
And, they also didn't really follow Microsoft WDDM spec:
http://msdn.microsoft.com/en-us/windows/hardware/gg487382.aspx
Per spec,
ODM should keep _BCM works fine for any other OS didn't support WDDM
driver, but they didn't.
At last year, I told Acer PM one time for this issue, they said will
check but finally didn't response me.
Thanks
Joey Lee
So touching the PCI LBB register is the only feasible solution now
(even though it may not be a clean method) ?
Thanks,
Pradeep Subrahmanion
--
To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Per my understood, EC firmware should change brightness but didn't do
that, another
way is touch i915 register in _BCM.
how do we do this ? you mean change the _BCM implementation ?
"BIOS guy" should do something like this:
Method (AINT, 2, NotSerialized)
{
...
If (LEqual (Arg0, One))
{
Store (Divide (Multiply (Arg1, 0xFF), 0x64, ), BCLP)
Or (BCLP, 0x80000000, BCLP) <== touch BCLP register
Store (0x02, ASLC)
}
Method (_BCM, 1, NotSerialized)
{
If (LAnd (LGreaterEqual (Arg0, Zero), LLessEqual (Arg0, 0x64)))
{
AINT (One, Arg0) <== call AINT method
Store (Arg0, BRTL)
}
}
Just for reference, they should do that when EC didn't wire to
backlight.
quoted
quoted
Acer machine provide a broken _BCM implementation and they didn't test
it.
quoted
quoted
quoted
By ' ACPI interface' , I mean 'acpi_video0' inside the
/sys/class/backlight. I havn't tried the /sys/class/backlight interface
directly . I will try that also.
So writing values into /sys/class/backlight/acpi_video0/brightness does
nothing?
No change in value when writing
to /sys/class/backlight/acpi_video0/brightness.
Another thing is that when i did boot with acpi_backlight = 'acer_wmi' ,
in new kernel (3.3.0-rc7) , it shows following messages ,
[ 8.350825] wmi: Mapper loaded
[ 10.363975] acer_wmi: Acer Laptop ACPI-WMI Extras
[ 10.396186] acer_wmi: Function bitmap for Communication Device: 0x91
[ 10.396385] acer_wmi: Brightness must be controlled by generic video
driver
Also there was no interface inside /sys/class/backlight for acer_wmi.
Yes, acer_wmi support backlight control with AMW0 interface, your
machine didn't have AMW0 interface.
Normally, backlight should control by standard acpi interface.
quoted
I also tried writing directly to Embedded controller register .But no
change.
The machine has broken _BCM method, because EC should do something after
_BCM changed EC register.
Thanks ,
Pradeep Subrahmanion
Why they didn't find _BCM not work?
My guess is:
Because the backlight control is through WDDM driver on Windows platform
but not through standard ACPI method _BCM. They only test Windows
platform, so, they didn't find _BCM broken.
And, they also didn't really follow Microsoft WDDM spec:
http://msdn.microsoft.com/en-us/windows/hardware/gg487382.aspx
Per spec,
ODM should keep _BCM works fine for any other OS didn't support WDDM
driver, but they didn't.
At last year, I told Acer PM one time for this issue, they said will
check but finally didn't response me.
quoted
Thanks
Joey Lee
So touching the PCI LBB register is the only feasible solution now
(even though it may not be a clean method) ?
Thanks,
Pradeep Subrahmanion
That will be better leave LBB register only touched by i915 driver.
If 'acpi_backlight=vendor' works to you, maybe we can add a quirk to
video_detect.c.
You can try the following patch.
Thanks a lot!
Joey Lee
From 038bd3c4e53b7195f34e9d46c999b8dcb279da5e Mon Sep 17 00:00:00 2001
From: "Lee, Chun-Yi" <jlee@suse.com>
Date: Thu, 15 Mar 2012 16:03:45 +0800
Subject: [PATCH] acer-wmi: Add quirk table for video backlight vendor mode
Add quirk table for video backlight vendor mode
Signed-off-by: "Lee, Chun-Yi" <jlee@suse.com>
---
drivers/acpi/video_detect.c | 27 +++++++++++++++++++++++++++
1 files changed, 27 insertions(+), 0 deletions(-)
Per my understood, EC firmware should change brightness but didn't do
that, another
way is touch i915 register in _BCM.
how do we do this ? you mean change the _BCM implementation ?
"BIOS guy" should do something like this:
Method (AINT, 2, NotSerialized)
{
...
If (LEqual (Arg0, One))
{
Store (Divide (Multiply (Arg1, 0xFF), 0x64, ), BCLP)
Or (BCLP, 0x80000000, BCLP) <== touch BCLP register
Store (0x02, ASLC)
}
Method (_BCM, 1, NotSerialized)
{
If (LAnd (LGreaterEqual (Arg0, Zero), LLessEqual (Arg0, 0x64)))
{
AINT (One, Arg0) <== call AINT method
Store (Arg0, BRTL)
}
}
Just for reference, they should do that when EC didn't wire to
backlight.
quoted
quoted
Acer machine provide a broken _BCM implementation and they didn't test
it.
quoted
quoted
quoted
By ' ACPI interface' , I mean 'acpi_video0' inside the
/sys/class/backlight. I havn't tried the /sys/class/backlight interface
directly . I will try that also.
So writing values into /sys/class/backlight/acpi_video0/brightness does
nothing?
No change in value when writing
to /sys/class/backlight/acpi_video0/brightness.
Another thing is that when i did boot with acpi_backlight = 'acer_wmi' ,
in new kernel (3.3.0-rc7) , it shows following messages ,
[ 8.350825] wmi: Mapper loaded
[ 10.363975] acer_wmi: Acer Laptop ACPI-WMI Extras
[ 10.396186] acer_wmi: Function bitmap for Communication Device: 0x91
[ 10.396385] acer_wmi: Brightness must be controlled by generic video
driver
Also there was no interface inside /sys/class/backlight for acer_wmi.
Yes, acer_wmi support backlight control with AMW0 interface, your
machine didn't have AMW0 interface.
Normally, backlight should control by standard acpi interface.
quoted
I also tried writing directly to Embedded controller register .But no
change.
The machine has broken _BCM method, because EC should do something after
_BCM changed EC register.
Thanks ,
Pradeep Subrahmanion
Why they didn't find _BCM not work?
My guess is:
Because the backlight control is through WDDM driver on Windows platform
but not through standard ACPI method _BCM. They only test Windows
platform, so, they didn't find _BCM broken.
And, they also didn't really follow Microsoft WDDM spec:
http://msdn.microsoft.com/en-us/windows/hardware/gg487382.aspx
Per spec,
ODM should keep _BCM works fine for any other OS didn't support WDDM
driver, but they didn't.
At last year, I told Acer PM one time for this issue, they said will
check but finally didn't response me.
quoted
Thanks
Joey Lee
So touching the PCI LBB register is the only feasible solution now
(even though it may not be a clean method) ?
Thanks,
Pradeep Subrahmanion
That will be better leave LBB register only touched by i915 driver.
If 'acpi_backlight=vendor' works to you, maybe we can add a quirk to
video_detect.c.
You can try the following patch.
Thanks . I tried your patch .acpi_backlight=vendor allows me to control
brightness with hot key.But there are problems with it like increasing
brightness after maximum level causes blank screen.So I am trying it
sort it out.
Thank you ,
Pradeep Subrahmanion
quoted hunk
Thanks a lot!
Joey Lee
quoted
From 038bd3c4e53b7195f34e9d46c999b8dcb279da5e Mon Sep 17 00:00:00 2001
From: "Lee, Chun-Yi" <jlee@suse.com>
Date: Thu, 15 Mar 2012 16:03:45 +0800
Subject: [PATCH] acer-wmi: Add quirk table for video backlight vendor mode
Add quirk table for video backlight vendor mode
Signed-off-by: "Lee, Chun-Yi" <jlee@suse.com>
---
drivers/acpi/video_detect.c | 27 +++++++++++++++++++++++++++
1 files changed, 27 insertions(+), 0 deletions(-)
Per my understood, EC firmware should change brightness but didn't do
that, another
way is touch i915 register in _BCM.
how do we do this ? you mean change the _BCM implementation ?
"BIOS guy" should do something like this:
Method (AINT, 2, NotSerialized)
{
...
If (LEqual (Arg0, One))
{
Store (Divide (Multiply (Arg1, 0xFF), 0x64, ), BCLP)
Or (BCLP, 0x80000000, BCLP) <== touch BCLP register
Store (0x02, ASLC)
}
Method (_BCM, 1, NotSerialized)
{
If (LAnd (LGreaterEqual (Arg0, Zero), LLessEqual (Arg0, 0x64)))
{
AINT (One, Arg0) <== call AINT method
Store (Arg0, BRTL)
}
}
Just for reference, they should do that when EC didn't wire to
backlight.
quoted
quoted
Acer machine provide a broken _BCM implementation and they didn't test
it.
quoted
quoted
quoted
By ' ACPI interface' , I mean 'acpi_video0' inside the
/sys/class/backlight. I havn't tried the /sys/class/backlight interface
directly . I will try that also.
So writing values into /sys/class/backlight/acpi_video0/brightness does
nothing?
No change in value when writing
to /sys/class/backlight/acpi_video0/brightness.
Another thing is that when i did boot with acpi_backlight = 'acer_wmi' ,
in new kernel (3.3.0-rc7) , it shows following messages ,
[ 8.350825] wmi: Mapper loaded
[ 10.363975] acer_wmi: Acer Laptop ACPI-WMI Extras
[ 10.396186] acer_wmi: Function bitmap for Communication Device: 0x91
[ 10.396385] acer_wmi: Brightness must be controlled by generic video
driver
Also there was no interface inside /sys/class/backlight for acer_wmi.
Yes, acer_wmi support backlight control with AMW0 interface, your
machine didn't have AMW0 interface.
Normally, backlight should control by standard acpi interface.
quoted
I also tried writing directly to Embedded controller register .But no
change.
The machine has broken _BCM method, because EC should do something after
_BCM changed EC register.
Thanks ,
Pradeep Subrahmanion
Why they didn't find _BCM not work?
My guess is:
Because the backlight control is through WDDM driver on Windows platform
but not through standard ACPI method _BCM. They only test Windows
platform, so, they didn't find _BCM broken.
And, they also didn't really follow Microsoft WDDM spec:
http://msdn.microsoft.com/en-us/windows/hardware/gg487382.aspx
Per spec,
ODM should keep _BCM works fine for any other OS didn't support WDDM
driver, but they didn't.
At last year, I told Acer PM one time for this issue, they said will
check but finally didn't response me.
quoted
Thanks
Joey Lee
So touching the PCI LBB register is the only feasible solution now
(even though it may not be a clean method) ?
Thanks,
Pradeep Subrahmanion
That will be better leave LBB register only touched by i915 driver.
If 'acpi_backlight=vendor' works to you, maybe we can add a quirk to
video_detect.c.
You can try the following patch.
Thanks . I tried your patch .acpi_backlight=vendor allows me to control
brightness with hot key.But there are problems with it like increasing
brightness after maximum level causes blank screen.So I am trying it
sort it out.
Thank you ,
Pradeep Subrahmanion
quoted hunk
Thanks a lot!
Joey Lee
quoted
From 038bd3c4e53b7195f34e9d46c999b8dcb279da5e Mon Sep 17 00:00:00 2001
From: "Lee, Chun-Yi" <jlee@suse.com>
Date: Thu, 15 Mar 2012 16:03:45 +0800
Subject: [PATCH] acer-wmi: Add quirk table for video backlight vendor mode
Add quirk table for video backlight vendor mode
Signed-off-by: "Lee, Chun-Yi" <jlee@suse.com>
---
drivers/acpi/video_detect.c | 27 +++++++++++++++++++++++++++
1 files changed, 27 insertions(+), 0 deletions(-)
Per my understood, EC firmware should change brightness but didn't do
that, another
way is touch i915 register in _BCM.
how do we do this ? you mean change the _BCM implementation ?
"BIOS guy" should do something like this:
Method (AINT, 2, NotSerialized)
{
...
If (LEqual (Arg0, One))
{
Store (Divide (Multiply (Arg1, 0xFF), 0x64, ), BCLP)
Or (BCLP, 0x80000000, BCLP) <== touch BCLP register
Store (0x02, ASLC)
}
Method (_BCM, 1, NotSerialized)
{
If (LAnd (LGreaterEqual (Arg0, Zero), LLessEqual (Arg0, 0x64)))
{
AINT (One, Arg0) <== call AINT method
Store (Arg0, BRTL)
}
}
Just for reference, they should do that when EC didn't wire to
backlight.
quoted
quoted
Acer machine provide a broken _BCM implementation and they didn't test
it.
quoted
quoted
quoted
By ' ACPI interface' , I mean 'acpi_video0' inside the
/sys/class/backlight. I havn't tried the /sys/class/backlight interface
directly . I will try that also.
So writing values into /sys/class/backlight/acpi_video0/brightness does
nothing?
No change in value when writing
to /sys/class/backlight/acpi_video0/brightness.
Another thing is that when i did boot with acpi_backlight = 'acer_wmi' ,
in new kernel (3.3.0-rc7) , it shows following messages ,
[ 8.350825] wmi: Mapper loaded
[ 10.363975] acer_wmi: Acer Laptop ACPI-WMI Extras
[ 10.396186] acer_wmi: Function bitmap for Communication Device: 0x91
[ 10.396385] acer_wmi: Brightness must be controlled by generic video
driver
Also there was no interface inside /sys/class/backlight for acer_wmi.
Yes, acer_wmi support backlight control with AMW0 interface, your
machine didn't have AMW0 interface.
Normally, backlight should control by standard acpi interface.
quoted
I also tried writing directly to Embedded controller register .But no
change.
The machine has broken _BCM method, because EC should do something after
_BCM changed EC register.
Thanks ,
Pradeep Subrahmanion
Why they didn't find _BCM not work?
My guess is:
Because the backlight control is through WDDM driver on Windows platform
but not through standard ACPI method _BCM. They only test Windows
platform, so, they didn't find _BCM broken.
And, they also didn't really follow Microsoft WDDM spec:
http://msdn.microsoft.com/en-us/windows/hardware/gg487382.aspx
Per spec,
ODM should keep _BCM works fine for any other OS didn't support WDDM
driver, but they didn't.
At last year, I told Acer PM one time for this issue, they said will
check but finally didn't response me.
quoted
Thanks
Joey Lee
So touching the PCI LBB register is the only feasible solution now
(even though it may not be a clean method) ?
Thanks,
Pradeep Subrahmanion
That will be better leave LBB register only touched by i915 driver.
If 'acpi_backlight=vendor' works to you, maybe we can add a quirk to
video_detect.c.
You can try the following patch.
Thanks . I tried your patch .acpi_backlight=vendor allows me to control
brightness with hot key.But there are problems with it like increasing
OK, thanks for your testing, I will send out patch and add Cc. to you.
brightness after maximum level causes blank screen.So I am trying it
sort it out.
Thank you ,
Pradeep Subrahmanion
For the maximum level causes blank screen...
Please kindly help to identify which driver handle the brightness
change, run the following 2 commands:
# echo 5 > /sys/class/backlight/acer-wmi/brightness
# echo 5 > /sys/class/backlight/intel_backlight/brightness
Which one works to change brightness on your machine?
Thanks a lot!
Joey Lee
For the maximum level causes blank screen...
Please kindly help to identify which driver handle the brightness
change, run the following 2 commands:
# echo 5 > /sys/class/backlight/acer-wmi/brightness
# echo 5 > /sys/class/backlight/intel_backlight/brightness
Which one works to change brightness on your machine?
Both of them do not work for me.Only hot keys are working.
Writing to /sys/class/backlight/acer-wmi/brightness
and /sys/class/backlight/intel_backlight/brightness do not cause any
change in brightness.
Regards ,
Pradeep Subrahmanion
Hi Pradeep,
於 一,2012-03-19 於 17:03 +0530,Pradeep Subrahmanion 提到:
quoted
For the maximum level causes blank screen...
Please kindly help to identify which driver handle the brightness
change, run the following 2 commands:
# echo 5 > /sys/class/backlight/acer-wmi/brightness
# echo 5 > /sys/class/backlight/intel_backlight/brightness
Which one works to change brightness on your machine?
Both of them do not work for me.Only hot keys are working.
Writing to /sys/class/backlight/acer-wmi/brightness
and /sys/class/backlight/intel_backlight/brightness do not cause any
change in brightness.
Regards ,
Pradeep Subrahmanion
A bit strange...
Could you please paste your /proc/cmdline ? Did you add
acpi_osi="Linux" ?
Thanks a lot!
Joey Lee
Per my understood, EC firmware should change brightness but didn't do
that, another
way is touch i915 register in _BCM.
how do we do this ? you mean change the _BCM implementation ?
"BIOS guy" should do something like this:
Method (AINT, 2, NotSerialized)
{
...
If (LEqual (Arg0, One))
{
Store (Divide (Multiply (Arg1, 0xFF), 0x64, ), BCLP)
Or (BCLP, 0x80000000, BCLP) <== touch BCLP register
Store (0x02, ASLC)
}
Method (_BCM, 1, NotSerialized)
{
If (LAnd (LGreaterEqual (Arg0, Zero), LLessEqual (Arg0, 0x64)))
{
AINT (One, Arg0) <== call AINT method
Store (Arg0, BRTL)
}
}
Just for reference, they should do that when EC didn't wire to
backlight.
quoted
quoted
Acer machine provide a broken _BCM implementation and they didn't test
it.
quoted
quoted
quoted
By ' ACPI interface' , I mean 'acpi_video0' inside the
/sys/class/backlight. I havn't tried the /sys/class/backlight interface
directly . I will try that also.
So writing values into /sys/class/backlight/acpi_video0/brightness does
nothing?
No change in value when writing
to /sys/class/backlight/acpi_video0/brightness.
Another thing is that when i did boot with acpi_backlight = 'acer_wmi' ,
in new kernel (3.3.0-rc7) , it shows following messages ,
[ 8.350825] wmi: Mapper loaded
[ 10.363975] acer_wmi: Acer Laptop ACPI-WMI Extras
[ 10.396186] acer_wmi: Function bitmap for Communication Device: 0x91
[ 10.396385] acer_wmi: Brightness must be controlled by generic video
driver
Also there was no interface inside /sys/class/backlight for acer_wmi.
Yes, acer_wmi support backlight control with AMW0 interface, your
machine didn't have AMW0 interface.
Normally, backlight should control by standard acpi interface.
quoted
I also tried writing directly to Embedded controller register .But no
change.
The machine has broken _BCM method, because EC should do something after
_BCM changed EC register.
Thanks ,
Pradeep Subrahmanion
Why they didn't find _BCM not work?
My guess is:
Because the backlight control is through WDDM driver on Windows platform
but not through standard ACPI method _BCM. They only test Windows
platform, so, they didn't find _BCM broken.
And, they also didn't really follow Microsoft WDDM spec:
http://msdn.microsoft.com/en-us/windows/hardware/gg487382.aspx
Per spec,
ODM should keep _BCM works fine for any other OS didn't support WDDM
driver, but they didn't.
At last year, I told Acer PM one time for this issue, they said will
check but finally didn't response me.
quoted
Thanks
Joey Lee
So touching the PCI LBB register is the only feasible solution now
(even though it may not be a clean method) ?
Thanks,
Pradeep Subrahmanion
That will be better leave LBB register only touched by i915 driver.
If 'acpi_backlight=vendor' works to you, maybe we can add a quirk to
video_detect.c.
You can try the following patch.
Thanks . I tried your patch .acpi_backlight=vendor allows me to control
brightness with hot key.But there are problems with it like increasing
OK, thanks for your testing, I will send out patch and add Cc. to you.
Could you please kindly try this new patch? I follow Matthew's kindly
suggestion put the quirk table to acer-wmi driver.
Please help to apply the following patch to acer-wmi and remember remove
my last patch of video_detect.c, then rebuild your kernel.
Hope this patch also can fix your problem.
Thanks a lot!
Joey Lee
From 5da43d2ee6c87dcf17fda34f0b50fe11b04a16bf Mon Sep 17 00:00:00 2001
From: "Lee, Chun-Yi" <jlee@suse.com>
Date: Tue, 20 Mar 2012 19:00:58 +0800
Subject: [PATCH] acer-wmi: add quirk table for video backlight vendor mode
There have some acer laptop have broken _BCM implemenation, the AML
code wrote value to EC register but firmware didn't change brighenss.
Fortunately, the brightness control works on those machines with
vendor mode. So, add quirk table for video backlight vendor mode
and unregister acpi video interface on those machines.
Tested on Acer TravelMate 4750
Signed-off-by: Lee, Chun-Yi <jlee@suse.com>
---
drivers/platform/x86/Kconfig | 4 ++++
drivers/platform/x86/acer-wmi.c | 38 +++++++++++++++++++++++++++++++++++---
2 files changed, 39 insertions(+), 3 deletions(-)
@@ -26,6 +26,10 @@ config ACER_WMIdepends onRFKILL||RFKILL=ndepends onACPI_WMIselectINPUT_SPARSEKMAP+# Acer WMI depends on ACPI_VIDEO when ACPI is enabled+# but for select to work, need to select ACPI_VIDEO's dependencies, ick+selectVIDEO_OUTPUT_CONTROLifACPI+selectACPI_VIDEOifACPI---help---ThisisadriverfornewerAcer(andWistron)laptops.Itaddswirelessradioandbluetoothcontrol,andonsomelaptops,
@@ -478,6 +479,33 @@ static struct dmi_system_id acer_quirks[] = {{}};+staticintvideo_set_backlight_video_vendor(conststructdmi_system_id*d)+{+interface->capability&=~ACER_CAP_BRIGHTNESS;+pr_info("Brightness must be controlled by generic video driver\n");+return0;+}++staticconststructdmi_system_idvideo_vendor_dmi_table[]={+{+.callback=video_set_backlight_video_vendor,+.ident="Acer Aspire 4736",+.matches={+DMI_MATCH(DMI_BOARD_VENDOR,"Acer"),+DMI_MATCH(DMI_PRODUCT_NAME,"Aspire 4736"),+},+},+{+.callback=video_set_backlight_video_vendor,+.ident="Acer TravelMate 4750",+.matches={+DMI_MATCH(DMI_BOARD_VENDOR,"Acer"),+DMI_MATCH(DMI_PRODUCT_NAME,"TravelMate 4750"),+},+},+{}+};+/* Find which quirks are needed for a particular vendor/ model pair */staticvoidfind_quirks(void){
@@ -1981,9 +2009,13 @@ static int __init acer_wmi_init(void)set_quirks();if(acpi_video_backlight_support()){-interface->capability&=~ACER_CAP_BRIGHTNESS;-pr_info("Brightness must be controlled by "-"generic video driver\n");+if(dmi_check_system(video_vendor_dmi_table)){+acpi_video_unregister();+}else{+interface->capability&=~ACER_CAP_BRIGHTNESS;+pr_info("Brightness must be controlled by "+"acpi video driver\n");+}}if(wmi_has_guid(WMID_GUID3)){
From 5da43d2ee6c87dcf17fda34f0b50fe11b04a16bf Mon Sep 17 00:00:00 2001
From: "Lee, Chun-Yi" <jlee@suse.com>
Date: Tue, 20 Mar 2012 19:00:58 +0800
Subject: [PATCH] acer-wmi: add quirk table for video backlight vendor mode
There have some acer laptop have broken _BCM implemenation, the AML
code wrote value to EC register but firmware didn't change brighenss.
Fortunately, the brightness control works on those machines with
vendor mode. So, add quirk table for video backlight vendor mode
and unregister acpi video interface on those machines.
Tested on Acer TravelMate 4750
Signed-off-by: Lee, Chun-Yi <jlee@suse.com>
---
drivers/platform/x86/Kconfig | 4 ++++
drivers/platform/x86/acer-wmi.c | 38 +++++++++++++++++++++++++++++++++++---
2 files changed, 39 insertions(+), 3 deletions(-)
@@ -26,6 +26,10 @@ config ACER_WMIdepends onRFKILL||RFKILL=ndepends onACPI_WMIselectINPUT_SPARSEKMAP+# Acer WMI depends on ACPI_VIDEO when ACPI is enabled+# but for select to work, need to select ACPI_VIDEO's dependencies, ick+selectVIDEO_OUTPUT_CONTROLifACPI+selectACPI_VIDEOifACPI---help---ThisisadriverfornewerAcer(andWistron)laptops.Itaddswirelessradioandbluetoothcontrol,andonsomelaptops,
@@ -478,6 +479,33 @@ static struct dmi_system_id acer_quirks[] = {{}};+staticintvideo_set_backlight_video_vendor(conststructdmi_system_id*d)+{+interface->capability&=~ACER_CAP_BRIGHTNESS;+pr_info("Brightness must be controlled by generic video driver\n");+return0;+}++staticconststructdmi_system_idvideo_vendor_dmi_table[]={+{+.callback=video_set_backlight_video_vendor,+.ident="Acer Aspire 4736",+.matches={+DMI_MATCH(DMI_BOARD_VENDOR,"Acer"),+DMI_MATCH(DMI_PRODUCT_NAME,"Aspire 4736"),+},+},+{+.callback=video_set_backlight_video_vendor,+.ident="Acer TravelMate 4750",+.matches={+DMI_MATCH(DMI_BOARD_VENDOR,"Acer"),+DMI_MATCH(DMI_PRODUCT_NAME,"TravelMate 4750"),+},+},+{}+};+/* Find which quirks are needed for a particular vendor/ model pair */staticvoidfind_quirks(void){
@@ -1981,9 +2009,13 @@ static int __init acer_wmi_init(void)set_quirks();if(acpi_video_backlight_support()){-interface->capability&=~ACER_CAP_BRIGHTNESS;-pr_info("Brightness must be controlled by "-"generic video driver\n");+if(dmi_check_system(video_vendor_dmi_table)){+acpi_video_unregister();+}else{+interface->capability&=~ACER_CAP_BRIGHTNESS;+pr_info("Brightness must be controlled by "+"acpi video driver\n");+}}if(wmi_has_guid(WMID_GUID3)){
I tried out applied your patch . Boot message shows ,
[11.220410] acer_wmi: Brightness must be controlled by generic video
driver
Now 'acpi_video0' and 'intel_backlight' are present
inside /sys/class/backlight .Hot key works like earlier ( ie problem
after maximum level still exists).
I tried following commands ,
echo 5 > /sys/class/backlight/acpi_video0/brightness
echo 5 > /sys/class/backlight/intel_backlight/brightness
But it doesn't make any change .
In my case , 'acpi_backlight = vendor' does not make any difference since the hot key control
already starts working with 'acpi_osi=Linux' option.
cat /proc/cmdline gives ,
BOOT_IMAGE=/boot/vmlinuz-3.3.0+
root=UUIDð197a59-c067-4fd8-ad90-c4d721816077 ro acpi_osi=Linux
Thanks ,
Pradeep Subrahmanion
From 5da43d2ee6c87dcf17fda34f0b50fe11b04a16bf Mon Sep 17 00:00:00 2001
From: "Lee, Chun-Yi" <jlee@suse.com>
Date: Tue, 20 Mar 2012 19:00:58 +0800
Subject: [PATCH] acer-wmi: add quirk table for video backlight vendor mode
There have some acer laptop have broken _BCM implemenation, the AML
code wrote value to EC register but firmware didn't change brighenss.
Fortunately, the brightness control works on those machines with
vendor mode. So, add quirk table for video backlight vendor mode
and unregister acpi video interface on those machines.
Tested on Acer TravelMate 4750
Signed-off-by: Lee, Chun-Yi <jlee@suse.com>
---
drivers/platform/x86/Kconfig | 4 ++++
drivers/platform/x86/acer-wmi.c | 38 +++++++++++++++++++++++++++++++++++---
2 files changed, 39 insertions(+), 3 deletions(-)
@@ -26,6 +26,10 @@ config ACER_WMIdepends onRFKILL||RFKILL=ndepends onACPI_WMIselectINPUT_SPARSEKMAP+# Acer WMI depends on ACPI_VIDEO when ACPI is enabled+# but for select to work, need to select ACPI_VIDEO's dependencies, ick+selectVIDEO_OUTPUT_CONTROLifACPI+selectACPI_VIDEOifACPI---help---ThisisadriverfornewerAcer(andWistron)laptops.Itaddswirelessradioandbluetoothcontrol,andonsomelaptops,
@@ -478,6 +479,33 @@ static struct dmi_system_id acer_quirks[] = {{}};+staticintvideo_set_backlight_video_vendor(conststructdmi_system_id*d)+{+interface->capability&=~ACER_CAP_BRIGHTNESS;+pr_info("Brightness must be controlled by generic video driver\n");+return0;+}++staticconststructdmi_system_idvideo_vendor_dmi_table[]={+{+.callback=video_set_backlight_video_vendor,+.ident="Acer Aspire 4736",+.matches={+DMI_MATCH(DMI_BOARD_VENDOR,"Acer"),+DMI_MATCH(DMI_PRODUCT_NAME,"Aspire 4736"),+},+},+{+.callback=video_set_backlight_video_vendor,+.ident="Acer TravelMate 4750",+.matches={+DMI_MATCH(DMI_BOARD_VENDOR,"Acer"),+DMI_MATCH(DMI_PRODUCT_NAME,"TravelMate 4750"),+},+},+{}+};+/* Find which quirks are needed for a particular vendor/ model pair */staticvoidfind_quirks(void){
@@ -1981,9 +2009,13 @@ static int __init acer_wmi_init(void)set_quirks();if(acpi_video_backlight_support()){-interface->capability&=~ACER_CAP_BRIGHTNESS;-pr_info("Brightness must be controlled by "-"generic video driver\n");+if(dmi_check_system(video_vendor_dmi_table)){+acpi_video_unregister();+}else{+interface->capability&=~ACER_CAP_BRIGHTNESS;+pr_info("Brightness must be controlled by "+"acpi video driver\n");+}}if(wmi_has_guid(WMID_GUID3)){
I tried out applied your patch . Boot message shows ,
[11.220410] acer_wmi: Brightness must be controlled by generic video
driver
Now 'acpi_video0' and 'intel_backlight' are present
inside /sys/class/backlight .Hot key works like earlier ( ie problem
after maximum level still exists).
I tried following commands ,
It's not the expected behavior.
This new patch should remove acpi_video0 interface on your machine.
Please kindly provide your dmidecode:
dmidecode > dmidecode.log
And,
please make should the patch really applied, you can do a bit change on
pr_info message by yourself.
echo 5 > /sys/class/backlight/acpi_video0/brightness
echo 5 > /sys/class/backlight/intel_backlight/brightness
But it doesn't make any change .
In my case , 'acpi_backlight = vendor' does not make any difference since the hot key control
already starts working with 'acpi_osi=Linux' option.
cat /proc/cmdline gives ,
BOOT_IMAGE=/boot/vmlinuz-3.3.0+
root=UUIDğ197a59-c067-4fd8-ad90-c4d721816077 ro acpi_osi=Linux
Thanks ,
Pradeep Subrahmanion
OK, that's more clearly, please remove acpi_osi=Linux then re-test, I
think the hotkey of backlight control only works with acpi_osi=Linux ?
Thanks a lot!
Joey Lee
--
To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
From 5da43d2ee6c87dcf17fda34f0b50fe11b04a16bf Mon Sep 17 00:00:00 2001
From: "Lee, Chun-Yi" <jlee@suse.com>
Date: Tue, 20 Mar 2012 19:00:58 +0800
Subject: [PATCH] acer-wmi: add quirk table for video backlight vendor mode
There have some acer laptop have broken _BCM implemenation, the AML
code wrote value to EC register but firmware didn't change brighenss.
Fortunately, the brightness control works on those machines with
vendor mode. So, add quirk table for video backlight vendor mode
and unregister acpi video interface on those machines.
Tested on Acer TravelMate 4750
Signed-off-by: Lee, Chun-Yi <jlee@suse.com>
---
drivers/platform/x86/Kconfig | 4 ++++
drivers/platform/x86/acer-wmi.c | 38 +++++++++++++++++++++++++++++++++++---
2 files changed, 39 insertions(+), 3 deletions(-)
@@ -26,6 +26,10 @@ config ACER_WMIdepends onRFKILL||RFKILL=ndepends onACPI_WMIselectINPUT_SPARSEKMAP+# Acer WMI depends on ACPI_VIDEO when ACPI is enabled+# but for select to work, need to select ACPI_VIDEO's dependencies, ick+selectVIDEO_OUTPUT_CONTROLifACPI+selectACPI_VIDEOifACPI---help---ThisisadriverfornewerAcer(andWistron)laptops.Itaddswirelessradioandbluetoothcontrol,andonsomelaptops,
@@ -478,6 +479,33 @@ static struct dmi_system_id acer_quirks[] = {{}};+staticintvideo_set_backlight_video_vendor(conststructdmi_system_id*d)+{+interface->capability&=~ACER_CAP_BRIGHTNESS;+pr_info("Brightness must be controlled by generic video driver\n");+return0;+}++staticconststructdmi_system_idvideo_vendor_dmi_table[]={+{+.callback=video_set_backlight_video_vendor,+.ident="Acer Aspire 4736",+.matches={+DMI_MATCH(DMI_BOARD_VENDOR,"Acer"),+DMI_MATCH(DMI_PRODUCT_NAME,"Aspire 4736"),+},+},+{+.callback=video_set_backlight_video_vendor,+.ident="Acer TravelMate 4750",+.matches={+DMI_MATCH(DMI_BOARD_VENDOR,"Acer"),+DMI_MATCH(DMI_PRODUCT_NAME,"TravelMate 4750"),+},+},+{}+};+/* Find which quirks are needed for a particular vendor/ model pair */staticvoidfind_quirks(void){
@@ -1981,9 +2009,13 @@ static int __init acer_wmi_init(void)set_quirks();if(acpi_video_backlight_support()){-interface->capability&=~ACER_CAP_BRIGHTNESS;-pr_info("Brightness must be controlled by "-"generic video driver\n");+if(dmi_check_system(video_vendor_dmi_table)){+acpi_video_unregister();+}else{+interface->capability&=~ACER_CAP_BRIGHTNESS;+pr_info("Brightness must be controlled by "+"acpi video driver\n");+}}if(wmi_has_guid(WMID_GUID3)){
I tried out applied your patch . Boot message shows ,
[11.220410] acer_wmi: Brightness must be controlled by generic video
driver
Now 'acpi_video0' and 'intel_backlight' are present
inside /sys/class/backlight .Hot key works like earlier ( ie problem
after maximum level still exists).
I tried following commands ,
It's not the expected behavior.
This new patch should remove acpi_video0 interface on your machine.
Please kindly provide your dmidecode:
dmidecode > dmidecode.log
And,
please make should the patch really applied, you can do a bit change on
pr_info message by yourself.
Sorry . I think there was some mistake . I tried the patch again. Now
I see only intel_backlight inside /sys/class/backlight. There is no
acer-wmi interface . Is this the expected behavior ? . Or am I missing
anything ?
quoted
echo 5 > /sys/class/backlight/acpi_video0/brightness
echo 5 > /sys/class/backlight/intel_backlight/brightness
But it doesn't make any change .
In my case , 'acpi_backlight = vendor' does not make any difference since the hot key control
already starts working with 'acpi_osi=Linux' option.
cat /proc/cmdline gives ,
BOOT_IMAGE=/boot/vmlinuz-3.3.0+
root=UUIDğ197a59-c067-4fd8-ad90-c4d721816077 ro acpi_osi=Linux
Thanks ,
Pradeep Subrahmanion
OK, that's more clearly, please remove acpi_osi=Linux then re-test, I
think the hotkey of backlight control only works with acpi_osi=Linux ?
Thanks a lot!
Joey Lee
Thanks ,
Pradeep Subrahmanion
--
To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
This new patch should remove acpi_video0 interface on your machine.
Please kindly provide your dmidecode:
dmidecode > dmidecode.log
And,
please make should the patch really applied, you can do a bit change on
pr_info message by yourself.
Sorry . I think there was some mistake . I tried the patch again. Now
I see only intel_backlight inside /sys/class/backlight. There is no
acer-wmi interface . Is this the expected behavior ? . Or am I missing
anything ?
Yes, this is the expected behavior! But, now I doubt your issue was
workaround by acpi_osi=Linux but not intel_backlight.
quoted
quoted
echo 5 > /sys/class/backlight/acpi_video0/brightness
echo 5 > /sys/class/backlight/intel_backlight/brightness
But it doesn't make any change .
In my case , 'acpi_backlight = vendor' does not make any difference since the hot key control
already starts working with 'acpi_osi=Linux' option.
cat /proc/cmdline gives ,
BOOT_IMAGE=/boot/vmlinuz-3.3.0+
root=UUIDğ197a59-c067-4fd8-ad90-c4d721816077 ro acpi_osi=Linux
Thanks ,
Pradeep Subrahmanion
OK, that's more clearly, please remove acpi_osi=Linux then re-test, I
think the hotkey of backlight control only works with acpi_osi=Linux ?
Does your backlight control still work if you remove acpi_osi=Linux ?
Thanks a lot!
Joey Lee
--
To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
This new patch should remove acpi_video0 interface on your machine.
Please kindly provide your dmidecode:
dmidecode > dmidecode.log
And,
please make should the patch really applied, you can do a bit change on
pr_info message by yourself.
Sorry . I think there was some mistake . I tried the patch again. Now
I see only intel_backlight inside /sys/class/backlight. There is no
acer-wmi interface . Is this the expected behavior ? . Or am I missing
anything ?
Yes, this is the expected behavior! But, now I doubt your issue was
workaround by acpi_osi=Linux but not intel_backlight.
quoted
quoted
quoted
echo 5 > /sys/class/backlight/acpi_video0/brightness
echo 5 > /sys/class/backlight/intel_backlight/brightness
But it doesn't make any change .
In my case , 'acpi_backlight = vendor' does not make any difference since the hot key control
already starts working with 'acpi_osi=Linux' option.
cat /proc/cmdline gives ,
BOOT_IMAGE=/boot/vmlinuz-3.3.0+
root=UUIDğ197a59-c067-4fd8-ad90-c4d721816077 ro acpi_osi=Linux
Thanks ,
Pradeep Subrahmanion
OK, that's more clearly, please remove acpi_osi=Linux then re-test, I
think the hotkey of backlight control only works with acpi_osi=Linux ?
Does your backlight control still work if you remove acpi_osi=Linux ?
If I remove acpi_osi=Linux , the hot key control stops working .
Thanks a lot!
Joey Lee
Thanks ,
Pradeep Subrahmanion
--
To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
This new patch should remove acpi_video0 interface on your machine.
Please kindly provide your dmidecode:
dmidecode > dmidecode.log
And,
please make should the patch really applied, you can do a bit change on
pr_info message by yourself.
Sorry . I think there was some mistake . I tried the patch again. Now
I see only intel_backlight inside /sys/class/backlight. There is no
acer-wmi interface . Is this the expected behavior ? . Or am I missing
anything ?
Yes, this is the expected behavior! But, now I doubt your issue was
workaround by acpi_osi=Linux but not intel_backlight.
quoted
quoted
quoted
quoted
echo 5 > /sys/class/backlight/acpi_video0/brightness
echo 5 > /sys/class/backlight/intel_backlight/brightness
But it doesn't make any change .
In my case , 'acpi_backlight = vendor' does not make any difference since the hot key control
already starts working with 'acpi_osi=Linux' option.
cat /proc/cmdline gives ,
BOOT_IMAGE=/boot/vmlinuz-3.3.0+
root=UUIDğ197a59-c067-4fd8-ad90-c4d721816077 ro acpi_osi=Linux
Thanks ,
Pradeep Subrahmanion
OK, that's more clearly, please remove acpi_osi=Linux then re-test, I
think the hotkey of backlight control only works with acpi_osi=Linux ?
Does your backlight control still work if you remove acpi_osi=Linux ?
If I remove acpi_osi=Linux , the hot key control stops working .
What is the preload OS in your machine when you bought it? Windows XP,
Vista or Windows 7?
thanks
Joey Lee
--
To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
This new patch should remove acpi_video0 interface on your machine.
Please kindly provide your dmidecode:
dmidecode > dmidecode.log
And,
please make should the patch really applied, you can do a bit change on
pr_info message by yourself.
Sorry . I think there was some mistake . I tried the patch again. Now
I see only intel_backlight inside /sys/class/backlight. There is no
acer-wmi interface . Is this the expected behavior ? . Or am I missing
anything ?
Yes, this is the expected behavior! But, now I doubt your issue was
workaround by acpi_osi=Linux but not intel_backlight.
quoted
quoted
quoted
quoted
echo 5 > /sys/class/backlight/acpi_video0/brightness
echo 5 > /sys/class/backlight/intel_backlight/brightness
But it doesn't make any change .
In my case , 'acpi_backlight = vendor' does not make any difference since the hot key control
already starts working with 'acpi_osi=Linux' option.
cat /proc/cmdline gives ,
BOOT_IMAGE=/boot/vmlinuz-3.3.0+
root=UUIDğ197a59-c067-4fd8-ad90-c4d721816077 ro acpi_osi=Linux
Thanks ,
Pradeep Subrahmanion
OK, that's more clearly, please remove acpi_osi=Linux then re-test, I
think the hotkey of backlight control only works with acpi_osi=Linux ?
Does your backlight control still work if you remove acpi_osi=Linux ?
If I remove acpi_osi=Linux , the hot key control stops working .
What is the preload OS in your machine when you bought it? Windows XP,
Vista or Windows 7?
It was Windows XP.
thanks
Joey Lee
Thanks ,
Pradeep Subrahmanion
--
To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
This new patch should remove acpi_video0 interface on your machine.
Please kindly provide your dmidecode:
dmidecode > dmidecode.log
And,
please make should the patch really applied, you can do a bit change on
pr_info message by yourself.
Sorry . I think there was some mistake . I tried the patch again. Now
I see only intel_backlight inside /sys/class/backlight. There is no
acer-wmi interface . Is this the expected behavior ? . Or am I missing
anything ?
Yes, this is the expected behavior! But, now I doubt your issue was
workaround by acpi_osi=Linux but not intel_backlight.
quoted
quoted
quoted
quoted
echo 5 > /sys/class/backlight/acpi_video0/brightness
echo 5 > /sys/class/backlight/intel_backlight/brightness
But it doesn't make any change .
In my case , 'acpi_backlight = vendor' does not make any difference since the hot key control
already starts working with 'acpi_osi=Linux' option.
cat /proc/cmdline gives ,
BOOT_IMAGE=/boot/vmlinuz-3.3.0+
root=UUIDğ197a59-c067-4fd8-ad90-c4d721816077 ro acpi_osi=Linux
Thanks ,
Pradeep Subrahmanion
OK, that's more clearly, please remove acpi_osi=Linux then re-test, I
think the hotkey of backlight control only works with acpi_osi=Linux ?
Does your backlight control still work if you remove acpi_osi=Linux ?
If I remove acpi_osi=Linux , the hot key control stops working .
What is the preload OS in your machine when you bought it? Windows XP,
Vista or Windows 7?
It was Windows XP.
The WDDM driver didn't support by Windows XP, the brightness control on
XP should works with _BCM or OpRegion.
Wonder how does brightness control work on XP with your machine.
I will dig more in your dsdt...
Thanks
Joey Lee
--
To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
From acer acpi ,I came to know that the 4730 series uses new wmi interface .
http://code.google.com/p/aceracpi/wiki/SupportedHardware
Thanks ,
Pradeep Subrahmanion
On Thu, Mar 22, 2012 at 9:24 AM, joeyli [off-list ref] wrote:
This new patch should remove acpi_video0 interface on your machine.
Please kindly provide your dmidecode:
dmidecode > dmidecode.log
And,
please make should the patch really applied, you can do a bit change on
pr_info message by yourself.
Sorry . I think there was some mistake . I tried the patch again. Now
I see only intel_backlight inside /sys/class/backlight. There is no
acer-wmi interface . Is this the expected behavior ? . Or am I missing
anything ?
Yes, this is the expected behavior! But, now I doubt your issue was
workaround by acpi_osi=Linux but not intel_backlight.
quoted
quoted
quoted
quoted
echo 5 > /sys/class/backlight/acpi_video0/brightness
echo 5 > /sys/class/backlight/intel_backlight/brightness
But it doesn't make any change .
In my case , 'acpi_backlight = vendor' does not make any difference since the hot key control
already starts working with 'acpi_osi=Linux' option.
cat /proc/cmdline gives ,
BOOT_IMAGE=/boot/vmlinuz-3.3.0+
root=UUIDð197a59-c067-4fd8-ad90-c4d721816077 ro acpi_osi=Linux
Thanks ,
Pradeep Subrahmanion
OK, that's more clearly, please remove acpi_osi=Linux then re-test, I
think the hotkey of backlight control only works with acpi_osi=Linux ?
Does your backlight control still work if you remove acpi_osi=Linux ?
If I remove acpi_osi=Linux , the hot key control stops working .
What is the preload OS in your machine when you bought it? Windows XP,
Vista or Windows 7?
It was Windows XP.
The WDDM driver didn't support by Windows XP, the brightness control on
XP should works with _BCM or OpRegion.
Wonder how does brightness control work on XP with your machine.
I will dig more in your dsdt...
Thanks
Joey Lee
This new patch should remove acpi_video0 interface on your machine.
Please kindly provide your dmidecode:
dmidecode > dmidecode.log
And,
please make should the patch really applied, you can do a bit change on
pr_info message by yourself.
Sorry . I think there was some mistake . I tried the patch again. Now
I see only intel_backlight inside /sys/class/backlight. There is no
acer-wmi interface . Is this the expected behavior ? . Or am I missing
anything ?
Yes, this is the expected behavior! But, now I doubt your issue was
workaround by acpi_osi=Linux but not intel_backlight.
quoted
quoted
quoted
quoted
echo 5 > /sys/class/backlight/acpi_video0/brightness
echo 5 > /sys/class/backlight/intel_backlight/brightness
But it doesn't make any change .
In my case , 'acpi_backlight = vendor' does not make any difference since the hot key control
already starts working with 'acpi_osi=Linux' option.
cat /proc/cmdline gives ,
BOOT_IMAGE=/boot/vmlinuz-3.3.0+
root=UUIDğ197a59-c067-4fd8-ad90-c4d721816077 ro acpi_osi=Linux
Thanks ,
Pradeep Subrahmanion
OK, that's more clearly, please remove acpi_osi=Linux then re-test, I
think the hotkey of backlight control only works with acpi_osi=Linux ?
Does your backlight control still work if you remove acpi_osi=Linux ?
If I remove acpi_osi=Linux , the hot key control stops working .
What is the preload OS in your machine when you bought it? Windows XP,
Vista or Windows 7?
It was Windows XP.
The WDDM driver didn't support by Windows XP, the brightness control on
XP should works with _BCM or OpRegion.
Wonder how does brightness control work on XP with your machine.
I will dig more in your dsdt...
Please kindly try acpi_osi="!Windows 2006", I think it also works to
you.
Thanks
Joey Lee
--
To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
This new patch should remove acpi_video0 interface on your machine.
Please kindly provide your dmidecode:
dmidecode > dmidecode.log
And,
please make should the patch really applied, you can do a bit change on
pr_info message by yourself.
Sorry . I think there was some mistake . I tried the patch again. Now
I see only intel_backlight inside /sys/class/backlight. There is no
acer-wmi interface . Is this the expected behavior ? . Or am I missing
anything ?
Yes, this is the expected behavior! But, now I doubt your issue was
workaround by acpi_osi=Linux but not intel_backlight.
quoted
quoted
quoted
quoted
echo 5 > /sys/class/backlight/acpi_video0/brightness
echo 5 > /sys/class/backlight/intel_backlight/brightness
But it doesn't make any change .
In my case , 'acpi_backlight = vendor' does not make any difference since the hot key control
already starts working with 'acpi_osi=Linux' option.
cat /proc/cmdline gives ,
BOOT_IMAGE=/boot/vmlinuz-3.3.0+
root=UUIDğ197a59-c067-4fd8-ad90-c4d721816077 ro acpi_osi=Linux
Thanks ,
Pradeep Subrahmanion
OK, that's more clearly, please remove acpi_osi=Linux then re-test, I
think the hotkey of backlight control only works with acpi_osi=Linux ?
Does your backlight control still work if you remove acpi_osi=Linux ?
If I remove acpi_osi=Linux , the hot key control stops working .
What is the preload OS in your machine when you bought it? Windows XP,
Vista or Windows 7?
It was Windows XP.
The WDDM driver didn't support by Windows XP, the brightness control on
XP should works with _BCM or OpRegion.
Wonder how does brightness control work on XP with your machine.
I will dig more in your dsdt...
Please kindly try acpi_osi="!Windows 2006", I think it also works to
you.
I tried giving this option . It gives me a blank screen while
booting. Hot keys are not working .
Thanks
Joey Lee
Regards,
Pradeep Subrahmanion.
--
To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
think the hotkey of backlight control only works with acpi_osi=Linux ?
yes , hot key control only works with this option.Any ideas about where
the hot key events gets handled ? I tried logging inside
'acpi_video_device_notify' method in video.c . But the control does not
seem to reach here .
Thanks,
Pradeep Subrahmanion
think the hotkey of backlight control only works with acpi_osi=Linux ?
yes , hot key control only works with this option.Any ideas about where
the hot key events gets handled ? I tried logging inside
'acpi_video_device_notify' method in video.c . But the control does not
seem to reach here .
Thanks,
Pradeep Subrahmanion
Hotkey change status is through _Q11 and _Q12 event but not wmi:
Method (_Q11, 0, NotSerialized) /* Brightness down */
{
If (LGreaterEqual (OSYS, 0x07D6)) /* Vista or later */
{
If (LEqual (OBV, 0xFF))
{
Notify (^^^PEGP.VGA.LCD, 0x87)
}
Else
{
Notify (^^^OVGA.DD03, 0x87)
}
}
Else /* 0x07D1 (XP) or 0x03E8 (Linux) */
{
^^^OVGA.AINT (One, BRTS) /* access AINT, it touch BCLP register */
If (LEqual (^^^WMID.BAEF, One))
{
Store (BRTS, Local1)
Store (^^^WMID.LBL0, Local2)
Add (Local2, Local1, Local2)
Store (Local2, ^^^WMID.NTDC)
Notify (WMID, 0x80)
}
}
}
Method (AINT, 2, NotSerialized)
{
...
Else
{
If (LEqual (Arg0, One)) /* Linux or XP */
{
Add (Arg1, One, Arg1)
Store (Divide (Multiply (Arg1, 0xFF), 0x0A, ), BCLP)
Or (BCLP, 0x80000000, BCLP) /* touch BCLP register */
Store (0x02, ASLC)
}
That's why I said acpi_osi"!Windows 2006" should also works to you. Unfortunately,
there have something wrong in video driver for support this machine on XP mode.
thanks a lot!
Joey Lee