From: sashiko-bot@kernel.org
To: "Stefano Radaelli" <stefano.radaelli21@gmail.com>
Cc: imx@lists.linux.dev, devicetree@vger.kernel.org, robh@kernel.org,
Frank.Li@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v2 03/11] ARM: dts: imx6ul: Add Variscite SoM and DART base files
Date: Sun, 27 Sep 2026 11:06:18 +0000 [thread overview]
Message-ID: <20260927110619.2ED1E1F00893@smtp.kernel.org> (raw)
In-Reply-To: <888149bd87b619a1706d3befefa5f873d746a9dc.1790413032.git.stefano.r@variscite.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Missing voltage constraints on touch_3v3_regulator break ADC scale
--
commit 1c2bc49be02f8a5da660fe024ca1908ba6a36cd7
Author: Stefano Radaelli <stefano.r@variscite.com>
ARM: dts: imx6ul: Add Variscite SoM and DART base files
Add shared DTSI files for the VAR-SOM-6UL and DART-6UL modules and
SoC-specific wrappers for i.MX6UL, i.MX6ULL and i.MX6ULZ.
Keep storage, audio and carrier options in separate DTSI files so
board variants can include the hardware assembled on each board.
> diff --git a/arch/arm/boot/dts/nxp/imx/imx6ul-imx6ull-var-dart.dtsi b/arch/arm/boot/dts/nxp/imx/imx6ul-imx6ull-var-dart.dtsi
> new file mode 100644
> index 0000000000000..3cbfea6e2b24c
> --- /dev/null
> +++ b/arch/arm/boot/dts/nxp/imx/imx6ul-imx6ull-var-dart.dtsi
> @@ -0,0 +1,205 @@
[ ... ]
> + touch_3v3_regulator: regulator-touch-3v3 {
> + compatible = "regulator-fixed";
> + regulator-name = "touch_3v3_supply";
> + regulator-always-on;
> + };
[Severity: Medium]
Does the missing voltage constraints here break the ADC scale?
Without regulator-min-microvolt and regulator-max-microvolt constraints,
the voltage is unknown and regulator_get_voltage() returns -EINVAL.
The vf610-adc driver stores this error code in an unsigned integer variable
(u32 vref_uv), causing an underflow to ~4.29 billion.
This garbage value is then exposed to userspace as the channel's scale when
reading in_voltageX_scale sysfs attributes, breaking functional ADC
measurements.
> diff --git a/arch/arm/boot/dts/nxp/imx/imx6ul-imx6ull-var-som.dtsi b/arch/arm/boot/dts/nxp/imx/imx6ul-imx6ull-var-som.dtsi
> new file mode 100644
> index 0000000000000..7c778adfeb13e
> --- /dev/null
> +++ b/arch/arm/boot/dts/nxp/imx/imx6ul-imx6ull-var-som.dtsi
> @@ -0,0 +1,201 @@
[ ... ]
> + touch_3v3_regulator: regulator-touch-3v3 {
> + compatible = "regulator-fixed";
> + regulator-name = "touch_3v3_supply";
> + regulator-always-on;
> + };
[Severity: Medium]
Does this duplicated definition also miss the voltage constraints and break
the ADC scale in the same way?
--
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1790413032.git.stefano.r@variscite.com?part=3
next prev parent reply other threads:[~2026-09-27 11:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-26 11:05 [PATCH v2 00/11] ARM: dts: imx6ul: Add Variscite VAR-SOM-6UL and DART-6UL Stefano Radaelli
2026-09-26 11:05 ` [PATCH v2 01/11] dt-bindings: arm: fsl: Document Variscite i.MX6UL boards Stefano Radaelli
2026-09-26 11:05 ` [PATCH v2 02/11] dt-bindings: net: micrel: Fix RMII clock select property type Stefano Radaelli
2026-09-26 11:05 ` [PATCH v2 03/11] ARM: dts: imx6ul: Add Variscite SoM and DART base files Stefano Radaelli
2026-09-27 11:06 ` sashiko-bot [this message]
2026-09-26 11:05 ` [PATCH v2 04/11] ARM: dts: imx6ul: Add Variscite audio codec files Stefano Radaelli
2026-09-26 11:05 ` [PATCH v2 05/11] ARM: dts: imx6ul: Add Variscite storage and wireless files Stefano Radaelli
2026-09-27 11:06 ` sashiko-bot
2026-09-26 11:05 ` [PATCH v2 06/11] ARM: dts: imx6ul: Add Variscite carrier board files Stefano Radaelli
2026-09-27 11:06 ` sashiko-bot
2026-09-26 11:05 ` [PATCH v2 07/11] ARM: dts: imx6ul: Reuse Variscite DTSI files for Concerto Stefano Radaelli
2026-09-27 11:06 ` sashiko-bot
2026-09-26 11:05 ` [PATCH v2 08/11] ARM: dts: imx6ul: Add Variscite i.MX6UL board variants Stefano Radaelli
2026-09-27 11:06 ` sashiko-bot
2026-09-26 11:05 ` [PATCH v2 09/11] ARM: dts: imx6ull: Add Variscite i.MX6ULL " Stefano Radaelli
2026-09-26 11:05 ` [PATCH v2 10/11] ARM: dts: imx6ulz: Add Variscite i.MX6ULZ " Stefano Radaelli
2026-09-27 11:06 ` sashiko-bot
2026-09-26 11:05 ` [PATCH v2 11/11] ARM: dts: imx6ul: Enable Variscite i.MX6UL board DTBs Stefano Radaelli
2026-09-27 11:06 ` sashiko-bot
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=20260927110619.2ED1E1F00893@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