From: Sudeep Holla <sudeep.holla@arm.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Xiongfeng Wang <wangxiongfeng2@huawei.com>,
rjw@rjwysocki.net, guohanjun@huawei.com, ionela.voinescu@arm.com,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: [Question]: about 'cpuinfo_cur_freq' shown in sysfs when the CPU is in idle state
Date: Wed, 3 Jun 2020 11:17:53 +0100 [thread overview]
Message-ID: <20200603101753.GC7259@bogus> (raw)
In-Reply-To: <20200603101010.alijrfmte2c6xv5c@vireshk-i7>
On Wed, Jun 03, 2020 at 03:40:10PM +0530, Viresh Kumar wrote:
> On 03-06-20, 11:07, Sudeep Holla wrote:
> > But I have another question. If we can detect that CPPC on some platforms
> > rely on CPU registers(I assume FFH registers here and not system/io/...
> > type of GAS registers), can we set dvfs_on_any_cpu(can't recall exact
> > flag name) to false if not already done to prevent such issues. Or I am
> > talking non-sense as it may be applicable only for _set operation and
>
> Yes, non-sense :)
>
Thanks for confirming 👍.
--
Regards,
Sudeep
next prev parent reply other threads:[~2020-06-03 10:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 3:34 [Question]: about 'cpuinfo_cur_freq' shown in sysfs when the CPU is in idle state Xiongfeng Wang
2020-06-03 2:05 ` Hanjun Guo
2020-06-03 7:52 ` Viresh Kumar
2020-06-03 10:07 ` Sudeep Holla
2020-06-03 10:10 ` Viresh Kumar
2020-06-03 10:17 ` Sudeep Holla [this message]
2020-06-03 10:21 ` Viresh Kumar
2020-06-03 10:40 ` Sudeep Holla
2020-06-03 13:39 ` Rafael J. Wysocki
2020-06-04 1:32 ` Xiongfeng Wang
2020-06-04 4:41 ` Viresh Kumar
2020-06-04 10:42 ` Rafael J. Wysocki
2020-06-04 12:58 ` Sudeep Holla
2020-06-10 9:40 ` Ionela Voinescu
2020-06-11 1:52 ` Xiongfeng Wang
2020-06-12 11:55 ` Rafael J. Wysocki
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=20200603101753.GC7259@bogus \
--to=sudeep.holla@arm.com \
--cc=guohanjun@huawei.com \
--cc=ionela.voinescu@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@linaro.org \
--cc=wangxiongfeng2@huawei.com \
/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.