1. 13 Oct, 2017 2 commits
  2. 10 Oct, 2017 2 commits
  3. 03 Oct, 2017 1 commit
  4. 25 Sep, 2017 1 commit
  5. 23 Jun, 2017 1 commit
  6. 22 Jun, 2017 2 commits
  7. 23 Feb, 2017 1 commit
  8. 07 Feb, 2017 1 commit
  9. 30 Jan, 2017 11 commits
  10. 27 Jan, 2017 8 commits
  11. 06 Dec, 2016 7 commits
  12. 30 Nov, 2016 1 commit
    • Stephen Boyd's avatar
      PM / OPP: Pass opp_table to dev_pm_opp_put_regulator() · 91291d9a
      Stephen Boyd authored
      Joonyoung Shim reported an interesting problem on his ARM octa-core
      Odoroid-XU3 platform. During system suspend, dev_pm_opp_put_regulator()
      was failing for a struct device for which dev_pm_opp_set_regulator() is
      called earlier.
      
      This happened because an earlier call to
      dev_pm_opp_of_cpumask_remove_table() function (from cpufreq-dt.c file)
      removed all the entries from opp_table->dev_list apart from the last CPU
      device in the cpumask of CPUs sharing the OPP.
      
      But both dev_pm_opp_set_regulator() and dev_pm_opp_put_regulator()
      routines get CPU device for the first CPU in the cpumask. And so the OPP
      core failed to find the OPP table for the struct device.
      
      This patch attempts to fix this problem by returning a pointer to the
      opp_table from dev_pm_opp_set_regulator() and using that as the
      parameter to dev_pm_opp_put_regulator(). This ensures that the
      dev_pm_opp_put_regulator() doesn't fail to find the opp table.
      
      Note that similar design problem also exists with other
      dev_pm_opp_put_*() APIs, but those aren't used currently by anyone and
      so we don't need to update them for now.
      
      Cc: 4.4+ <stable@vger.kernel.org> # 4.4+
      Reported-by: default avatarJoonyoung Shim <jy0922.shim@samsung.com>
      Signed-off-by: default avatarStephen Boyd <sboyd@codeaurora.org>
      Signed-off-by: default avatarViresh Kumar <viresh.kumar@linaro.org>
      [ Viresh: Wrote commit log and tested on exynos 5250 ]
      Signed-off-by: default avatarRafael J. Wysocki <rafael.j.wysocki@intel.com>
      91291d9a
  13. 16 Sep, 2016 1 commit
    • Arnd Bergmann's avatar
      PM / OPP: avoid maybe-uninitialized warning · 4df27c91
      Arnd Bergmann authored
      When CONFIG_OPTIMIZE_INLINING is set and we are building with -Wmaybe-uninitialized
      enabled, we can get a warning for the opp core driver:
      
      drivers/base/power/opp/core.c: In function 'dev_pm_opp_set_rate':
      drivers/base/power/opp/core.c:560:8: warning: 'ou_volt_min' may be used uninitialized in this function [-Wmaybe-uninitialized]
      
      This has only now appeared as a result of commit 797da559 ("PM / devfreq:
      Add COMPILE_TEST for build coverage"), which makes the driver visible in
      some configurations that didn't have it before.
      
      The warning is a false positive that I got with gcc-6.1.1, but there is
      a simple workaround in removing the local variables that we get warnings
      for (all three are affected depending on the configuration). This also
      makes the code easier to read.
      Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
      Reviewed-by: default avatarStephen Boyd <sboyd@codeaurora.org>
      Acked-by: default avatarViresh Kumar <viresh.kumar@linaro.org>
      Signed-off-by: default avatarRafael J. Wysocki <rafael.j.wysocki@intel.com>
      4df27c91
  14. 28 Jul, 2016 1 commit