On 18-10-16, 17:30, Robert Jarzmik wrote: > Viresh Kumar <[email protected]> writes: > > > On 15-10-16, 21:57, Robert Jarzmik wrote: > >> Add the relevant data taken from the PXA 25x Electrical, Mechanical, and > >> Thermal Specfication. This will be input data for cpufreq-dt driver. > >> > >> Signed-off-by: Robert Jarzmik <[email protected]> > >> --- > >> arch/arm/boot/dts/pxa25x.dtsi | 25 +++++++++++++++++++++++++ > >> 1 file changed, 25 insertions(+) > >> > >> diff --git a/arch/arm/boot/dts/pxa25x.dtsi b/arch/arm/boot/dts/pxa25x.dtsi > >> index 0d1e012178c4..16b4e8bad4a5 100644 > >> --- a/arch/arm/boot/dts/pxa25x.dtsi > >> +++ b/arch/arm/boot/dts/pxa25x.dtsi > >> @@ -89,4 +89,29 @@ > >> clocks = <&clktimer>; > >> status = "okay"; > >> }; > >> + > >> + pxa250_opp_table: opp_table0 { > >> + compatible = "operating-points-v2"; > >> + > >> + opp@99500 { > > > > We have been keeping the values in ^^^ same as the values present > > below. Any specific reason for making it different here ? > No, that's a good comment, I'll change that. > > I wrote this incrementaly, first the node, then the opp-hz. Then I realized > that > the source crystal, at 3.8684 MHz didn't provide a round 99.5 MHz core clock, > but a 99.5328 MHz clock. > > Anyway, I'll change that ... let's say into opp@99533 in this case ?
Just write the whole value 99532800. -- viresh
