All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wang Weidong <wangweidong1@huawei.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	guohanjun@huawei.com
Subject: Re: [PATCH 0/2] fix some problems for cpufreq
Date: Wed, 3 Dec 2014 13:49:19 +0800	[thread overview]
Message-ID: <547EA45F.6060600@huawei.com> (raw)
In-Reply-To: <CAKohpomMWj8QRW5eYdTGXT+HEZpSA6AV5C6mUzYyC1N1fWV7vg@mail.gmail.com>

On 2014/12/2 12:38, Viresh Kumar wrote:
> On 30 November 2014 at 13:53, Wang Weidong <wangweidong1@huawei.com> 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.
> 

Nice, Thanks for your reply.

Got it.

Wang,
Regards

>> Although, it doesn't impact on us. So just ignore the patch#2. :)
> 
> Probably yes.
> 
> 



WARNING: multiple messages have this Message-ID (diff)
From: Wang Weidong <wangweidong1@huawei.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	<guohanjun@huawei.com>
Subject: Re: [PATCH 0/2] fix some problems for cpufreq
Date: Wed, 3 Dec 2014 13:49:19 +0800	[thread overview]
Message-ID: <547EA45F.6060600@huawei.com> (raw)
In-Reply-To: <CAKohpomMWj8QRW5eYdTGXT+HEZpSA6AV5C6mUzYyC1N1fWV7vg@mail.gmail.com>

On 2014/12/2 12:38, Viresh Kumar wrote:
> On 30 November 2014 at 13:53, Wang Weidong <wangweidong1@huawei.com> 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.
> 

Nice, Thanks for your reply.

Got it.

Wang,
Regards

>> Although, it doesn't impact on us. So just ignore the patch#2. :)
> 
> Probably yes.
> 
> 



  reply	other threads:[~2014-12-03  5:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-28  2:43 [PATCH 0/2] fix some problems for cpufreq Wang Weidong
2014-11-28  2:43 ` Wang Weidong
2014-11-28  2:43 ` [PATCH 1/2] acpi-cpufreq: make the freq_table store the same freq value Wang Weidong
2014-11-28  2:43   ` Wang Weidong
2014-11-28  2:43 ` [PATCH 2/2] cpufreq: show the real avail freqs with the freq_table Wang Weidong
2014-11-28  2:43   ` Wang Weidong
2014-11-29  1:26 ` [PATCH 0/2] fix some problems for cpufreq Rafael J. Wysocki
2014-11-29  1:40   ` Wang Weidong
2014-11-29  1:40     ` Wang Weidong
2014-11-29 22:30     ` Rafael J. Wysocki
2014-11-30  8:23       ` Wang Weidong
2014-11-30  8:23         ` Wang Weidong
2014-12-02  4:38         ` Viresh Kumar
2014-12-03  5:49           ` Wang Weidong [this message]
2014-12-03  5:49             ` Wang Weidong
2014-11-30 10:17 ` [PATCH v2] acpi-cpufreq: make the freq_table store the same freq value Wang Weidong
2014-11-30 10:17   ` Wang Weidong
2014-12-27  1:33   ` [PATCH RESEND " Wang Weidong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=547EA45F.6060600@huawei.com \
    --to=wangweidong1@huawei.com \
    --cc=guohanjun@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=viresh.kumar@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.