[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAJZ5v0hWo=75tVGVZa5ARC3Nwtb5R_DR6s-V1X_e79S4E2RucQ@mail.gmail.com>
Date: Thu, 11 Dec 2025 20:11:15 +0100
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Alison Schofield <alison.schofield@...el.com>
Cc: "Rafael J. Wysocki" <rafael@...nel.org>, Linux ACPI <linux-acpi@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>, Linux PM <linux-pm@...r.kernel.org>,
Armin Wolf <w_armin@....de>, Hans de Goede <hansg@...nel.org>,
Dan Williams <dan.j.williams@...el.com>, Vishal Verma <vishal.l.verma@...el.com>,
Dave Jiang <dave.jiang@...el.com>, Ira Weiny <ira.weiny@...el.com>, nvdimm@...ts.linux.dev
Subject: Re: [RFT][PATCH v1 6/6] ACPI: NFIT: core: Convert the driver to a
platform one
On Thu, Dec 11, 2025 at 7:40 PM Alison Schofield
<alison.schofield@...el.com> wrote:
>
> On Thu, Dec 11, 2025 at 03:22:00PM +0100, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki <rafael.j.wysocki@...el.com>
> >
> > While binding drivers directly to struct acpi_device objects allows
> > basic functionality to be provided, at least in the majority of cases,
> > there are some problems with it, related to general consistency, sysfs
> > layout, power management operation ordering, and code cleanliness.
> >
> > Overall, it is better to bind drivers to platform devices than to their
> > ACPI companions, so convert the ACPI NFIT core driver to a platform one.
> >
> > While this is not expected to alter functionality, it changes sysfs
> > layout and so it will be visible to user space.
>
> Changes sysfs layout? That means it changes sysfs paths?
> Does it change paths defined in Documentation/ABI/testing/sysfs "What:"
No, it doesn't AFAICS.
It changes things like /sys/bus/platform/drivers/ for instance and the like.
Powered by blists - more mailing lists