topology2: pipeline: add constraints on pipeline.priority attribute

kv2019i · kv2019i · commit 07b762e0ae77 · 2024-04-05T21:13:37.000+03:00
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 &lt;kai.vehmanen@linux.intel.com&gt;
diff --git 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

Original file line number	Diff line number	Diff line change
`@@ -57,10 +57,14 @@ Class.Widget."pipeline" {`
`57`	`57`	`}`
`58`	`58`	`}`
`59`	`59`
`60`		`- # pipeline priority`
	`60`	`+ # pipeline priority (0 = highest priority, 7 = lowest)`
`61`	`61`	`DefineAttribute."priority" {`
`62`	`62`	`# Token reference and type`
`63`	`63`	`token_ref "scheduler.word"`
	`64`	`+ constraints {`
	`65`	`+ min 0`
	`66`	`+ max 7`
	`67`	`+ }`
`64`	`68`	`}`
`65`	`69`
`66`	`70`	`# core that the pipeline should be scheduled on`