From: "Wilczynski, Michal" <michal.wilczynski@intel.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: Jonathan Woithe <jwoithe@just42.net>,
Hans de Goede <hdegoede@redhat.com>,
Mark Gross <markgross@kernel.org>,
<platform-driver-x86@vger.kernel.org>,
<linux-acpi@vger.kernel.org>, <rafael@kernel.org>
Subject: Re: [PATCH v4 21/35] platform/x86/fujitsu-laptop: Move handler installing logic to driver
Date: Fri, 2 Jun 2023 15:49:40 +0200 [thread overview]
Message-ID: <7fcb9041-9a78-ac9e-6a23-47bbccdfd30a@intel.com> (raw)
In-Reply-To: <f0e58bde-c1e6-872e-3879-ab3c2dadfd7@linux.intel.com>
On 6/2/2023 3:30 PM, Ilpo Järvinen wrote:
> On Thu, 1 Jun 2023, Michal Wilczynski 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_device_install_event_handler() at the end of .add() callback.
>> Call acpi_device_remove_event_handler() at the beginning of .remove()
>> callback. Change arguments passed to the notify callback to match with
>> what's required by acpi_device_install_event_handler().
>>
>> Signed-off-by: Michal Wilczynski <michal.wilczynski@intel.com>
>> ---
>> drivers/platform/x86/fujitsu-laptop.c | 86 +++++++++++++++++----------
>> 1 file changed, 54 insertions(+), 32 deletions(-)
>>
>> diff --git a/drivers/platform/x86/fujitsu-laptop.c b/drivers/platform/x86/fujitsu-laptop.c
>> index 085e044e888e..001333edba9f 100644
>> --- a/drivers/platform/x86/fujitsu-laptop.c
>> +++ b/drivers/platform/x86/fujitsu-laptop.c
>> @@ -136,6 +136,8 @@ struct fujitsu_laptop {
>>
>> static struct acpi_device *fext;
>>
>> +static void acpi_fujitsu_laptop_notify(acpi_handle handle, u32 event, void *data);
>> +
>> /* Fujitsu ACPI interface function */
>>
>> static int call_fext_func(struct acpi_device *device,
>> @@ -382,6 +384,37 @@ static int fujitsu_backlight_register(struct acpi_device *device)
>> return 0;
>> }
>>
>> +static void acpi_fujitsu_bl_notify(acpi_handle handle, u32 event, void *data)
>> +{
>> + struct acpi_device *device = data;
>> + struct fujitsu_bl *priv;
>> + int oldb, newb;
>> +
>> + priv = acpi_driver_data(device);
>> +
>> + if (event != ACPI_FUJITSU_NOTIFY_CODE) {
>> + acpi_handle_info(device->handle, "unsupported event [0x%x]\n",
>> + event);
>> + sparse_keymap_report_event(priv->input, -1, 1, true);
>> + return;
>> + }
>> +
>> + oldb = priv->brightness_level;
>> + get_lcd_level(device);
>> + newb = priv->brightness_level;
>> +
>> + acpi_handle_debug(device->handle,
>> + "brightness button event [%i -> %i]\n", oldb, newb);
>> +
>> + if (oldb == newb)
>> + return;
>> +
>> + if (!disable_brightness_adjust)
>> + set_lcd_level(device, newb);
>> +
>> + sparse_keymap_report_event(priv->input, oldb < newb, 1, true);
>> +}
>> +
>> static int acpi_fujitsu_bl_add(struct acpi_device *device)
>> {
>> struct fujitsu_bl *priv;
>> @@ -410,37 +443,17 @@ static int acpi_fujitsu_bl_add(struct acpi_device *device)
>> if (ret)
>> return ret;
>>
>> - return fujitsu_backlight_register(device);
>> -}
>> + ret = fujitsu_backlight_register(device);
>> + if (ret)
>> + return ret;
>>
>> -/* Brightness notify */
>> + return acpi_device_install_event_handler(device, ACPI_DEVICE_NOTIFY,
>> + acpi_fujitsu_bl_notify);
>> +}
>>
>> -static void acpi_fujitsu_bl_notify(struct acpi_device *device, u32 event)
>> +static void acpi_fujitsu_bl_remove(struct acpi_device *device)
>> {
>> - struct fujitsu_bl *priv = acpi_driver_data(device);
>> - int oldb, newb;
>> -
>> - if (event != ACPI_FUJITSU_NOTIFY_CODE) {
>> - acpi_handle_info(device->handle, "unsupported event [0x%x]\n",
>> - event);
>> - sparse_keymap_report_event(priv->input, -1, 1, true);
>> - return;
>> - }
>> -
>> - oldb = priv->brightness_level;
>> - get_lcd_level(device);
>> - newb = priv->brightness_level;
>> -
>> - acpi_handle_debug(device->handle,
>> - "brightness button event [%i -> %i]\n", oldb, newb);
>> -
>> - if (oldb == newb)
>> - return;
>> -
>> - if (!disable_brightness_adjust)
>> - set_lcd_level(device, newb);
>> -
>> - sparse_keymap_report_event(priv->input, oldb < newb, 1, true);
>> + acpi_device_remove_event_handler(device, ACPI_DEVICE_NOTIFY, acpi_fujitsu_bl_notify);
> Please move the function in a separate (no function changes intended)
> patch to keep this patch on point.
Sure I can do that, however this moving around make sense in context of this patch as
it's necessary to compile with the new event installation method.
>
>> }
>>
>> /* ACPI device for hotkey handling */
>> @@ -839,6 +852,11 @@ static int acpi_fujitsu_laptop_add(struct acpi_device *device)
>> if (ret)
>> goto err_free_fifo;
>>
>> + ret = acpi_device_install_event_handler(device, ACPI_DEVICE_NOTIFY,
>> + acpi_fujitsu_laptop_notify);
>> + if (ret)
>> + goto err_free_fifo;
> Here too, fujitsu_laptop_platform_remove() is necessary, goto + put it
> into the rollback path.
>
> Please go through your patches with these rollback corrections in mind,
> I'll skip looking through the rest of platform/x86 patches until you've
> done that.
Will do that,
Thank you for your time !
>
>> +
>> return 0;
>>
>> err_free_fifo:
>> @@ -851,6 +869,8 @@ static void acpi_fujitsu_laptop_remove(struct acpi_device *device)
>> {
>> struct fujitsu_laptop *priv = acpi_driver_data(device);
>>
>> + acpi_device_remove_event_handler(device, ACPI_DEVICE_NOTIFY, acpi_fujitsu_laptop_notify);
>> +
>> fujitsu_laptop_platform_remove(device);
>>
>> kfifo_free(&priv->fifo);
>
next prev parent reply other threads:[~2023-06-02 13:49 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 13:17 [PATCH v4 02/35] acpi/ac: Move handler installing logic to driver Michal Wilczynski
2023-06-01 13:17 ` [PATCH v4 03/35] acpi/video: " Michal Wilczynski
2023-06-01 13:17 ` [PATCH v4 04/35] acpi/battery: " Michal Wilczynski
2023-06-01 13:17 ` [PATCH v4 05/35] acpi/button: " Michal Wilczynski
2023-06-01 13:17 ` [PATCH v4 06/35] acpi/hed: " Michal Wilczynski
2023-06-01 13:17 ` [PATCH v4 07/35] acpi/nfit: " Michal Wilczynski
2023-06-01 13:17 ` [PATCH v4 08/35] acpi/thermal: " Michal Wilczynski
2023-06-01 13:17 ` [PATCH v4 09/35] acpi/tiny-power-button: " Michal Wilczynski
2023-06-01 13:17 ` [PATCH v4 10/35] hwmon/acpi_power_meter: " Michal Wilczynski
2023-06-01 13:51 ` Guenter Roeck
2023-06-01 13:17 ` [PATCH v4 11/35] iio/acpi-als: " Michal Wilczynski
2023-06-04 10:53 ` Jonathan Cameron
2023-06-01 13:17 ` [PATCH v4 12/35] platform/chromeos_tbmc: " Michal Wilczynski
2023-06-01 13:17 ` [PATCH v4 13/35] platform/wilco_ec: " Michal Wilczynski
2023-06-01 13:17 ` [PATCH v4 14/35] platform/surface/button: " Michal Wilczynski
2023-06-01 13:17 ` [PATCH v4 15/35] platform/x86/acer-wireless: " Michal Wilczynski
2023-06-01 13:17 ` [PATCH v4 16/35] platform/x86/asus-laptop: " Michal Wilczynski
2023-06-01 13:17 ` [PATCH v4 17/35] platform/x86/asus-wireless: " Michal Wilczynski
2023-06-02 13:09 ` Ilpo Järvinen
2023-06-02 13:16 ` Wilczynski, Michal
2023-06-01 13:17 ` [PATCH v4 18/35] platform/x86/classmate-laptop: " Michal Wilczynski
2023-06-02 10:29 ` Thadeu Lima de Souza Cascardo
2023-06-02 13:25 ` Wilczynski, Michal
2023-06-01 13:17 ` [PATCH v4 19/35] platform/x86/dell/dell-rbtn: " Michal Wilczynski
2023-06-02 13:20 ` Ilpo Järvinen
2023-06-02 13:41 ` Wilczynski, Michal
2023-06-02 14:01 ` Ilpo Järvinen
2023-06-01 13:17 ` [PATCH v4 20/35] platform/x86/eeepc-laptop: " Michal Wilczynski
2023-06-02 13:24 ` Ilpo Järvinen
2023-06-01 13:17 ` [PATCH v4 21/35] platform/x86/fujitsu-laptop: " Michal Wilczynski
2023-06-02 13:30 ` Ilpo Järvinen
2023-06-02 13:49 ` Wilczynski, Michal [this message]
2023-06-02 13:55 ` Ilpo Järvinen
2023-06-01 13:17 ` [PATCH v4 22/35] platform/x86/lg-laptop: " Michal Wilczynski
2023-06-01 13:17 ` [PATCH v4 23/35] platform/x86/panasonic-laptop: " Michal Wilczynski
2023-06-01 13:17 ` [PATCH v4 24/35] platform/x86/system76_acpi: " Michal Wilczynski
2023-06-01 13:17 ` [PATCH v4 25/35] platform/x86/topstar-laptop: " Michal Wilczynski
2023-06-01 13:17 ` [PATCH v4 26/35] platform/x86/toshiba_acpi: " Michal Wilczynski
2023-06-01 13:17 ` [PATCH v4 27/35] platform/x86/toshiba_bluetooth: " Michal Wilczynski
2023-06-01 13:17 ` [PATCH v4 28/35] platform/x86/toshiba_haps: " Michal Wilczynski
2023-06-01 13:17 ` [PATCH v4 29/35] platform/x86/wireless-hotkey: " Michal Wilczynski
2023-06-01 13:17 ` [PATCH v4 30/35] platform/x86/xo15-ebook: " Michal Wilczynski
2023-06-01 13:17 ` [PATCH v4 31/35] platform/x86/sony-laptop: " Michal Wilczynski
2023-06-01 13:17 ` [PATCH v4 32/35] virt/vmgenid: " 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=7fcb9041-9a78-ac9e-6a23-47bbccdfd30a@intel.com \
--to=michal.wilczynski@intel.com \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jwoithe@just42.net \
--cc=linux-acpi@vger.kernel.org \
--cc=markgross@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox