Message ID | CACUGKYPLSdih0_+Dt5LP2E1JACfU7NbAvtCibWftKbzTf6R8FA@mail.gmail.com (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
On Mon, Dec 16, 2013 at 05:40:15PM -0800, John Tobias wrote: > iMX6SL device tree doesn't have a configuration settings to enable the > frequency scaling and power management. > > From: John Tobias <john.tobias.ph@gmail.com> Please use 'git format-patch' and 'git send-email'. Also, it's never been a good idea to use the exactly same patch subject for 3 different changes. Shawn > > > diff --git a/arch/arm/boot/dts/imx6sl.dtsi b/arch/arm/boot/dts/imx6sl.dtsi > index 28558f1..0ad2f6a 100644 > --- a/arch/arm/boot/dts/imx6sl.dtsi > +++ b/arch/arm/boot/dts/imx6sl.dtsi > @@ -38,6 +38,19 @@ > device_type = "cpu"; > reg = <0x0>; > next-level-cache = <&L2>; > + operating-points = < > + /* kHz uV */ > + 1000000 1275000 > + 792000 1150000 > + >; > + clock-latency = <61036>; /* two CLK32 periods */ > + clocks = <&clks IMX6SL_CLK_ARM>, <&clks > IMX6SL_CLK_PLL2_PFD2>, <&clks IMX6SL_CLK_STEP>, > + <&clks IMX6SL_CLK_PLL1_SW>, <&clks > IMX6SL_CLK_PLL1_SYS>; > + clock-names = "arm", "pll2_pfd2_396m", "step", > + "pll1_sw", "pll1_sys"; > + arm-supply = <®_arm>; > + pu-supply = <®_pu>; > + soc-supply = <®_soc>; > }; > };
diff --git a/arch/arm/boot/dts/imx6sl.dtsi b/arch/arm/boot/dts/imx6sl.dtsi index 28558f1..0ad2f6a 100644 --- a/arch/arm/boot/dts/imx6sl.dtsi +++ b/arch/arm/boot/dts/imx6sl.dtsi @@ -38,6 +38,19 @@ device_type = "cpu"; reg = <0x0>; next-level-cache = <&L2>; + operating-points = < + /* kHz uV */ + 1000000 1275000 + 792000 1150000 + >; + clock-latency = <61036>; /* two CLK32 periods */ + clocks = <&clks IMX6SL_CLK_ARM>, <&clks IMX6SL_CLK_PLL2_PFD2>, <&clks IMX6SL_CLK_STEP>, + <&clks IMX6SL_CLK_PLL1_SW>, <&clks IMX6SL_CLK_PLL1_SYS>; + clock-names = "arm", "pll2_pfd2_396m", "step", + "pll1_sw", "pll1_sys"; + arm-supply = <®_arm>; + pu-supply = <®_pu>; + soc-supply = <®_soc>; };
iMX6SL device tree doesn't have a configuration settings to enable the frequency scaling and power management. From: John Tobias <john.tobias.ph@gmail.com> };