From: sashiko-bot@kernel.org
To: "Lukas Timmermann" <foss@timmermann.space>
Cc: dmitry.torokhov@gmail.com, robh@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: [PATCH 1/7] dt-bindings: input: touchscreen: samsung,s6sy761: Add S6SY791 and reset GPIO
Date: Sun, 11 Oct 2026 12:53:36 +0000 [thread overview]
Message-ID: <sashiko-outbox-167228@kernel.org> (raw)
In-Reply-To: <20261011-lat3st-google-raven-touch-upstream-v1-1-2a9f55159b9e@timmermann.space>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dt-bindings: unconditional SPI properties allow I2C variant to pass with invalid properties
--
commit ea887456e038f98ac0c943c8af10e4e502dc0827
Author: Lukas Timmermann <foss@timmermann.space>
dt-bindings: input: touchscreen: samsung,s6sy761: Add S6SY791 and reset GPIO
This patch adds the S6SY791 SPI-based touchscreen controller as a variant
alongside the existing I2C-based S6SY761. It also adds support for an optional
reset GPIO and references spi-peripheral-props for the SPI bus properties.
> diff --git a/Documentation/devicetree/bindings/input/touchscreen/samsung,s6sy761.yaml b/Documentation/devicetree/bindings/input/touchscreen/samsung,s6sy761.yaml
> index 1ffd17af3c53f..d24f35038934a 100644
> --- a/Documentation/devicetree/bindings/input/touchscreen/samsung,s6sy761.yaml
> +++ b/Documentation/devicetree/bindings/input/touchscreen/samsung,s6sy761.yaml
> @@ -8,13 +8,17 @@ title: Samsung S6SY761 touchscreen controller
>
> maintainers:
> - Andi Shyti <andi.shyti@kernel.org>
> + - Lukas Timmermann <foss@timmermann.space>
>
> allOf:
> - $ref: touchscreen.yaml#
> + - $ref: /schemas/spi/spi-peripheral-props.yaml#
[Severity: Low]
Does this allow the I2C variant to pass validation with invalid properties?
By unconditionally referencing spi-peripheral-props.yaml in the global allOf
list, device trees for the I2C variant (samsung,s6sy761) can now include SPI
properties and silently pass schema validation.
Should this $ref be moved to an if-then block that matches only the
samsung,s6sy791 compatible string?
[ ... ]
> avdd-supply: true
> vdd-supply: true
>
> + spi-max-frequency: true
> +
> + spi-cpha: true
> +
> + spi-cpol: true
> +
[Severity: Low]
Similarly, these SPI properties are added at the top-level. Does this globally
permit them for both interfaces, defeating the unevaluatedProperties: false
check for the I2C variant?
Could these properties be restricted to the samsung,s6sy791 variant using an
if-then block?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261011-lat3st-google-raven-touch-upstream-v1-0-2a9f55159b9e@timmermann.space?part=1
next prev parent reply other threads:[~2026-10-11 12:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-11 12:44 [PATCH 0/7] Input: s6sy761 - add SPI support for the S6SY791 Lukas Timmermann
2026-10-11 12:44 ` [PATCH 1/7] dt-bindings: input: touchscreen: samsung,s6sy761: Add S6SY791 and reset GPIO Lukas Timmermann
2026-10-11 12:53 ` sashiko-bot [this message]
2026-10-12 11:30 ` Krzysztof Kozlowski
2026-10-11 12:44 ` [PATCH 2/7] Input: s6sy761 - split into core and I2C modules Lukas Timmermann
2026-10-11 12:57 ` sashiko-bot
2026-10-12 11:04 ` Uwe Kleine-König
2026-10-11 12:44 ` [PATCH 3/7] Input: s6sy761 - add reset GPIO support Lukas Timmermann
2026-10-11 12:58 ` sashiko-bot
2026-10-11 12:44 ` [PATCH 4/7] Input: s6sy761 - add SPI support for S6SY791 Lukas Timmermann
2026-10-11 13:02 ` sashiko-bot
2026-10-11 12:45 ` [PATCH 5/7] arm64: dts: exynos: gs101-pixel-common: add labels for touchscreen supplies Lukas Timmermann
2026-10-11 12:45 ` [PATCH 6/7] arm64: dts: exynos: gs101-raven: add S6SY791 touchscreen Lukas Timmermann
2026-10-11 12:45 ` [PATCH 7/7] MAINTAINERS: add entry for Samsung S6SY761 touchscreen driver Lukas Timmermann
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-167228@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=foss@timmermann.space \
--cc=linux-input@vger.kernel.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.