From: Viresh Kumar <viresh.kumar@linaro.org>
To: Abhishek <huntbag@linux.vnet.ibm.com>
Cc: ego@linux.vnet.ibm.com, rjw@rjwysocki.net,
benh@kernel.crashing.org, paulus@samba.org, mpe@ellerman.id.au,
linux-pm@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpufreq: powernv: Add support of frequency domain
Date: Mon, 18 Dec 2017 13:59:35 +0530 [thread overview]
Message-ID: <20171218082935.GH19815@vireshk-i7> (raw)
In-Reply-To: <93cc9d38-4fd8-d340-2263-108329b69b94@linux.vnet.ibm.com>
On 18-12-17, 10:41, Abhishek wrote:
> We need to do it in this way as the current implementation takes the max of
> the PMSR of the cores. Thus, when the frequency is required to be ramped up,
> it suffices to write to just the local PMSR, but when the frequency is to be
> ramped down, if we don't send the IPI it breaks the compatibility with P8.
Looks strange really that you have to program this differently for speeding up
or down. These CPUs are part of one cpufreq policy and so I would normally
expect changes to any CPU should reflect for other CPUs as well.
@Goutham: Do you know why it is so ?
--
viresh
next prev parent reply other threads:[~2017-12-18 8:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 8:19 [PATCH] cpufreq: powernv: Add support of frequency domain Abhishek Goel
2017-12-14 4:42 ` Viresh Kumar
2017-12-18 5:11 ` Abhishek
2017-12-18 8:29 ` Viresh Kumar [this message]
2017-12-19 9:20 ` Gautham R Shenoy
2017-12-19 10:21 ` Balbir Singh
2017-12-20 8:04 ` Gautham R Shenoy
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=20171218082935.GH19815@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=benh@kernel.crashing.org \
--cc=ego@linux.vnet.ibm.com \
--cc=huntbag@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=rjw@rjwysocki.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).