From: "Kasagar, Srinidhi" <srinidhi.kasagar@intel.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Brandewie, Dirk J" <dirk.j.brandewie@intel.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"Rudramuni, Vishwesh M" <vishwesh.m.rudramuni@intel.com>
Subject: Re: [PATCH] cpufreq: Add sfi based cpufreq driver support
Date: Fri, 10 Oct 2014 22:44:01 +0530 [thread overview]
Message-ID: <20141010171401.GA27359@intel-desktop> (raw)
In-Reply-To: <CAKohponh_1zBPZ9PxNACUZ-3WzPnbkpQCwmCmiTDEwGEW5D=Rg@mail.gmail.com>
On Fri, Oct 10, 2014 at 02:27:17PM +0530, Viresh Kumar wrote:
> On 10 October 2014 22:21, Kasagar, Srinidhi <srinidhi.kasagar@intel.com> wrote:
> > I have not debugged that. However, to double check the same I have rebased to the
> > clean upstream tree and I don't see ->target_index() is called for any
> > other CPUs during the offline-online path..
>
> OKay, this is getting a bit confusing.
>
> ->target_index() is called for which CPU?
It was called for the sibling cpu of the onlined one.
Srinidhi
next prev parent reply other threads:[~2014-10-10 9:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 14:07 [PATCH] cpufreq: Add sfi based cpufreq driver support Kasagar, Srinidhi
2014-10-07 10:22 ` Viresh Kumar
2014-10-08 19:14 ` Kasagar, Srinidhi
2014-10-09 4:03 ` Viresh Kumar
2014-10-09 18:08 ` Kasagar, Srinidhi
2014-10-09 10:18 ` Viresh Kumar
2014-10-09 19:07 ` Kasagar, Srinidhi
2014-10-09 11:15 ` Viresh Kumar
2014-10-10 16:51 ` Kasagar, Srinidhi
2014-10-10 8:57 ` Viresh Kumar
2014-10-10 17:14 ` Kasagar, Srinidhi [this message]
2014-10-10 9:27 ` Viresh Kumar
2014-10-10 10:47 ` Kasagar, Srinidhi
2014-10-10 11:11 ` Viresh Kumar
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=20141010171401.GA27359@intel-desktop \
--to=srinidhi.kasagar@intel.com \
--cc=dirk.j.brandewie@intel.com \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@linaro.org \
--cc=vishwesh.m.rudramuni@intel.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 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).