From: "Danilo Krummrich" <dakr@kernel.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Linux ACPI" <linux-acpi@vger.kernel.org>,
"LKML" <linux-kernel@vger.kernel.org>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Bjorn Helgaas" <helgaas@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Hans de Goede" <hansg@kernel.org>,
"Linux Documentation" <linux-doc@vger.kernel.org>,
"Mika Westerberg" <mika.westerberg@linux.intel.com>,
"Zhang Rui" <rui.zhang@intel.com>, "Armin Wolf" <w_armin@gmx.de>,
"Ilpo Jarvinen" <ilpo.jarvinen@linux.intel.com>,
"Mario Limonciello" <mario.limonciello@amd.com>,
"Randy Dunlap" <rdunlap@infradead.org>
Subject: Re: [PATCH v2] ACPI: Documentation: driver-api: Disapprove of using ACPI drivers
Date: Tue, 06 Jan 2026 15:01:34 +0100 [thread overview]
Message-ID: <DFHK7ZS7H7LJ.1POCUDPSLC3CP@kernel.org> (raw)
In-Reply-To: <2396510.ElGaqSPkdT@rafael.j.wysocki>
On Tue Jan 6, 2026 at 1:27 PM CET, Rafael J. Wysocki wrote:
> +This means that it really should never be necessary to bind a driver directly to
> +an ACPI device node because there is a "proper" device object representing the
> +corresponding piece of hardware that can be bound to by a "proper" driver using
> +the given ACPI device node as the device's ACPI companion. Thus, in principle,
> +there is no reason to use ACPI drivers and if they all were replaced with other
> +driver types (for example, platform drivers), some code could be dropped and
> +some complexity would go away.
I think it would be good to explicitly encourage people to convert existing
drivers (maybe even list some of those) and rephrase the last sentence to list
what exact infrastructure, complexity, etc. can go away once that happened.
I think this would make it more likely to receive some contributions towards
this goal.
next prev parent reply other threads:[~2026-01-06 14:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 12:27 [PATCH v2] ACPI: Documentation: driver-api: Disapprove of using ACPI drivers Rafael J. Wysocki
2026-01-06 14:01 ` Danilo Krummrich [this message]
2026-01-07 12:14 ` Rafael J. Wysocki
2026-01-07 12:21 ` Danilo Krummrich
2026-01-27 18:50 ` Rafael J. Wysocki
2026-01-06 15:47 ` Mario Limonciello (AMD) (kernel.org)
2026-01-07 12:22 ` Rafael J. Wysocki
2026-01-13 21:58 ` Mario Limonciello (AMD) (kernel.org)
2026-01-13 22:02 ` Rafael J. Wysocki
2026-01-06 16:16 ` Randy Dunlap
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=DFHK7ZS7H7LJ.1POCUDPSLC3CP@kernel.org \
--to=dakr@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hansg@kernel.org \
--cc=helgaas@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael@kernel.org \
--cc=rdunlap@infradead.org \
--cc=rui.zhang@intel.com \
--cc=w_armin@gmx.de \
/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