Am Montag, den 26.05.2014, 16:02 +0530 schrieb Viresh Kumar: > On 26 May 2014 15:45, Lucas Stach <l.stach@xxxxxxxxxxxxxx> wrote: > > SoC specific driver to be able to handle PLL reprogramming > > for exact OPP frequencies and additional power saving. > > > > Signed-off-by: Lucas Stach <l.stach@xxxxxxxxxxxxxx> > > --- > > .../devicetree/bindings/cpufreq/cpufreq-imx5.txt | 43 +++ > > drivers/cpufreq/Kconfig.arm | 8 + > > drivers/cpufreq/Makefile | 1 + > > drivers/cpufreq/imx5-cpufreq.c | 302 +++++++++++++++++++++ > > 4 files changed, 354 insertions(+) > > create mode 100644 Documentation/devicetree/bindings/cpufreq/cpufreq-imx5.txt > > create mode 100644 drivers/cpufreq/imx5-cpufreq.c > > What stops you to use cpufreq-cpu0 driver with a CPU clock > driver? Its highly discouraged to add a new driver here if you > can reuse it.. Which is more or less confirmed from a broad look.. This driver handles the i.MX5 specific clock reparenting to be able to reprogramm the PLL. cpufreq-cpu0 can only change a postdivider of the PLL, which means we can't reach the exact OPP frequencies and can not profit from the additional power savings of a slower running PLL. Also without reprogramming the PLL we could possibly not scale to the highest OPPs if the bootloader left the PLL at a slower rate. This is the case for many i.MX53 boards, as the CPU regulator normally does start up with the voltage required for 800MHz operation. If the bootloader decides to not touch the regulator and set the PLL to 800MHz the 1GHz and 1.2GHz operating points won't be useable. Regards, Lucas -- Pengutronix e.K. | Lucas Stach | Industrial Linux Solutions | http://www.pengutronix.de/ | -- 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
