From: "Danilo Krummrich" <dakr@kernel.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Linux Driver Core Development" <driver-core@lists.linux.dev>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Linux ACPI" <linux-acpi@vger.kernel.org>,
"LKML" <linux-kernel@vger.kernel.org>,
"Michael Kelley" <mhklinux@outlook.com>,
"Hyper-V List" <linux-hyperv@vger.kernel.org>
Subject: Re: [PATCH v3] driver core/ACPI: Introduce companion_bus_register()
Date: Fri, 25 Sep 2026 13:34:51 +0200 [thread overview]
Message-ID: <DLOD6E6L35CN.KDDA9DEG9WP0@kernel.org> (raw)
In-Reply-To: <12985239.O9o76ZdvQC@rafael.j.wysocki>
On Fri Sep 25, 2026 at 11:23 AM CEST, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>
> The ACPI bus type does not allow drivers to be matched to devices, so
> the sysfs attributes related to drivers created for it are useless and
> their existence is confusing.
>
> Moreover, it is better to prevent drivers from being registered and
> looked up for a bus like that.
>
> To allow skipping the creation of those sysfs attributes and preventing
> driver registration and lookup for the ACPI bus type, introduce a
> "companion" bus type concept and add a special registration function
> for registering "companion" bus types, companion_bus_register().
>
> The "drivers" directory under the ACPI bus type is still needed because
> there are versions of systemd that depend on it [1].
Maybe we should also add a brief note above kset_create_and_add("drivers", ...)
why we retain the directory even if !use_drivers.
> Link: https://lore.kernel.org/linux-acpi/SN6PR02MB41575266A4580339E186E5D9D4812@SN6PR02MB4157.namprd02.prod.outlook.com/ [1]
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Reviewed-by: Danilo Krummrich <dakr@kernel.org>
next prev parent reply other threads:[~2026-09-25 11:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 9:23 Rafael J. Wysocki
2026-09-25 11:34 ` Danilo Krummrich [this message]
2026-09-25 15:31 ` Rafael J. Wysocki (Intel)
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=DLOD6E6L35CN.KDDA9DEG9WP0@kernel.org \
--to=dakr@kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhklinux@outlook.com \
--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
all inboxes | Powered by JetHome®