From: Maximilian Luz <luzmaximilian@gmail.com>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
Hans de Goede <hdegoede@redhat.com>,
Mark Gross <markgross@kernel.org>
Cc: platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH] platform/surface: avoid flush_scheduled_work() usage
Date: Fri, 10 Jun 2022 13:29:53 +0200 [thread overview]
Message-ID: <df69c497-0ec1-0ffa-b434-dede30a36c36@gmail.com> (raw)
In-Reply-To: <63ec2d45-c67c-1134-f6d3-490c8ba67a01@I-love.SAKURA.ne.jp>
On 6/10/22 07:41, Tetsuo Handa wrote:
> Use local wq in order to avoid flush_scheduled_work() usage.
>
> Signed-off-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
> ---
> Please see commit c4f135d643823a86 ("workqueue: Wrap flush_workqueue()
> using a macro") for background.
>
> This is a blind conversion, and is only compile tested.
Looks good to me, thanks!
Reviewed-by: Maximilian Luz <luzmaximilian@gmail.com>
Tested-by: Maximilian Luz <luzmaximilian@gmail.com>
> .../platform/surface/surface_acpi_notify.c | 27 ++++++++++++++++---
> 1 file changed, 24 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/platform/surface/surface_acpi_notify.c b/drivers/platform/surface/surface_acpi_notify.c
> index 7b758f8cc137..c0e12f0b9b79 100644
> --- a/drivers/platform/surface/surface_acpi_notify.c
> +++ b/drivers/platform/surface/surface_acpi_notify.c
> @@ -37,6 +37,7 @@ struct san_data {
> #define to_san_data(ptr, member) \
> container_of(ptr, struct san_data, member)
>
> +static struct workqueue_struct *san_wq;
>
> /* -- dGPU notifier interface. ---------------------------------------------- */
>
> @@ -356,7 +357,7 @@ static u32 san_evt_bat_nf(struct ssam_event_notifier *nf,
>
> memcpy(&work->event, event, sizeof(struct ssam_event) + event->length);
>
> - schedule_delayed_work(&work->work, delay);
> + queue_delayed_work(san_wq, &work->work, delay);
> return SSAM_NOTIF_HANDLED;
> }
>
> @@ -861,7 +862,7 @@ static int san_remove(struct platform_device *pdev)
> * We have unregistered our event sources. Now we need to ensure that
> * all delayed works they may have spawned are run to completion.
> */
> - flush_scheduled_work();
> + flush_workqueue(san_wq);
>
> return 0;
> }
> @@ -881,7 +882,27 @@ static struct platform_driver surface_acpi_notify = {
> .probe_type = PROBE_PREFER_ASYNCHRONOUS,
> },
> };
> -module_platform_driver(surface_acpi_notify);
> +
> +static int __init san_init(void)
> +{
> + int ret;
> +
> + san_wq = alloc_workqueue("san_wq", 0, 0);
> + if (!san_wq)
> + return -ENOMEM;
> + ret = platform_driver_register(&surface_acpi_notify);
> + if (ret)
> + destroy_workqueue(san_wq);
> + return ret;
> +}
> +module_init(san_init);
> +
> +static void __exit san_exit(void)
> +{
> + platform_driver_unregister(&surface_acpi_notify);
> + destroy_workqueue(san_wq);
> +}
> +module_exit(san_exit);
>
> MODULE_AUTHOR("Maximilian Luz <luzmaximilian@gmail.com>");
> MODULE_DESCRIPTION("Surface ACPI Notify driver for Surface System Aggregator Module");
next prev parent reply other threads:[~2022-06-10 11:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 5:41 [PATCH] platform/surface: avoid flush_scheduled_work() usage Tetsuo Handa
2022-06-10 11:29 ` Maximilian Luz [this message]
2022-06-17 10:40 ` Tetsuo Handa
2022-06-17 11:31 ` Maximilian Luz
2022-06-22 10:04 ` Hans de Goede
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=df69c497-0ec1-0ffa-b434-dede30a36c36@gmail.com \
--to=luzmaximilian@gmail.com \
--cc=hdegoede@redhat.com \
--cc=markgross@kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=platform-driver-x86@vger.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