On Fri, Jun 19, 2015 at 01:55:46PM -0500, Zhi Li wrote: > On Fri, Jun 19, 2015 at 12:05 PM, Nicolae Rosia <[email protected]> > wrote: > > Hi, > > > > On Fri, Jun 19, 2015 at 6:32 PM, <[email protected]> wrote: > >> From: Frank Li <[email protected]> > > [...] > >> + cpus { > >> + #address-cells = <1>; > >> + #size-cells = <0>; > >> + > >> + cpu0: cpu@0 { > >> + compatible = "arm,cortex-a7"; > >> + device_type = "cpu"; > >> + reg = <0>; > >> + clock-latency = <61036>; /* two CLK32 periods */ > >> + operating-points = < > >> + /* kHz uV */ > >> + 528000 1250000 > >> + 396000 1150000 > >> + 198000 1150000 > >> + >; > >> + fsl,soc-operating-points = < > >> + /* KHz uV */ > >> + 528000 1250000 > >> + 396000 1150000 > >> + 198000 1150000 > >> + >; > > Why is this necessary? Can't you adapt the driver to use operating-points? > > I have looked through other imx dts and saw that some had different > > values in these two tables. > > It is used by internal busfreq driver. I will remove it at next version.
It's used by mainline imx6q-cpufreq driver, but it's a piece of undocumented binding. Basically, on i.MX6 series, when CPU frequency scales, there are two voltages, 'core' and 'soc', need to scale accordingly. The OPP binding v1 only supports one voltage. Shawn -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
