From: Mario Limonciello <mario.limonciello@amd.com>
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
Subject: Re: [PATCH v3 0/2] hid-asus: asus-wmi: refactor Ally suspend/resume
Date: Thu, 27 Feb 2025 08:35:15 -0600 [thread overview]
Message-ID: <78e96d3c-be3a-4a62-a6cb-4540f4a5c86e@amd.com> (raw)
In-Reply-To: <20250227085817.1007697-1-luke@ljones.dev>
On 2/27/2025 02:58, Luke Jones wrote:
> This short series refactors the Ally suspend/resume functionality in the
> asus-wmi driver along with adding support for ROG Ally MCU version checking.
>
> The version checking is then used to toggle the use of older CSEE call hacks
> that were initially used to combat Ally suspend/wake issues arising from the MCU
> not clearing a particular flag on resume. ASUS have since corrected this
> especially for Linux in newer firmware versions.
>
> - hid-asus requests the MCU version and displays a warning if the version is
> older than the one that fixes the issue.
> - hid-asus awill also toggle the CSEE hack off, and mcu_powersave to on if the
> version is high enough.
>
> *Note: In review it was requested by Mario that I try strsep() for parsing
> the version. I did try this and a few variations but the result was much
> more code due to having to check more edge cases due to the input being
> raw bytes. In the end the cleaned up while loop proved more robust.
>
> - Changelog:
> + V2: https://lore.kernel.org/platform-driver-x86/20250226010129.32043-1-luke@ljones.dev/T/#t
> - Adjust warning message to explicitly mention suspend issues
> - Use switch/case block to set min_version
> - Set min_version to 0 by default and toggle hacks off
> + V3
> - Remove noise (excess pr_info)
> - Use kstrtoint, not kstrtolong
> - Use __free(kfree) for allocated mem and drop goto + logging
> - Use print_hex_dump() to show failed data after pr_err in mcu_request_version()
> - Use pr_debug in set_ally_mcu_hack() and set_ally_mcu_powersave() plus
> correct the message.
>
> Luke D. Jones (2):
> hid-asus: check ROG Ally MCU version and warn
> platform/x86: asus-wmi: Refactor Ally suspend/resume
>
> drivers/hid/hid-asus.c | 111 +++++++++++++++++-
> drivers/platform/x86/asus-wmi.c | 130 ++++++++++++++-------
> include/linux/platform_data/x86/asus-wmi.h | 15 +++
> 3 files changed, 215 insertions(+), 41 deletions(-)
>
Reviewed-by: Mario Limonciello <mario.limonciello@amd.com>
next prev parent reply other threads:[~2025-02-27 14:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 8:58 Luke Jones
2025-02-27 8:58 ` [PATCH v3 1/2] hid-asus: check ROG Ally MCU version and warn Luke Jones
2025-02-27 8:58 ` [PATCH v3 2/2] platform/x86: asus-wmi: Refactor Ally suspend/resume Luke Jones
2025-03-08 2:55 ` kernel test robot
2025-03-12 21:57 ` Luke Jones
2025-02-27 14:35 ` Mario Limonciello [this message]
2025-03-04 20:56 ` [PATCH v3 0/2] hid-asus: asus-wmi: refactor " Jiri Kosina
2025-03-06 12:58 ` Ilpo Järvinen
2025-03-21 3:51 Luke Jones
2025-03-21 3:53 ` Luke D. Jones
2025-03-21 17:39 ` Antheas Kapenekakis
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=78e96d3c-be3a-4a62-a6cb-4540f4a5c86e@amd.com \
--to=mario.limonciello@amd.com \
--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=luke@ljones.dev \
--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
all inboxes | Powered by JetHome®