From: "Rafael J. Wysocki" <rafael@kernel.org>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
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: [PATCH v1 0/2] platform/x86: system76: Bind to a platform device instead of an ACPI one
Date: Thu, 12 Mar 2026 15:09:26 +0100 [thread overview]
Message-ID: <2841136.mvXUDI8C0e@rafael.j.wysocki> (raw)
Hi All,
This series is part of a larger effort to switch over all drivers using
the struct acpi_driver interface to the more common struct platform_driver
interface and eliminate the former. The background is explained in
Documentation/driver-api/acpi/acpi-drivers.rst and in the changelog of
the patch that introduced the above document:
https://lore.kernel.org/all/2396510.ElGaqSPkdT@rafael.j.wysocki/
The bottom line is that the kernel would be better off without struct
acpi_driver and so it is better to get rid of it.
This series carries out driver conversion of the platform x86 System76
ACPI driver.
Patch [1/2] updates the driver to install an ACPI notify handler by itself
instead of using the .notify() callback from struct acpi_driver, which is
requisite for the driver conversion.
Patch [2/2] converts the driver to using struct platform_driver for device
binding.
Thanks!
next reply other threads:[~2026-03-12 14:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 14:09 Rafael J. Wysocki [this message]
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
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=2841136.mvXUDI8C0e@rafael.j.wysocki \
--to=rafael@kernel.org \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--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 \
/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