linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Rafael Wysocki <rjw@rjwysocki.net>
Cc: linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org, steve.muckle@linaro.org
Subject: Re: [PATCH V5 0/2] cpufreq: Sorted policy->freq_table
Date: Thu, 7 Jul 2016 08:36:38 -0700	[thread overview]
Message-ID: <20160707153638.GC3932@ubuntu> (raw)
In-Reply-To: <cover.1467001203.git.viresh.kumar@linaro.org>

On 27-06-16, 09:59, Viresh Kumar wrote:
> Hi Rafael,
> 
> This series is aimed to make traversing of cpufreq table more efficient
> for platforms that already sort the frequency tables. The cpufreq core
> now checks if the freq table is sorted and applies a different set of
> helpers on such tables while traversing them.
> 
> All the patches are pushed here for testing in case anyone wants to try:
> git://git.kernel.org/pub/scm/linux/kernel/git/vireshk/pm.git cpufreq/sorted-freq-table
> 
> V4->V4:
> - s/cpufreq_table_find_index_unsorted/cpufreq_table_index_unsorted
> - return error for duplicate frequencies
> - freq-table-sorted is an enum now
> - Remove freq_is_invalid() and clamp the frequencies at the top of few
>   helpers.
> - Remove few checks which were impossible to hit (best == -1)

Thanks Rafael for applying this series.

@Steve: I think you are unblocked now (sorry for the long delay) to get your
work going.

-- 
viresh

      parent reply	other threads:[~2016-07-07 15:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-27  4:29 [PATCH V5 0/2] cpufreq: Sorted policy->freq_table Viresh Kumar
2016-06-27  4:29 ` [PATCH V5 1/2] cpufreq: Handle sorted frequency tables more efficiently Viresh Kumar
2016-06-27 10:10   ` Francesco Lavra
2016-06-27 10:34   ` [PATCH V6 " Viresh Kumar
2016-07-07 13:29     ` Rafael J. Wysocki
2016-06-27  4:29 ` [PATCH V5 2/2] cpufreq: Reuse new freq-table helpers Viresh Kumar
2016-07-07 13:29   ` Rafael J. Wysocki
2016-07-07 15:36 ` Viresh Kumar [this message]

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=20160707153638.GC3932@ubuntu \
    --to=viresh.kumar@linaro.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=steve.muckle@linaro.org \
    /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).