An error occurred fetching the project authors.
  1. 06 Jan, 2014 1 commit
    • Viresh Kumar's avatar
      cpufreq: Mark ARM drivers with CPUFREQ_NEED_INITIAL_FREQ_CHECK flag · ae6b4271
      Viresh Kumar authored
      Sometimes boot loaders set CPU frequency to a value outside of frequency table
      present with cpufreq core. In such cases CPU might be unstable if it has to run
      on that frequency for long duration of time and so its better to set it to a
      frequency which is specified in frequency table.
      
      On some systems we can't really say what frequency we're running at the moment
      and so for these we shouldn't check if we are running at a frequency present in
      frequency table. And so we really can't force this for all the cpufreq drivers.
      
      Hence we are created another flag here: CPUFREQ_NEED_INITIAL_FREQ_CHECK that
      will be marked by platforms which want to go for this check at boot time.
      
      Initially this is done for all ARM platforms but others may follow if required.
      Signed-off-by: default avatarViresh Kumar <viresh.kumar@linaro.org>
      Signed-off-by: default avatarRafael J. Wysocki <rafael.j.wysocki@intel.com>
      ae6b4271
  2. 30 Oct, 2013 1 commit
  3. 25 Oct, 2013 1 commit
    • Viresh Kumar's avatar
      cpufreq: Implement light weight ->target_index() routine · 9c0ebcf7
      Viresh Kumar authored
      Currently, the prototype of cpufreq_drivers target routines is:
      
      int target(struct cpufreq_policy *policy, unsigned int target_freq,
      		unsigned int relation);
      
      And most of the drivers call cpufreq_frequency_table_target() to get a valid
      index of their frequency table which is closest to the target_freq. And they
      don't use target_freq and relation after that.
      
      So, it makes sense to just do this work in cpufreq core before calling
      cpufreq_frequency_table_target() and simply pass index instead. But this can be
      done only with drivers which expose their frequency table with cpufreq core. For
      others we need to stick with the old prototype of target() until those drivers
      are converted to expose frequency tables.
      
      This patch implements the new light weight prototype for target_index() routine.
      It looks like this:
      
      int target_index(struct cpufreq_policy *policy, unsigned int index);
      
      CPUFreq core will call cpufreq_frequency_table_target() before calling this
      routine and pass index to it. Because CPUFreq core now requires to call routines
      present in freq_table.c CONFIG_CPU_FREQ_TABLE must be enabled all the time.
      
      This also marks target() interface as deprecated. So, that new drivers avoid
      using it. And Documentation is updated accordingly.
      
      It also converts existing .target() to newly defined light weight
      .target_index() routine for many driver.
      Acked-by: default avatarHans-Christian Egtvedt <egtvedt@samfundet.no>
      Acked-by: default avatarJesper Nilsson <jesper.nilsson@axis.com>
      Acked-by: default avatarLinus Walleij <linus.walleij@linaro.org>
      Acked-by: default avatarRussell King <linux@arm.linux.org.uk>
      Acked-by: default avatarDavid S. Miller <davem@davemloft.net>
      Tested-by: default avatarAndrew Lunn <andrew@lunn.ch>
      Signed-off-by: default avatarViresh Kumar <viresh.kumar@linaro.org>
      Signed-off-by: default avatarRafael J. Wysocki <rjw@rjwysocki.net>
      9c0ebcf7
  4. 15 Oct, 2013 4 commits
  5. 30 Sep, 2013 1 commit
  6. 24 Jun, 2013 1 commit
  7. 08 Apr, 2013 1 commit
  8. 02 Apr, 2013 3 commits
  9. 05 May, 2012 1 commit
  10. 12 Mar, 2012 1 commit
  11. 31 Oct, 2011 1 commit
  12. 04 May, 2011 1 commit
    • Dominik Brodowski's avatar
      [CPUFREQ] use dynamic debug instead of custom infrastructure · 2d06d8c4
      Dominik Brodowski authored
      With dynamic debug having gained the capability to report debug messages
      also during the boot process, it offers a far superior interface for
      debug messages than the custom cpufreq infrastructure. As a first step,
      remove the old cpufreq_debug_printk() function and replace it with a call
      to the generic pr_debug() function.
      
      How can dynamic debug be used on cpufreq? You need a kernel which has
      CONFIG_DYNAMIC_DEBUG enabled.
      
      To enabled debugging during runtime, mount debugfs and
      
      $ echo -n 'module cpufreq +p' > /sys/kernel/debug/dynamic_debug/control
      
      for debugging the complete "cpufreq" module. To achieve the same goal during
      boot, append
      
      	ddebug_query="module cpufreq +p"
      
      as a boot parameter to the kernel of your choice.
      
      For more detailled instructions, please see
      Documentation/dynamic-debug-howto.txt
      Signed-off-by: default avatarDominik Brodowski <linux@dominikbrodowski.net>
      Signed-off-by: default avatarDave Jones <davej@redhat.com>
      2d06d8c4
  13. 31 Mar, 2011 1 commit
  14. 28 Feb, 2011 1 commit
    • Axel Lin's avatar
      davinci: cpufreq: fix section mismatch warning · 079db590
      Axel Lin authored
      Fix below section mismatch warning:
      WARNING: vmlinux.o(.data+0x673c): Section mismatch in reference from the variable davinci_driver to the function .init.text:davinci_cpu_init()
      The variable davinci_driver references
      the function __init davinci_cpu_init()
      If the reference is valid then annotate the
      variable with __init* or __refdata (see linux/init.h) or name the variable:
      *_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console,
      Signed-off-by: default avatarAxel Lin <axel.lin@gmail.com>
      Acked-by: default avatarSekhar Nori <nsekhar@ti.com>
      Signed-off-by: default avatarKevin Hilman <khilman@ti.com>
      079db590
  15. 24 Sep, 2010 2 commits
    • Sekhar Nori's avatar
      davinci: cpufreq: add support for keeping an additional clock constant · 30a2c5d2
      Sekhar Nori authored
      On OMAP-L138 SoC, some of the sysclks need not be at a fixed ratio
      to CPU clock and can be kept at a relatively constant rate by
      adjusting the PLLDIVn ratio even as cpufreq goes ahead and changes
      the CPU clock.
      
      This feature can be used to keep the EMIFA (PLL0 SYSCLK3) clock at a
      constant rate so that the EMIF timings need not be re-programmed
      whenever the CPU frequency changes.
      
      This patch adds the required suppport to cpufreq driver.
      Signed-off-by: default avatarSekhar Nori <nsekhar@ti.com>
      Signed-off-by: default avatarKevin Hilman <khilman@deeprootsystems.com>
      30a2c5d2
    • Sekhar Nori's avatar
      davinci: cpufreq: bailout on regulator errors · fca97b33
      Sekhar Nori authored
      Current cpufreq code does not consider errors that can occur while
      changing voltage. Code to increase CPU  frequency goes ahead even in
      the case the regulator has failed to increase the voltage. This leads
      to hard error since lower voltages cannot support increased frequency.
      
      Prevent this by not increasing frequency in case increasing voltage
      is not successful.
      
      Also, do not lower the voltage if changing the cpu frequency has failed
      for some reason.
      
      Note that we do not return error on failure to decrease voltage as
      that is not a hard error.
      
      Build fix for non-cpufreq kernels by Caglar Akyuz.
      Signed-off-by: default avatarSekhar Nori <nsekhar@ti.com>
      Cc: Caglar Akyuz <caglar@bilkon-kontrol.com.tr>
      Signed-off-by: default avatarKevin Hilman <khilman@deeprootsystems.com>
      fca97b33
  16. 25 Nov, 2009 2 commits