public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chanwoo Choi <chanwoo@kernel.org>
To: Marco Crivellari <marco.crivellari@suse.com>,
	linux-kernel@vger.kernel.org
Cc: Tejun Heo <tj@kernel.org>, Lai Jiangshan <jiangshanlai@gmail.com>,
	Frederic Weisbecker <frederic@kernel.org>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Michal Hocko <mhocko@suse.com>,
	MyungJoo Ham <myungjoo.ham@samsung.com>,
	Chanwoo Choi <cw00.choi@samsung.com>
Subject: Re: [PATCH] extcon: int3496: replace use of system_wq with system_percpu_wq
Date: Mon, 24 Nov 2025 00:36:20 +0900	[thread overview]
Message-ID: <439953a2-177f-4e7c-9bd2-0fc7d204ca1a@kernel.org> (raw)
In-Reply-To: <20251104110105.116858-1-marco.crivellari@suse.com>

Hi,

25. 11. 4. 20:01에 Marco Crivellari 이(가) 쓴 글:
> Currently if a user enqueue a work item using schedule_delayed_work() the
> used wq is "system_wq" (per-cpu wq) while queue_delayed_work() use
> WORK_CPU_UNBOUND (used when a cpu is not specified). The same applies to
> schedule_work() that is using system_wq and queue_work(), that makes use
> again of WORK_CPU_UNBOUND.
> 
> This lack of consistentcy cannot be addressed without refactoring the API.
> 
> This patch continues the effort to refactor worqueue APIs, which has begun
> with the change introducing new workqueues and a new alloc_workqueue flag:
> 
> commit 128ea9f6ccfb ("workqueue: Add system_percpu_wq and system_dfl_wq")
> commit 930c2ea566af ("workqueue: Add new WQ_PERCPU flag")
> 
> system_wq should be the per-cpu workqueue, yet in this name nothing makes
> that clear, so replace system_wq with system_percpu_wq.
> 
> The old wq (system_wq) will be kept for a few release cycles.
> 
> Suggested-by: Tejun Heo <tj@kernel.org>
> Signed-off-by: Marco Crivellari <marco.crivellari@suse.com>
> ---
>  drivers/extcon/extcon-intel-int3496.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/extcon/extcon-intel-int3496.c b/drivers/extcon/extcon-intel-int3496.c
> index ded1a85a5549..7d16d5b7d58f 100644
> --- a/drivers/extcon/extcon-intel-int3496.c
> +++ b/drivers/extcon/extcon-intel-int3496.c
> @@ -106,7 +106,7 @@ static irqreturn_t int3496_thread_isr(int irq, void *priv)
>  	struct int3496_data *data = priv;
>  
>  	/* Let the pin settle before processing it */
> -	mod_delayed_work(system_wq, &data->work, DEBOUNCE_TIME);
> +	mod_delayed_work(system_percpu_wq, &data->work, DEBOUNCE_TIME);
>  
>  	return IRQ_HANDLED;
>  }
> @@ -181,7 +181,7 @@ static int int3496_probe(struct platform_device *pdev)
>  	}
>  
>  	/* process id-pin so that we start with the right status */
> -	queue_delayed_work(system_wq, &data->work, 0);
> +	queue_delayed_work(system_percpu_wq, &data->work, 0);
>  	flush_delayed_work(&data->work);
>  
>  	platform_set_drvdata(pdev, data);

Applied it. Thanks.

-- 
Best Regards,
Samsung Electronics
Chanwoo Choi


  reply	other threads:[~2025-11-23 15:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-04 11:01 [PATCH] extcon: int3496: replace use of system_wq with system_percpu_wq Marco Crivellari
2025-11-23 15:36 ` Chanwoo Choi [this message]
2026-04-02 12:53   ` Marco Crivellari

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=439953a2-177f-4e7c-9bd2-0fc7d204ca1a@kernel.org \
    --to=chanwoo@kernel.org \
    --cc=bigeasy@linutronix.de \
    --cc=cw00.choi@samsung.com \
    --cc=frederic@kernel.org \
    --cc=jiangshanlai@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marco.crivellari@suse.com \
    --cc=mhocko@suse.com \
    --cc=myungjoo.ham@samsung.com \
    --cc=tj@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