From: Hans de Goede <hdegoede@redhat.com>
To: "Luke D. Jones" <luke@ljones.dev>, linux-kernel@vger.kernel.org
Cc: platform-driver-x86@vger.kernel.org,
ilpo.jarvinen@linux.intel.com, corentin.chary@gmail.com,
superm1@kernel.org
Subject: Re: [PATCH 0/3] platfom/x86: asus-wmi: revert ROG Ally quirks
Date: Sat, 5 Oct 2024 16:37:06 +0200 [thread overview]
Message-ID: <5c21455c-c688-4287-a4ad-d047efa180eb@redhat.com> (raw)
In-Reply-To: <20240926095344.1291013-1-luke@ljones.dev>
Hi Luke,
On 26-Sep-24 11:53 AM, Luke D. Jones wrote:
> The ASUS ROG Ally (and Ally X) quirks that I added over the last year
> are not required. I worked with ASUS to pinpoint the exact cause of
> the original issue (MCU USB dev missing every second resume) and the
> result is a new MCU firmware which will be released on approx 16/10/24.
First of all let me say that it is great that you have gotten Asus
to come up with a fixed firmware, thank you.
With that said I believe that it is way too early to revert these quirks,
users are usually not great at installing BIOS updates and that assumes
this will be handled as part of a BIOS update, if it requires running
a separate tool then the chances of users not installing the update
will likely be even worse.
So IMHO for now we should keep these quirks around to avoid regressions
for users who don't have the MCU update.
Related, have you seen this series:
https://lore.kernel.org/platform-driver-x86/20240922172258.48435-1-lkml@antheas.dev/
that seems to fix the same issue ?
And it does so in another, arguably better way.
Although unfortunately as patch 3/5 shows just calling the global
"display off" callback before suspending devices is not enough
fixing things still requires inserting a sleep using a DMI quirk :|
Still that series including the DMI quirk might be a cleaner way
to deal with this and if that is merged then dropping the quirks
from asus-wmi makes sense.
Regards,
Hans
> All users should update to MCU FW as soon as released to:
> - Ally 1: v319
> - Ally X: v313
>
> Luke D. Jones (3):
> Revert "platform/x86: asus-wmi: ROG Ally increase wait time, allow MCU
> powersave"
> Revert "platform/x86: asus-wmi: disable USB0 hub on ROG Ally before
> suspend"
> platfom/x86: asus-wmi: cleanup after Ally quirk reverts
>
> drivers/platform/x86/asus-wmi.c | 39 +--------------------------------
> 1 file changed, 1 insertion(+), 38 deletions(-)
>
next prev parent reply other threads:[~2024-10-05 14:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 9:53 Luke D. Jones
2024-09-26 9:53 ` [PATCH 1/3] Revert "platform/x86: asus-wmi: ROG Ally increase wait time, allow MCU powersave" Luke D. Jones
2024-09-26 9:53 ` [PATCH 2/3] Revert "platform/x86: asus-wmi: disable USB0 hub on ROG Ally before suspend" Luke D. Jones
2024-09-26 9:53 ` [PATCH 3/3] platfom/x86: asus-wmi: cleanup after Ally quirk reverts Luke D. Jones
2024-09-28 20:56 ` kernel test robot
2024-09-26 13:36 ` [PATCH 0/3] platfom/x86: asus-wmi: revert ROG Ally quirks Mario Limonciello
2024-10-02 8:12 ` Luke Jones
2024-10-05 14:37 ` Hans de Goede [this message]
2024-10-05 19:48 ` Luke Jones
2024-10-05 21:59 ` Hans de Goede
2024-10-08 0:03 ` Luke Jones
2024-10-08 1:53 ` Mario Limonciello
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=5c21455c-c688-4287-a4ad-d047efa180eb@redhat.com \
--to=hdegoede@redhat.com \
--cc=corentin.chary@gmail.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luke@ljones.dev \
--cc=platform-driver-x86@vger.kernel.org \
--cc=superm1@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®