mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Jaroslav Pulchart <jaroslav.pulchart@gooddata.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux ACPI <linux-acpi@vger.kernel.org>,
	linux-hwmon@vger.kernel.org
Subject: Re: [PATCH v1 3/3] hwmon: (acpi_power_meter) Convert ACPI driver to a platform one
Date: Sun, 1 Mar 2026 16:01:28 -0800	[thread overview]
Message-ID: <b93aae74-6b66-4597-9eda-71e2363f7bba@roeck-us.net> (raw)
In-Reply-To: <1952740.tdWV9SEqCh@rafael.j.wysocki>

On Sun, Mar 01, 2026 at 02:18:49PM +0100, Rafael J. Wysocki wrote:
> From: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
> 
> In all cases in which a struct acpi_driver is used for binding a driver
> to an ACPI device object, a corresponding platform device is created by
> the ACPI core and that device is regarded as a proper representation of
> underlying hardware.  Accordingly, a struct platform_driver should be
> used by driver code to bind to that device.  There are multiple reasons
> why drivers should not bind directly to ACPI device objects [1].
> 
> Overall, it is better to bind drivers to platform devices than to their
> ACPI companions, so convert the hwmon ACPI power meter driver to a
> platform one.
> 
> After this change, the subordinate hwmon device will be registered
> under the platform device representing the ACPI power meter, sysfs
> notifications will trigger on that device, and diagnostic messages
> will be printed relative to it instead of its ACPI companion.
> 
> Link: https://lore.kernel.org/all/2396510.ElGaqSPkdT@rafael.j.wysocki/ [1]
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

Thanks a lot for this cleanup work.

I decided to apply the entire series right away to hopefully get some test
feedback before the next commit window.

Thanks,
Guenter

      reply	other threads:[~2026-03-02  0:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-01 13:16 [PATCH v1 0/3] hwmon: (acpi_power_meter) Bind the driver to a platform device Rafael J. Wysocki
2026-03-01 13:17 ` [PATCH v1 1/3] hwmon: (acpi_power_meter) Drop redundant checks from three functions Rafael J. Wysocki
2026-03-01 23:53   ` Guenter Roeck
2026-03-01 13:18 ` [PATCH v1 2/3] hwmon: (acpi_power_meter) Register ACPI notify handler directly Rafael J. Wysocki
2026-03-01 23:54   ` Guenter Roeck
2026-03-01 13:18 ` [PATCH v1 3/3] hwmon: (acpi_power_meter) Convert ACPI driver to a platform one Rafael J. Wysocki
2026-03-02  0:01   ` Guenter Roeck [this message]

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=b93aae74-6b66-4597-9eda-71e2363f7bba@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=jaroslav.pulchart@gooddata.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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®