Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Stefano Radaelli" <stefano.radaelli21@gmail.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org,
	Frank.Li@kernel.org, imx@lists.linux.dev, robh@kernel.org
Subject: Re: [PATCH v1 2/2] arm64: dts: imx8mm-var-som-symphony: keep RGB_SEL low
Date: Wed, 03 Jun 2026 22:59:29 +0000	[thread overview]
Message-ID: <20260603225929.DD9A81F00893@smtp.kernel.org> (raw)
In-Reply-To: <55fb7ba8f5249a0be5296a0b3523ce20a668a89e.1780527068.git.stefano.r@variscite.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The newly added gpio-hog node is named `lvds-brg-enable-hog`, but it is documented to control the `RGB_SEL` line and its `line-name` property is set to `rgb_sel`. This is likely a copy-paste error.
--

commit 9c97f65e1888df2bd494aacf3412a0fd8cf0a5db
Author: Stefano Radaelli <stefano.r@variscite.com>

arm64: dts: imx8mm-var-som-symphony: keep RGB_SEL low

This commit drives the RGB_SEL line low on the Symphony carrier board.
It does this by adding a gpio-hog subnode to the pca6408 GPIO controller
to ensure the board remains in the expected display configuration.

> diff --git a/arch/arm64/boot/dts/freescale/imx8mm-var-som-symphony.dts b/arch/arm64/boot/dts/freescale/imx8mm-var-som-symphony.dts
> --- a/arch/arm64/boot/dts/freescale/imx8mm-var-som-symphony.dts
> +++ b/arch/arm64/boot/dts/freescale/imx8mm-var-som-symphony.dts
> @@ -168,6 +168,14 @@ pca6408: gpio@21 {
>  		reg = <0x21>;
>  		gpio-controller;
>  		#gpio-cells = <2>;
> +
> +		/* RGB_SEL */
> +		lvds-brg-enable-hog {

[Severity: Low]
This isn't a bug, but is this node name a copy-paste error? It is documented
to control RGB_SEL and sets the line-name to "rgb_sel", so a name like
rgb-sel-hog might be more appropriate to avoid confusion.

> +			gpio-hog;
> +			gpios = <7 GPIO_ACTIVE_HIGH>;
> +			output-low;
> +			line-name = "rgb_sel";
> +		};
>  	};

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1780527068.git.stefano.r@variscite.com?part=2

      reply	other threads:[~2026-06-03 22:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-03 22:53 [PATCH v1 0/2] arm64: dts: imx8mm-var-som-symphony: minor board updates Stefano Radaelli
2026-06-03 22:53 ` [PATCH v1 1/2] arm64: dts: imx8mm-var-som-symphony: add wakeup sources Stefano Radaelli
2026-06-03 22:54 ` [PATCH v1 2/2] arm64: dts: imx8mm-var-som-symphony: keep RGB_SEL low Stefano Radaelli
2026-06-03 22:59   ` 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=20260603225929.DD9A81F00893@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