From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Hans de Goede <hansg@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux ACPI <linux-acpi@vger.kernel.org>,
platform-driver-x86@vger.kernel.org,
Jeremy Soller <jeremy@system76.com>,
System76 Product Development <productdev@system76.com>
Subject: Re: [PATCH v1 2/2] platform/x86: system76: Convert ACPI driver to a platform one
Date: Wed, 18 Mar 2026 13:51:02 +0200 (EET) [thread overview]
Message-ID: <c674edfd-d4ef-c135-2497-0d13b2a29a8c@linux.intel.com> (raw)
In-Reply-To: <CAJZ5v0h4w1=1LGHR6J5=yu7MjV_z27e3GXOBq8yjH2uNSBxmBQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 6513 bytes --]
On Tue, 17 Mar 2026, Rafael J. Wysocki wrote:
> On Tue, Mar 17, 2026 at 6:48 PM Ilpo Järvinen
> <ilpo.jarvinen@linux.intel.com> wrote:
> >
> > On Thu, 12 Mar 2026, 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 System76 ACPI driver to a platform one.
> > >
> > > After this change, the subordinate hwmon, input and LED class devices
> > > will be registered under the platform device used for driver binding
> > > instead of its ACPI companion.
> > >
> > > While this is not expected to alter functionality, it changes sysfs
> > > layout and so it will be visible to user space.
> > >
> > > Link: https://lore.kernel.org/all/2396510.ElGaqSPkdT@rafael.j.wysocki/ [1]
> > > Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> > > ---
> > > drivers/platform/x86/system76_acpi.c | 52 +++++++++++++++-------------
> > > 1 file changed, 27 insertions(+), 25 deletions(-)
> > >
> > > diff --git a/drivers/platform/x86/system76_acpi.c b/drivers/platform/x86/system76_acpi.c
> > > index 35e294a55fa3..b3a4254156ae 100644
> > > --- a/drivers/platform/x86/system76_acpi.c
> > > +++ b/drivers/platform/x86/system76_acpi.c
> > > @@ -18,6 +18,7 @@
> > > #include <linux/leds.h>
> > > #include <linux/module.h>
> > > #include <linux/pci_ids.h>
> > > +#include <linux/platform_device.h>
> > > #include <linux/power_supply.h>
> > > #include <linux/sysfs.h>
> > > #include <linux/types.h>
> > > @@ -670,16 +671,19 @@ static void system76_notify(acpi_handle handle, u32 event, void *context)
> > > }
> > > }
> > >
> > > -// Add a System76 ACPI device
> > > -static int system76_add(struct acpi_device *acpi_dev)
> > > +// Probe a System76 platform device
> > > +static int system76_probe(struct platform_device *pdev)
> > > {
> > > + struct acpi_device *acpi_dev = ACPI_COMPANION(&pdev->dev);
> > > struct system76_data *data;
> > > int err;
> > >
> > > - data = devm_kzalloc(&acpi_dev->dev, sizeof(*data), GFP_KERNEL);
> > > + data = devm_kzalloc(&pdev->dev, sizeof(*data), GFP_KERNEL);
> > > if (!data)
> > > return -ENOMEM;
> > > - acpi_dev->driver_data = data;
> > > +
> > > + platform_set_drvdata(pdev, data);
> > > +
> > > data->acpi_dev = acpi_dev;
> > >
> > > // Some models do not run open EC firmware. Check for an ACPI method
> > > @@ -695,7 +699,7 @@ static int system76_add(struct acpi_device *acpi_dev)
> > > data->ap_led.brightness_set_blocking = ap_led_set;
> > > data->ap_led.max_brightness = 1;
> > > data->ap_led.default_trigger = "rfkill-none";
> > > - err = devm_led_classdev_register(&acpi_dev->dev, &data->ap_led);
> > > + err = devm_led_classdev_register(&pdev->dev, &data->ap_led);
> > > if (err)
> > > return err;
> > >
> > > @@ -739,19 +743,19 @@ static int system76_add(struct acpi_device *acpi_dev)
> > > }
> > >
> > > if (data->kbled_type != KBLED_NONE) {
> > > - err = devm_led_classdev_register(&acpi_dev->dev, &data->kb_led);
> > > + err = devm_led_classdev_register(&pdev->dev, &data->kb_led);
> > > if (err)
> > > return err;
> > > }
> > >
> > > - data->input = devm_input_allocate_device(&acpi_dev->dev);
> > > + data->input = devm_input_allocate_device(&pdev->dev);
> > > if (!data->input)
> > > return -ENOMEM;
> > >
> > > data->input->name = "System76 ACPI Hotkeys";
> > > data->input->phys = "system76_acpi/input0";
> > > data->input->id.bustype = BUS_HOST;
> > > - data->input->dev.parent = &acpi_dev->dev;
> > > + data->input->dev.parent = &pdev->dev;
> > > input_set_capability(data->input, EV_KEY, KEY_SCREENLOCK);
> > >
> > > err = input_register_device(data->input);
> > > @@ -767,7 +771,7 @@ static int system76_add(struct acpi_device *acpi_dev)
> > > if (err)
> > > goto error;
> > >
> > > - data->therm = devm_hwmon_device_register_with_info(&acpi_dev->dev,
> > > + data->therm = devm_hwmon_device_register_with_info(&pdev->dev,
> > > "system76_acpi", data, &thermal_chip_info, NULL);
> > > err = PTR_ERR_OR_ZERO(data->therm);
> > > if (err)
> > > @@ -795,14 +799,13 @@ static int system76_add(struct acpi_device *acpi_dev)
> > > return err;
> > > }
> > >
> > > -// Remove a System76 ACPI device
> > > -static void system76_remove(struct acpi_device *acpi_dev)
> > > +// Remove a System76 platform device
> > > +static void system76_remove(struct platform_device *pdev)
> > > {
> > > - struct system76_data *data;
> > > -
> > > - acpi_dev_remove_notify_handler(acpi_dev, ACPI_DEVICE_NOTIFY, system76_notify);
> > > + struct system76_data *data = platform_get_drvdata(pdev);
> > >
> > > - data = acpi_driver_data(acpi_dev);
> > > + acpi_dev_remove_notify_handler(ACPI_COMPANION(&pdev->dev),
> > > + ACPI_DEVICE_NOTIFY, system76_notify);
> > >
> > > if (data->has_open_ec) {
> > > system76_battery_exit();
> > > @@ -810,22 +813,21 @@ static void system76_remove(struct acpi_device *acpi_dev)
> > > kfree(data->ntmp);
> > > }
> > >
> > > - devm_led_classdev_unregister(&acpi_dev->dev, &data->ap_led);
> > > - devm_led_classdev_unregister(&acpi_dev->dev, &data->kb_led);
> > > + devm_led_classdev_unregister(&pdev->dev, &data->ap_led);
> > > + devm_led_classdev_unregister(&pdev->dev, &data->kb_led);
> >
> > With devm_* being used, why are these needed?
>
> I just preserved the existing pattern. I can remove it, but that
> would be a separate patch, wouldn't it?
Yes, to own patch.
--
i.
prev parent reply other threads:[~2026-03-18 11:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 14:09 [PATCH v1 0/2] platform/x86: system76: Bind to a platform device instead of an ACPI one Rafael J. Wysocki
2026-03-12 14:13 ` [PATCH v1 1/2] platform/x86: system76: Register ACPI notify handler directly Rafael J. Wysocki
2026-03-12 14:28 ` [PATCH v1 2/2] platform/x86: system76: Convert ACPI driver to a platform one Rafael J. Wysocki
2026-03-12 16:09 ` Jeremy Soller
2026-03-12 16:29 ` Rafael J. Wysocki
2026-03-17 17:48 ` Ilpo Järvinen
2026-03-17 19:04 ` Rafael J. Wysocki
2026-03-18 11:51 ` Ilpo Järvinen [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=c674edfd-d4ef-c135-2497-0d13b2a29a8c@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=hansg@kernel.org \
--cc=jeremy@system76.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=productdev@system76.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.