1. 27 11月, 2012 1 次提交
  2. 14 4月, 2012 1 次提交
    • K
      cpufreq: OMAP: fix build errors: depends on ARCH_OMAP2PLUS · 2d59dcfb
      Kevin Hilman 提交于
      The OMAP driver needs a 'depends on ARCH_OMAP2PLUS' since it only
      builds for OMAP2+ platforms.
      
      This 'depends on' was in the original patch from Russell King, but was
      erroneously removed by me when making this option user-selectable in
      commit b09db45c (cpufreq: OMAP driver depends CPUfreq tables.)  This
      patch remedies that.
      
      Apologies to Russell King for breaking his originally working patch.
      
      Also, thanks to Grazvydas Ignotas for reporting the same problem.
      
      Cc: Russell King <rmk+kernel@arm.linux.org.uk>
      Cc: Grazvydas Ignotas <notasas@gmail.com>
      Signed-off-by: NKevin Hilman <khilman@ti.com>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      2d59dcfb
  3. 05 4月, 2012 1 次提交
  4. 15 3月, 2012 2 次提交
  5. 01 3月, 2012 2 次提交
    • H
      [CPUFREQ] Add S3C2416/S3C2450 cpufreq driver · 34ee5507
      Heiko Stübner 提交于
      The S3C2416/S3C2450 SoCs support two sources for the armclk.
      
      The first source is the so called armdiv which divides the msysclk down
      to provide necessary cpu rates. In this mode the core voltage must be
      always at 1.3V. The frequency from the armdiv is not allowed to be
      lower than the hclk frequency.
      
      In the second mode the armclk can be sourced directly from the hclk in
      the so called "dynamic voltags scaling" (dvs) mode. Here the armdiv
      isn't used at all. Also in this mode the core voltage may be lowered.
      Existing hardware and tests with it suggest 1.0V as sufficient.
      
      When changing the clock source to the armdiv from the hclk, the SoC
      shows stability issues if the new frequency is higher than the current
      hclk frequency. Hence the driver always forces the armdiv to the hclk
      frequency before the source change and lets the cpufreq issue another
      set_target call for higher frequencies.
      
      To mark the hclk frequency as lower as the corresponding armdiv
      frequency it is set 1MHz below the real frequency. This lets the cpufreq
      framework change between 133MHz based on hclk and 133MHz based on armdiv
      at will.
      Signed-off-by: NHeiko Stuebner <heiko@sntech.de>
      Tested-by: NAndrey Gusakov <dron0gus@gmail.com>
      Signed-off-by: NDave Jones <davej@redhat.com>
      34ee5507
    • R
      [CPUFREQ] Fix exposure of ARM_EXYNOS4210_CPUFREQ · 063b0ee4
      Russell King 提交于
      exynos4210-cpufreq.c is not buildable on non-exynos builds, so it's
      pointless allowing this option to be exposed.  Fix this by adding a
      dependency on ARCH_EXYNOS.
      
      drivers/cpufreq/exynos4210-cpufreq.c:20:29: error: mach/regs-clock.h: No such file or directory
      drivers/cpufreq/exynos4210-cpufreq.c:21:26: error: mach/cpufreq.h: No such file or directory
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      Cc: cpufreq@vger.kernel.org
      Cc: Kukjin Kim <kgene.kim@samsung.com>
      Signed-off-by: NDave Jones <davej@redhat.com>
      063b0ee4
  6. 22 2月, 2012 1 次提交
  7. 09 1月, 2012 1 次提交
  8. 14 7月, 2011 2 次提交