From: Jiri Slaby <jirislaby@kernel.org>
To: Luke Jones <luke@ljones.dev>, linux-kernel@vger.kernel.org
Cc: hdegoede@redhat.com, ilpo.jarvinen@linux.intel.com,
platform-driver-x86@vger.kernel.org, linux-input@vger.kernel.org,
bentiss@kernel.org, jikos@kernel.org, mario.limonciello@amd.com,
lkml@antheas.dev
Subject: Re: [PATCH v4 2/2] platform/x86: asus-wmi: Refactor Ally suspend/resume
Date: Wed, 20 Aug 2025 05:47:09 +0200 [thread overview]
Message-ID: <07815053-0e31-4e8e-8049-b652c929323b@kernel.org> (raw)
In-Reply-To: <20250323023421.78012-3-luke@ljones.dev>
On 23. 03. 25, 3:34, Luke Jones wrote:
> From: "Luke D. Jones" <luke@ljones.dev>
>
> Adjust how the CSEE direct call hack is used.
>
> The results of months of testing combined with help from ASUS to
> determine the actual cause of suspend issues has resulted in this
> refactoring which immensely improves the reliability for devices which
> do not have the following minimum MCU FW version:
> - ROG Ally X: 313
> - ROG Ally 1: 319
...
> --- a/drivers/platform/x86/asus-wmi.c
> +++ b/drivers/platform/x86/asus-wmi.c
...
> @@ -5010,6 +5060,10 @@ static int asus_wmi_probe(struct platform_device *pdev)
> return ret;
> }
>
> + ret = acpi_register_lps0_dev(&asus_ally_s2idle_dev_ops);
This likely causes crashes:
https://bugzilla.suse.com/show_bug.cgi?id=1246924
> asus-nb-wmi asus-nb-wmi: Detected ATK, not ASUSWMI, use DSTS
> list_add double add: new=ffffffffc2094460, prev=ffffffffafa5cd20,
next=ffffffffc2094460.
> ------------[ cut here ]------------
> kernel BUG at lib/list_debug.c:35!
...
> acpi_register_lps0_dev.cold (include/linux/list.h:88
include/linux/list.h:150 include/linux/list.h:169
drivers/acpi/x86/s2idle.c:663)
> asus_wmi_probe (drivers/platform/x86/asus-wmi.c:5045 (discriminator
1) drivers/platform/x86/asus-wmi.c:5089 (discriminator 1)) asus_wmi
> platform_probe (drivers/base/platform.c:1404)
> really_probe (drivers/base/dd.c:579)
It looks like acpi_register_lps0_dev() is called twice with those ops...
Should the above be registered only if it is this RC71 device?
thanks,
--
js
suse labs
next prev parent reply other threads:[~2025-08-20 3:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-23 2:34 [PATCH v4 0/2] hid-asus: asus-wmi: refactor Ally suspend/resume Luke Jones
2025-03-23 2:34 ` [PATCH v4 1/2] hid-asus: check ROG Ally MCU version and warn Luke Jones
2025-03-25 1:27 ` Mario Limonciello
2025-03-23 2:34 ` [PATCH v4 2/2] platform/x86: asus-wmi: Refactor Ally suspend/resume Luke Jones
2025-03-24 12:10 ` Ilpo Järvinen
2025-03-24 22:39 ` Luke D. Jones
2025-03-25 1:28 ` Mario Limonciello
2025-08-20 3:47 ` Jiri Slaby [this message]
2025-03-23 11:41 ` [PATCH v4 0/2] hid-asus: asus-wmi: refactor " Antheas Kapenekakis
2025-03-24 1:41 ` Luke D. Jones
2025-03-24 8:11 ` Antheas Kapenekakis
2025-03-24 10:33 ` Luke D. Jones
2025-03-24 14:46 ` Antheas Kapenekakis
2025-03-24 23:43 ` Luke D. Jones
2025-03-24 23:47 ` Antheas Kapenekakis
2025-05-05 13:52 ` Ilpo Järvinen
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=07815053-0e31-4e8e-8049-b652c929323b@kernel.org \
--to=jirislaby@kernel.org \
--cc=bentiss@kernel.org \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@antheas.dev \
--cc=luke@ljones.dev \
--cc=mario.limonciello@amd.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).