13 Feb
2024
13 Feb
'24
11:48 p.m.
Hi Takashi,
On 2/13/2024 2:59 AM, Takashi Iwai wrote:
On Tue, 13 Feb 2024 01:54:01 +0100, Wesley Cheng wrote:
+static int __init qc_usb_audio_offload_init(void) +{
- struct uaudio_qmi_svc *svc;
- int ret;
- svc = kzalloc(sizeof(struct uaudio_qmi_svc), GFP_KERNEL);
- if (!svc)
return -ENOMEM;- svc->uaudio_wq = create_singlethread_workqueue("uaudio_svc");
- if (!svc->uaudio_wq) {
ret = -ENOMEM;goto free_svc;- }
Do we need a dedicated workqueue? I don't mind much, but an own workqueue isn't usually needed unless specifically required such as the request quantity control or isolation.
I think we can remove this. I checked the QMI interface implementation and looks like they are running all the notifications on its own WQ, so doing duplicate work with queuing to our own WQ here in qc_audio_offload.
Thanks Wesley Cheng