Bug 38342
Summary: | [Ironlake LVDS Vaio-Y i915] Backlight controls ineffective | ||
---|---|---|---|
Product: | ACPI | Reporter: | Michel Alexandre Salim (salimma) |
Component: | Power-Video | Assignee: | acpi_power-video |
Status: | CLOSED INSUFFICIENT_DATA | ||
Severity: | normal | CC: | rui.zhang |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 3.0-rc4 | Subsystem: | |
Regression: | No | Bisected commit-id: | |
Attachments: |
lspci -vv
Disassembled DSDT dmesg changes from setting brightness dmesg changes from issuing setpci command mjg's i915 native GPU backlight control patch from linux-next |
Description
Michel Alexandre Salim
2011-06-27 09:54:51 UTC
Created attachment 63582 [details]
lspci -vv
Created attachment 63602 [details] Disassembled DSDT Taken with acpidump followed by iasl, per http://www.linux.it/~malattia/wiki/index.php/Disassemble_your_DSDT Created attachment 63622 [details]
dmesg changes from setting brightness
(brightness set by echo-ing to /sys/class/backlight/acpi_video0/brightness -- kernel booted with options i915.lvds_use_ssc=0 drm.debug=0x06)
Created attachment 63632 [details]
dmesg changes from issuing setpci command
[root@sojourner sony]# setpci -s 00:02.0 f4.b=ff
[root@sojourner sony]# setpci -s 00:02.0 f4.b
00
Same results with 3.0-rc5 Created attachment 65412 [details]
mjg's i915 native GPU backlight control patch from linux-next
Applying Matthew Garrett's latest iteration of the i915 native backlight patch,
already in linux-next, on top of Linus' 3.0rc7 fixes the issue for me.
Several points:
1) it'd be nice if the acpi_video0 interface is not made available since it does not work - is there a way to blacklist my particular hardware?
2) is there a kernel switch for selecting the graphics device's backlight control, similar to how now the user can select between video.ko and the vendor-supplied driver?
It's great that the kernel bugzilla is back. Can you please verify if the problem still exists in the latest upstream kernel? bug closed as there is no response from the bug reporter. please feel free to reopen it if the problem still exists in the latest upstream kernel. |