From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Asai Neko <sugar@sne.moe>
Cc: Corentin Chary <corentin.chary@gmail.com>,
"Luke D. Jones" <luke@ljones.dev>,
Denis Benato <denis.benato@linux.dev>,
Hans de Goede <hansg@kernel.org>,
platform-driver-x86@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] platform/x86: asus-wmi: don't warn when LPS0 is unavailable
Date: Thu, 17 Sep 2026 11:51:56 +0300 (EEST) [thread overview]
Message-ID: <c2be7ab0-8e9f-1b40-b019-c32a3a97fcc9@linux.intel.com> (raw)
In-Reply-To: <20260917-asus-wmi-lps0-unavailable-warn-v2-1-aa8e3d73634a@sne.moe>
[-- Attachment #1: Type: text/plain, Size: 3100 bytes --]
On Thu, 17 Sep 2026, Asai Neko wrote:
> asus-wmi attempts to register its LPS0 suspend-to-idle callback during
> probe. acpi_register_lps0_dev() returns -ENODEV when the LPS0 interface
> is unavailable or explicitly disabled, but the driver treats this
> expected condition as a registration failure and prints:
>
> failed to register LPS0 sleep handler in asus-wmi
>
> This occurs on the ASUS ROG STRIX X670E-A GAMING WIFI with BIOS 2704.
> The system exposes no PNP0D80 ACPI device and uses deep suspend. The
> warning therefore misleadingly suggests a sleep-related malfunction
> on a platform where the LPS0 callback is not applicable.
>
> Suppress the warning for -ENODEV while retaining it for other errors.
> Leave callback registration and suspend/resume behavior unchanged.
>
> Signed-off-by: Asai Neko <sugar@sne.moe>
Thanks, I've replaced v1 with this one in the review-ilpo-next branch.
Next time, please collect the Reviewed-by (and possible Tested-by) tags
from the previous version(s) when sending another version because our
maintainer tools only collect them for the current version.
Only if you make really major changes, then you may opt to drop the tags.
--
i.
> ---
> Avoid the misleading ASUS WMI warning when LPS0 is unavailable.
> The diagnosis and rationale are included in the patch commit
> message.
> ---
> Changes in v2:
> - Fix the missing format specifier for ret reported by kernel test robot.
> - Shorten the warning message to keep the format string on one line.
> - Report: https://lore.kernel.org/oe-kbuild-all/202609170237.IYNujwsM-lkp@intel.com/
> - Link to v1: https://patch.msgid.link/20260916-asus-wmi-lps0-unavailable-warn-v1-1-9bd6fb4c10f9@sne.moe
>
> To: Corentin Chary <corentin.chary@gmail.com>
> To: "Luke D. Jones" <luke@ljones.dev>
> To: Denis Benato <denis.benato@linux.dev>
> To: Hans de Goede <hansg@kernel.org>
> To: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
> Cc: platform-driver-x86@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
> ---
> drivers/platform/x86/asus-wmi.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/platform/x86/asus-wmi.c b/drivers/platform/x86/asus-wmi.c
> index a65090429ca7..c2af1f049b67 100644
> --- a/drivers/platform/x86/asus-wmi.c
> +++ b/drivers/platform/x86/asus-wmi.c
> @@ -5421,8 +5421,11 @@ static struct acpi_s2idle_dev_ops asus_ally_s2idle_dev_ops = {
>
> static void asus_s2idle_check_register(void)
> {
> - if (acpi_register_lps0_dev(&asus_ally_s2idle_dev_ops))
> - pr_warn("failed to register LPS0 sleep handler in asus-wmi\n");
> + int ret;
> +
> + ret = acpi_register_lps0_dev(&asus_ally_s2idle_dev_ops);
> + if (ret && ret != -ENODEV)
> + pr_warn("failed to register LPS0 sleep handler: %d\n", ret);
> }
>
> static void asus_s2idle_check_unregister(void)
>
> ---
> base-commit: 587858367581b9c55c3690f4e63382ad622719d4
> change-id: 20260916-asus-wmi-lps0-unavailable-warn-9a72be44b9ed
>
> Best regards,
> --
> Asai Neko <sugar@sne.moe>
>
>
>
next prev parent reply other threads:[~2026-09-17 8:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 16:32 [PATCH] " Asai Neko
2026-09-15 17:15 ` Mario Limonciello
2026-09-15 17:16 ` Denis Benato
2026-09-16 11:00 ` Ilpo Järvinen
2026-09-16 18:13 ` kernel test robot
2026-09-16 18:38 ` [PATCH v2] " Asai Neko
2026-09-17 8:51 ` Ilpo Järvinen [this message]
2026-09-16 18:46 ` [PATCH] " kernel test robot
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=c2be7ab0-8e9f-1b40-b019-c32a3a97fcc9@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=corentin.chary@gmail.com \
--cc=denis.benato@linux.dev \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luke@ljones.dev \
--cc=platform-driver-x86@vger.kernel.org \
--cc=sugar@sne.moe \
/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
all inboxes | Powered by JetHome®