From: sashiko-bot@kernel.org
To: "David Heidelberg" <david@ixit.cz>
Cc: conor+dt@kernel.org, media-ci@linuxtv.org, robh@kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: media: i2c: dongwoon,dw9714: Document DW9714A and V variant
Date: Wed, 29 Jul 2026 22:03:10 +0000 [thread overview]
Message-ID: <20260729220310.90FDE1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260729-dw9714v-v1-1-3c479b3cf8c0@ixit.cz>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The YAML schema enforces a strict linear inheritance chain requiring the `dw9714v` compatible string to fall back to `dw9714a`, which contradicts the commit message implying they are parallel successors.
--
--- Patch [1]: [PATCH 1/2] dt-bindings: media: i2c: dongwoon,dw9714: Document DW9714A and V variant ---
commit 365235f208f468a1251293b975a2766eb66ab8bc
Author: David Heidelberg <david@ixit.cz>
dt-bindings: media: i2c: dongwoon,dw9714: Document DW9714A and V variant
This commit updates the device tree binding for the Dongwoon DW9714 to
document the DW9714A and DW9714V variants. It uses a oneOf structure to
allow the new successors as compatible strings.
> diff --git a/Documentation/devicetree/bindings/media/i2c/dongwoon,dw9714.yaml b/Documentation/devicetree/bindings/media/i2c/dongwoon,dw9714.yaml
> --- a/Documentation/devicetree/bindings/media/i2c/dongwoon,dw9714.yaml
> +++ b/Documentation/devicetree/bindings/media/i2c/dongwoon,dw9714.yaml
[ ... ]
> @@ -15,7 +15,15 @@ description:
>
> properties:
> compatible:
> - const: dongwoon,dw9714
> + oneOf:
> + - items:
> + - const: dongwoon,dw9714v
> + - const: dongwoon,dw9714a
> + - const: dongwoon,dw9714
[Severity: Medium]
The commit message states "Both of these successors are backward compatible",
implying that the DW9714A and DW9714V variants are parallel successors to
the base DW9714.
However, this schema enforces a linear 3-item inheritance chain requiring
dongwoon,dw9714v to fall back to dongwoon,dw9714a before dongwoon,dw9714.
If a devicetree node defines a 2-item fallback for the V variant like
"dongwoon,dw9714v", "dongwoon,dw9714", it will fail dt_binding_check
validation.
Should dongwoon,dw9714v be allowed to fall back directly to dongwoon,dw9714
as a 2-item list if they are parallel successors?
> + - items:
> + - const: dongwoon,dw9714a
> + - const: dongwoon,dw9714
> + - const: dongwoon,dw9714
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260729-dw9714v-v1-0-3c479b3cf8c0@ixit.cz?part=1
next prev parent reply other threads:[~2026-07-29 22:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 21:53 [PATCH 0/2] Enable DW9714V camera focus coil on SHIFT 6MQ David Heidelberg via B4 Relay
2026-07-29 21:53 ` David Heidelberg
2026-07-29 21:53 ` [PATCH 1/2] dt-bindings: media: i2c: dongwoon,dw9714: Document DW9714A and V variant David Heidelberg via B4 Relay
2026-07-29 21:53 ` David Heidelberg
2026-07-29 22:03 ` sashiko-bot [this message]
2026-07-29 21:53 ` [PATCH 2/2] arm64: dts: qcom: sdm845-shift-axolotl: Add actuator for main rear camera David Heidelberg via B4 Relay
2026-07-29 21:53 ` David Heidelberg
2026-07-29 22:08 ` 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=20260729220310.90FDE1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=david@ixit.cz \
--cc=devicetree@vger.kernel.org \
--cc=media-ci@linuxtv.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.