From: Zhang Rui <rui.zhang@intel.com>
To: linux-pm@vger.kernel.org
Cc: amit.daniel@samsung.com, gu1@aeroxteam.fr,
hongbo.zhang@linaro.org, Zhang Rui <rui.zhang@intel.com>
Subject: [PATCH V2 0/2] Thermal: cpufreq cooling fix
Date: Fri, 8 Feb 2013 15:12:07 +0800 [thread overview]
Message-ID: <1360307529-5454-1-git-send-email-rui.zhang@intel.com> (raw)
cpufreq cooling uses different frequencies as different cooling states.
But the per_cpu cpufreq_frequency_table may contain duplicate,
invalid entries, and it may be in either ascending or descending order.
And currently, code for parsing the per_cpu cpufreq_frequency_table
is used in several places and inconsistent.
To fix this,
New code is introduce in Patch 1/2, which contains the logic
of parsing per_cpu cpufreq_frequency_table, and this piece of
code can be used to:
1. get the maximum cooling states
2. translate cpu frequency to cooling state
3. translate cooling state to cpu frequency
Patch 2/2 converts exynos_thermal driver to use the new code
introduced in Patch 1/2.
History:
V2: remove cpu cooling table to avoid extra memory allocation.
V1: introduce code to convert per_cpu cpufreq_frequency_table
to clean cpu cooling table (no invalid entry,
no duplicate entry, in descending order).
I just run build test here. It would be great that some of you
can test it on exynos.
any comments?
thanks,
rui
next reply other threads:[~2013-02-08 7:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 7:12 Zhang Rui [this message]
2013-02-08 7:12 ` [PATCH V2 1/2] Thermal: cpufreq cooling: fix parsing per_cpu cpufreq_frequency_table Zhang Rui
2013-02-08 7:12 ` [PATCH V2 2/2] Thermal: exynos: fix cooling state translation Zhang Rui
[not found] <CADGdYn5=SdybVW7zJdaXBmfj40Y4inkwtHrjikaYOwVabUz4MA@mail.gmail.com>
2013-02-11 3:44 ` [PATCH V2 0/2] Thermal: cpufreq cooling fix amit daniel kachhap
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=1360307529-5454-1-git-send-email-rui.zhang@intel.com \
--to=rui.zhang@intel.com \
--cc=amit.daniel@samsung.com \
--cc=gu1@aeroxteam.fr \
--cc=hongbo.zhang@linaro.org \
--cc=linux-pm@vger.kernel.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).