From: Lucas Stach <l.stach@pengutronix.de>
To: Leonard Crestez <leonard.crestez@nxp.com>
Cc: Anson Huang <Anson.Huang@nxp.com>,
Irina Tirdea <irina.tirdea@nxp.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
linux-pm@vger.kernel.org, "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>,
Octavian Purdila <octavian.purdila@nxp.com>,
Sascha Hauer <kernel@pengutronix.de>,
Fabio Estevam <fabio.estevam@nxp.com>,
Robin Gong <yibin.gong@nxp.com>, Shawn Guo <shawnguo@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 5/5] ARM: dts: imx6qp-sabresd: Set reg_arm regulator supply
Date: Tue, 04 Apr 2017 11:53:08 +0200 [thread overview]
Message-ID: <1491299588.2367.18.camel@pengutronix.de> (raw)
In-Reply-To: <6711393cb78e8f975014e26e4008481828459463.1490987945.git.leonard.crestez@nxp.com>
Am Freitag, den 31.03.2017, 22:25 +0300 schrieb Leonard Crestez:
> On imx6qp-sabresd LDO_ARM is connected to a different PMIC output than
> the other imx6qdl-sabresd boards.
>
> Setting cpu0 arm-supply to sw2_reg is wrong, this must have mistakenly
> slipped out of the vendor tree where this is are used for LDO bypass.
>
> Signed-off-by: Leonard Crestez <leonard.crestez@nxp.com>
Reviewed-by: Lucas Stach <l.stach@pengutronix.de>
> ---
> arch/arm/boot/dts/imx6qp-sabresd.dts | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/boot/dts/imx6qp-sabresd.dts b/arch/arm/boot/dts/imx6qp-sabresd.dts
> index b234580..a8a5004 100644
> --- a/arch/arm/boot/dts/imx6qp-sabresd.dts
> +++ b/arch/arm/boot/dts/imx6qp-sabresd.dts
> @@ -50,8 +50,8 @@
> compatible = "fsl,imx6qp-sabresd", "fsl,imx6qp";
> };
>
> -&cpu0 {
> - arm-supply = <&sw2_reg>;
> +®_arm {
> + vin-supply = <&sw2_reg>;
> };
>
> &iomuxc {
prev parent reply other threads:[~2017-04-04 9:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 19:25 [PATCH 0/5] ARM: imx: Set LDO regulator supply Leonard Crestez
2017-03-31 19:25 ` [PATCH 1/5] ARM: imx: gpc: Do not print error message for EPROBE_DEFER Leonard Crestez
2017-04-04 9:46 ` Lucas Stach
2017-04-04 10:28 ` Leonard Crestez
2017-04-04 10:30 ` Lucas Stach
2017-03-31 19:25 ` [PATCH 2/5] cpufreq: imx6q: Fix handling EPROBE_DEFER from regulator Leonard Crestez
2017-04-04 9:48 ` Lucas Stach
2017-03-31 19:25 ` [PATCH 3/5] cpufreq: imx6q: Set max suspend_freq to avoid changes during suspend Leonard Crestez
2017-04-04 9:51 ` Lucas Stach
2017-04-04 17:04 ` Leonard Crestez
2017-03-31 19:25 ` [PATCH 4/5] ARM: dts: imx6qdl-sabresd: Set LDO regulator supply Leonard Crestez
2017-04-04 9:52 ` Lucas Stach
2017-03-31 19:25 ` [PATCH 5/5] ARM: dts: imx6qp-sabresd: Set reg_arm " Leonard Crestez
2017-04-04 9:53 ` Lucas Stach [this message]
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=1491299588.2367.18.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=Anson.Huang@nxp.com \
--cc=broonie@kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=irina.tirdea@nxp.com \
--cc=kernel@pengutronix.de \
--cc=leonard.crestez@nxp.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=octavian.purdila@nxp.com \
--cc=rjw@rjwysocki.net \
--cc=shawnguo@kernel.org \
--cc=viresh.kumar@linaro.org \
--cc=yibin.gong@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).