[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<CAGwozwHZCLaVD8iRgRxvQNqw3v+T9J+omMF+JoNe1r=+S1-OsA@mail.gmail.com>
Date: Mon, 24 Feb 2025 23:55:43 +0100
From: Antheas Kapenekakis <lkml@...heas.dev>
To: Armin Wolf <W_Armin@....de>
Cc: Luke Jones <luke@...nes.dev>, Mark Pearson <mpearson-lenovo@...ebb.ca>,
"Limonciello, Mario" <mario.limonciello@....com>,
Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>,
Len Brown <lenb@...nel.org>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
linux-kernel@...r.kernel.org,
"platform-driver-x86@...r.kernel.org" <platform-driver-x86@...r.kernel.org>,
"Rafael J. Wysocki" <rafael@...nel.org>, Hans de Goede <hdegoede@...hat.com>,
me@...egospodneti.ch
Subject: Re: [PATCH 0/3] ACPI: platform_profile: fix legacy sysfs with
multiple handlers
> I see. Maybe extending userspace to support the new platform-profile class interface
> could solve this issue without breaking already existing scripts.
>
> However i do not know the amount of work which needs to be done to achieve this.
The patch series I proposed here restores the behavior of the legacy
API 1-1 with 6.13, ensuring that there are no userspace breakages and
allows for maintaining the legacy interface's usefulness in the
future. Without it, once more power profile handlers are added, it
will begin to regress even more. We are also not sure it is just Asus,
it is very likely there will be other breakages.
Currently, platform profile handlers are split in half between
low-power and quiet, and another third has additional options.
The legacy interface is still good for most cases, there is no need to
start moving non-specialized power managers such as ppd to it just
yet.
Antheas
Powered by blists - more mailing lists