diff options
| author | Marco Crivellari <marco.crivellari@suse.com> | 2025-11-05 13:11:34 +0300 |
|---|---|---|
| committer | Maíra Canal <mcanal@igalia.com> | 2026-02-16 14:22:09 +0300 |
| commit | 0ef1dcf4c16bb6d90e8fbf7b18f3d76b79fcde9d (patch) | |
| tree | 456231b1fe1d7884499789d91a95043d8d3f1f6e /include/linux/platform_data | |
| parent | 20e0c197802c545db220157fafd567a10f2b7672 (diff) | |
| download | linux-0ef1dcf4c16bb6d90e8fbf7b18f3d76b79fcde9d.tar.xz | |
drm/vc4: hdmi: replace use of system_wq with system_percpu_wq
Currently if a user enqueues 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 consistency 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>
Reviewed-by: Maíra Canal <mcanal@igalia.com>
Link: https://patch.msgid.link/20251105101134.82064-1-marco.crivellari@suse.com
Signed-off-by: Maíra Canal <mcanal@igalia.com>
Diffstat (limited to 'include/linux/platform_data')
0 files changed, 0 insertions, 0 deletions
