[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJZ5v0jpSN_Tq6D3OrRj5KDuXwqVuzcwyNXwEuL90fr=juH48g@mail.gmail.com>
Date: Tue, 25 Feb 2025 21:22:21 +0100
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Antheas Kapenekakis <lkml@...heas.dev>
Cc: Armin Wolf <W_Armin@....de>, 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
On Tue, Feb 25, 2025 at 7:07 AM Antheas Kapenekakis <lkml@...heas.dev> wrote:
>
> Yes, making asus-wmi use low-power is indeed the easiest solution, but
> if I thought it was good enough, I would have done that already as a
> downstream consumer of the kernel.
>
> I just want to be done with this once and for all, so I spent an extra
> hour today solving this in a cleaner way.
What about adding "quiet" as a "hidden choice" to amd-pmf such that it
would allow the test_bit(*bit, handler->choices) check in
_store_class_profile() to pass, but it would not cause this "choice"
to become visible in the new I/F (or when amd-pmf becomes the only
platform-profile driver) and it would be aliased to "low-power"
internally?
Powered by blists - more mailing lists