All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis Benato <denis.benato@linux.dev>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
	"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,
	"Corentin Chary" <corentin.chary@gmail.com>,
	"Luke D. Jones" <luke@ljones.dev>,
	"João Paulo Rechi Vita" <jprvita@gmail.com>
Subject: Re: [PATCH v1 2/4] platform/x86: asus-laptop: Convert ACPI driver to a platform one
Date: Tue, 31 Mar 2026 21:19:14 +0200	[thread overview]
Message-ID: <7dcebac5-ef4a-4ddb-a276-82ffdb4796c4@linux.dev> (raw)
In-Reply-To: <d42eed14-b6b1-b8f4-b73a-6033162e79e7@linux.intel.com>


On 3/31/26 10:14, Ilpo Järvinen wrote:
> On Sat, 28 Feb 2026, Denis Benato wrote:
>> On 2/28/26 16:11, 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 Asus laptop ACPI 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.
>> Alright I will take a look if asus-linux software is affected and act accordingly.
>> How much time do I have?
>>
>> Thanks. 
> Hi Denis,
>
> Has there been some progress with this check?
Hi!

I quickly looked at it and I think there shouldn't be any problem.

Worst case scenario I update the criteria udev uses to find certain
things but it shouldn't be necessary (or at least I can't find a problematic spot).

