From: l.majewski@samsung.com (Lukasz Majewski)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC v3 0/5] cpufreq:LAB: Support for LAB governor.
Date: Mon, 17 Mar 2014 16:38:24 +0100 [thread overview]
Message-ID: <20140317163824.3c5480b3@amdc2363> (raw)
In-Reply-To: <1393928852-22725-1-git-send-email-l.majewski@samsung.com>
Dear all,
> Despite this patch set is working and applicable on top of 3.14-rc5,
> please regard it solely as a pure RFC.
>
> This patch provides support for LAB governor build on top of ondemand.
> Previous version of LAB can be found here:
> http://thread.gmane.org/gmane.linux.kernel/1484746/match=cpufreq
>
> LAB short reminder:
>
> LAB uses information about how many cores are in "idle" state (the
> core idleness is represented as the value between 0 and 100) and the
> overall load of the system (from 0 to 100) to decide about frequency
> to be set. It is extremely useful with SoCs like Exynos4412, which
> can set only one frequency for all cores.
>
> Important design decisions:
>
> - Reuse well established ondemand governor's internal code. To do this
> I had to expose some previously static internal ondemand code.
> This allowed smaller LAB code when compared to previous version.
>
> - LAB works on top of ondemand, which means that one via device tree
> attributes can specify if and when e.g. BOOST shall be enabled or
> if any particular frequency shall be imposed. For situation NOT
> important from the power consumption reduction viewpoint the ondemand
> is used to set proper frequency.
>
> - It is only possible to either compile in or not the LAB into the
> kernel. There is no "M" option for Kconfig. It is done on purpose,
> since ondemand itself can be also compiled as a module and then it
> would be possible to remove ondemand when LAB is working on top of it.
>
> - The LAB operation is specified (and thereof extendable) via device
> tree lab-ctrl-freq attribute defined at /cpus/cpu0.
>
>
> Problems:
> - How the governor will work for big.LITTLE systems (especially
> Global Task Scheduling).
> - Will there be agreement to expose internal ondemand code to be
> reused for more specialized governors.
>
> Test HW:
> Exynos4412 - Trats2 board.
> Above patches were posted on top of Linux 3.14-rc5
> (SHA1: 3f9590c281c66162bf8ae9b7b2d987f0a89043c6)
>
Any comments about those patches?
> Lukasz Majewski (5):
> cpufreq:LAB:ondemand Adjust ondemand to be able to reuse its methods
> cpufreq:LAB:cpufreq_governor Adjust cpufreq_governor.[h|c] to
> support LAB
> cpufreq:LAB:lab Add LAB governor code
> cpufreq:LAB:Kconfig Add LAB definitions to Kconfig
> cpufreq:LAB:dts:trats2: Add DTS nodes for LAB governor
>
> arch/arm/boot/dts/exynos4412-trats2.dts | 29 ++
> drivers/cpufreq/Kconfig | 28 ++
> drivers/cpufreq/Makefile | 1 +
> drivers/cpufreq/cpufreq_governor.c | 7 +
> drivers/cpufreq/cpufreq_governor.h | 12 +
> drivers/cpufreq/cpufreq_lab.c | 457
> +++++++++++++++++++++++++++++++
> drivers/cpufreq/cpufreq_ondemand.c | 24 +- 7 files changed,
> 550 insertions(+), 8 deletions(-) create mode 100644
> drivers/cpufreq/cpufreq_lab.c
>
--
Best regards,
Lukasz Majewski
Samsung R&D Institute Poland (SRPOL) | Linux Platform Group
next parent reply other threads:[~2014-03-17 15:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1367590072-10496-1-git-send-email-jonghwa3.lee@samsung.com>
[not found] ` <1393928852-22725-1-git-send-email-l.majewski@samsung.com>
2014-03-17 15:38 ` Lukasz Majewski [this message]
2014-03-18 6:55 ` [RFC v3 0/5] cpufreq:LAB: Support for LAB governor Viresh Kumar
2014-03-18 9:17 ` Lukasz Majewski
2014-03-24 6:47 ` Lukasz Majewski
2014-03-24 6:51 ` Viresh Kumar
2014-03-24 8:48 ` Viresh Kumar
2014-03-24 10:00 ` Lukasz Majewski
2014-03-24 10:15 ` 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=20140317163824.3c5480b3@amdc2363 \
--to=l.majewski@samsung.com \
--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