> On 10. 5. 2023, at 9:17, Krzysztof Kozlowski <krzysztof.kozlowski@xxxxxxxxxx> wrote: > > On 09/05/2023 17:34, Martin Povišer wrote: >> A bunch of TI's codecs have binding schemas which force #sound-dai-cells >> to one despite those codecs only having a single DAI. Allow for bindings >> with zero DAI cells and deprecate the former non-zero value. >> >> Signed-off-by: Martin Povišer <povik+lin@xxxxxxxxxxx> >> --- >> Documentation/devicetree/bindings/sound/tas2562.yaml | 6 ++++-- >> Documentation/devicetree/bindings/sound/tas2770.yaml | 6 ++++-- >> Documentation/devicetree/bindings/sound/tas27xx.yaml | 6 ++++-- >> 3 files changed, 12 insertions(+), 6 deletions(-) >> >> diff --git a/Documentation/devicetree/bindings/sound/tas2562.yaml b/Documentation/devicetree/bindings/sound/tas2562.yaml >> index a5bb561bfcfb..31a3024ea789 100644 >> --- a/Documentation/devicetree/bindings/sound/tas2562.yaml >> +++ b/Documentation/devicetree/bindings/sound/tas2562.yaml >> @@ -55,7 +55,9 @@ properties: >> description: TDM TX current sense time slot. >> >> '#sound-dai-cells': >> - const: 1 >> + # The codec has a single DAI, the #sound-dai-cells=<1>; case is left in for backward >> + # compatibility but is deprecated. >> + enum: [0, 1] > > Does it? I see playback and capture. I think so. Playback and capture are not separate DAIs. Martin > > Best regards, > Krzysztof
