From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756633AbcCUOqs (ORCPT ); Mon, 21 Mar 2016 10:46:48 -0400 Received: from v094114.home.net.pl ([79.96.170.134]:51927 "HELO v094114.home.net.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1756151AbcCUOqL (ORCPT ); Mon, 21 Mar 2016 10:46:11 -0400 From: "Rafael J. Wysocki" To: Linux PM list Cc: Linux Kernel Mailing List , Viresh Kumar Subject: [PATCH 0/3] cpufreq: Governor start handling unification and cpufreq_resume() cleanup Date: Mon, 21 Mar 2016 15:44:17 +0100 Message-ID: <1780622.pJaGsuQWcI@vostro.rjw.lan> User-Agent: KMail/4.11.5 (Linux/4.5.0-rc1+; KDE/4.11.5; x86_64; ; ) MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, As per the subject, the following patches unify the handling of governor start throughout the cpufreq core and clean up the way cpufreq_resume() deals with policy->cur being out of sync with the real frequency. [1/3] introduces cpufreq_start_governor() to implement the repeating governor start code pattern. [2/3] moves the frequency update code from cpufreq_update_policy() to a separate function, cpufreq_update_current_freq(). [3/3] makes cpufreq_start_governor() call cpufreq_update_current_freq() and drops the (super-ugly and racy) piece of code to synchrnonize the frequency of the boot CPU with its policy->cur. Thanks, Rafael