From: sashiko-bot@kernel.org
To: "Stefano Radaelli" <stefano.radaelli21@gmail.com>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org,
Frank.Li@kernel.org, robh@kernel.org, imx@lists.linux.dev
Subject: Re: [PATCH v1 10/12] arm64: dts: imx8mp-var-som-symphony: keep RGB_SEL low
Date: Wed, 03 Jun 2026 12:04:46 +0000 [thread overview]
Message-ID: <20260603120446.DEA0D1F00893@smtp.kernel.org> (raw)
In-Reply-To: <642c165fa5ce0951352d7d164ae7d871120e8631.1780487415.git.stefano.r@variscite.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The gpio-hog DT node is named 'lvds-brg-enable-hog' while the line-name and comments refer to 'rgb_sel'. This mismatch creates confusion regarding the hardware's actual configuration and may be a copy-paste error.
--
commit 1f0ff0206f69fa2f47bd286b774f7b26db9168ed
Author: Stefano Radaelli <stefano.r@variscite.com>
arm64: dts: imx8mp-var-som-symphony: keep RGB_SEL low
This commit drives the RGB_SEL line low on the Symphony carrier board.
It ensures the board remains in the expected display configuration rather
than leaving the line floating.
> diff --git a/arch/arm64/boot/dts/freescale/imx8mp-var-som-symphony.dts b/arch/arm64/boot/dts/freescale/imx8mp-var-som-symphony.dts
> index df4409af26a26..d796c32f50cc6 100644
> --- a/arch/arm64/boot/dts/freescale/imx8mp-var-som-symphony.dts
> +++ b/arch/arm64/boot/dts/freescale/imx8mp-var-som-symphony.dts
> @@ -191,6 +191,14 @@ pcal6408: gpio@21 {
> reg = <0x21>;
> #gpio-cells = <2>;
> gpio-controller;
> +
> + /* RGB_SEL */
> + lvds-brg-enable-hog {
[Severity: Low]
This isn't a bug, but is the node name lvds-brg-enable-hog intentional here?
The comment and line-name both refer to rgb_sel. Naming the node
lvds-brg-enable-hog creates a mismatch that looks like it might be a
leftover from a copy-paste.
> + gpio-hog;
> + gpios = <7 GPIO_ACTIVE_HIGH>;
> + output-low;
> + line-name = "rgb_sel";
> + };
> };
--
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1780487415.git.stefano.r@variscite.com?part=10
next prev parent reply other threads:[~2026-06-03 12:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 11:55 [PATCH v1 00/12] arm64: dts: imx8mp-var-som-symphony: align DTS with hardware revision Stefano Radaelli
2026-06-03 11:55 ` [PATCH v1 01/12] arm64: dts: imx8mp-var-som-symphony: add input keys Stefano Radaelli
2026-06-03 11:55 ` [PATCH v1 02/12] arm64: dts: imx8mp-var-som-symphony: enable USB support Stefano Radaelli
2026-06-03 12:14 ` sashiko-bot
2026-06-03 11:55 ` [PATCH v1 03/12] arm64: dts: imx8mp-var-som-symphony: add TPM support Stefano Radaelli
2026-06-03 11:55 ` [PATCH v1 04/12] arm64: dts: imx8mp-var-som-symphony: add external RTC Stefano Radaelli
2026-06-03 11:55 ` [PATCH v1 05/12] arm64: dts: imx8mp-var-som-symphony: enable header UARTs Stefano Radaelli
2026-06-03 11:55 ` [PATCH v1 06/12] arm64: dts: imx8mp-var-som-symphony: enable PCIe Stefano Radaelli
2026-06-03 12:14 ` sashiko-bot
2026-06-03 11:55 ` [PATCH v1 07/12] arm64: dts: imx8mp-var-som-symphony: add HDMI support Stefano Radaelli
2026-06-03 12:13 ` sashiko-bot
2026-06-03 11:55 ` [PATCH v1 08/12] arm64: dts: imx8mp-var-som-symphony: add capacitive touchscreen Stefano Radaelli
2026-06-03 11:55 ` [PATCH v1 09/12] arm64: dts: imx8mp-var-som-symphony: enable ECSPI2 Stefano Radaelli
2026-06-03 11:55 ` [PATCH v1 10/12] arm64: dts: imx8mp-var-som-symphony: keep RGB_SEL low Stefano Radaelli
2026-06-03 12:04 ` sashiko-bot [this message]
2026-06-03 11:55 ` [PATCH v1 11/12] arm64: dts: imx8mp-var-som-symphony: enable PWM1 Stefano Radaelli
2026-06-03 11:55 ` [PATCH v1 12/12] arm64: dts: freescale: imx8mp-var-som: add I2C1 bus recovery GPIOs 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=20260603120446.DEA0D1F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox