devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vincent Guittot <vincent.guittot@linaro.org>
To: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linaro-dev@lists.linaro.org,
	devicetree-discuss@lists.ozlabs.org
Cc: linux@arm.linux.org.uk, a.p.zijlstra@chello.nl,
	grant.likely@secretlab.ca, rob.herring@calxeda.com,
	yong.zhang0@gmail.com, namhyung@kernel.org,
	jean.pihet@newoldbits.com,
	Vincent Guittot <vincent.guittot@linaro.org>
Subject: [PATCH v3 0/5] ARM: topology: set the capacity of each cores for big.LITTLE
Date: Wed, 20 Jun 2012 17:19:17 +0200	[thread overview]
Message-ID: <1340205562-7653-1-git-send-email-vincent.guittot@linaro.org> (raw)

This patchset creates an arch_scale_freq_power function for ARM, which is used 
to set the relative capacity of each core of a big.LITTLE system. It also removes
the broken power estimation of x86.

Modification since v2:
 - set_power_scale function becomes static
 - Rework loop in update_siblings_masks
 - Remove useless code in parse_dt_topology

Modification since v1:
 - Add and update explanation about the use of the table and the range of the value 
 - Remove the use of NR_CPUS and use nr_cpu_ids instead
 - Remove broken power estimation of x86

Peter Zijlstra (1):
  sched, x86: Remove broken power estimation

Vincent Guittot (4):
  ARM: topology: Add arch_scale_freq_power function
  ARM: topology: factorize the update of sibling masks
  ARM: topology: Update cpu_power according to DT information
  sched: cpu_power: enable ARCH_POWER

 arch/arm/kernel/topology.c   |  209 +++++++++++++++++++++++++++++++++++++-----
 arch/x86/kernel/cpu/Makefile |    2 +-
 arch/x86/kernel/cpu/sched.c  |   55 -----------
 kernel/sched/features.h      |    2 +-
 4 files changed, 189 insertions(+), 79 deletions(-)
 delete mode 100644 arch/x86/kernel/cpu/sched.c

-- 
1.7.9.5

             reply	other threads:[~2012-06-20 15:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-20 15:19 Vincent Guittot [this message]
     [not found] ` <1340205562-7653-1-git-send-email-vincent.guittot-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2012-06-20 15:19   ` [PATCH v3 1/5] ARM: topology: Add arch_scale_freq_power function Vincent Guittot
2012-06-20 15:19   ` [PATCH v3 3/5] ARM: topology: Update cpu_power according to DT information Vincent Guittot
2012-07-02  9:11     ` Peter Zijlstra
2012-07-02 12:11       ` Vincent Guittot
     [not found]         ` <CAKfTPtAHvKcdgiL4xx-zBJU5DZ5YwGUbjgtoh9a1tf_C2Amg5w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-07-02 12:30           ` Peter Zijlstra
2012-06-20 15:19   ` [PATCH v3 4/5] sched, x86: Remove broken power estimation Vincent Guittot
2012-06-20 15:19   ` [PATCH v3 5/5] sched: cpu_power: enable ARCH_POWER Vincent Guittot
2012-06-20 15:19 ` [PATCH v3 2/5] ARM: topology: factorize the update of sibling masks Vincent Guittot
2012-06-21  0:01   ` Namhyung Kim

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=1340205562-7653-1-git-send-email-vincent.guittot@linaro.org \
    --to=vincent.guittot@linaro.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=jean.pihet@newoldbits.com \
    --cc=linaro-dev@lists.linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=namhyung@kernel.org \
    --cc=rob.herring@calxeda.com \
    --cc=yong.zhang0@gmail.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).