The checks are not coming from device node name, but from matchingOn 18/05/2022 19:36, Sameer Pujar wrote:Idea was to keep these node names consistent across DT files and parent
+description: |Why? We enforce only generic names in shared schemas and this is neither
+ The Multi Band Dynamic Range Compressor (MBDRC) is part of Output
+ Processing Engine (OPE) which interfaces with Audio Hub (AHUB) via
+ Audio Client Interface (ACIF). MBDRC can be used as a traditional
+ single full band or a dual band or a multi band dynamic processor.
+
+maintainers:
+ - Jon Hunter <jonathanh@xxxxxxxxxx>
+ - Mohan Kumar <mkumard@xxxxxxxxxx>
+ - Sameer Pujar <spujar@xxxxxxxxxx>
+
+properties:
+ $nodename:
+ pattern: "^mbdrc@[0-9a-f]*$"
shared schema nor is it generic name.
node can allow a given list of child nodes with strict checks. Does name
like "dynamic-range-compressor@xxx"
schema to compatible. Why do you need consistent names across DTS files?
They should be anyway generic but what happens if they differ?
Additionally, the parent schema enforces nodes of children, so if this
is included in other schema, then the change is pointless.