From: Frieder Schrempf <frieder.schrempf@kontron.de>
To: Michael Walle <michael@walle.cc>, Heiko Thiery <heiko.thiery@gmail.com>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzk@kernel.org>,
Joakim Zhang <qiangqing.zhang@nxp.com>,
Shengjiu Wang <shengjiu.wang@nxp.com>,
Rob Herring <robh+dt@kernel.org>, Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>
Subject: Re: [PATCH] arm64: dts: imx8mm-kontron-n801x-som: do not allow to switch off buck2
Date: Wed, 15 Sep 2021 14:09:06 +0200 [thread overview]
Message-ID: <898fd5e0-2073-3689-89b6-2c5071773786@kontron.de> (raw)
In-Reply-To: <7e7ee4244ababc0a46e0875222c7e37d@walle.cc>
On 15.09.21 14:05, Michael Walle wrote:
> Am 2021-09-15 14:03, schrieb Heiko Thiery:
>> The buck2 output of the PMIC is the VDD core voltage of the cpu.
>> Switching off this will poweroff the CPU. Add the 'regulator-always-on'
>> property to avoid this.
>
> Mh, have this ever worked? Is there a commit which introduced a regression?
Yes, this did work before, even without 'regulator-always-on'. I
currently don't understand why this is needed. The regulator is
referenced in the CPU nodes as 'cpu-supply'. This should be enough to
not disable it as long as the CPU is up.
next prev parent reply other threads:[~2021-09-15 12:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 12:03 [PATCH] arm64: dts: imx8mm-kontron-n801x-som: do not allow to switch off buck2 Heiko Thiery
2021-09-15 12:05 ` Michael Walle
2021-09-15 12:09 ` Frieder Schrempf [this message]
2021-09-17 7:28 ` Heiko Thiery
2021-09-17 8:21 ` Michael Walle
2021-09-17 8:51 ` Heiko Thiery
2021-09-17 11:44 ` Lucas Stach
2021-09-17 16:10 ` Heiko Thiery
2021-09-20 7:31 ` Frieder Schrempf
2021-09-20 7:43 ` Michael Walle
2021-09-20 8:10 ` Lucas Stach
2021-10-04 12:39 ` Shawn Guo
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=898fd5e0-2073-3689-89b6-2c5071773786@kontron.de \
--to=frieder.schrempf@kontron.de \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=heiko.thiery@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@walle.cc \
--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).