From: Michael Walle <michael@walle.cc>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: Heiko Thiery <heiko.thiery@gmail.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Fabio Estevam <festevam@gmail.com>,
Shengjiu Wang <shengjiu.wang@nxp.com>,
Joakim Zhang <qiangqing.zhang@nxp.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
NXP Linux Team <linux-imx@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>
Subject: Re: [PATCH v2] arm64: dts: imx8mq-kontron-pitx-imx8m: remove vqmmc-supply node
Date: Tue, 14 Sep 2021 11:12:43 +0200 [thread overview]
Message-ID: <9e3d52c297ed024594a1e610a5cf61b2@walle.cc> (raw)
In-Reply-To: <2dc72116ec935a5a5d7a1a176868b7af7ff3227c.camel@pengutronix.de>
Am 2021-09-14 10:52, schrieb Lucas Stach:
> Am Dienstag, dem 14.09.2021 um 10:32 +0200 schrieb Michael Walle:
>> Hi Lucas,
>>
>> Am 2021-09-14 10:20, schrieb Lucas Stach:
>> > Am Dienstag, dem 14.09.2021 um 09:26 +0200 schrieb Heiko Thiery:
>> > > The sw4 output (V_1V8_S0 voltage) from the PMIC is the main supply for
>> > > the 1V8 power domain. It is not only used as supply for the eMMC.
>> > > So this voltage can not be changed and is not allowed to switched off.
>> > > Therefore we do not want to provide this regulator to the SDHC driver
>> > > to
>> > > control this voltage.
>> > >
>> > This specific requirement should not be solved by removing the
>> > regulator connection from the SDHCI node, but instead by constraining
>> > the regulator voltage range to a fixed 3.3V and marking the regulator
>> > as always-on to reflect the hardware requirements in the DT.
>> >
>> > Also if your eMMC vqmmc is a fixed 3.3V, I don't think you need the
>> > faster pinctrl states, as you can't use the faster pin states anyways,
>> > as they require a 1.8V signaling voltage.
>>
>> Are you speaking of the 1.8V signalling modes? As far as I know the
>> IMX SDHC controller will switch the voltage by its own function pin.
>> That is, its not a GPIO.
>
> Ah, I mixed things up here. This is a fixed 1.8V supply, which is valid
> for eMMC, so the high-speed modes are available. My comment still
> applies that this should be fixed by constraining the regulator, not by
> removing the DT connection.
>
> vqmmc is the MMC IO voltage, which can be switched either by the
> function pin, which gets toggled automatically when software does the
> voltage switch, or by explicitly switching the regulator voltage. eMMCs
> are a bit special as they can work with a fixed 1.8V IO supply and
> don't need to start with 3.3V.
I tend to agree. There might be some useful information, like the driver
could fetch the voltage although it is not able to change it.
NB. the regulator is already fixed at 1.8V and is marked as always on.
from arch/arm64/boot/dts/freescale/imx8mq-kontron-pitx-imx8m.dts:
sw4_reg: sw4 {
regulator-name = "V_1V8_S0";
regulator-min-microvolt = <1800000>;
regulator-max-microvolt = <1800000>;
regulator-always-on;
};
-michael
next prev parent reply other threads:[~2021-09-14 9:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 7:26 [PATCH v2] arm64: dts: imx8mq-kontron-pitx-imx8m: remove vqmmc-supply node Heiko Thiery
2021-09-14 8:20 ` Lucas Stach
2021-09-14 8:32 ` Michael Walle
2021-09-14 8:52 ` Lucas Stach
2021-09-14 9:12 ` Michael Walle [this message]
2021-09-14 9:37 ` Heiko Thiery
2023-12-12 13:41 ` Uwe Kleine-König
[not found] ` <CAEyMn7Y_ZsGQjKJtFn6zuqzRzUzf_ueSi7JWhjOX0zeDsBzM8w@mail.gmail.com>
2023-12-12 15:58 ` Uwe Kleine-König
2021-09-14 9:39 ` Michael Walle
2021-09-14 12:34 ` Lucas Stach
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=9e3d52c297ed024594a1e610a5cf61b2@walle.cc \
--to=michael@walle.cc \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=heiko.thiery@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzk@kernel.org \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=qiangqing.zhang@nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=shengjiu.wang@nxp.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;
as well as URLs for NNTP newsgroup(s).