All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis Benato <denis.benato@linux.dev>
To: "Rebecca Mara Müller" <rebecca.mara@posteo.de>
Cc: Jiri Kosina <jikos@kernel.org>,
	Benjamin Tissoires <bentiss@kernel.org>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	Luke Jones <luke@ljones.dev>,
	Joshua Leivenzon <hacker1024@users.sourceforge.net>,
	Ivan Levchenko <me@livan.pro>,
	Nathan Chancellor <nathan@kernel.org>,
	Paolo Pisati <p.pisati@gmail.com>
Subject: Re: [PATCH v3 7/7] HID: asus: Re-send the Zenbook Duo keyboard handshake after probe
Date: Mon, 19 Oct 2026 22:38:11 +0200	[thread overview]
Message-ID: <5e44ab55-09e3-4043-a369-05b792b5e0d3@linux.dev> (raw)
In-Reply-To: <20261019133557.14092-1-rebecca.mara@posteo.de>


On 10/19/26 15:36, Rebecca Mara Müller wrote:
> On Mon, Oct 19, 2026 at 01:03:34PM +0200, Denis Benato wrote:
>> Very good to see it sleeps just fine. So yeah a command is missing...
> Thank you for the roadmap, I went through it on the UX8407AA with
> BIOS UX8407AA.308. I have since updated to 310, the latest one; its
> ACPI tables only differ from 308 in relocated memory regions, so the
> findings below should hold for both:

Most findings will hold for multiple models across different years
as asus reuses a lot of code for the same lineup. Thankfully!

> - asus-nb-wmi only exposes the basics here (kbd_backlight 0-3,
>   throttle_thermal_policy, charge_mode, screenpad); no TUF/ROG lighting
>   or power-state attributes.

Fair enough.

> - In the decompiled DSDT, WMNB answers 75 device IDs. None of the
>   TUF LED power IDs is among them, so it is not a firmware that claims
>   "unsupported" and accepts the write anyway. The kbd backlight ID
>   0x00050021 goes to the EC (SLKB), which does not reach the detachable
>   keyboard, a separate USB/BT device.

Does this laptop have other lights? I wonder what that is changing...

> - The LPS0 _DSM in PEPD only notifies the EC (MS entry/exit 0x9a/0x9b,
>   display off/on 0xb7/0xb8, entry/exit 0xae/0xaf). With
>   pm_debug_messages on, Linux calls all of them on s2idle (screen off,
>   lps0 ms entry, lps0 entry, and the exits), so nothing is skipped on
>   our side.

I have a cursed TUF that does the same and looks correct and yet it
doesn't sleep in linux... Someday I will understand what's going on
with that. Thankfully it's not the case here as the sleep residency
is high for you.

> - With dynamic debug on usbcore, the keyboard does go to USB suspend
>   ("usb 3-6: usb suspend, wakeup 1", and "wakeup 0" with wakeup
>   disabled), and the backlight stays on in both cases.

Wow... okay... so it was actually designed this way. 

> - The backlight only goes off when the keyboard loses the connection:
>   lifting it off the dock during s2idle turns it off immediately.

Probably because the idea is that "keyboard lit" = "ready to go"/"press a key to resume".

> So the keyboard simply keeps its backlight while it is connected, and
> I guess Windows either cuts the port power in Modern Standby or MyASUS
> turns the light off. I have no Windows on this machine at the moment
> to check which.

Could be that they simply leave it on as said above.

Doesn't look like something to be investigated further, perhaps try to see
if there is some unknown devid in wmi that does something cool.

> Following your advice I did it in userspace: a systemd-sleep hook that
> saves asus::kbd_backlight and writes 0 on "pre", and restores it on
> "post". With v3 loaded the light now goes off just before the screen
> and comes back on resume. If it is useful to anyone else I can post it.

in the OGC discord (ex asus-linux discord, you find it on our website) people
are planning a GUI redesign, perhaps if you have spare time you can add an option
to asusd to shutdown leds when entering sleep to have a GUI on a widely used tool
but I think this is time consuming enough that is probably not worth unless you find
it funny to do.

> Thanks,
> Rebecca

  reply	other threads:[~2026-10-19 20:38 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-13 10:39 [PATCH v3 0/7] HID: asus: ASUS Zenbook Duo keyboard support Paolo Pisati
2026-10-13 10:39 ` [PATCH v3 1/7] HID: asus: Fix up Zenbook Duo report descriptors Paolo Pisati
2026-10-18 15:50   ` Denis Benato
2026-10-18 16:18     ` Rebecca Mara Müller
2026-10-18 17:52       ` Denis Benato
2026-10-13 10:39 ` [PATCH v3 2/7] HID: asus: Add missing Zenbook Duo hotkeys Paolo Pisati
2026-10-18 15:55   ` Denis Benato
2026-10-18 21:38     ` Nathan Chancellor
2026-10-18 21:39       ` Denis Benato
2026-10-13 10:40 ` [PATCH v3 3/7] HID: asus: Force hid-input to bind to the Zenbook Duo hotkey interface Paolo Pisati
2026-10-18 16:06   ` Denis Benato
2026-10-13 10:40 ` [PATCH v3 4/7] HID: asus: Cycle the platform profile from the Zenbook Duo profile key Paolo Pisati
2026-10-18 16:27   ` Denis Benato
2026-10-13 10:40 ` [PATCH v3 5/7] HID: asus: Do not send feature reports larger than declared Paolo Pisati
2026-10-18 16:52   ` Denis Benato
2026-10-13 10:40 ` [PATCH v3 6/7] HID: asus: add prod-id, quirk for Zenbook Duo keyboard Paolo Pisati
2026-10-18 16:57   ` Denis Benato
2026-10-18 21:43     ` Nathan Chancellor
2026-10-18 21:46       ` Denis Benato
2026-10-13 10:40 ` [PATCH v3 7/7] HID: asus: Re-send the Zenbook Duo keyboard handshake after probe Paolo Pisati
2026-10-18 17:10   ` Denis Benato
2026-10-18 19:18     ` Rebecca Mara Müller
2026-10-18 19:48       ` Denis Benato
2026-10-19  6:12         ` Rebecca Mara Müller
2026-10-19 11:03           ` Denis Benato
2026-10-19 13:36             ` Rebecca Mara Müller
2026-10-19 20:38               ` Denis Benato [this message]
2026-10-20  7:42                 ` Rebecca Mara Müller
2026-10-13 11:45 ` [PATCH v3 0/7] HID: asus: ASUS Zenbook Duo keyboard support Rebecca Mara Müller
2026-10-13 13:56   ` Denis Benato
2026-10-14 13:21     ` Paolo Pisati
2026-10-18 17:21       ` Denis Benato

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=5e44ab55-09e3-4043-a369-05b792b5e0d3@linux.dev \
    --to=denis.benato@linux.dev \
    --cc=bentiss@kernel.org \
    --cc=hacker1024@users.sourceforge.net \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luke@ljones.dev \
    --cc=me@livan.pro \
    --cc=nathan@kernel.org \
    --cc=p.pisati@gmail.com \
    --cc=rebecca.mara@posteo.de \
    /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.