[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <109868b9492aecaca0a7170cba9fb51e62de7116.camel@gmail.com>
Date: Tue, 14 Feb 2023 14:02:27 +0100
From: Alexander Sverdlin <alexander.sverdlin@...il.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
devicetree@...r.kernel.org
Cc: Hartley Sweeten <hsweeten@...ionengravers.com>,
Liam Girdwood <lgirdwood@...il.com>,
Mark Brown <broonie@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
alsa-devel@...a-project.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: sound: ep93xx: Add I2S and AC'97
descriptions
Hello Krzysztof,
thank you for the quick review!
On Tue, 2023-02-14 at 11:58 +0100, Krzysztof Kozlowski wrote:
> > +properties:
> > + compatible:
> > + const: cirrus,ep9301-i2s
> > +
> > + '#sound-dai-cells':
> > + const: 0
> > +
> > + reg:
> > + maxItems: 1
> > +
> > + interrupts:
> > + maxItems: 1
> > +
> > + clocks:
> > + minItems: 3
>
> maxItems instead
reg and clocks are required, I suppose I should include both minItems
and maxItems for both of them?
> > +
> > + clock-names:
> > + items:
> > + - const: mclk
> > + - const: sclk
> > + - const: lrclk
>
>
> The clk suffixes are quite redundant. Don't these inputs have some
> meaningful name?
They are actually meaningful, as they are usually named in I2S, please
refer to the EP93xx User's Guide:
https://cdn.embeddedts.com/resource-attachments/ts-7000_ep9301-ug.pdf
page 71, for instance.
--
Alexander Sverdlin.
Powered by blists - more mailing lists