Thanks,
Denis
> --
>  i.
>
>>> Link: https://lore.kernel.org/all/2396510.ElGaqSPkdT@rafael.j.wysocki/ [1]
>>> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>> Reviewed-by: Denis Benato <denis.benato@linux.dev>
>>> ---
>>>  drivers/platform/x86/asus-laptop.c | 35 +++++++++++++++---------------
>>>  1 file changed, 18 insertions(+), 17 deletions(-)
>>>
>>> diff --git a/drivers/platform/x86/asus-laptop.c b/drivers/platform/x86/asus-laptop.c
>>> index c927665dfa96..dbbb6292cd11 100644
>>> --- a/drivers/platform/x86/asus-laptop.c
>>> +++ b/drivers/platform/x86/asus-laptop.c
>>> @@ -1824,8 +1824,9 @@ static void asus_dmi_check(void)
>>>  
>>>  static bool asus_device_present;
>>>  
>>> -static int asus_acpi_add(struct acpi_device *device)
>>> +static int asus_acpi_probe(struct platform_device *pdev)
>>>  {
>>> +	struct acpi_device *device = ACPI_COMPANION(&pdev->dev);
>>>  	struct asus_laptop *asus;
>>>  	int result;
>>>  
>>> @@ -1837,7 +1838,6 @@ static int asus_acpi_add(struct acpi_device *device)
>>>  	asus->handle = device->handle;
>>>  	strscpy(acpi_device_name(device), ASUS_LAPTOP_DEVICE_NAME);
>>>  	strscpy(acpi_device_class(device), ASUS_LAPTOP_CLASS);
>>> -	device->driver_data = asus;
>>>  	asus->device = device;
>>>  
>>>  	asus_dmi_check();
>>> @@ -1846,6 +1846,8 @@ static int asus_acpi_add(struct acpi_device *device)
>>>  	if (result)
>>>  		goto fail_platform;
>>>  
>>> +	platform_set_drvdata(pdev, asus);
>>> +
>>>  	/*
>>>  	 * Need platform type detection first, then the platform
>>>  	 * device.  It is used as a parent for the sub-devices below.
>>> @@ -1907,11 +1909,12 @@ static int asus_acpi_add(struct acpi_device *device)
>>>  	return result;
>>>  }
>>>  
>>> -static void asus_acpi_remove(struct acpi_device *device)
>>> +static void asus_acpi_remove(struct platform_device *pdev)
>>>  {
>>> -	struct asus_laptop *asus = acpi_driver_data(device);
>>> +	struct asus_laptop *asus = platform_get_drvdata(pdev);
>>>  
>>> -	acpi_dev_remove_notify_handler(device, ACPI_DEVICE_NOTIFY, asus_acpi_notify);
>>> +	acpi_dev_remove_notify_handler(asus->device, ACPI_DEVICE_NOTIFY,
>>> +				       asus_acpi_notify);
>>>  	asus_backlight_exit(asus);
>>>  	asus_rfkill_exit(asus);
>>>  	asus_led_exit(asus);
>>> @@ -1930,15 +1933,13 @@ static const struct acpi_device_id asus_device_ids[] = {
>>>  };
>>>  MODULE_DEVICE_TABLE(acpi, asus_device_ids);
>>>  
>>> -static struct acpi_driver asus_acpi_driver = {
>>> -	.name = ASUS_LAPTOP_NAME,
>>> -	.class = ASUS_LAPTOP_CLASS,
>>> -	.ids = asus_device_ids,
>>> -	.flags = ACPI_DRIVER_ALL_NOTIFY_EVENTS,
>>> -	.ops = {
>>> -		.add = asus_acpi_add,
>>> -		.remove = asus_acpi_remove,
>>> -		},
>>> +static struct platform_driver asus_acpi_driver = {
>>> +	.probe = asus_acpi_probe,
>>> +	.remove = asus_acpi_remove,
>>> +	.driver = {
>>> +		.name = ASUS_LAPTOP_NAME,
>>> +		.acpi_match_table = asus_device_ids,
>>> +	},
>>>  };
>>>  
>>>  static int __init asus_laptop_init(void)
>>> @@ -1949,7 +1950,7 @@ static int __init asus_laptop_init(void)
>>>  	if (result < 0)
>>>  		return result;
>>>  
>>> -	result = acpi_bus_register_driver(&asus_acpi_driver);
>>> +	result = platform_driver_register(&asus_acpi_driver);
>>>  	if (result < 0)
>>>  		goto fail_acpi_driver;
>>>  	if (!asus_device_present) {
>>> @@ -1959,7 +1960,7 @@ static int __init asus_laptop_init(void)
>>>  	return 0;
>>>  
>>>  fail_no_device:
>>> -	acpi_bus_unregister_driver(&asus_acpi_driver);
>>> +	platform_driver_unregister(&asus_acpi_driver);
>>>  fail_acpi_driver:
>>>  	platform_driver_unregister(&platform_driver);
>>>  	return result;
>>> @@ -1967,7 +1968,7 @@ static int __init asus_laptop_init(void)
>>>  
>>>  static void __exit asus_laptop_exit(void)
>>>  {
>>> -	acpi_bus_unregister_driver(&asus_acpi_driver);
>>> +	platform_driver_unregister(&asus_acpi_driver);
>>>  	platform_driver_unregister(&platform_driver);
>>>  }
>>>  

  reply	other threads:[~2026-03-31 19:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-28 15:09 [PATCH v1 0/4] platform/x86: asus: Bind drivers to platform devices instead of ACPI ones Rafael J. Wysocki
2026-02-28 15:10 ` [PATCH v1 1/4] platform/x86: asus-laptop: Register ACPI notify handler directly Rafael J. Wysocki
2026-02-28 16:59   ` Denis Benato
2026-02-28 15:11 ` [PATCH v1 2/4] platform/x86: asus-laptop: Convert ACPI driver to a platform one Rafael J. Wysocki
2026-02-28 17:01   ` Denis Benato
2026-03-01 13:08     ` Rafael J. Wysocki
2026-03-02 11:21     ` Ilpo Järvinen
2026-03-31  8:14     ` Ilpo Järvinen
2026-03-31 19:19       ` Denis Benato [this message]
2026-02-28 15:12 ` [PATCH v1 3/4] platform/x86: asus-wireless: Register ACPI notify handler directly Rafael J. Wysocki
2026-02-28 17:02   ` Denis Benato
2026-02-28 15:12 ` [PATCH v1 4/4] platform/x86: asus-wireless: Convert ACPI driver to a platform one Rafael J. Wysocki
2026-02-28 17:02   ` Denis Benato
2026-04-07  9:49   ` 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=7dcebac5-ef4a-4ddb-a276-82ffdb4796c4@linux.dev \
    --to=denis.benato@linux.dev \
    --cc=corentin.chary@gmail.com \
    --cc=hansg@kernel.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=jprvita@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luke@ljones.dev \
    --cc=platform-driver-x86@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 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.