From 179bbd570dd61638d2e10dc55d06f7ab95efedec Mon Sep 17 00:00:00 2001 From: Kai Vehmanen Date: Tue, 21 Nov 2023 20:36:54 +0200 Subject: [PATCH] topology2: pipeline: add constraints on pipeline.priority attribute Add constraints on valid pipeline priority values and document the semantics so that 0 is considered the highest priority and such pipeline should be run first. The range matches definitions in include/ipc4/pipeline.h and SOF_IPC4_MAX_PIPELINE_PRIORITY. Signed-off-by: Kai Vehmanen --- tools/topology/topology2/include/components/pipeline.conf | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/tools/topology/topology2/include/components/pipeline.conf b/tools/topology/topology2/include/components/pipeline.conf index ddb6448bd4cb..3a69354e30d2 100644 --- a/tools/topology/topology2/include/components/pipeline.conf +++ b/tools/topology/topology2/include/components/pipeline.conf @@ -57,10 +57,14 @@ Class.Widget."pipeline" { } } - # pipeline priority + # pipeline priority (0 = highest priority, 7 = lowest) DefineAttribute."priority" { # Token reference and type token_ref "scheduler.word" + constraints { + min 0 + max 7 + } } # core that the pipeline should be scheduled on