From: sashiko-bot@kernel.org
To: "Marek Vasut" <marek.vasut+renesas@mailbox.org>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org,
wsa+renesas@sang-engineering.com,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 1/4] dt-bindings: display: panel: Document 10" Raspberry Pi Touch Display 2
Date: Thu, 20 Aug 2026 19:05:26 +0000 [thread overview]
Message-ID: <20260820190527.08C9B1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260820185506.84448-1-marek.vasut+renesas@mailbox.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Adding `raspberrypi,dsi-10inch` without conditional blocks unconditionally forces incorrect hardware constraints (discrete supplies and enable-gpios) onto the new panel variant.
--
--- Patch [1]: [PATCH v2 1/4] dt-bindings: display: panel: Document 10" Raspberry Pi Touch Display 2 ---
commit 2739ad573af941325eae5c172cd4464d44cc6055
Author: Marek Vasut <marek.vasut+renesas@mailbox.org>
dt-bindings: display: panel: Document 10" Raspberry Pi Touch Display 2
This commit documents the 10" Raspberry Pi Touch Display 2 MIPI-DSI TFT
LCD panel. The panel is based on the Ilitek ILI79600A controller.
> diff --git a/Documentation/devicetree/bindings/display/panel/ilitek,il79900a.yaml b/Documentation/devicetree/bindings/display/panel/ilitek,il79900a.yaml
> index 02f7fb1f16dc7..f8644e9a4478d 100644
> --- a/Documentation/devicetree/bindings/display/panel/ilitek,il79900a.yaml
> +++ b/Documentation/devicetree/bindings/display/panel/ilitek,il79900a.yaml
> @@ -14,10 +14,15 @@ allOf:
>
> properties:
> compatible:
> - items:
> - - enum:
> - - tianma,tl121bvms07-00
> - - const: ilitek,il79900a
> + oneOf:
> + - items:
> + - enum:
> + - raspberrypi,dsi-10inch
> + - const: ilitek,ili79600a
[Severity: Medium]
Will this unconditionally force incorrect hardware constraints onto the new
panel variant?
Adding the compatible string here causes the raspberrypi,dsi-10inch panel
to inherit the global required properties present later in this file:
required:
- compatible
- reg
- enable-gpios
- avdd-supply
- avee-supply
- pp1800-supply
If device trees omit enable-gpios or the discrete supplies for this new
hardware variant, will they incorrectly fail dtbs_check schema validation?
Should the binding use conditional blocks to handle the different required
properties for each hardware variant?
> + - items:
> + - enum:
> + - tianma,tl121bvms07-00
> + - const: ilitek,il79900a
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260820185506.84448-1-marek.vasut+renesas@mailbox.org?part=1
prev parent reply other threads:[~2026-08-20 19:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 18:54 [PATCH v2 1/4] dt-bindings: display: panel: Document 10" Raspberry Pi Touch Display 2 Marek Vasut
2026-08-20 18:54 ` [PATCH v2 2/4] drm/panel: ilitek-ili9882t: Make enable GPIO optional Marek Vasut
2026-08-20 18:54 ` [PATCH v2 3/4] drm/panel: ilitek-ili9882t: Set prepare_prev_first Marek Vasut
2026-08-20 18:54 ` [PATCH v2 4/4] drm/panel: ilitek-ili9882t: Add support for Ilitek ILI79600A-based panels Marek Vasut
2026-08-20 19:05 ` sashiko-bot [this message]
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=20260820190527.08C9B1F000E9@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=marek.vasut+renesas@mailbox.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 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.