On Tue 09 Jan 2024 at 22:38, Krzysztof Kozlowski <krzysztof.kozlowski@xxxxxxxxxx> wrote: > Instead of accepting any value for sound-dai-cells, the common DAI > properties schema should narrow them to sane choice. > > Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@xxxxxxxxxx> > Adding a constraint solely based on current usage feels wrong. A DAI provider in its generic form must have the sound-dai-cells to provide one. It says nothing about how many parameters an actual device might need. That is the idea behind this binding. It is up to the device specific bindings to define that value. If restricting things here is really important, defaulting to 0 (with a comment explaining it) and letting actual devices then override the value would feel less 'made up' > --- > > Mostly sound-dai-cells are 0 or 1, but > Documentation/devicetree/bindings/sound/amlogic,aiu.yaml has value of 2. > --- > Documentation/devicetree/bindings/sound/dai-common.yaml | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/Documentation/devicetree/bindings/sound/dai-common.yaml b/Documentation/devicetree/bindings/sound/dai-common.yaml > index 1aed2f0f1775..6db35887cbe6 100644 > --- a/Documentation/devicetree/bindings/sound/dai-common.yaml > +++ b/Documentation/devicetree/bindings/sound/dai-common.yaml > @@ -13,6 +13,7 @@ allOf: > - $ref: component-common.yaml# > > properties: > - '#sound-dai-cells': true > + '#sound-dai-cells': > + enum: [0, 1, 2] > > additionalProperties: true -- Jerome
