From: "Arnd Bergmann" <arnd@arndb.de>
To: "Armin Wolf" <W_Armin@gmx.de>,
"Alexandre Ghiti" <alexghiti@rivosinc.com>,
"Rafael J . Wysocki" <rafael@kernel.org>,
"Len Brown" <lenb@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Mario Limonciello" <mario.limonciello@amd.com>,
"Mark Pearson" <mpearson-lenovo@squebb.ca>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH] drivers: acpi: Fix platform profile driver on !acpi platforms
Date: Fri, 23 May 2025 12:44:47 +0200 [thread overview]
Message-ID: <9fd12267-bfba-4f94-a132-b20c5be601b0@app.fastmail.com> (raw)
In-Reply-To: <91458376-dfc7-46fc-8523-aa176907d703@gmx.de>
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
next prev parent reply other threads:[~2025-05-23 10:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 14:13 [PATCH] drivers: acpi: Fix platform profile driver on !acpi platforms Alexandre Ghiti
2025-05-22 14:18 ` Arnd Bergmann
2025-05-22 14:20 ` Mark Pearson
2025-05-22 20:04 ` Armin Wolf
2025-05-23 10:11 ` Alexandre Ghiti
2025-05-23 10:50 ` Rafael J. Wysocki
2025-05-23 14:46 ` Rafael J. Wysocki
2025-05-23 20:01 ` Alexandre Ghiti
2025-05-23 10:44 ` Arnd Bergmann [this message]
2025-06-10 16:28 ` patchwork-bot+linux-riscv
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=9fd12267-bfba-4f94-a132-b20c5be601b0@app.fastmail.com \
--to=arnd@arndb.de \
--cc=W_Armin@gmx.de \
--cc=alexghiti@rivosinc.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mario.limonciello@amd.com \
--cc=mpearson-lenovo@squebb.ca \
--cc=rafael@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