All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 221583] Lenovo 82KU: keyboard backlight works via Fn+Space but no kbd_backlight LED device exposed
Date: Fri, 05 Jun 2026 05:55:30 +0000	[thread overview]
Message-ID: <bug-221583-215701-m4AciOBtn6@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221583-215701@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=221583

--- Comment #12 from George (george.stafilidis@proton.me) ---
Created attachment 310268
  --> https://bugzilla.kernel.org/attachment.cgi?id=310268&action=edit
current dsdt.dsl

Hi Rong,
I’ve attached my current dsdt.dsl. With this version, the GNOME Quick Settings
panel correctly displays all three states (Off, Low, High), but clicking any of
them has no effect on the physical backlight. Additionally, pressing Fn+Space
no longer triggers the OSD popup at all.

For context, I previously had a version where Off and Low worked physically and
the OSD appeared, but selecting High would instantly reset the state to Off.
Through EC memory dumping, I confirmed my laptop uses register 0x8A (not 0x2A
as in the original patch), and that writing 0x02 to the 2-bit KLEN field
inadvertently sets the UCHE (USB Charging) bit, which cuts power to the
backlight or whatever qwant thinks I have no idea.

I’m not confident enough in ASL to resolve this safely.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

      parent reply	other threads:[~2026-06-05  5:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-27 19:47 [Bug 221583] New: Lenovo 82KU: keyboard backlight works via Fn+Space but no kbd_backlight LED device exposed bugzilla-daemon
2026-06-01 17:30 ` [Bug 221583] " bugzilla-daemon
2026-06-01 18:06 ` bugzilla-daemon
2026-06-02 13:44 ` bugzilla-daemon
2026-06-02 20:39 ` bugzilla-daemon
2026-06-03 20:13 ` bugzilla-daemon
2026-06-03 21:19 ` bugzilla-daemon
2026-06-04 19:19 ` bugzilla-daemon
2026-06-05  0:11 ` bugzilla-daemon
2026-06-05  1:36 ` bugzilla-daemon
2026-06-05  1:40 ` bugzilla-daemon
2026-06-05  1:48 ` bugzilla-daemon
2026-06-05  5:55 ` bugzilla-daemon [this message]

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=bug-221583-215701-m4AciOBtn6@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.