All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Aaron Kling" <webgeek1234@gmail.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org,
	dri-devel@lists.freedesktop.org, conor+dt@kernel.org
Subject: Re: [PATCH v2 1/4] dt-bindings: display: visionox,vtdr6130: Add Retroid Pocket 6 panel
Date: Fri, 25 Sep 2026 07:12:38 +0000	[thread overview]
Message-ID: <20260925071239.09DF11F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260925-rp6-panel-v2-1-19c425e523de@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] dt-bindings: vdd-supply validation dropped for visionox,vtdr6130
--

commit a3a48cee05612d79cd6eb27b26e83813b38aff64
Author: Aaron Kling <webgeek1234@gmail.com>

dt-bindings: display: visionox,vtdr6130: Add Retroid Pocket 6 panel

The vtdr6130 is a display driver integrated circuit, a common chip used
for various panels. One such panel is used in the Retroid Pocket 6.

> diff --git a/Documentation/devicetree/bindings/display/panel/visionox,vtdr6130.yaml b/Documentation/devicetree/bindings/display/panel/visionox,vtdr6130.yaml
> index c99f4146f1bb0..682f30dc9ee43 100644
> --- a/Documentation/devicetree/bindings/display/panel/visionox,vtdr6130.yaml
> +++ b/Documentation/devicetree/bindings/display/panel/visionox,vtdr6130.yaml

[ ... ]

> @@ -25,13 +29,13 @@ properties:
>    vdd-supply: true
>    port: true
>    reset-gpios: true
> +  rotation: true
>  
>  required:
>    - compatible
>    - reg
>    - vddio-supply
>    - vci-supply
> -  - vdd-supply

[Severity: Medium]
By dropping vdd-supply globally from the required list, does this cause
incomplete schema validation for the original visionox,vtdr6130 hardware?

Device trees using compatible = "visionox,vtdr6130" might now erroneously
omit the previously required vdd-supply property and silently pass schema
validation.

Should this be solved using an allOf and if-then block to conditionally
require vdd-supply only for the original hardware?

>    - reset-gpios
>    - port
>

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260925-rp6-panel-v2-0-19c425e523de@gmail.com?part=1

  reply	other threads:[~2026-09-25  7:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-25  7:08 [PATCH v2 0/4] drm/panel: Support Retroid Pocket 6 panel Aaron Kling via B4 Relay
2026-09-25  7:08 ` Aaron Kling
2026-09-25  7:08 ` [PATCH v2 1/4] dt-bindings: display: visionox,vtdr6130: Add " Aaron Kling via B4 Relay
2026-09-25  7:08   ` Aaron Kling
2026-09-25  7:12   ` sashiko-bot [this message]
2026-09-25  7:08 ` [PATCH v2 2/4] drm/panel: visionox-vtdr6130: Add panel orientation support Aaron Kling via B4 Relay
2026-09-25  7:08   ` Aaron Kling
2026-09-25  7:08 ` [PATCH v2 3/4] drm/panel: visionox-vtdr6130: Modularize panel config Aaron Kling via B4 Relay
2026-09-25  7:08   ` Aaron Kling
2026-09-25  7:15   ` sashiko-bot
2026-09-25  8:48   ` Neil Armstrong
2026-09-25  7:08 ` [PATCH v2 4/4] drm/panel: visionox-vtdr6130: Add Retroid Pocket 6 panel Aaron Kling via B4 Relay
2026-09-25  7:08   ` Aaron Kling
2026-09-25  7:16   ` sashiko-bot
2026-10-02  9:16 ` [PATCH v2 0/4] drm/panel: Support " Neil Armstrong

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=20260925071239.09DF11F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=webgeek1234@gmail.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 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.