From: Shawn Guo <shawnguo@kernel.org>
To: Anson Huang <Anson.Huang@nxp.com>
Cc: s.hauer@pengutronix.de, kernel@pengutronix.de,
fabio.estevam@nxp.com, robh+dt@kernel.org, mark.rutland@arm.com,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, yibin.gong@nxp.com,
Linux-imx@nxp.com
Subject: Re: [PATCH 4/4] ARM: dts: imx6sl-evk: make pfuze100 sw4 always on
Date: Tue, 17 Jul 2018 15:18:09 +0800 [thread overview]
Message-ID: <20180717071807.GM4576@dragon> (raw)
In-Reply-To: <1531804325-3476-4-git-send-email-Anson.Huang@nxp.com>
On Tue, Jul 17, 2018 at 01:12:05PM +0800, Anson Huang wrote:
> From: Robin Gong <yibin.gong@nxp.com>
>
> On i.MX6SL EVK board, pfuze100 sw4 supplies
> LPDDR2 which is critical for system, must be
> always on.
>
> Signed-off-by: Anson Huang <Anson.Huang@nxp.com>
Robin's SoB is missing, since it's authorized by him. I fixed it up and
applied all patches.
Shawn
> ---
> arch/arm/boot/dts/imx6sl-evk.dts | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm/boot/dts/imx6sl-evk.dts b/arch/arm/boot/dts/imx6sl-evk.dts
> index 046cfab..679b448 100644
> --- a/arch/arm/boot/dts/imx6sl-evk.dts
> +++ b/arch/arm/boot/dts/imx6sl-evk.dts
> @@ -201,6 +201,7 @@
> sw4_reg: sw4 {
> regulator-min-microvolt = <800000>;
> regulator-max-microvolt = <3300000>;
> + regulator-always-on;
> };
>
> swbst_reg: swbst {
> --
> 2.7.4
>
prev parent reply other threads:[~2018-07-17 7:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 5:12 [PATCH 1/4] ARM: dts: imx6qdl-sabresd: make pfuze100 sw4 always on Anson Huang
2018-07-17 5:12 ` [PATCH 2/4] ARM: dts: imx6sx-sdb-reva: " Anson Huang
2018-07-17 5:12 ` [PATCH 3/4] ARM: dts: imx6sll-evk: " Anson Huang
2018-07-17 5:12 ` [PATCH 4/4] ARM: dts: imx6sl-evk: " Anson Huang
2018-07-17 7:18 ` Shawn Guo [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=20180717071807.GM4576@dragon \
--to=shawnguo@kernel.org \
--cc=Anson.Huang@nxp.com \
--cc=Linux-imx@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--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).