Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • I ipipe-ppc32
  • Project information
    • Project information
    • Activity
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Commits
Collapse sidebar
  • xenomaixenomai
  • ipipe-ppc32
  • Repository
Switch branch/tag
  • ipipe-ppc32
  • drivers
  • cpufreq
  • cpufreq.c
Find file BlameHistoryPermalink
  • Viresh Kumar's avatar
    cpufreq: Restart governor as soon as possible · 9591becb
    Viresh Kumar authored Jun 10, 2015
    
    
    __cpufreq_remove_dev_finish() is doing two things today:
    - Restarts the governor if some CPUs from concerned policy are still
      online.
    - Frees the policy if all CPUs are offline.
    
    The first task of restarting the governor can be moved to
    __cpufreq_remove_dev_prepare() to restart the governor early. There is
    no race between _prepare() and _finish() as they would be handling
    completely different cases. _finish() will only be required if we are
    going to free the policy and that has nothing to do with restarting the
    governor.
    
    Original-by: default avatarSaravana Kannan <skannan@codeaurora.org>
    Signed-off-by: default avatarViresh Kumar <viresh.kumar@linaro.org>
    Signed-off-by: default avatarRafael J. Wysocki <rafael.j.wysocki@intel.com>
    9591becb

Imprint & Privacy Policy