Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753732AbaLBEi0 (ORCPT ); Mon, 1 Dec 2014 23:38:26 -0500 Received: from mail-ob0-f179.google.com ([209.85.214.179]:47276 "EHLO mail-ob0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752701AbaLBEiY (ORCPT ); Mon, 1 Dec 2014 23:38:24 -0500 MIME-Version: 1.0 In-Reply-To: <547AD41F.7030907@huawei.com> References: <1417142619-14548-1-git-send-email-wangweidong1@huawei.com> <2248504.pAVebap2qN@vostro.rjw.lan> <547923F2.6000701@huawei.com> <4004530.x5fm24OG42@vostro.rjw.lan> <547AD41F.7030907@huawei.com> Date: Tue, 2 Dec 2014 10:08:24 +0530 Message-ID: Subject: Re: [PATCH 0/2] fix some problems for cpufreq From: Viresh Kumar To: Wang Weidong Cc: "Rafael J. Wysocki" , "linux-pm@vger.kernel.org" , Linux Kernel Mailing List , guohanjun@huawei.com Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 30 November 2014 at 13:53, Wang Weidong wrote: > No, there are not utilities and scripts relying on it. How can you be so sure about it ? There might be scripts/utils you aren't aware of and are depending on this.. > I just confuse that: > If the policy->min and policy-max is changed while it shows all available freqs > though scaling_available_frequencies. I can't set all freq-steps, only [policy->min, policy->max]. > why should it show all the available freqs. That's not the only purpose of those frequencies there. It shows list of all possible frequencies. Now, there can be issues if those lists are updated. Suppose somebody just played with the min/max frequency, now how would anybody come to know about the frequencies available above/below the user-max/min frequency? So as you mentioned in your example above: User space would never know about 1.05 Ghz and 2.3GHz anymore.. Unless you remember it or save it somewhere. > Although, it doesn't impact on us. So just ignore the patch#2. :) Probably yes. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/