1. 23 Feb, 2017 1 commit
  2. 09 Feb, 2017 1 commit
    • Tang Yuantian's avatar
      cpufreq: qoriq: Don't look at clock implementation details · b1e9a649
      Tang Yuantian authored
      Get the CPU clock's potential parent clocks from the clock interface
      itself, rather than manually parsing the clocks property to find a
      phandle, looking at the clock-names property of that, and assuming that
      those are valid parent clocks for the cpu clock.
      
      This is necessary now that the clocks are generated based on the clock
      driver's knowledge of the chip rather than a fragile device-tree
      description of the mux options.
      
      We can now rely on the clock driver to ensure that the mux only exposes
      options that are valid.  The cpufreq driver was currently being overly
      conservative in some cases -- for example, the "min_cpufreq =
      get_bus_freq()" restriction only applies to chips with erratum
      A-004510, and whether the freq_mask used on p5020 is needed depends on
      the actual frequencies of the PLLs (FWIW, p5040 has a similar
      limitation but its .freq_mask was zero) -- and the frequency mask
      mechanism made assumptions about particular parent clock indices that
      are no longer valid.
      Signed-off-by: default avatarScott Wood <scottwood@nxp.com>
      Signed-off-by: default avatarTang Yuantian <yuantian.tang@nxp.com>
      Acked-by: default avatarViresh Kumar <viresh.kumar@linaro.org>
      Signed-off-by: default avatarRafael J. Wysocki <rafael.j.wysocki@intel.com>
      b1e9a649
  3. 25 Apr, 2016 3 commits
  4. 09 Dec, 2015 1 commit
  5. 15 Jun, 2015 1 commit
  6. 11 Apr, 2015 1 commit
    • Arnd Bergmann's avatar
      cpufreq: fix qoriq uniprocessor build · 4492d1a2
      Arnd Bergmann authored
      The qoriq-cpufreq driver contains a hack for powerpc to include
      asm/smp.h on uniprocessor builds so it can get the hardware CPU
      number. On ARM, it does not require this hack, but instead gets
      a compile error:
      
      In file included from drivers/cpufreq/qoriq-cpufreq.c:24:0:
      arch/arm/include/asm/smp.h:18:3: error: #error "<asm/smp.h> included in non-SMP build"
      arch/arm/include/asm/smp.h:21:0: warning: "raw_smp_processor_id" redefined
      
      This adds an #ifdef to mirror the one in its get_cpu_physical_id()
      function.
      Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
      Fixes: 2f249358 ("cpufreq: qoriq: rename the driver")
      Cc: Tang Yuantian <Yuantian.Tang@freescale.com>
      Signed-off-by: default avatarRafael J. Wysocki <rafael.j.wysocki@intel.com>
      4492d1a2
  7. 18 Mar, 2015 2 commits
  8. 04 Mar, 2015 1 commit
  9. 30 Sep, 2014 1 commit
  10. 06 Jun, 2014 1 commit
  11. 28 Apr, 2014 1 commit
  12. 21 Apr, 2014 1 commit
  13. 08 Apr, 2014 1 commit
  14. 20 Mar, 2014 1 commit
  15. 12 Mar, 2014 1 commit
  16. 17 Jan, 2014 1 commit
  17. 30 Oct, 2013 1 commit
  18. 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
  19. 15 Oct, 2013 2 commits
  20. 30 Sep, 2013 1 commit
  21. 10 Aug, 2013 1 commit
  22. 05 Jun, 2013 1 commit