Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Hyunuk Son" <hyunuk.son@irondevice.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 1/2] ASoC: dt-bindings: Add Iron Device MA5311
Date: Thu, 15 Oct 2026 06:09:08 +0000	[thread overview]
Message-ID: <sashiko-outbox-172330@kernel.org> (raw)
In-Reply-To: <20261015060408.128711-2-hyunuk.son@irondevice.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dt-bindings: additionalProperties: false with allOf breaks inherited properties
--

commit 28fede9028d5369d7e76bfe368a2b05ad5391a52
Author: Hyunuk Son <hyunuk.son@irondevice.com>

ASoC: dt-bindings: Add Iron Device MA5311
    
Add a Device Tree binding for the Iron Device MA5311 audio codec.

> diff --git a/Documentation/devicetree/bindings/sound/irondevice,ma5311.yaml b/Documentation/devicetree/bindings/sound/irondevice,ma5311.yaml
> new file mode 100644
> index 0000000000000..ae4a13c2981ab
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/sound/irondevice,ma5311.yaml
> @@ -0,0 +1,69 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/sound/irondevice,ma5311.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#

[ ... ]

> +allOf:
> +  - $ref: dai-common.yaml#
> +
> +properties:

[ ... ]

> +required:
> +  - compatible
> +  - reg
> +  - reg-names
> +  - '#sound-dai-cells'
> +
> +additionalProperties: false

[Severity: Low]
Because this schema includes dai-common.yaml# in its allOf block, will
additionalProperties: false incorrectly reject standard DAI properties?

In JSON schema, additionalProperties: false only evaluates explicitly defined
properties in the local properties dictionary, ignoring properties brought in
via a $ref. This causes make dt_binding_check to fail with "additional
property is not allowed" errors when valid common DAI properties are used
in the device tree.

Should this use unevaluatedProperties: false instead, as documented in
writing-schema.rst?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261015060408.128711-1-hyunuk.son@irondevice.com?part=1

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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-15  6:04 [PATCH 0/2] ASoC: Add driver for Iron Device MA5311 Hyunuk Son
2026-10-15  6:04 ` [PATCH 1/2] ASoC: dt-bindings: Add " Hyunuk Son
2026-10-15  6:09   ` sashiko-bot [this message]
2026-10-15 10:36   ` Krzysztof Kozlowski
2026-10-15  6:04 ` [PATCH 2/2] ASoC: codecs: Add driver for " Hyunuk Son
2026-10-15  6:14   ` sashiko-bot
2026-10-15 10:41   ` 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=sashiko-outbox-172330@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=hyunuk.son@irondevice.com \
    --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