[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <9fd12267-bfba-4f94-a132-b20c5be601b0@app.fastmail.com>
Date: Fri, 23 May 2025 12:44:47 +0200
From: "Arnd Bergmann" <arnd@...db.de>
To: "Armin Wolf" <W_Armin@....de>, "Alexandre Ghiti" <alexghiti@...osinc.com>,
"Rafael J . Wysocki" <rafael@...nel.org>, "Len Brown" <lenb@...nel.org>,
Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>,
"Mario Limonciello" <mario.limonciello@....com>,
"Mark Pearson" <mpearson-lenovo@...ebb.ca>, linux-acpi@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-riscv@...ts.infradead.org
Subject: Re: [PATCH] drivers: acpi: Fix platform profile driver on !acpi platforms
On Thu, May 22, 2025, at 22:04, Armin Wolf wrote:
> Am 22.05.25 um 16:13 schrieb Alexandre Ghiti:
>
> I already submitted a patch for this problem (see
> https://lore.kernel.org/linux-acpi/a6d92cdd-4dc3-4080-9ed9-5b1f02f247e0@gmx.de/T/)
> that only disables the legacy sysfs interface while keeping the
> class-based interface functional
> as it does not depend on ACPI at all.
Just for my understanding: what users of the platform profile are
there that work without ACPI? I see that CONFIG_ACPI_PLATFORM_PROFILE
is hidden under CONFIG_ACPI and cannot be selected in configurations
that turn off ACPI, so if that is an intended usecase, there is
probably still something wrong in Kconfig.
Should the driver be moved out of drivers/acpi to drivers/platform
in order to let non-ACPI platforms use it?
Arnd
Powered by blists - more mailing lists