usb: device_next: cdc_acm: set the thread name after initializing it

The cdc-acm workqueue thread name is set before initializing it right
now, which results in an empty thread name as apparently it gets cleared
by k_work_queue_init. Fix it by moving the thread name setting after the
workqueu is initialized and started.

Signed-off-by: Fabio Baltieri <[email protected]>

subsys/usb/device_next/class/usbd_cdc_acm.c

@@ -1026,6 +1026,7 @@ static int usbd_cdc_acm_init_wq(void)
 	k_work_queue_start(&cdc_acm_work_q, cdc_acm_stack,
 			   K_KERNEL_STACK_SIZEOF(cdc_acm_stack),
 			   CONFIG_SYSTEM_WORKQUEUE_PRIORITY, NULL);
+	k_thread_name_set(&cdc_acm_work_q.thread, "cdc_acm_work_q");
 
 	return 0;
 }
@@ -1037,8 +1038,6 @@ static int usbd_cdc_acm_preinit(const struct device *dev)
 	ring_buf_reset(data->tx_fifo.rb);
 	ring_buf_reset(data->rx_fifo.rb);
 
-	k_thread_name_set(&cdc_acm_work_q.thread, "cdc_acm_work_q");
-
 	k_work_init_delayable(&data->tx_fifo_work, cdc_acm_tx_fifo_handler);
 	k_work_init(&data->rx_fifo_work, cdc_acm_rx_fifo_handler);
 	k_work_init(&data->irq_cb_work, cdc_acm_irq_cb_handler);