From: Stefano Radaelli <stefano.radaelli21@gmail.com>
To: Frank Li <Frank.li@oss.nxp.com>
Cc: sashiko-reviews@lists.linux.dev, Frank.Li@kernel.org,
robh@kernel.org, imx@lists.linux.dev, conor+dt@kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v4 2/3] ARM: dts: imx7d: add Variscite VAR-SOM-MX7 support
Date: Tue, 25 Aug 2026 18:06:53 +0200 [thread overview]
Message-ID: <ao29neQwKSWlK4Lx@GLaDOS.station> (raw)
In-Reply-To: <ao2p-Yj1HfJeeVOM@SMW015318>
On Tue, Aug 25, 2026 at 09:43:05AM -0500, Frank Li wrote:
> >
> > [Severity: Medium]
> > Does this GPIO hog conflict with the native usdhc3 pinctrl configuration
> > for SD3_RESET_B?
> >
> > The sd3-pwr-hog statically claims gpio6 11, which corresponds to
> > MX7D_PAD_SD3_RESET_B. The pinctrl_usdhc3 later claims the exact same pad as
> > SD3_RESET_B in its native mode.
> >
>
> Is it true?
It's true, I'll fix it.
>
> > [Severity: High]
> > Does setting the sw1a maximum voltage to 3.3V violate the hardware limits
> > for the i.MX7D core voltage?
> >
> > The sw1a regulator supplies the cpu0 and cpu1 cores. The PFUZE3000 SW1A limit
> > for this design is typically around 1.475V, and the absolute maximum rating
> > for the i.MX7D ARM cores is usually around 1.15V.
> >
> > If a driver scales the core voltage up to 3.3V based on these boundaries,
> > could this result in hardware damage?
>
> Please double check this one?
>
I double-checked this.
PFUZE3000 SW1A supports selector values up to 3.3 V;
the 1.475V limit applies to SW1B, not SW1A.
The regulator-max-microvolt value only defines the regulator constraint,
while the actual CPU voltage is selected according to the i.MX7 OPP table.
Therefore, the 3.3 V constraint does not cause the CPU supply to be
driven to 3.3 V.
Best Regards,
Stefano
next prev parent reply other threads:[~2026-08-25 16:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 6:56 [PATCH v4 0/3] Add support for Variscite VAR-SOM-MX7 and MX7CustomBoard Stefano Radaelli
2026-08-25 6:56 ` [PATCH v4 1/3] dt-bindings: arm: fsl: add Variscite VAR-SOM-MX7 boards Stefano Radaelli
2026-08-25 6:56 ` [PATCH v4 2/3] ARM: dts: imx7d: add Variscite VAR-SOM-MX7 support Stefano Radaelli
2026-08-25 7:16 ` sashiko-bot
2026-08-25 14:43 ` Frank Li
2026-08-25 16:06 ` Stefano Radaelli [this message]
2026-08-25 6:56 ` [PATCH v4 3/3] ARM: dts: imx7d: add Variscite MX7CustomBoard 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=ao29neQwKSWlK4Lx@GLaDOS.station \
--to=stefano.radaelli21@gmail.com \
--cc=Frank.Li@kernel.org \
--cc=Frank.li@oss.nxp.com \
--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 \
/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