Searched hist:b18ae08deac23187e4a22a8c94a1a473be8e8c93 (Results 1 – 2 of 2) sorted by relevance
| /openbmc/linux/arch/powerpc/platforms/cell/ |
| H A D | cpufreq_spudemand.c | diff b18ae08deac23187e4a22a8c94a1a473be8e8c93 Sun Jan 02 21:49:25 CST 2011 Tejun Heo <tj@kernel.org> powerpc/cell: Use system_wq in cpufreq_spudemand
With cmwq, there's no reason to use a separate workqueue in
cpufreq_spudemand. Use system_wq instead. The work items are already
sync canceled on stop, so it's already guaranteed that no work is
running when spu_gov_exit() is entered.
Signed-off-by: Tejun Heo <tj@kernel.org>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: linuxppc-dev@lists.ozlabs.org
Cc: Dave Jones <davej@redhat.com>
Cc: cpufreq@vger.kernel.org
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
|
| /openbmc/linux/arch/powerpc/kernel/ |
| H A D | time.c | diff b18ae08deac23187e4a22a8c94a1a473be8e8c93 Sun Jan 02 21:49:25 CST 2011 Tejun Heo <tj@kernel.org> powerpc/cell: Use system_wq in cpufreq_spudemand
With cmwq, there's no reason to use a separate workqueue in
cpufreq_spudemand. Use system_wq instead. The work items are already
sync canceled on stop, so it's already guaranteed that no work is
running when spu_gov_exit() is entered.
Signed-off-by: Tejun Heo <tj@kernel.org>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: linuxppc-dev@lists.ozlabs.org
Cc: Dave Jones <davej@redhat.com>
Cc: cpufreq@vger.kernel.org
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
|