linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] cpufreq: cpu0: Extend support beyond CPU0
Date: Wed, 25 Jun 2014 14:12:27 +0530	[thread overview]
Message-ID: <cover.1403684824.git.viresh.kumar@linaro.org> (raw)

Stephen Boyd sent few patches today around a new cpufreq driver for Qualcomm's
Krait SoC: https://lkml.org/lkml/2014/6/24/918.

Krait couldn't use existing cpufreq-cpu0 driver as it doesn't have support for
SoC's with multiple clusters or SoC's which don't share clock line for all CPUs.
And I thought about trying updating cpu0 driver to see if we can get rid of this
limitation easily and use it for Krait as well.

It took me longer than I thought, around 4 hours to get this working on my dual
A15 exynos board.

First patch adds some space for driver specific data in 'struct cpufreq_policy'
and second one updates cpufreq-cpu0..

@Stephen: Can you please test this on Krait and see if it works?

Pushed here:
Rebased over rc2:
git://git.linaro.org/people/viresh.kumar/linux.git cpufreq/cpu0-krait

For guys looking to test on exynos, rebased over linux-next + some patches from
Thomas Abraham to use cpufreq-cpu0 for exynos:
git://git.linaro.org/people/viresh.kumar/linux.git cpufreq/cpu0-exynos


In case this is acceptable and bug free, next step would be to get cpufreq-cpu0
renamed a bit as its not about CPU0 anymore. Any suggestions on that would be
great :), cpufreq_generic.c ?

Thanks.

Viresh Kumar (2):
  cpufreq: Add support for per-policy driver data
  cpufreq: cpu0: Extend support beyond CPU0

 .../devicetree/bindings/cpufreq/cpufreq-cpu0.txt   |   8 +-
 drivers/cpufreq/Kconfig                            |   5 +-
 drivers/cpufreq/cpufreq-cpu0.c                     | 280 +++++++++++++--------
 include/linux/cpufreq.h                            |   3 +
 4 files changed, 193 insertions(+), 103 deletions(-)

-- 
2.0.0.rc2

             reply	other threads:[~2014-06-25  8:42 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-25  8:42 Viresh Kumar [this message]
2014-06-25  8:42 ` [PATCH 1/2] cpufreq: Add support for per-policy driver data Viresh Kumar
2014-06-25  8:42 ` [PATCH 2/2] cpufreq: cpu0: Extend support beyond CPU0 Viresh Kumar
2014-06-25 19:02   ` Stephen Boyd
2014-06-26  1:55     ` Viresh Kumar
2014-06-26  7:34     ` Viresh Kumar
2014-06-26 10:52     ` Viresh Kumar
2014-06-27  0:06       ` Stephen Boyd
2014-06-27  1:53         ` Mike Turquette
2014-06-27  2:15           ` Viresh Kumar
2014-06-30  7:57             ` Viresh Kumar
2014-06-30 18:33               ` Rob Herring
2014-07-01 11:14                 ` Viresh Kumar
2014-07-01 22:00                   ` Mike Turquette
2014-07-02  3:32                     ` Viresh Kumar
2014-06-27  2:26         ` Viresh Kumar
2014-06-26 22:08     ` Mark Brown
2014-06-28 14:52   ` Shawn Guo
2014-06-30  4:50     ` 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=cover.1403684824.git.viresh.kumar@linaro.org \
    --to=viresh.kumar@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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).