https://bugzilla.kernel.org/show_bug.cgi?id=204251
Sharadh Rajaraman (r.shar...@yahoo.com.sg) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |r.shar...@yahoo.com.sg
--- Comment #26 from Sharadh Rajaraman (r.shar...@yahoo.com.sg) ---
On my notebook, a Dell Precision 7530 running Arch Linux with kernel
5.4.6.arch3-1, pressing the brightness up/down keys (Fn + up/down arrows)
throws precisely the same seven lines of ACPI errors.
However, writing values directly to /sys/class/intel_backlight/brightness
*works* (as described in the Arch wiki:
https://wiki.archlinux.org/index.php/Backlight#ACPI ) and the internal LCD
brightness changes.
I haven’t tried using the kernel parameter i915.enable_dpcd_backlight=1 yet,
but I shall as soon as I get back to my notebook.
That said, I’m more interested in patching the SSDT method if possible, to keep
the native functionality, as mentioned in the comment:
(In reply to Zhang Rui from comment #24)
> acpiexec dsdt.dat:
> - find BRT6
> \_SB.PCI0.GFX0.BRT6 Method 0x55e9480d0200 001 Args 2 Len
> 001A Aml 0x7f26bbc23cd9
> \_SB.PCI0.PEG0.PEGP.BRT6 Method 0x55e9480d2640 001 Args 2 Len
> 0022 Aml 0x7f26bbc2401b
> - find LCD
> \_SB.PCI0.GFX0.LCD Device 0x55e9480cdf50 001
>
> so we have two BRT6 method, they share similar code.
> it is okay for \_SB.PCI0.GFX0.BRT6 to use relative path LCD, but it is not
> okay for
> \_SB.PCI0.PEG0.PEGP.BRT6 to do so.
>
> Method (BRT6, 2, NotSerialized)
> {
> If ((EVD5 == One))
> {
> If ((Arg0 == One))
> {
> Notify (LCD, 0x86) // Device-Specific
> }
>
> If ((Arg0 & 0x02))
> {
> Notify (LCD, 0x87) // Device-Specific
> }
> }
> }
> I guess the ACPI errors will go away if we replace LCD with
> \_SB.PCI0.GFX0.LCD.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
