Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • I ipipe-ppc32
  • Project information
    • Project information
    • Activity
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Model experiments
  • Analytics
    • Analytics
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Commits
Collapse sidebar
  • xenomaixenomai
  • ipipe-ppc32
  • Repository
  • ipipe-ppc32
  • drivers
  • cpufreq
  • cpufreq.c
Find file Blame History Permalink
  • Rafael J. Wysocki's avatar
    cpufreq: Do not clear real_cpus mask on policy init · f4510146
    Rafael J. Wysocki authored Feb 13, 2017
    
    
    If new_policy is set in cpufreq_online(), the policy object has just
    been created and its real_cpus mask has been zeroed on allocation,
    and the driver's ->init() callback should not touch it.
    
    It doesn't need to be cleared again, so don't do that.
    
    Signed-off-by: default avatarRafael J. Wysocki <rafael.j.wysocki@intel.com>
    Acked-by: default avatarViresh Kumar <viresh.kumar@linaro.org>
    f4510146

Imprint & Privacy Policy