lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Wed, 22 May 2024 08:24:40 +0000
From: Xingyu Wu <xingyu.wu@...rfivetech.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>, Liam Girdwood
	<lgirdwood@...il.com>, Mark Brown <broonie@...nel.org>, Claudiu Beznea
	<Claudiu.Beznea@...rochip.com>, Jaroslav Kysela <perex@...ex.cz>, Takashi
 Iwai <tiwai@...e.com>, Rob Herring <robh+dt@...nel.org>, Krzysztof Kozlowski
	<krzysztof.kozlowski+dt@...aro.org>, Conor Dooley
	<conor.dooley@...rochip.com>
CC: "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"alsa-devel@...a-project.org" <alsa-devel@...a-project.org>,
	"linux-sound@...r.kernel.org" <linux-sound@...r.kernel.org>
Subject: RE: [PATCH v3 1/2] ASoC: dt-bindings: Add bindings for Cadence I2S-MC
 controller

On 22/05/2024 15:30, Krzysztof Kozlowski wrote:
> 
> On 08/05/2024 10:03, Krzysztof Kozlowski wrote:
> > On 08/05/2024 09:04, Xingyu Wu wrote:
> >> Add bindings for the Multi-Channel I2S controller of Cadence.
> >>
> >> The Multi-Channel I2S (I2S-MC) implements a function of the 8-channel
> >> I2S bus interfasce. Each channel can become receiver or transmitter.
> >> Four I2S instances are used on the StarFive
> >> JH8100 SoC. One instance of them is limited to 2 channels, two
> >> instance are limited to 4 channels, and the other one can use most 8
> >> channels. Add a unique property about 'starfive,i2s-max-channels' to
> >> distinguish each instance.
> >>
> >> Signed-off-by: Xingyu Wu <xingyu.wu@...rfivetech.com>
> >
> >
> >> +
> >> +  starfive,i2s-max-channels:
> >> +    description:
> >> +      Number of I2S max stereo channels supported on the StarFive
> >> +      JH8100 SoC.
> >> +    $ref: /schemas/types.yaml#/definitions/uint32
> >> +    enum: [2, 4, 8]
> >> +
> >> +allOf:
> >> +  - $ref: dai-common.yaml#
> >> +  - if:
> >> +      properties:
> >> +        compatible:
> >> +          contains:
> >> +            const: starfive,jh8100-i2s
> >> +    then:
> >> +      required:
> >> +        - starfive,i2s-max-channels
> >> +    else:
> >> +      properties:
> >> +        starfive,i2s-max-channels: false
> >> +
> >> +required:
> >
> > I asked to put it after properties: block, not after allOf:. See
> > example-schema for preferred order. Why? Because we are used to it and
> > it makes reading the schema easier for us.
> >
> > Rest looks good, so with the re-order:
> >
> > Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
> 
> Since you do not plan to fix it and already started pinging mark, I retract my
> review.
> 
> Unreviewed-by.
> 
> Implement the feedback I already asked you BEFORE.
> 
> Best regards,
> Krzysztof

Sorry, I thought my reply email went out but it didn't. I will re-order it and put
the required before the allOf in the next version.

I thought it would be nice to update both bindings and driver patches in the
next version, so I ping mark.

Best regards,
Xingyu Wu

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