Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: chancel.liu@oss.nxp.com
Cc: conor+dt@kernel.org, robh@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 1/2] ASoC: dt-bindings: cirrus,cs42xx8: Add SPI bus support
Date: Wed, 03 Jun 2026 10:00:07 +0000	[thread overview]
Message-ID: <20260603100008.2CF491F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260603095041.3906558-2-chancel.liu@oss.nxp.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Conflicting GPIO cell counts for the '&gpio' phandle in the newly added SPI example.
--

commit f4759f9ac7c7f10e085045f8fabd1df333354abf
Author: Chancel Liu <chancel.liu@nxp.com>

ASoC: dt-bindings: cirrus,cs42xx8: Add SPI bus support

This commit adds SPI control interface support to the CS42448/CS42888 codec
bindings, which can operate at up to 6MHz. It updates the schema with SPI
properties and provides a new SPI example configuration.

> diff --git a/Documentation/devicetree/bindings/sound/cirrus,cs42xx8.yaml b/Documentation/devicetree/bindings/sound/cirrus,cs42xx8.yaml
> --- a/Documentation/devicetree/bindings/sound/cirrus,cs42xx8.yaml
> +++ b/Documentation/devicetree/bindings/sound/cirrus,cs42xx8.yaml

[ ... ]

> @@ -86,3 +90,22 @@ examples:
>            reset-gpios = <&gpio 1>;
>        };
>      };
> +
> +    spi {
> +      #address-cells = <1>;
> +      #size-cells = <0>;
> +      cs-gpios = <&gpio 8 0>;
> +
> +      codec@0 {
> +          compatible = "cirrus,cs42888";
> +          reg = <0>;
> +          spi-max-frequency = <6000000>;
> +          clocks = <&codec_mclk 0>;
> +          clock-names = "mclk";
> +          VA-supply = <&reg_audio>;
> +          VD-supply = <&reg_audio>;
> +          VLS-supply = <&reg_audio>;
> +          VLC-supply = <&reg_audio>;
> +          reset-gpios = <&gpio 1>;

[Severity: Low]
Will this cause a dt_binding_check failure due to a cell size mismatch?

The cs-gpios property uses 2 argument cells for the &gpio phandle, but
reset-gpios uses 1 argument cell for the exact same &gpio label.

A single device tree node can only have a single #gpio-cells value. When
dt_binding_check auto-generates a dummy node for the unresolved &gpio
reference, it will infer a #gpio-cells value that conflicts with one of
these references. 

Should a different label (e.g., &gpio2) be used for cs-gpios, or should
reset-gpios be updated to use 2 cells?

> +      };
> +    };

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260603095041.3906558-1-chancel.liu@oss.nxp.com?part=1

  reply	other threads:[~2026-06-03 10:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260601080224.1410292-1-chancel.liu@oss.nxp.com>
2026-06-03  9:50 ` [PATCH v2 0/2] ASoC: cs42xx8: Add SPI bus support for CS42448/CS42888 codec chancel.liu
2026-06-03  9:50   ` [PATCH v2 1/2] ASoC: dt-bindings: cirrus,cs42xx8: Add SPI bus support chancel.liu
2026-06-03 10:00     ` sashiko-bot [this message]
2026-06-03  9:50   ` [PATCH v2 2/2] ASoC: cs42xx8: Add SPI bus support for CS42448/CS42888 codec chancel.liu
2026-06-03 10:15     ` sashiko-bot
2026-06-03 11:46   ` [PATCH v2 0/2] " Charles Keepax
2026-06-03 11:57   ` Mark Brown
2026-06-03 12:14     ` Chancel Liu (OSS)
2026-06-03 11:57   ` Mark Brown

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=20260603100008.2CF491F00893@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=chancel.liu@oss.nxp.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@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