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 13:03:34 +0200 [thread overview]
Message-ID: <07076668-3291-4eb6-888b-0e6c518ef21b@linux.dev> (raw)
In-Reply-To: <20261019061209.415930-1-rebecca.mara@posteo.de>
19 ott 2026 08:12:47 Rebecca Mara Müller <rebecca.mara@posteo.de>:
> On Sun, Oct 18, 2026 at 09:48:21PM +0200, Denis Benato wrote:
>> Well you know how this things go... Only who does nothing can claim
>> to have made no mistakes.
>
> Thank you, Denis, that was kind.
>
>> So I am concerned that hardware isn't entering s2idle properly...
>> Are you sure it is?
>
> I checked it this morning on the UX8407AA (Panther Lake), keyboard
> docked, with 30 s of s2idle via rtcwake -m freeze -s 30, reading
> /sys/power/suspend_stats/last_hw_sleep and
> /sys/devices/system/cpu/cpuidle/low_power_idle_system_residency_us:
>
> without hid-asus (hid-generic): 27.6 s hardware sleep, S0ix +27.6 s
> with v3 loaded: 28.6 s hardware sleep, S0ix +28.6 s
>
> So it does reach S0ix, with and without the series. With v3 loaded and
> the backlight set to level 3 before suspending, the keyboard backlight
> stayed on unchanged for the whole time, no change in brightness or
> pattern. So I guess it is the second case you mention: nothing tells
> the keyboard to switch the backlight off on suspend.
>
Very good to see it sleeps just fine. So yeah a command is missing... On top of my mind there are a few possibilities:
- is has a tuf leds power devid in asus-wmi (please check in /sys/class/platform/asus* what's available
- as the previous one, but firmware is bugged and the query of the capability returns not supported while the write goes through (there is at least another model doing that)
- it supports ROG-style power controls of zones and asusctl is lacking support
- it has some other devid for that
First thing I would do is to follow instructions in gitlab.com/asus-linux/reverse-engineering to grab the acpi and search for devid that does things (I suggest an llm to quickly find unmapped/missing IDS) and if that fails I would head to windows to see what the asus software sends over USB... On what I deal with (ROGs mainly) the application is armoury crate, but perhaps on zenbooks and other line-ups it's not available and you only have myasus.
If that fails, and windows gets leds off, with "fails" meaning there is no command to tell the firmware what to do on s2idle.... Fire up a windows VM, pass the hid device to it, setup the vm for s2idle and run a capture with wireshark on linux.... That should tell you if an explicit command is needed.
If that's the case setup userspace to turn leds off, don't do it in kernel or TUFs will break lighting while in s2idle.
> And if you ever need something tested, on this machine or anything
> else, feel free to ping me. I enjoyed this and learned a lot, and I
> would like to keep learning.
>
> Thanks,
> Rebecca
next prev parent reply other threads:[~2026-10-19 11:03 UTC|newest]
Thread overview: 29+ 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 [this message]
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=07076668-3291-4eb6-888b-0e6c518ef21b@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox