All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kasagar, Srinidhi" <srinidhi.kasagar@intel.com>
To: rjw@rjwysocki.net, len.brown@intel.com
Cc: viresh.kumar@linaro.org, linux-pm@vger.kernel.org,
	vishwesh.m.rudramuni@intel.com, lenb@kernel.org,
	srinidhi.kasagar@intel.com
Subject: Re: [PATCH v5] cpufreq: Add SFI based cpufreq driver support
Date: Tue, 18 Nov 2014 11:40:31 +0530	[thread overview]
Message-ID: <20141118061031.GA28886@intel-desktop> (raw)
In-Reply-To: <20141118054537.GA28516@intel-desktop>

On Tue, Nov 18, 2014 at 11:15:45AM +0530, Srinidhi Kasagar wrote:
> This adds the SFI based cpu freq driver for some of the Intel's
> Silvermont based Atom architectures like Z34xx and Z35xx.
> 
> Signed-off-by: Rudramuni, Vishwesh M <vishwesh.m.rudramuni@intel.com>
> Signed-off-by: Srinidhi Kasagar <srinidhi.kasagar@intel.com>
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
> ---

[..]

> +static int sfi_cpufreq_register_performance(struct sfi_cpufreq_performance *pr)
> +{
> +	mutex_lock(&performance_mutex);
> +
> +	/* parse the freq table from SFI */
> +	sfi_table_parse(SFI_SIG_FREQ, NULL, NULL, parse_freq);
> +
> +	pr->state_count = sfi_cpufreq_num;
> +	if (pr->state_count <= 1) {
> +		pr_err("No p-states discovered\n");
> +		return -ENODEV;
Was in a hurry, will release the mutex in the next version. Let me
knmow if you have further comments.

Srinidhi

  reply	other threads:[~2014-11-18  6:09 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 [this message]
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
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=20141118061031.GA28886@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 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.