From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/2] thermal: mediatek: Add cpu power cooling model
Date: Fri, 6 Nov 2015 08:50:46 +0530 [thread overview]
Message-ID: <20151106032046.GK3773@ubuntu> (raw)
In-Reply-To: <1446721761.4016.56.camel@mtksdaap41>
On 05-11-15, 19:09, dawei chien wrote:
> Thank you for your kindly explaining, now I could understand what I
> miss, I will send device tree binding on next version such like
> following description.
>
> --- a/Documentation/devicetree/bindings/clock/mt8173-cpu-dvfs.txt
> +++ b/Documentation/devicetree/bindings/clock/mt8173-cpu-dvfs.txt
> @@ -10,6 +10,17 @@ Required properties:
> Please refer to
> Documentation/devicetree/bindings/clk/clock-bindings.txt for
> generic clock consumer properties.
> - proc-supply: Regulator for Vproc of CPU cluster.
> +- dynamic-power-coefficient:
> + Usage: optional
> + Value type: <prop-encoded-array>
> + Definition: A u32 value that represents an indicative
> + running time dynamic power coefficient in
> + fundamental units of mW/MHz/uVolt^2.
> + The dynamic energy consumption of the CPU
> + is proportional to the square of the
> + Voltage (V) and the clock frequency (f).
> + Pdyn = dynamic-power-coefficient * V^2 * f
> + where voltage is in uV, frequency is in MHz.
Please check with Punit if he is planning to add the same..
> Thank you for your kindly explaining, Now I know I should develop and
> test on mainline branch since this is where I try to add code.
>
> However, please understanding currently mt8173_cpufreq.c is not ready
> for OPPV2 in mainline as far, that's the reason why currently I can't
> reuse OPPV2 and extend for static power table. My propose is for adding
> CPU cooling device for our own product.
Firstly, we don't care. You are pushing something to mainline, you
have to get it tested someway on mainline.
Secondly, there are *almost* no changes required to the mtk cpufreq
driver for OPPV2. Just update your DT in a similar way it is done for
one of the exynos platforms and it should just work fine.
--
viresh
next prev parent reply other threads:[~2015-11-06 3:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 12:02 [PATCH v3 0/2] thermal: mediatek: Add cpu power cooling model Dawei Chien
2015-10-22 12:02 ` [PATCH v3 1/2] " Dawei Chien
2015-11-04 19:40 ` Eduardo Valentin
2015-11-05 11:10 ` dawei chien
2015-11-06 3:24 ` Viresh Kumar
2015-11-10 11:20 ` Javi Merino
2015-11-10 18:41 ` Eduardo Valentin
2015-11-11 9:36 ` Javi Merino
2015-11-13 5:02 ` Viresh Kumar
2015-10-22 12:02 ` [PATCH v3 2/2] arm64: dts: mt8173: Add thermal zone node for mt8173 Dawei Chien
2015-10-28 15:39 ` Viresh Kumar
2015-11-02 10:51 ` dawei chien
2015-11-04 19:41 ` Eduardo Valentin
2015-11-05 11:10 ` dawei chien
2015-10-28 15:44 ` [PATCH v3 0/2] thermal: mediatek: Add cpu power cooling model Viresh Kumar
2015-11-02 10:46 ` dawei chien
2015-11-02 12:10 ` Viresh Kumar
2015-11-05 11:09 ` dawei chien
2015-11-06 3:20 ` Viresh Kumar [this message]
2015-11-11 12:00 ` dawei chien
2015-11-02 15:53 ` Punit Agrawal
2015-11-02 16:10 ` Viresh Kumar
2015-11-04 19:36 ` Eduardo Valentin
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=20151106032046.GK3773@ubuntu \
--to=viresh.kumar@linaro.org \
--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;
as well as URLs for NNTP newsgroup(s).