From: sashiko-bot@kernel.org
To: "Neil Armstrong" <neil.armstrong@linaro.org>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org,
wsa+renesas@sang-engineering.com, robh@kernel.org
Subject: Re: [PATCH v6 1/2] dt-bindings: display: panel: document the Renesas R63419 based dual-DSI video mode Display Panels
Date: Fri, 22 May 2026 13:00:18 +0000 [thread overview]
Message-ID: <20260522130018.C999A1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260522-topic-sm8650-ayaneo-pocket-s2-r63419-v6-1-16edddda9951@linaro.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Incorrect use of `additionalProperties: false` with a `$ref` to a common schema, causing validation failures for standard properties.
--
commit d5d9023fc9149b85c30a89eb9e658f1d3b246c85
Author: Neil Armstrong <neil.armstrong@linaro.org>
dt-bindings: display: panel: document the Renesas R63419 based dual-DSI video mode Display Panels
This commit documents the Renesas R63419 generic display driver IC used to
control dual-DSI LCD panels. It introduces a new YAML binding schema for
devices such as the Ayaneo gaming handheld panels.
> diff --git a/Documentation/devicetree/bindings/display/panel/renesas,r63419.yaml b/Documentation/devicetree/bindings/display/panel/renesas,r63419.yaml
> new file mode 100644
> index 0000000000000..adfdd2c300a35
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/display/panel/renesas,r63419.yaml
[ ... ]
> +allOf:
> + - $ref: panel-common-dual.yaml#
> +
> +properties:
> + compatible:
[ ... ]
> + vdd-supply: true
> + vddio-supply: true
> + vsp-supply: true
> + vsn-supply: true
> + vci-supply: true
> +
> + backlight: true
> + reset-gpios: true
> + rotation: true
> + ports: true
> +
> +required:
> + - compatible
> + - reg
> + - vdd-supply
> + - vddio-supply
> + - vsp-supply
> + - vsn-supply
> + - vci-supply
> + - backlight
> + - reset-gpios
> + - ports
> +
> +additionalProperties: false
[Severity: Low]
Should unevaluatedProperties: false be used here instead of
additionalProperties: false?
Because this schema includes a reference to panel-common-dual.yaml in an
allOf block, additionalProperties only considers the properties explicitly
declared in this local file. This requires redundantly redeclaring standard
properties like backlight, reset-gpios, rotation, and ports to prevent
validation errors during dtbs_check.
Using unevaluatedProperties: false would properly evaluate against the
referenced schemas and allow removing the redundant property declarations.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260522-topic-sm8650-ayaneo-pocket-s2-r63419-v6-0-16edddda9951@linaro.org?part=1
next prev parent reply other threads:[~2026-05-22 13:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 12:51 [PATCH v6 0/2] drm: panel: support the R63419 based dual-DSI video mode Display Panels Neil Armstrong
2026-05-22 12:51 ` [PATCH v6 1/2] dt-bindings: display: panel: document the Renesas " Neil Armstrong
2026-05-22 13:00 ` sashiko-bot [this message]
2026-05-22 12:51 ` [PATCH v6 2/2] drm: panel: add support for " Neil Armstrong
2026-05-22 13:17 ` 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=20260522130018.C999A1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=wsa+renesas@sang-engineering.com \
/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