From: "Kasagar, Srinidhi" <srinidhi.kasagar@intel.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
"Brown, Len" <len.brown@intel.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"Rudramuni, Vishwesh M" <vishwesh.m.rudramuni@intel.com>,
Len Brown <lenb@kernel.org>
Subject: Re: [PATCH v5] cpufreq: Add SFI based cpufreq driver support
Date: Wed, 19 Nov 2014 15:15:36 +0530 [thread overview]
Message-ID: <20141119094536.GA24181@intel-desktop> (raw)
In-Reply-To: <CAKohpo=hveN_pcmNHz4G2dGRM4u+ZSZEUTBgOTUzTqK-SPW-wQ@mail.gmail.com>
On Wed, Nov 19, 2014 at 01:03:38PM +0530, Viresh Kumar wrote:
> On 18 November 2014 22:51, Kasagar, Srinidhi <srinidhi.kasagar@intel.com> wrote:
> > Not anymore now..I have fixed it in my earlier version.
> >
> > $ cat /sys/devices/system/cpu/cpu*/cpufreq/affected_cpus
> > 0
> > 1
> > 2
> > 3
> >
> > $ cat /sys/devices/system/cpu/cpu*/cpufreq/related_cpus
> > 0
> > 1
> > 2
> > 3
>
> What do you mean by you have fixed it? Weren't the CPUs sharing clock lines?
> I hope cpu 0 and 1 should be sharing their clock lines, i.e. they
> change freq together.
> Also same for cpu 2 and 3.
The architecture supports both, and the current code allows me
to change the freq independently and that's why the above
output lines.
Srinidhi
next prev parent reply other threads:[~2014-11-19 9:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 5:45 [PATCH v5] cpufreq: Add SFI based cpufreq driver support Srinidhi Kasagar
2014-11-18 6:10 ` Kasagar, Srinidhi
2014-11-18 11:03 ` Viresh Kumar
2014-11-18 17:21 ` Kasagar, Srinidhi
2014-11-19 7:33 ` Viresh Kumar
2014-11-19 9:45 ` Kasagar, Srinidhi [this message]
2014-11-19 9:47 ` Viresh Kumar
2014-11-19 10:02 ` Kasagar, Srinidhi
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=20141119094536.GA24181@intel-desktop \
--to=srinidhi.kasagar@intel.com \
--cc=len.brown@intel.com \
--cc=lenb@kernel.org \
--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).