• Rafael J. Wysocki's avatar
    cpufreq: governor: Get rid of governor events · e788892b
    Rafael J. Wysocki authored
    The design of the cpufreq governor API is not very straightforward,
    as struct cpufreq_governor provides only one callback to be invoked
    from different code paths for different purposes.  The purpose it is
    invoked for is determined by its second "event" argument, causing it
    to act as a "callback multiplexer" of sorts.
    
    Unfortunately, that leads to extra complexity in governors, some of
    which implement the ->governor() callback as a switch statement
    that simply checks the event argument and invokes a separate function
    to handle that specific event.
    
    That extra complexity can be eliminated by replacing the all-purpose
    ->governor() callback with a family of callbacks to carry out specific
    governor operations: initialization and exit, start and stop and policy
    limits updates.  That also turns out to reduce the code size too, so
    do it.
    Signed-off-by: 's avatarRafael J. Wysocki <rafael.j.wysocki@intel.com>
    Acked-by: 's avatarViresh Kumar <viresh.kumar@linaro.org>
    e788892b