schedule: zephyr_ll: update zephyr_ll_task_insert_unlocked comments

Clarify the inline comment in zephyr_ll_task_insert_unlocked()
explaining the task priority semantics. The old text is not clear on
what is "high priority". Make it explicit that 0 is the highest priority
and that the tasks are executed in order of task priority.

Signed-off-by: Kai Vehmanen <[email protected]>

src/schedule/zephyr_ll.c

@@ -96,9 +96,11 @@ static void zephyr_ll_task_insert_unlocked(struct zephyr_ll *sch, struct task *t
 	task->state = SOF_TASK_STATE_QUEUED;
 
 	/*
-	 * Tasks are added into the list from highest to lowest priority. This
-	 * way they can then be run in the same order. Tasks with the same
-	 * priority are served on a first-come-first-serve basis
+	 * Tasks are added into the list with largest priority value
+	 * first, followed by smaller values. The list is used to run
+	 * the tasks in priority order, with priority 0 being the
+	 * highest and always run first. Tasks with the same
+	 * priority are served on a first-come-first-serve basis.
 	 */
 	list_for_item(list, &sch->tasks) {
 		task_iter = container_of(list, struct task, list);