public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Mario Limonciello <mario.limonciello@amd.com>
To: Antheas Kapenekakis <lkml@antheas.dev>
Cc: Luke Jones <luke@ljones.dev>,
	"Derek J. Clark" <derekjohn.clark@gmail.com>,
	me@kylegospodneti.ch, Denis Benato <benato.denis96@gmail.com>,
	linux-pm@vger.kernel.org
Subject: Re: [PATCH v2 0/5] acpi/x86: s2idle: move Display off/on calls outside suspend (fixes ROG Ally suspend)
Date: Mon, 23 Sep 2024 12:15:30 -0500	[thread overview]
Message-ID: <ea2232b7-fb29-429b-af9d-af43a2c0cacb@amd.com> (raw)
In-Reply-To: <CAGwozwGsyebGE78SKMckkm2=8uqDTX+S-Jnxrn61X_UHVEDcDA@mail.gmail.com>

On 9/23/2024 11:54, Antheas Kapenekakis wrote:

>> I hope that more of these handhelds with MCUs that get regular updates
>> make the same investment.
> 
> I do not think every manufacturer creates a HID spec for updates. They
> use the same cookiecutter stuff, for which there is no linux
> implementation at all, so kind of the same. Probably after we do 1-3,
> we will have all of them.

Actually there are already about a dozen implementations for HID 
protocols in fwupd.  I've written a few myself, Richard has written way 
more than me, and there are even have vendors contributing to their own 
plugins now.

I do think that it's very likely that ASUS uses the same implementation 
on a lot of their devices, so yes if we get firmware updating figured 
out on one we'll probably have it for many more.

> 
> I saw that HID interface though, and the Legion Go has one and I am
> none the wiser.
> 
> I've been doing HID for over a year by now, so I am used to it.

Considering the previous experience, maybe you can help to document 
their update protocol?  I'm happy to collaborate on the fwupd side if 
you can help push it along.

> Biggest problem is you cannot trigger an update in Windows whenever
> you want to sniff it. At least on the Lenovo.
> 
> However, I think I have bigger fish to fry, so it is not high in my
> priority list.
> 

AFAICT any need for this series goes away when you have an easy way to 
update a handheld that is running Linux already.  I would take a pile of 
userspace code over kernel quirks any day.

  reply	other threads:[~2024-09-23 17:15 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-22 17:22 [PATCH v2 0/5] acpi/x86: s2idle: move Display off/on calls outside suspend (fixes ROG Ally suspend) Antheas Kapenekakis
2024-09-22 17:22 ` [PATCH v2 1/5] acpi/x86: s2idle: add support for Display Off and Display On callbacks Antheas Kapenekakis
2024-09-23 15:57   ` Mario Limonciello
2024-09-22 17:22 ` [PATCH v2 2/5] acpi/x86: s2idle: handle Display On/Off calls outside of suspend sequence Antheas Kapenekakis
2024-09-23 16:03   ` Mario Limonciello
2024-09-23 16:15     ` Antheas Kapenekakis
2024-09-23 16:30       ` Mario Limonciello
2024-09-23 16:43         ` Antheas Kapenekakis
2024-09-23 17:01           ` Antheas Kapenekakis
2024-09-23 17:05           ` Mario Limonciello
2024-09-23 17:13             ` Antheas Kapenekakis
2024-09-22 17:22 ` [PATCH v2 3/5] acpi/x86: s2idle: add quirk table for modern standby delays Antheas Kapenekakis
2024-09-22 17:54   ` Denis Benato
2024-09-22 18:00     ` Antheas Kapenekakis
2024-09-22 17:22 ` [PATCH v2 4/5] acpi/x86: s2idle: call Display On/Off as part of callbacks and rename Antheas Kapenekakis
2024-09-22 17:22 ` [PATCH v2 5/5] platform/x86: asus-wmi: remove Ally (1st gen) and Ally X suspend quirk Antheas Kapenekakis
2024-09-22 18:15 ` [PATCH v2 0/5] acpi/x86: s2idle: move Display off/on calls outside suspend (fixes ROG Ally suspend) Derek J. Clark
2024-09-22 19:40   ` Antheas Kapenekakis
2024-09-23  1:35     ` Derek J. Clark
2024-09-23  5:57       ` Antheas Kapenekakis
2024-09-23 11:09         ` Luke Jones
2024-09-23 13:11           ` Antheas Kapenekakis
2024-09-23 15:56             ` Mario Limonciello
2024-09-23 16:11               ` Antheas Kapenekakis
2024-09-23 16:21                 ` Mario Limonciello
2024-09-23 16:54                   ` Antheas Kapenekakis
2024-09-23 17:15                     ` Mario Limonciello [this message]
2024-09-23 17:48                       ` Antheas Kapenekakis
2024-10-05 14:21 ` Hans de Goede
2024-10-05 15:10   ` Antheas Kapenekakis
2024-10-05 16:24     ` Hans de Goede
2024-10-05 16:27       ` Hans de Goede
2024-10-05 16:50         ` Antheas Kapenekakis
2024-10-05 16:57       ` Antheas Kapenekakis
2024-10-05 21:47       ` Hans de Goede
2024-10-05 22:15         ` Antheas Kapenekakis
2024-10-06 10:16           ` Hans de Goede
2024-10-06 11:29             ` 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=ea2232b7-fb29-429b-af9d-af43a2c0cacb@amd.com \
    --to=mario.limonciello@amd.com \
    --cc=benato.denis96@gmail.com \
    --cc=derekjohn.clark@gmail.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=lkml@antheas.dev \
    --cc=luke@ljones.dev \
    --cc=me@kylegospodneti.ch \
    /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