From: sashiko-bot@kernel.org
To: "Stefano Radaelli" <stefano.radaelli21@gmail.com>
Cc: conor+dt@kernel.org, robh@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v1 3/4] arm64: dts: am62p5-var-som-symphony: add touchscreen support
Date: Sun, 28 Jun 2026 17:13:45 +0000 [thread overview]
Message-ID: <20260628171346.4C92C1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <8c1c298100af75da363ec03126c31fead6dba947.1782665899.git.stefano.r@variscite.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The commit message claims to configure both the interrupt and wakeup pins, but the device tree node and pinctrl only configure the interrupt pin, lacking a wakeup pin configuration.
--
commit 6d6b56a3161a61ca2f1a68dce1765826d0594c86
Author: Stefano Radaelli <stefano.radaelli21@gmail.com>
arm64: dts: am62p5-var-som-symphony: add touchscreen support
This commit adds support for the capacitive touchscreen on the Symphony
carrier board. It describes the FT5x06 touchscreen controller, configures
its pins, and marks it as a wakeup source.
> diff --git a/arch/arm64/boot/dts/ti/k3-am62p5-var-som-symphony.dts b/arch/arm64/boot/dts/ti/k3-am62p5-var-som-symphony.dts
> index 5ba4ed56755b4..5c41647ff43fa 100644
> --- a/arch/arm64/boot/dts/ti/k3-am62p5-var-som-symphony.dts
> +++ b/arch/arm64/boot/dts/ti/k3-am62p5-var-som-symphony.dts
[ ... ]
> @@ -293,6 +293,21 @@ &main_i2c1 {
> clock-frequency = <400000>;
> status = "okay";
>
> + /* Capacitive touch controller */
> + ft5x06_ts: touchscreen@38 {
> + compatible = "edt,edt-ft5206";
> + reg = <0x38>;
> + pinctrl-names = "default";
> + pinctrl-0 = <&pinctrl_captouch_pins>;
> + interrupt-parent = <&main_gpio1>;
> + interrupts = <16 IRQ_TYPE_EDGE_FALLING>;
> + touchscreen-size-x = <800>;
> + touchscreen-size-y = <480>;
> + touchscreen-inverted-x;
> + touchscreen-inverted-y;
> + wakeup-source;
> + };
[Severity: Medium]
The commit message claims to configure both the interrupt and wakeup pins,
but ft5x06_ts only configures the interrupt pin in its pinctrl.
Does this node also need a wake-gpios property to match the commit message
and properly wake the device from hibernation?
[ ... ]
> @@ -307,6 +322,12 @@ &main_mcan0 {
> };
>
> &main_pmx0 {
> + pinctrl_captouch_pins: main-captouch-default-pins {
> + pinctrl-single,pins = <
> + AM62PX_IOPAD(0x01b8, PIN_INPUT, 7) /* (E20) SPI0_CS1.GPIO1_16 */
> + >;
> + };
> +
--
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1782665899.git.stefano.r@variscite.com?part=3
next prev parent reply other threads:[~2026-06-28 17:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-28 17:06 [PATCH v1 0/4] arm64: dts: am62p5-var-som-symphony: align DTS with hardware revision Stefano Radaelli
2026-06-28 17:06 ` [PATCH v1 1/4] arm64: dts: ti: var-som-am62p: fix Ethernet PHY configuration Stefano Radaelli
2026-06-28 17:17 ` sashiko-bot
2026-06-28 17:06 ` [PATCH v1 2/4] arm64: dts: ti: var-som-am62p: update audio codec configuration Stefano Radaelli
2026-06-28 17:15 ` sashiko-bot
2026-06-28 17:06 ` [PATCH v1 3/4] arm64: dts: am62p5-var-som-symphony: add touchscreen support Stefano Radaelli
2026-06-28 17:13 ` sashiko-bot [this message]
2026-06-28 17:06 ` [PATCH v1 4/4] arm64: dts: am62p5-var-som-symphony: add TPM support Stefano Radaelli
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=20260628171346.4C92C1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=stefano.radaelli21@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.