linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: "ego@linux.vnet.ibm.com" <ego@linux.vnet.ibm.com>
Cc: Linux PM list <linux-pm@vger.kernel.org>,
	"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
	Anton Blanchard <anton@samba.org>,
	"Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
Subject: Re: [PATCH v3 1/5] powernv: cpufreq driver for powernv platform
Date: Fri, 21 Mar 2014 19:04:27 +0530	[thread overview]
Message-ID: <CAKohpom9MFsWjionC0S7zyZ479s8tsK150hhZ0frdJ-QKN_ZNg@mail.gmail.com> (raw)
In-Reply-To: <20140321132326.GE2493@in.ibm.com>

On 21 March 2014 18:53, Gautham R Shenoy <ego@linux.vnet.ibm.com> wrote:
> Ok, I had based my code on linus's git tree. I checked the 'pm-cpufreq'

Always check his bleeding-edge or linux-next branch.

> branch of Rafael's 'linux-pm' tree and freq_table.c contains the
> following code snippet in show_available_frequencies:
>
>         if (show_boost ^ (table[i].driver_data == CPUFREQ_BOOST_FREQ))
>                         continue;
>
> I suspect we're talking about different code bases. So could you
> please tell me which one should I be looking at ?

Okay, there is some problem here. I will check how can I simplify this..
And yes, you were correct.

>> Because cpufreq_frequency_table_get_attr() and
>> cpufreq_frequency_table_put_attr() don't exist anymore :)
>
> Well, it does in the codebases that I was looking at. May be I've been
> looking at the wrong place.

Check the one I mentioned.

  reply	other threads:[~2014-03-21 13:34 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-20 12:10 [PATCH v3 0/5] powernv: Enable Dynamic Frequency Gautham R. Shenoy
2014-03-20 12:10 ` [PATCH v3 1/5] powernv: cpufreq driver for powernv platform Gautham R. Shenoy
2014-03-21  8:41   ` Viresh Kumar
2014-03-21 10:43     ` Gautham R Shenoy
2014-03-21 10:54       ` Viresh Kumar
2014-03-21 11:40         ` Srivatsa S. Bhat
2014-03-21 13:23         ` Gautham R Shenoy
2014-03-21 13:34           ` Viresh Kumar [this message]
2014-03-21 14:54         ` Gautham R Shenoy
2014-03-22  3:43           ` Viresh Kumar
2014-03-21 14:48       ` Vaidyanathan Srinivasan
2014-03-22  3:43         ` Viresh Kumar
2014-03-21 11:45     ` Srivatsa S. Bhat
2014-03-21 11:47       ` Viresh Kumar
2014-03-20 12:10 ` [PATCH v3 2/5] powernv, cpufreq:Add per-core locking to serialize frequency transitions Gautham R. Shenoy
2014-03-21  6:24   ` Gautham R Shenoy
2014-03-21  8:42   ` Viresh Kumar
2014-03-21  9:56     ` Srivatsa S. Bhat
2014-03-20 12:10 ` [PATCH v3 3/5] powernv:cpufreq: Create pstate_id_to_freq() helper Gautham R. Shenoy
2014-03-21  6:24   ` Gautham R Shenoy
2014-03-20 12:10 ` [PATCH v3 4/5] powernv:cpufreq: Export nominal frequency via sysfs Gautham R. Shenoy
2014-03-21  8:47   ` Viresh Kumar
2014-03-21  9:55     ` Gautham R Shenoy
2014-03-21  9:57       ` Viresh Kumar
2014-03-20 12:11 ` [PATCH v3 5/5] powernv:cpufreq: Implement the driver->get() method Gautham R. Shenoy
2014-03-21  6:25   ` Gautham R Shenoy
2014-03-21  9:31   ` Viresh Kumar
2014-03-21 11:04     ` Gautham R Shenoy
2014-03-21 11:45       ` Viresh Kumar
2014-03-21 12:01         ` David Laight
2014-03-21 12:31           ` Gautham R Shenoy
2014-03-21 12:34           ` Viresh Kumar
2014-03-21 15:01             ` David Laight
2014-03-21 13:04         ` Gautham R Shenoy
2014-03-21 13:12           ` Viresh Kumar
2014-03-21 14:25             ` Gautham R Shenoy
2014-03-21 22:56       ` Benjamin Herrenschmidt
2014-03-22  7:53         ` Gautham R Shenoy
2014-03-21  7:46 ` [PATCH v3 0/5] powernv: Enable Dynamic Frequency Viresh Kumar
2014-03-21  8:19   ` 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=CAKohpom9MFsWjionC0S7zyZ479s8tsK150hhZ0frdJ-QKN_ZNg@mail.gmail.com \
    --to=viresh.kumar@linaro.org \
    --cc=anton@samba.org \
    --cc=ego@linux.vnet.ibm.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=srivatsa.bhat@linux.vnet.ibm.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).