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: Thu, 04 Jun 2026 19:19:58 +0000	[thread overview]
Message-ID: <bug-221583-215701-gYAnVbtqCO@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 #7 from Rong Zhang (i@rong.moe) ---
Created attachment 310266
  --> https://bugzilla.kernel.org/attachment.cgi?id=310266&action=edit
DSDT patch

Hi George,

Thanks for debugging. Based on the information, software control should be
possible by overriding the device's DSDT with appropriate ACPI methods properly
implemented, which is (unfortunately) not upstreamable.

But as the first step, please try writing to the address via /dev/mem and see
if the keyboard backlight brightness changes (replace 0xXX with the values you
found):

  sudo busybox devmem 0xFE00D42A 8 0xXX

Writing to EC registers could be dangerous, so please be cautious.

I copied and pasted some code from my device's DSDT to create a DSDT patch for
your device. If writing to the address works, you may use it to provide the
required ACPI method to ideapad-laptop. I'm not an expert in writing ASL and
didn't test it at all, so there is a chance that things could go wrong. Be
cautious.

See
https://www.kernel.org/doc/html/latest/admin-guide/acpi/initrd_table_override.html
and https://wiki.archlinux.org/title/DSDT for detailed instructions on
overriding DSDT.

I'd recommend overriding it using GRUB2. See also
https://www.gnu.org/software/grub/manual/grub/html_node/acpi.html
If it ain't work, try GRUB_EARLY_INITRD_LINUX_CUSTOM. See
https://www.gnu.org/software/grub/manual/grub/html_node/Simple-configuration.html

-- 
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-04 19:19 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 [this message]
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

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-gYAnVbtqCO@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.