Linux kernel and device drivers for NXP i.MX platforms
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Frank Li via B4 Relay" <devnull+Frank.Li.nxp.com@kernel.org>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	Frank.Li@kernel.org, imx@lists.linux.dev,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v2] ASoC: dt-bindings: Convert eukrea-tlv320.txt to yaml
Date: Tue, 12 May 2026 20:11:44 +0000	[thread overview]
Message-ID: <20260512201144.D596DC2BCB0@smtp.kernel.org> (raw)
In-Reply-To: <20260511-eukrea-v2-1-cac317290978@nxp.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The properties `fsl,mux-int-port` and `fsl,mux-ext-port` are omitted from the `required` list in the new YAML binding schema.
--

commit 5251ce7d6c30896b16c3da8622760278420a910b
Author: Frank Li <Frank.Li@nxp.com>

ASoC: dt-bindings: Convert eukrea-tlv320.txt to yaml

This commit converts the eukrea-tlv320 device tree binding documentation
from plain text to the YAML schema format.

> diff --git a/Documentation/devicetree/bindings/sound/eukrea,asoc-tlv320.yaml b/Documentation/devicetree/bindings/sound/eukrea,asoc-tlv320.yaml
> new file mode 100644
> index 0000000000000..a95cd0323f6e4
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/sound/eukrea,asoc-tlv320.yaml

[ ... ]

> +required:
> +  - compatible
> +  - eukrea,model
> +  - ssi-controller
> +
> +additionalProperties: false

Should fsl,mux-int-port and fsl,mux-ext-port be included in this required 
list? 

In the original eukrea-tlv320.txt file being removed, both of these properties 
were explicitly listed under the Required properties section. 

Additionally, the kernel driver sound/soc/fsl/eukrea-tlv320.c appears to 
strictly check for these properties during probe, returning an error if they 
are missing. 

Does this omission introduce a regression where incomplete device tree nodes 
will silently pass dt_binding_check validation but fail at runtime?

[ ... ]

> diff --git a/Documentation/devicetree/bindings/sound/eukrea-tlv320.txt b/Documentation/devicetree/bindings/sound/eukrea-tlv320.txt
> deleted file mode 100644
> index 6dfa88c4dc1e8..0000000000000
> --- a/Documentation/devicetree/bindings/sound/eukrea-tlv320.txt
> +++ /dev/null
> @@ -1,26 +0,0 @@
> -Audio complex for Eukrea boards with tlv320aic23 codec.
> -
> -Required properties:
> -
> -  - compatible		: "eukrea,asoc-tlv320"
> -
> -  - eukrea,model	: The user-visible name of this sound complex.
> -
> -  - ssi-controller	: The phandle of the SSI controller.
> -
> -  - fsl,mux-int-port	: The internal port of the i.MX audio muxer (AUDMUX).
> -
> -  - fsl,mux-ext-port	: The external port of the i.MX audio muxer.

[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260511-eukrea-v2-1-cac317290978@nxp.com?part=1

      reply	other threads:[~2026-05-12 20:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-11 16:11 [PATCH v2] ASoC: dt-bindings: Convert eukrea-tlv320.txt to yaml Frank Li via B4 Relay
2026-05-12 20:11 ` sashiko-bot [this message]

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=20260512201144.D596DC2BCB0@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=Frank.Li@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=devnull+Frank.Li.nxp.com@kernel.org \
    --cc=imx@lists.linux.dev \
    --cc=krzk+dt@kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko@lists.linux.dev \
    /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