Devicetree
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: sashiko-reviews@lists.linux.dev
Cc: joakim.zhang@cixtech.com, conor+dt@kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v3 1/4] ASoC: dt-bindings: Add Cadence I2S-SC controller
Date: Fri, 9 Oct 2026 09:15:28 -0500	[thread overview]
Message-ID: <20261009141528.GA1631855-robh@kernel.org> (raw)
In-Reply-To: <sashiko-outbox-165170@kernel.org>

On Fri, Oct 09, 2026 at 09:32:13AM +0000, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Low] dt-bindings: loose schema constraint on dma-names allows invalid configurations
> --
> 
> commit 41d6caf5f15433436b2c0289025efcf429404414
> Author: Joakim Zhang <joakim.zhang@cixtech.com>
> 
> ASoC: dt-bindings: Add Cadence I2S-SC controller
>     
> Add the DT binding for the Cadence I2S-SC controller integrated in
> the CIX SKY1 audio subsystem. I2S-SC is a full-duplex stereo
> controller supporting standard I2S, left/right-justified and DSP
> formats, plus TDM operation with up to 16 slots.
> 
> > diff --git a/Documentation/devicetree/bindings/sound/cix,sky1-i2s-sc.yaml b/Documentation/devicetree/bindings/sound/cix,sky1-i2s-sc.yaml
> > new file mode 100644
> > index 0000000000000..3fdf2334c4926
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/sound/cix,sky1-i2s-sc.yaml
> 
> [ ... ]
> 
> > +  dmas:
> > +    minItems: 1
> > +    maxItems: 2
> > +    description:
> > +      One DMA channel for instances wired for a single direction, either
> > +      "tx" or "rx", or two channels for both transmit and receive.
> > +
> > +  dma-names:
> > +    minItems: 1
> > +    maxItems: 2
> > +    items:
> > +      enum: [ tx, rx ]
> 
> [Severity: Low]
> Does this schema definition permit invalid DMA combinations? 
> 
> Because items is set to just an enum, this allows combinations like ["tx", "tx"],
> ["rx", "rx"], or out-of-order configurations like ["rx", "tx"] to silently pass
> validation.

Yes, normally that is prevented, but IIRC there's a binding that needed 
something like this.

minItems: 1
uniqueItems: true
items:
  - enum: [ tx, rx ]
  - const: tx

Then when both are there the order is enforced.

Rob

  reply	other threads:[~2026-10-09 14:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-09  9:25 [PATCH v3 0/4] ASoC: cdns: Add Cadence I2S-SC and I2S-MC controller support joakim.zhang
2026-10-09  9:25 ` [PATCH v3 1/4] ASoC: dt-bindings: Add Cadence I2S-SC controller joakim.zhang
2026-10-09  9:32   ` sashiko-bot
2026-10-09 14:15     ` Rob Herring [this message]
2026-10-09 14:16   ` Rob Herring
2026-10-09 14:18   ` Rob Herring
2026-10-09  9:25 ` [PATCH v3 2/4] ASoC: cdns: Add Cadence I2S-SC controller driver joakim.zhang
2026-10-09  9:37   ` sashiko-bot
2026-10-09  9:25 ` [PATCH v3 3/4] ASoC: dt-bindings: Add Cadence I2S-MC controller joakim.zhang
2026-10-09  9:25 ` [PATCH v3 4/4] ASoC: cdns: Add Cadence I2S-MC controller driver joakim.zhang
2026-10-09  9:38   ` sashiko-bot

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=20261009141528.GA1631855-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=joakim.zhang@cixtech.com \
    --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