[PATCH] media: platform: mtk-mdp3: add WQ_PERCPU to alloc_workqueue users

[Marco Crivellari]

On Tue, Dec 9, 2025 at 9:57 PM Nicolas Dufresne <nicolas at ndufresne.ca> wrote:
>
> Hi,
> I have to admit, there is likely no review here due to the lack of knowledge, so
> in order to help educate myself (hopefully its not just me), can you explain why
> the new default of WQ_UNBOUND would not be a fit for this driver ? After all,
> the author didn't care and didn't make a choice, so I feel like its worth
> asking.

Hi Nicolas,

The fact is that "alloc_workqueue()" without WQ_UNBOUND it means per-cpu.
So what we are doing here is just make explicit that the workqueue is per-cpu.

Currently there are no behavioral changes in alloc_workqueue(); in a
future release
WQ_UNBOUND will be removed and unbound will be the default. But as for now,
it is still per-cpu.

We can of course change the current behavior and I can send the v2 with
WQ_UNBOUND instead. Looking at the code there are not per-cpu variable and
the workqueue does not have the WQ_BH flag, so we can convert it if it
is better.

Thanks!

--

Marco Crivellari

L3 Support Engineer