Hi Christoph, On Thu, Feb 8, 2018 at 9:13 AM, Christoph Fritz <chf.fritz@xxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxx> > Signed-off-by: Christian Hemp <c.hemp@xxxxxxxxx> > --- > 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@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
