[PATCH V2 1/2] ARM: imx: add vddsoc/pu setpoint info into dts
Shawn Guo
shawn.guo at linaro.org
Wed Dec 18 03:24:48 EST 2013
On Wed, Dec 18, 2013 at 03:17:42PM -0500, Anson Huang wrote:
> > > + operating-points = <
> > > + /* kHz uV */
> > > + 1200000 1275000
> > > + 996000 1250000
> > > + 792000 1150000
> > > + 396000 975000
> > > + >;
> > > + fsl,soc-operating-points = <
> > > + /* ARM kHz SOC-PU uV */
> > > + 1200000 1275000
> > > + 996000 1250000
> > > + 792000 1175000
> > > + 396000 1175000
> > > + >;
> > > + clock-latency = <61036>; /* two CLK32 periods */
> > > + clocks = <&clks 104>, <&clks 6>, <&clks 16>,
> > > + <&clks 17>, <&clks 170>;
> > > + clock-names = "arm", "pll2_pfd2_396m", "step",
> > > + "pll1_sw", "pll1_sys";
> > > + arm-supply = <®_arm>;
> > > + pu-supply = <®_pu>;
> > > + soc-supply = <®_soc>;
> >
> > Any properties in the example that are required for a successful driver
> > probe should be documented in 'Required properties', and others are in
> > 'Optional properties'.
>
> I will not list so many properties as example as long as I describe this
> preoperties should be included in cpu at 0's node?
The example is good. But you also need to document properties clocks,
clock-names, arm-supply etc.
Shawn
More information about the linux-arm-kernel
mailing list