NVDIMM Device and Persistent Memory development
 help / color / mirror / Atom feed
From: "Wilczynski, Michal" <michal.wilczynski@intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: <linux-acpi@vger.kernel.org>, <dan.j.williams@intel.com>,
	<vishal.l.verma@intel.com>, <lenb@kernel.org>,
	<dave.jiang@intel.com>, <ira.weiny@intel.com>,
	<rui.zhang@intel.com>, <linux-kernel@vger.kernel.org>,
	<nvdimm@lists.linux.dev>,
	"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>
Subject: Re: [PATCH v5 05/10] acpi/battery: Move handler installing logic to driver
Date: Fri, 30 Jun 2023 11:48:51 +0200	[thread overview]
Message-ID: <f875638a-ea61-04cc-7621-974d4bd2dd34@intel.com> (raw)
In-Reply-To: <CAJZ5v0i1-7p-V0nFHoNWHDXRZ-xvVwTXJKM387PTP1d4k7Wrdg@mail.gmail.com>



On 6/29/2023 6:05 PM, Rafael J. Wysocki wrote:
> On Fri, Jun 16, 2023 at 6:51 PM Michal Wilczynski
> <michal.wilczynski@intel.com> wrote:
>> Currently logic for installing notifications from ACPI devices is
>> implemented using notify callback in struct acpi_driver. Preparations
>> are being made to replace acpi_driver with more generic struct
>> platform_driver, which doesn't contain notify callback. Furthermore
>> as of now handlers are being called indirectly through
>> acpi_notify_device(), which decreases performance.
>>
>> Call acpi_dev_install_notify_handler() at the end of .add() callback.
>> Call acpi_dev_remove_notify_handler() at the beginning of .remove()
>> callback. Change arguments passed to the notify function to match with
>> what's required by acpi_install_notify_handler(). Remove .notify
>> callback initialization in acpi_driver.
>>
>> While at it, fix lack of whitespaces in .remove() callback.
>>
>> Suggested-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>> Signed-off-by: Michal Wilczynski <michal.wilczynski@intel.com>
>> ---
>>  drivers/acpi/battery.c | 30 ++++++++++++++++++++++++------
>>  1 file changed, 24 insertions(+), 6 deletions(-)
>>
>> diff --git a/drivers/acpi/battery.c b/drivers/acpi/battery.c
>> index 9c67ed02d797..6337e7b1f6e1 100644
>> --- a/drivers/acpi/battery.c
>> +++ b/drivers/acpi/battery.c
>> @@ -1034,11 +1034,14 @@ static void acpi_battery_refresh(struct acpi_battery *battery)
>>  }
>>
>>  /* Driver Interface */
>> -static void acpi_battery_notify(struct acpi_device *device, u32 event)
>> +static void acpi_battery_notify(acpi_handle handle, u32 event, void *data)
>>  {
>> -       struct acpi_battery *battery = acpi_driver_data(device);
>> +       struct acpi_device *device = data;
>> +       struct acpi_battery *battery;
>>         struct power_supply *old;
>>
>> +       battery = acpi_driver_data(device);
>> +
>>         if (!battery)
>>                 return;
>>         old = battery->bat;
>> @@ -1212,13 +1215,23 @@ static int acpi_battery_add(struct acpi_device *device)
>>
>>         device_init_wakeup(&device->dev, 1);
>>
>> -       return result;
>> +       result = acpi_dev_install_notify_handler(device,
>> +                                                ACPI_ALL_NOTIFY,
>> +                                                acpi_battery_notify);
>> +       if (result)
>> +               goto fail_deinit_wakup_and_unregister;
> You could call the label "fail_pm", for example, which would be more
> concise and so slightly easier to follow, without any loss of clarity
> AFAICS.

Sure

>
>> +
>> +       return 0;
>>
>> +fail_deinit_wakup_and_unregister:
>> +       device_init_wakeup(&device->dev, 0);
>> +       unregister_pm_notifier(&battery->pm_nb);
>>  fail:
>>         sysfs_remove_battery(battery);
>>         mutex_destroy(&battery->lock);
>>         mutex_destroy(&battery->sysfs_lock);
>>         kfree(battery);
>> +
>>         return result;
>>  }
>>
>> @@ -1228,10 +1241,17 @@ static void acpi_battery_remove(struct acpi_device *device)
>>
>>         if (!device || !acpi_driver_data(device))
>>                 return;
>> -       device_init_wakeup(&device->dev, 0);
>> +
>>         battery = acpi_driver_data(device);
>> +
>> +       acpi_dev_remove_notify_handler(device,
>> +                                      ACPI_ALL_NOTIFY,
>> +                                      acpi_battery_notify);
>> +
>> +       device_init_wakeup(&device->dev, 0);
>>         unregister_pm_notifier(&battery->pm_nb);
>>         sysfs_remove_battery(battery);
>> +
>>         mutex_destroy(&battery->lock);
>>         mutex_destroy(&battery->sysfs_lock);
>>         kfree(battery);
>> @@ -1264,11 +1284,9 @@ static struct acpi_driver acpi_battery_driver = {
>>         .name = "battery",
>>         .class = ACPI_BATTERY_CLASS,
>>         .ids = battery_device_ids,
>> -       .flags = ACPI_DRIVER_ALL_NOTIFY_EVENTS,
>>         .ops = {
>>                 .add = acpi_battery_add,
>>                 .remove = acpi_battery_remove,
>> -               .notify = acpi_battery_notify,
>>                 },
>>         .drv.pm = &acpi_battery_pm,
>>  };
>> --
>> 2.41.0
>>


  reply	other threads:[~2023-06-30  9:49 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-16 16:50 [PATCH v5 00/10] Remove .notify callback in acpi_device_ops Michal Wilczynski
2023-06-16 16:50 ` [PATCH v5 01/10] acpi/bus: Introduce wrappers for ACPICA event handler install/remove Michal Wilczynski
2023-06-16 16:50 ` [PATCH v5 02/10] acpi/bus: Set driver_data to NULL every time .add() fails Michal Wilczynski
2023-06-16 16:50 ` [PATCH v5 03/10] acpi/ac: Move handler installing logic to driver Michal Wilczynski
2023-06-29 15:55   ` Rafael J. Wysocki
2023-06-30  9:39     ` Wilczynski, Michal
2023-06-30  9:41       ` Rafael J. Wysocki
2023-06-30  9:45         ` Rafael J. Wysocki
2023-06-16 16:50 ` [PATCH v5 04/10] acpi/video: " Michal Wilczynski
2023-06-29 15:58   ` Rafael J. Wysocki
2023-06-30  9:42     ` Wilczynski, Michal
2023-06-16 16:50 ` [PATCH v5 05/10] acpi/battery: " Michal Wilczynski
2023-06-29 16:05   ` Rafael J. Wysocki
2023-06-30  9:48     ` Wilczynski, Michal [this message]
2023-06-16 16:50 ` [PATCH v5 06/10] acpi/hed: " Michal Wilczynski
2023-06-16 16:50 ` [PATCH v5 07/10] acpi/nfit: Move acpi_nfit_notify() before acpi_nfit_add() Michal Wilczynski
2023-06-29 16:06   ` Rafael J. Wysocki
2023-06-30  9:48     ` Wilczynski, Michal
2023-06-30 10:52       ` Rafael J. Wysocki
2023-06-16 16:50 ` [PATCH v5 08/10] acpi/nfit: Improve terminator line in acpi_nfit_ids Michal Wilczynski
2023-06-29 16:14   ` Rafael J. Wysocki
2023-06-30  9:52     ` Wilczynski, Michal
2023-06-30 11:04       ` Rafael J. Wysocki
2023-06-30 11:13         ` Rafael J. Wysocki
2023-06-30 12:02           ` Wilczynski, Michal
2023-06-29 20:51   ` Dan Williams
2023-06-30 10:10     ` Wilczynski, Michal
2023-06-16 16:50 ` [PATCH v5 09/10] acpi/nfit: Move handler installing logic to driver Michal Wilczynski
2023-06-29 16:18   ` Rafael J. Wysocki
2023-06-30  9:55     ` Wilczynski, Michal
2023-06-30 11:00       ` Rafael J. Wysocki
2023-06-29 20:54   ` Dan Williams
2023-06-30 16:56     ` Wilczynski, Michal
2023-06-30 17:19       ` Dan Williams
2023-06-30 17:26         ` Wilczynski, Michal
2023-06-16 16:50 ` [PATCH v5 10/10] acpi/thermal: " Michal Wilczynski

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=f875638a-ea61-04cc-7621-974d4bd2dd34@intel.com \
    --to=michal.wilczynski@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=ira.weiny@intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nvdimm@lists.linux.dev \
    --cc=rafael.j.wysocki@intel.com \
    --cc=rafael@kernel.org \
    --cc=rui.zhang@intel.com \
    --cc=vishal.l.verma@intel.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