From 1c2850d354ca9af4f26835fd6f42fcdb7dd9a058 Mon Sep 17 00:00:00 2001 From: Kai Vehmanen Date: Tue, 16 Jun 2026 20:45:41 +0300 Subject: [PATCH] schedule: zephyr_dp_sched_app: fix build error in release builds Release builds fail when building with DP user-space implementation. Build fails as CONFIG_THREAD_MAX_NAME_LEN is not defined. Problem not affecting when building with debug enabled, and/or configurations where the feature is disabled. Signed-off-by: Kai Vehmanen --- src/schedule/zephyr_dp_schedule_application.c | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/src/schedule/zephyr_dp_schedule_application.c b/src/schedule/zephyr_dp_schedule_application.c index ac03bb59fe5d..791e16ab190d 100644 --- a/src/schedule/zephyr_dp_schedule_application.c +++ b/src/schedule/zephyr_dp_schedule_application.c @@ -411,6 +411,7 @@ void scheduler_dp_internal_free(struct task *task) mod_free(pdata->mod, container_of(task, struct scheduler_dp_task_memory, task)); } +#ifdef CONFIG_THREAD_NAME static void scheduler_dp_thread_name_set(k_tid_t thread_id, struct processing_module *mod) { char name[CONFIG_THREAD_MAX_NAME_LEN]; @@ -419,6 +420,10 @@ static void scheduler_dp_thread_name_set(k_tid_t thread_id, struct processing_mo k_thread_name_set(thread_id, name); } +#else +/* k_thread_name_set() is a no-op so skip constructing a thread name */ +#define scheduler_dp_thread_name_set(x, y) +#endif /* Called only in IPC context */ int scheduler_dp_task_init(struct task **task, const struct sof_uuid_entry *uid,