1. 25 Jul, 2017 1 commit
    • Viresh Kumar's avatar
      cpufreq: Add CPUFREQ_NO_AUTO_DYNAMIC_SWITCHING cpufreq driver flag · fe829ed8
      Viresh Kumar authored
      The policy->transition_latency field is used for multiple purposes
      today and its not straight forward at all. This is how it is used:
      
      A. Set the correct transition_latency value.
      
      B. Set it to CPUFREQ_ETERNAL because:
         1. We don't want automatic dynamic switching (with
            ondemand/conservative) to happen at all.
         2. We don't know the transition latency.
      
      This patch handles the B.1. case in a more readable way. A new flag for
      the cpufreq drivers is added to disallow use of cpufreq governors which
      have dynamic_switching flag set.
      
      All the current cpufreq drivers which are setting transition_latency
      unconditionally to CPUFREQ_ETERNAL are updated to use it. They don't
      need to set transition_latency anymore.
      
      There shouldn't be any functional change after this patch.
      Signed-off-by: default avatarViresh Kumar <viresh.kumar@linaro.org>
      Reviewed-by: default avatarDominik Brodowski <linux@dominikbrodowski.net>
      Signed-off-by: default avatarRafael J. Wysocki <rafael.j.wysocki@intel.com>
      fe829ed8
  2. 23 Aug, 2016 1 commit
  3. 16 Jul, 2014 1 commit
  4. 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
  5. 30 Oct, 2013 1 commit
  6. 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: Linus Walleij's 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
  7. 15 Oct, 2013 3 commits
  8. 30 Sep, 2013 2 commits
  9. 10 Apr, 2013 1 commit
  10. 02 Apr, 2013 1 commit
  11. 09 Jul, 2012 1 commit
    • Russell King's avatar
      ARM: sa11x0/pxa: convert OS timer registers to IOMEM · 3169663a
      Russell King authored
      Make the OS timer registers have IOMEM like properities so they can
      be passed to readl_relaxed/writel_relaxed() et.al. rather than being
      straight volatile dereferences.  Add linux/io.h includes where
      required.
      
      linux/io.h includes added to arch/arm/mach-sa1100/cpu-sa1100.c,
       arch/arm/mach-sa1100/jornada720_ssp.c, arch/arm/mach-sa1100/leds-lart.c
       drivers/input/touchscreen/jornada720_ts.c, drivers/pcmcia/sa1100_shannon.c
      from Arnd.
      
      This fixes these warnings:
      
      arch/arm/mach-sa1100/time.c: In function 'sa1100_timer_init':
      arch/arm/mach-sa1100/time.c:104: warning: passing argument 1 of 'clocksource_mmio_init' discards qualifiers from pointer target type
      arch/arm/mach-pxa/time.c: In function 'pxa_timer_init':
      arch/arm/mach-pxa/time.c:126: warning: passing argument 1 of 'clocksource_mmio_init' discards qualifiers from pointer target type
      Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      3169663a
  12. 21 Dec, 2010 2 commits
  13. 01 May, 2010 1 commit
  14. 01 Dec, 2008 1 commit
  15. 06 Sep, 2008 1 commit
  16. 01 Sep, 2008 1 commit
  17. 16 Aug, 2008 1 commit
  18. 07 Aug, 2008 2 commits
  19. 04 Oct, 2007 1 commit
  20. 29 Oct, 2006 1 commit
  21. 14 Oct, 2006 1 commit
  22. 29 Jun, 2006 1 commit
  23. 01 Jul, 2005 1 commit
  24. 16 Apr, 2005 1 commit
    • Linus Torvalds's avatar
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds authored
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4