devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lukasz Majewski <lukma@denx.de>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>,
	Fabio Estevam <festevam@gmail.com>,
	Conor Dooley <conor+dt@kernel.org>,
	devicetree@vger.kernel.org, linux-sound@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: dt-bindings: Add dt bindings definition file for imx28 saif
Date: Wed, 28 Aug 2024 10:01:11 +0200	[thread overview]
Message-ID: <20240828100111.10852309@wsk> (raw)
In-Reply-To: <mzlrm7zkzuue4xsxehz32ffiesigy2dzbos2osirzfoi525q6q@7klbgtmht74a>

[-- Attachment #1: Type: text/plain, Size: 3952 bytes --]

Hi Krzysztof,

> On Tue, Aug 27, 2024 at 08:05:28PM +0200, Lukasz Majewski wrote:
> > This file allows correct check of DTS node for imx287 based
> > "fsl,imx28-saif" compatible device.
> > 
> > It corresponds to Documentation/devicetree/bindings/fsl,imx28-saif
> > 
> > Signed-off-by: Lukasz Majewski <lukma@denx.de>
> > ---
> >  .../devicetree/bindings/sound/fsl,saif.yaml   | 79
> > +++++++++++++++++++ 1 file changed, 79 insertions(+)  
> 
> There is a binding. Please perform conversion from TXT to DT schema,
> mentioning in commit msg any changes from pure conversion (e.g. new
> properties to match DTS).

Hmm.... OK.

> 
> Few more comments below.
> 
> >  create mode 100644
> > Documentation/devicetree/bindings/sound/fsl,saif.yaml
> > 
> > diff --git a/Documentation/devicetree/bindings/sound/fsl,saif.yaml
> > b/Documentation/devicetree/bindings/sound/fsl,saif.yaml new file
> > mode 100644 index 000000000000..747faa411a50
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/sound/fsl,saif.yaml
> > @@ -0,0 +1,79 @@
> > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > +%YAML 1.2
> > +---
> > +$id: http://devicetree.org/schemas/sound/fsl,saif.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: Freescale MXS Serial Audio Interface (SAIF)
> > +
> > +maintainers:
> > +  - Lukasz Majewski <lukma@denx.de>
> > +
> > +description: |  
> 
> Do not need '|' unless you need to preserve formatting.

Ok.

> 
> > +  The SAIF is based on I2S module that is used to communicate with
> > audio codecs,
> > +  but only with half-duplex manner (i.e. it can either transmit or
> > receive PCM
> > +  audio).
> > +
> > +properties:
> > +  compatible:
> > +    const: fsl,imx28-saif
> > +
> > +  reg:
> > +    maxItems: 1
> > +
> > +  "#sound-dai-cells":
> > +    const: 0
> > +
> > +  assigned-clock-parents: true
> > +  assigned-clock-rates: true
> > +  assigned-clocks: true  
> 
> These three should be dropped, redundant.

Last two are present in definition of saif[01] in imx28.dtsi - so IMHO
it shall be added.

Moreover, those are present in fsl,sg5000.yaml dt-schema description.

> 
> > +
> > +  interrupts:
> > +    maxItems: 1
> > +
> > +  dmas:
> > +    maxItems: 1
> > +
> > +  dma-names:
> > +    const: rx-tx
> > +
> > +  clocks:
> > +    maxItems: 1
> > +
> > +  fsl,saif-master:
> > +    description: Indicate that saif is a slave and its phandle
> > points to master
> > +    $ref: /schemas/types.yaml#/definitions/phandle
> > +
> > +required:
> > +  - compatible
> > +  - reg
> > +  - interrupts
> > +  - clocks
> > +  - dmas
> > +  - dma-names
> > +  - "#sound-dai-cells"  
> 
> Keep the same order as in "properties:" block.

Ok.

> 
> and here allOf: with $ref to dai-common.yaml

Ok.

> 
> > +
> > +unevaluatedProperties: false
> > +
> > +examples:
> > +  - |
> > +    saif0: saif@80042000 {
> > +        #sound-dai-cells = <0>;
> > +        compatible = "fsl,imx28-saif";
> > +        reg = <0x80042000 2000>;
> > +        interrupts = <59>;
> > +        clocks = <&clks 53>;
> > +        dmas = <&dma_apbx 4>;
> > +        dma-names = "rx-tx";
> > +    };
> > +  - |
> > +    saif1: saif@80046000 {  
> 
> Just one example, could be this one as more complete.

This is important, as saif1 has "fsl,saif-master" which allows to have
full duplex PCM communication (by default on imx28 single saif is
half-duplex).

> 
> > +        #sound-dai-cells = <0>;  
> 
> Keep it after "reg" (compatible and reg are always first).

Ok.

> 
> Best regards,
> Krzysztof
> 




Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH,      Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@denx.de

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2024-08-28  8:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-27 18:05 [PATCH] ASoC: dt-bindings: Add dt bindings definition file for imx28 saif Lukasz Majewski
2024-08-28  6:18 ` Krzysztof Kozlowski
2024-08-28  8:01   ` Lukasz Majewski [this message]
2024-08-28  8:11     ` Krzysztof Kozlowski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240828100111.10852309@wsk \
    --to=lukma@denx.de \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=robh@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).