From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: linux-kernel@vger.kernel.org, Luke Jones <luke@ljones.dev>
Cc: hdegoede@redhat.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 0/2] hid-asus: asus-wmi: refactor Ally suspend/resume
Date: Mon, 05 May 2025 16:52:19 +0300 [thread overview]
Message-ID: <174645313917.23202.9513224587280023124.b4-ty@linux.intel.com> (raw)
In-Reply-To: <20250323023421.78012-1-luke@ljones.dev>
On Sun, 23 Mar 2025 15:34:19 +1300, 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.
>
> [...]
Thank you for your contribution, it has been applied to my local
review-ilpo-next branch. Note it will show up in the public
platform-drivers-x86/review-ilpo-next branch only once I've pushed my
local branch there, which might take a while.
The list of commits applied:
[1/2] hid-asus: check ROG Ally MCU version and warn
commit: 6b4585948d1ed226f194195180be09fa24b760ec
[2/2] platform/x86: asus-wmi: Refactor Ally suspend/resume
commit: c26e7d5d2d89af198b43e4c57b1aff5289f65450
--
i.
prev parent reply other threads:[~2025-05-05 13:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-23 2:34 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
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 [this message]
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=174645313917.23202.9513224587280023124.b4-ty@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=bentiss@kernel.org \
--cc=hdegoede@redhat.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
all inboxes | Powered by JetHome®