From: sashiko-bot@kernel.org
To: "Frieder Schrempf" <frieder@fris.de>
Cc: devicetree@vger.kernel.org, imx@lists.linux.dev, robh@kernel.org,
conor+dt@kernel.org, Frank.Li@kernel.org
Subject: Re: [PATCH 3/8] arm64: dts: imx8mp-kontron: Remove obsolete VDD_CARRIER regulator
Date: Tue, 13 Oct 2026 10:04:22 +0000 [thread overview]
Message-ID: <sashiko-outbox-169447@kernel.org> (raw)
In-Reply-To: <20261013-upstreaming-gpio-label-fixes-v1-3-94f09ec520ef@kontron.de>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dts: Stale CARRIER_PWR_EN label in carrier board gpio-line-names overrides
--
commit b5bf4333f3ce6c5ca93d4fd597b09395c78fe9b7
Author: Eberhard Stoll <eberhard.stoll@kontron.de>
arm64: dts: imx8mp-kontron: Remove obsolete VDD_CARRIER regulator
This commit removes the VDD_CARRIER regulator from the Kontron OSM-S i.MX8MP
SoM devicetree. It also renames the CARRIER_PWR_EN gpio line to GPIO_C_1, as
the signal is now controlled by hardware on regular revisions rather than
software.
> diff --git a/arch/arm64/boot/dts/freescale/imx8mp-kontron-osm-s.dtsi b/arch/arm64/boot/dts/freescale/imx8mp-kontron-osm-s.dtsi
> index 3459ee2c0eb64..4fd42e7170ee8 100644
> --- a/arch/arm64/boot/dts/freescale/imx8mp-kontron-osm-s.dtsi
> +++ b/arch/arm64/boot/dts/freescale/imx8mp-kontron-osm-s.dtsi
[ ... ]
> @@ -185,7 +162,7 @@ &gpio4 {
> "GPIO_B_3", "GPIO_B_4",
> "GPIO_B_2", "GPIO_A_6", "CAN_A_TX", "UART_A_CTS",
> "UART_A_RTS", "CAN_A_RX", "CAN_B_TX", "CAN_B_RX",
> - "I2S_B_DATA_IN", "CARRIER_PWR_EN", "I2S_A_DATA_IN", "I2S_B_DATA_OUT";
> + "I2S_B_DATA_IN", "GPIO_C_1", "I2S_A_DATA_IN", "I2S_B_DATA_OUT";
> };
[Severity: Low]
Is this rename incomplete? While "CARRIER_PWR_EN" is updated to "GPIO_C_1"
here in the SoM's &gpio4 node, the carrier boards provide their own
gpio-line-names overrides for &gpio4 which still hardcode the old name.
For the BL OSM-S carrier board:
arch/arm64/boot/dts/freescale/imx8mp-kontron-bl-osm-s.dts:&gpio4 {
...
gpio-line-names = "CAN_B_RX", "CAN_B_TX", "CAN_A_RX", "CAN_A_TX",
...
"TFT_STBY", "CARRIER_PWR_EN", "I2S_A_DATA_IN", "I2S_LRCLK";
}
And similarly for the SMARC carrier board:
arch/arm64/boot/dts/freescale/imx8mp-kontron-smarc.dtsi:&gpio4 {
...
gpio-line-names = "", "", "", "",
...
"TEST", "CARRIER_PWR_EN", "I2S0_SDIN", "I2S0_LRCK";
}
Since the board-level overrides remain, the old label is still exported to
userspace on these boards. Does this defeat the purpose of the rename for
those devices?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261013-upstreaming-gpio-label-fixes-v1-0-94f09ec520ef@kontron.de?part=3
next prev parent reply other threads:[~2026-10-13 10:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 9:44 [PATCH 0/8] arm64: dts: Kontron i.MX OSM GPIO Label Fixes Frieder Schrempf
2026-10-13 9:44 ` [PATCH 1/8] arm64: dts: imx8mp-kontron: Fix GPIO label assignments Frieder Schrempf
2026-10-13 9:44 ` [PATCH 2/8] arm64: dts: imx8mp-kontron: Fix GPIO labels according to OSM spec Frieder Schrempf
2026-10-13 9:44 ` [PATCH 3/8] arm64: dts: imx8mp-kontron: Remove obsolete VDD_CARRIER regulator Frieder Schrempf
2026-10-13 10:04 ` sashiko-bot [this message]
2026-10-13 9:44 ` [PATCH 4/8] arm64: dts: imx8mm-kontron: Fix wrong label for SPI_A_SDI_(IO0) pad Frieder Schrempf
2026-10-13 9:44 ` [PATCH 5/8] arm64: dts: imx8mm-kontron: Fix GPIO label for PCIe_SM_ALERT# Frieder Schrempf
2026-10-13 9:44 ` [PATCH 6/8] arm64: dts: imx93-kontron: Fix ETH_B_TXD GPIO labels Frieder Schrempf
2026-10-13 9:44 ` [PATCH 7/8] arm64: dts: imx93-kontron: Fix UART RTS/CTS pad names Frieder Schrempf
2026-10-13 9:44 ` [PATCH 8/8] arm64: dts: imx93-kontron: Fix GPIO labels according to OSM spec Frieder Schrempf
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-169447@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frieder@fris.de \
--cc=imx@lists.linux.dev \
--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