From: amit kachhap <amit.kachhap@gmail.com>
To: Zhang Rui <rui.zhang@intel.com>
Cc: linux-pm@vger.kernel.org, Gu1 <gu1@aeroxteam.fr>,
Hongbo Zhang <hongbo.zhang@linaro.org>
Subject: Re: [PATCH V3 0/2] Thermal: cpufreq cooling fix
Date: Wed, 20 Mar 2013 11:15:34 +0530 [thread overview]
Message-ID: <CADGdYn4EZ7+3dmpSke0q+bgqoRJUL0HwL4rdDs9SCVwcHyWnow@mail.gmail.com> (raw)
In-Reply-To: <1363742754.2278.0.camel@rzhang1-mobl4>
On Wed, Mar 20, 2013 at 6:55 AM, Zhang Rui <rui.zhang@intel.com> wrote:
> Hi, Amit,
>
> On Fri, 2013-03-15 at 16:44 +0530, amit daniel kachhap wrote:
>> Hi Rui,
>>
>> For both the patches,
>> Acked by: Amit Daniel kachhap <amit.daniel@samsung.com>
>>
> thanks. Do you have a chance to test these patches?
yes I tested them and they are fine.
Feel free to add,
Tested by: Amit Daniel kachhap <amit.daniel@samsung.com>
Thanks,
Amit Daniel
>
> -rui
>
>> Thanks,
>> Amit Daniel
>>
>> On Fri, Mar 15, 2013 at 4:37 PM, AMIT DANIEL KACHHAP
>> <amit.daniel@samsung.com> wrote:
>> >
>> >
>> > ------- Original Message -------
>> > Sender : Zhang Rui<rui.zhang@intel.com>
>> > Date : Mar 12, 2013 00:33 (GMT+09:00)
>> > Title : [PATCH V3 0/2] Thermal: cpufreq cooling fix
>> >
>> > 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:
>> > V3: fix wrong return value of get_cpu_frequency().
>> > fix wrong return value of get_property() when property equals GET_MAXL.
>> >
>> > 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
>> > <p> </p><p> </p>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-pm" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
next prev parent reply other threads:[~2013-03-20 5:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <177643.168791363345666297.JavaMail.weblogic@epml10>
2013-03-15 11:14 ` [PATCH V3 0/2] Thermal: cpufreq cooling fix amit daniel kachhap
2013-03-20 1:25 ` Zhang Rui
2013-03-20 5:45 ` amit kachhap [this message]
2013-03-11 15:33 Zhang Rui
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=CADGdYn4EZ7+3dmpSke0q+bgqoRJUL0HwL4rdDs9SCVwcHyWnow@mail.gmail.com \
--to=amit.kachhap@gmail.com \
--cc=gu1@aeroxteam.fr \
--cc=hongbo.zhang@linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=rui.zhang@intel.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).