Linux clock framework development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Sascha Hauer" <s.hauer@pengutronix.de>
Cc: conor+dt@kernel.org, robh@kernel.org, linux-clk@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v9 1/2] dt-bindings: clock: add TI CDCE6214 binding
Date: Mon, 21 Sep 2026 06:57:08 +0000	[thread overview]
Message-ID: <20260921065708.72B961F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260921-clk-cdce6214-v9-1-f2ea74fd38a2@pengutronix.de>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] dt-bindings: invalid additionalProperties with $ref rejects inherited properties
--

commit 666b5411b0002edaa523fde47133ad3f08a2f5b5
Author: Sascha Hauer <s.hauer@pengutronix.de>

dt-bindings: clock: add TI CDCE6214 binding

This commit adds a device tree binding for the TI CDCE6214 clock generator.
It defines properties for clocks, pins, and specific IO configurations.

> diff --git a/Documentation/devicetree/bindings/clock/ti,cdce6214.yaml b/Documentation/devicetree/bindings/clock/ti,cdce6214.yaml
> new file mode 100644
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/clock/ti,cdce6214.yaml

[ ... ]

> +patternProperties:
> +  '-pins$':
> +    type: object
> +    additionalProperties: false
> +
> +    patternProperties:
> +      '^conf':
> +        type: object
> +        additionalProperties: false
> +        $ref: /schemas/pinctrl/pincfg-node.yaml#

[Severity: Medium]
Will this additionalProperties restriction reject the properties inherited from
the $ref schema?

In JSON Schema semantics, additionalProperties only considers the properties
explicitly enumerated in the local properties block. It does not evaluate
properties brought in by a $ref. 

Because of this, any attempt to use standard pinctrl properties in a device tree
will trigger a validation failure, as the local schema forcefully rejects them.

Should this use unevaluatedProperties: false instead to allow the standard
properties from pincfg-node.yaml to be evaluated properly?

[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260921-clk-cdce6214-v9-0-f2ea74fd38a2@pengutronix.de?part=1

  reply	other threads:[~2026-09-21  6:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-21  6:49 [PATCH v9 0/2] clk: add support for TI CDCE6214 Sascha Hauer
2026-09-21  6:49 ` [PATCH v9 1/2] dt-bindings: clock: add TI CDCE6214 binding Sascha Hauer
2026-09-21  6:57   ` sashiko-bot [this message]
2026-09-28  5:51   ` Krzysztof Kozlowski
2026-09-21  6:50 ` [PATCH v9 2/2] clk: add TI CDCE6214 clock driver Sascha Hauer
2026-09-21  7:01   ` sashiko-bot
2026-09-25  9:54   ` Jerome Brunet
2026-09-29 10:43     ` Sascha Hauer
2026-10-05 15:15       ` Jerome Brunet

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=20260921065708.72B961F00893@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --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