* [PATCH] ARM: dts: phycore-imx6: set buck regulator modes explicitly
@ 2018-02-08 11:13 Christoph Fritz
[not found] ` <1518088421.2347.9.camel-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
0 siblings, 1 reply; 4+ messages in thread
From: Christoph Fritz @ 2018-02-08 11:13 UTC (permalink / raw)
To: Shawn Guo
Cc: Fabio Estevam, Christian Hemp,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
This patch sets initial buck regulator modes explicitly to a state
this hardware needs. So a wrong initial mode set by bootloader or
pmic itself does not interfere anymore.
Signed-off-by: Christoph Fritz <chf.fritz-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
Signed-off-by: Christian Hemp <c.hemp-guT5V/WYfQezQB+pC5nmwQ@public.gmane.org>
---
arch/arm/boot/dts/imx6qdl-phytec-phycore-som.dtsi | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/imx6qdl-phytec-phycore-som.dtsi b/arch/arm/boot/dts/imx6qdl-phytec-phycore-som.dtsi
index 53e4337..2ad1336 100644
--- a/arch/arm/boot/dts/imx6qdl-phytec-phycore-som.dtsi
+++ b/arch/arm/boot/dts/imx6qdl-phytec-phycore-som.dtsi
@@ -109,6 +109,7 @@
regulator-name = "vdd_arm";
regulator-min-microvolt = <730000>;
regulator-max-microvolt = <1380000>;
+ regulator-initial-mode = <2>; /* SYNC */
regulator-always-on;
};
@@ -116,6 +117,7 @@
regulator-name = "vdd_soc";
regulator-min-microvolt = <730000>;
regulator-max-microvolt = <1380000>;
+ regulator-initial-mode = <2>; /* SYNC */
regulator-always-on;
};
@@ -123,6 +125,7 @@
regulator-name = "vdd_ddr3";
regulator-min-microvolt = <1500000>;
regulator-max-microvolt = <1500000>;
+ regulator-initial-mode = <2>; /* SYNC */
regulator-always-on;
};
@@ -130,6 +133,7 @@
regulator-name = "vdd_eth";
regulator-min-microvolt = <1200000>;
regulator-max-microvolt = <1200000>;
+ regulator-initial-mode = <2>; /* SYNC */
regulator-always-on;
};
--
2.1.4
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply related [flat|nested] 4+ messages in thread[parent not found: <1518088421.2347.9.camel-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>]
* Re: [PATCH] ARM: dts: phycore-imx6: set buck regulator modes explicitly [not found] ` <1518088421.2347.9.camel-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org> @ 2018-02-08 19:14 ` Fabio Estevam [not found] ` <CAOMZO5Bsp2VGY0++XBqMd4aXj6uo-guzfH-jQ9R6uyanStfMtA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 0 siblings, 1 reply; 4+ messages in thread From: Fabio Estevam @ 2018-02-08 19:14 UTC (permalink / raw) To: Christoph Fritz Cc: Shawn Guo, Fabio Estevam, Christian Hemp, devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Hi Christoph, On Thu, Feb 8, 2018 at 9:13 AM, Christoph Fritz <chf.fritz-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org> wrote: > This patch sets initial buck regulator modes explicitly to a state > this hardware needs. So a wrong initial mode set by bootloader or > pmic itself does not interfere anymore. > > Signed-off-by: Christoph Fritz <chf.fritz-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org> > Signed-off-by: Christian Hemp <c.hemp-guT5V/WYfQezQB+pC5nmwQ@public.gmane.org> > --- > arch/arm/boot/dts/imx6qdl-phytec-phycore-som.dtsi | 4 ++++ > 1 file changed, 4 insertions(+) > > diff --git a/arch/arm/boot/dts/imx6qdl-phytec-phycore-som.dtsi b/arch/arm/boot/dts/imx6qdl-phytec-phycore-som.dtsi > index 53e4337..2ad1336 100644 > --- a/arch/arm/boot/dts/imx6qdl-phytec-phycore-som.dtsi > +++ b/arch/arm/boot/dts/imx6qdl-phytec-phycore-som.dtsi > @@ -109,6 +109,7 @@ > regulator-name = "vdd_arm"; > regulator-min-microvolt = <730000>; > regulator-max-microvolt = <1380000>; > + regulator-initial-mode = <2>; /* SYNC */ According to Documentation/devicetree/bindings/regulator/twl-regulator.txt: "- regulator-initial-mode: initial operating mode. The set of possible operating modes depends on the capabilities of every hardware so each device binding documentation explains which values the regulator supports." However, I haven't found the explanation of this property for the da9062-regulator. Could you please add it into Documentation/devicetree/bindings/mfd/da9062.txt, so that we we know what the value 2 means here? -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 4+ messages in thread
[parent not found: <CAOMZO5Bsp2VGY0++XBqMd4aXj6uo-guzfH-jQ9R6uyanStfMtA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>]
* Re: [PATCH] ARM: dts: phycore-imx6: set buck regulator modes explicitly [not found] ` <CAOMZO5Bsp2VGY0++XBqMd4aXj6uo-guzfH-jQ9R6uyanStfMtA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> @ 2018-02-08 19:15 ` Fabio Estevam [not found] ` <CAOMZO5CbKWXmFGzB25HtZuVa+C3wZk9DncBoe54ir8jWhyw7aw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 0 siblings, 1 reply; 4+ messages in thread From: Fabio Estevam @ 2018-02-08 19:15 UTC (permalink / raw) To: Christoph Fritz Cc: Shawn Guo, Fabio Estevam, Christian Hemp, devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org On Thu, Feb 8, 2018 at 5:14 PM, Fabio Estevam <festevam-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > According to Documentation/devicetree/bindings/regulator/twl-regulator.txt: Sorry, I mean "Documentation/devicetree/bindings/regulator/regulator.txt". > > "- regulator-initial-mode: initial operating mode. The set of possible operating > modes depends on the capabilities of every hardware so each device binding > documentation explains which values the regulator supports." > > However, I haven't found the explanation of this property for the > da9062-regulator. > > Could you please add it into > Documentation/devicetree/bindings/mfd/da9062.txt, so that we we know > what the value 2 means here? -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 4+ messages in thread
[parent not found: <CAOMZO5CbKWXmFGzB25HtZuVa+C3wZk9DncBoe54ir8jWhyw7aw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>]
* Re: [PATCH] ARM: dts: phycore-imx6: set buck regulator modes explicitly [not found] ` <CAOMZO5CbKWXmFGzB25HtZuVa+C3wZk9DncBoe54ir8jWhyw7aw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> @ 2018-02-09 9:59 ` Christoph Fritz 0 siblings, 0 replies; 4+ messages in thread From: Christoph Fritz @ 2018-02-09 9:59 UTC (permalink / raw) To: Fabio Estevam Cc: Shawn Guo, Fabio Estevam, Christian Hemp, devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org On Thu, 2018-02-08 at 17:15 -0200, Fabio Estevam wrote: > On Thu, Feb 8, 2018 at 5:14 PM, Fabio Estevam <festevam-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > According to Documentation/devicetree/bindings/regulator/twl-regulator.txt: > > Sorry, I mean "Documentation/devicetree/bindings/regulator/regulator.txt". Thanks for pointing that out, I'll send a patchset with all changes. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2018-02-09 9:59 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-02-08 11:13 [PATCH] ARM: dts: phycore-imx6: set buck regulator modes explicitly Christoph Fritz
[not found] ` <1518088421.2347.9.camel-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2018-02-08 19:14 ` Fabio Estevam
[not found] ` <CAOMZO5Bsp2VGY0++XBqMd4aXj6uo-guzfH-jQ9R6uyanStfMtA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-02-08 19:15 ` Fabio Estevam
[not found] ` <CAOMZO5CbKWXmFGzB25HtZuVa+C3wZk9DncBoe54ir8jWhyw7aw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-02-09 9:59 ` Christoph Fritz
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).