From: sashiko-bot@kernel.org
To: Quchaosheng <quchaosheng000406@163.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/3] dt-bindings: display: ti,tpd12s015: Convert to DT schema
Date: Fri, 09 Oct 2026 11:14:27 +0000 [thread overview]
Message-ID: <sashiko-outbox-165335@kernel.org> (raw)
In-Reply-To: <20261009105601.301891-2-quchaosheng000406@163.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dt-bindings: display: ti,tpd12s015: gpios lacks minItems: 3 and is not required
--
commit 0e47bb58ccd4af1df6d3ff49895c7cf9fbc75cb8
Author: Chaosheng Qu <quchaosheng000406@163.com>
dt-bindings: display: ti,tpd12s015: Convert to DT schema
Convert the TPD12S015 HDMI level shifter binding to DT schema.
> diff --git a/Documentation/devicetree/bindings/display/ti/ti,tpd12s015.yaml b/Documentation/devicetree/bindings/display/ti/ti,tpd12s015.yaml
> new file mode 100644
> index 0000000000000..1927da3bd7361
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/display/ti/ti,tpd12s015.yaml
[ ... ]
> +properties:
> + compatible:
> + oneOf:
> + - const: ti,tpd12s015
> + - items:
> + - const: ti,tpd12s016
> + - const: ti,tpd12s015
> +
> + gpios:
> + description:
> + The CT CP HPD, LS OE and HPD GPIOs, in that order. The first controls
> + the level shifter, the second enables the level shifter outputs and
> + the third reads the hot-plug detect line.
> + maxItems: 3
[Severity: Low]
Does this schema accurately reflect the requirements for the GPIOs?
If a device tree node defines fewer than 3 GPIOs or omits the property
entirely, it will pass schema validation since maxItems is set to 3 without
minItems: 3, and gpios is omitted from the required block below.
However, both the DRM and FBDEV drivers unconditionally fetch index 2 (the
HPD GPIO) and fail probe if it is missing:
drivers/gpu/drm/bridge/ti-tpd12s015.c:tpd12s015_probe() {
...
gpio = devm_gpiod_get_index(&pdev->dev, NULL, 2, GPIOD_IN);
if (IS_ERR(gpio))
return PTR_ERR(gpio);
...
}
Should the schema include minItems: 3 under gpios and add gpios to the
required list to ensure device tree configurations that pass validation don't
silently fail during driver probe?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261009105601.301891-1-quchaosheng000406@163.com?part=1
next prev parent reply other threads:[~2026-10-09 11:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 10:55 [PATCH 0/3] dt-bindings: display: ti,tpd12s015: convert, and fix what the conversion exposed Quchaosheng
2026-10-09 10:55 ` [PATCH 1/3] dt-bindings: display: ti,tpd12s015: Convert to DT schema Quchaosheng
2026-10-09 11:14 ` sashiko-bot [this message]
2026-10-09 14:25 ` Conor Dooley
2026-10-09 14:44 ` Laurent Pinchart
2026-10-09 15:42 ` Conor Dooley
2026-10-09 17:34 ` Rob Herring
2026-10-10 0:48 ` Quchaosheng
2026-10-09 15:38 ` Rob Herring
2026-10-09 10:56 ` [PATCH 2/3] ARM: dts: ti/omap: drop the two unused gpios from the igep0050 hdmi encoder Quchaosheng
2026-10-09 10:56 ` [PATCH 3/3] ARM: dts: ti/omap: drop unit-address from tpd12s015 endpoints Quchaosheng
2026-10-09 11:03 ` [PATCH 0/3] dt-bindings: display: ti,tpd12s015: convert, and fix what the conversion exposed Laurent Pinchart
-- strict thread matches above, loose matches on Subject: below --
2026-10-09 10:54 Quchaosheng
2026-10-09 10:54 ` [PATCH 1/3] dt-bindings: display: ti,tpd12s015: Convert to DT schema Quchaosheng
2026-10-09 11:05 ` sashiko-bot
2026-10-09 10:53 [PATCH 0/3] dt-bindings: display: ti,tpd12s015: convert, and fix what the conversion exposed Quchaosheng
2026-10-09 10:53 ` [PATCH 1/3] dt-bindings: display: ti,tpd12s015: Convert to DT schema Quchaosheng
2026-10-09 11:03 ` sashiko-bot
2026-10-09 10:53 [PATCH 0/3] dt-bindings: display: ti,tpd12s015: convert, and fix what the conversion exposed Quchaosheng
2026-10-09 10:53 ` [PATCH 1/3] dt-bindings: display: ti,tpd12s015: Convert to DT schema Quchaosheng
2026-10-09 11:05 ` 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=sashiko-outbox-165335@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=quchaosheng000406@163.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox