From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Chanwoo Choi <cw00.choi@samsung.com>
Cc: kgene@kernel.org, l.majewski@samsung.com,
kyungmin.park@samsung.com, linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: dts: Add CPU cooling binding for Exynos3250-based Rinato/Monk board
Date: Thu, 02 Jul 2015 16:17:16 +0900 [thread overview]
Message-ID: <5594E57C.2010300@samsung.com> (raw)
In-Reply-To: <5594D5F4.3060508@samsung.com>
On 02.07.2015 15:11, Chanwoo Choi wrote:
> On 07/02/2015 02:54 PM, Krzysztof Kozlowski wrote:
>> On 02.07.2015 14:37, Chanwoo Choi wrote:
>>> This patch add the cooling device to control the overheating issue on
>>> Exynos3250-based Rinato/Monk board.
>>>
>>> Cc: Kukjin Kim <kgene@kernel.org>
>>> Cc: Krzysztof Kozlowski <k.kozlowski@samsung.com>
>>> Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
>>> Acked-by: Kyungmin Park <kyungmin.park@samsung.com>
>>> ---
>>> Depends on:
>>> This patch needs the cpufreq support of Exynos3250 SoC. So, this patch has the
>>> dependency on patch[1] which support the generic cpufreq for Exynos3250 SoC.
>>> [1] https://lkml.org/lkml/2015/7/1/696
>>> : [PATCH v6 0/3] cpufreq: Use cpufreq-dt driver for Exynos3250
>>>
>>> arch/arm/boot/dts/exynos3250-monk.dts | 15 +++++++++++++++
>>> arch/arm/boot/dts/exynos3250-rinato.dts | 15 +++++++++++++++
>>> arch/arm/boot/dts/exynos3250.dtsi | 1 +
>>> 3 files changed, 31 insertions(+)
>>>
>>> diff --git a/arch/arm/boot/dts/exynos3250-monk.dts b/arch/arm/boot/dts/exynos3250-monk.dts
>>> index 7863265d4868..540a0adf2be6 100644
>>> --- a/arch/arm/boot/dts/exynos3250-monk.dts
>>> +++ b/arch/arm/boot/dts/exynos3250-monk.dts
>>> @@ -116,6 +116,21 @@
>>> min-microvolt = <1100000>;
>>> max-microvolt = <2700000>;
>>> };
>>> +
>>> + thermal-zones {
>>> + cpu_thermal: cpu-thermal {
>>> + cooling-maps {
>>> + map0 {
>>> + /* Correspond to 500MHz at freq_table */
>>> + cooling-device = <&cpu0 5 5>;
>>> + };
>>> + map1 {
>>> + /* Correspond to 200MHz at freq_table */
>>> + cooling-device = <&cpu0 8 8>;
>>> + };
>>> + };
>>> + };
>>> + };
>>> };
>>>
>>> &adc {
>>> diff --git a/arch/arm/boot/dts/exynos3250-rinato.dts b/arch/arm/boot/dts/exynos3250-rinato.dts
>>> index ddd7ac283045..0e62a6435e07 100644
>>> --- a/arch/arm/boot/dts/exynos3250-rinato.dts
>>> +++ b/arch/arm/boot/dts/exynos3250-rinato.dts
>>> @@ -107,6 +107,21 @@
>>> min-microvolt = <1100000>;
>>> max-microvolt = <2700000>;
>>> };
>>> +
>>> + thermal-zones {
>>> + cpu_thermal: cpu-thermal {
>>> + cooling-maps {
>>> + map0 {
>>> + /* Corresponds to 500MHz */
>>> + cooling-device = <&cpu0 5 5>;
>>> + };
>>> + map1 {
>>> + /* Corresponds to 200MHz */
>>> + cooling-device = <&cpu0 8 8>;
>>> + };
>>> + };
>>> + };
>>> + };
>>> };
>>>
>>> &adc {
>>> diff --git a/arch/arm/boot/dts/exynos3250.dtsi b/arch/arm/boot/dts/exynos3250.dtsi
>>> index e0f3b2ed41a3..a4931b660ddb 100644
>>> --- a/arch/arm/boot/dts/exynos3250.dtsi
>>> +++ b/arch/arm/boot/dts/exynos3250.dtsi
>>> @@ -55,6 +55,7 @@
>>> clock-frequency = <1000000000>;
>>> clocks = <&cmu CLK_ARM_CLK>;
>>> clock-names = "cpu";
>>> + #cooling-cells = <2>;
>>>
>>
>> Don't you need also cooling-{min,max}-state properties?
>
> Yes, it is well working without cooling-{min,max}-state or cooling-{min,max}-level.
>
> I look for the some code to parse "cooling-{min,max}-state or cooling-{min,max}-level"
> in drivers/thermal/*. But, there are no any code to parse it.
>
> But, Documentation/devicetree/bindings/thermal/thermal.txt contains just the 'cooling-{min,max}-state.
>
> I think that there are mismatch between document and thermal core driver.
Thanks for explanation, looks good.
Acked-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Best regards,
Krzysztof
WARNING: multiple messages have this Message-ID (diff)
From: k.kozlowski@samsung.com (Krzysztof Kozlowski)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: Add CPU cooling binding for Exynos3250-based Rinato/Monk board
Date: Thu, 02 Jul 2015 16:17:16 +0900 [thread overview]
Message-ID: <5594E57C.2010300@samsung.com> (raw)
In-Reply-To: <5594D5F4.3060508@samsung.com>
On 02.07.2015 15:11, Chanwoo Choi wrote:
> On 07/02/2015 02:54 PM, Krzysztof Kozlowski wrote:
>> On 02.07.2015 14:37, Chanwoo Choi wrote:
>>> This patch add the cooling device to control the overheating issue on
>>> Exynos3250-based Rinato/Monk board.
>>>
>>> Cc: Kukjin Kim <kgene@kernel.org>
>>> Cc: Krzysztof Kozlowski <k.kozlowski@samsung.com>
>>> Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
>>> Acked-by: Kyungmin Park <kyungmin.park@samsung.com>
>>> ---
>>> Depends on:
>>> This patch needs the cpufreq support of Exynos3250 SoC. So, this patch has the
>>> dependency on patch[1] which support the generic cpufreq for Exynos3250 SoC.
>>> [1] https://lkml.org/lkml/2015/7/1/696
>>> : [PATCH v6 0/3] cpufreq: Use cpufreq-dt driver for Exynos3250
>>>
>>> arch/arm/boot/dts/exynos3250-monk.dts | 15 +++++++++++++++
>>> arch/arm/boot/dts/exynos3250-rinato.dts | 15 +++++++++++++++
>>> arch/arm/boot/dts/exynos3250.dtsi | 1 +
>>> 3 files changed, 31 insertions(+)
>>>
>>> diff --git a/arch/arm/boot/dts/exynos3250-monk.dts b/arch/arm/boot/dts/exynos3250-monk.dts
>>> index 7863265d4868..540a0adf2be6 100644
>>> --- a/arch/arm/boot/dts/exynos3250-monk.dts
>>> +++ b/arch/arm/boot/dts/exynos3250-monk.dts
>>> @@ -116,6 +116,21 @@
>>> min-microvolt = <1100000>;
>>> max-microvolt = <2700000>;
>>> };
>>> +
>>> + thermal-zones {
>>> + cpu_thermal: cpu-thermal {
>>> + cooling-maps {
>>> + map0 {
>>> + /* Correspond to 500MHz at freq_table */
>>> + cooling-device = <&cpu0 5 5>;
>>> + };
>>> + map1 {
>>> + /* Correspond to 200MHz at freq_table */
>>> + cooling-device = <&cpu0 8 8>;
>>> + };
>>> + };
>>> + };
>>> + };
>>> };
>>>
>>> &adc {
>>> diff --git a/arch/arm/boot/dts/exynos3250-rinato.dts b/arch/arm/boot/dts/exynos3250-rinato.dts
>>> index ddd7ac283045..0e62a6435e07 100644
>>> --- a/arch/arm/boot/dts/exynos3250-rinato.dts
>>> +++ b/arch/arm/boot/dts/exynos3250-rinato.dts
>>> @@ -107,6 +107,21 @@
>>> min-microvolt = <1100000>;
>>> max-microvolt = <2700000>;
>>> };
>>> +
>>> + thermal-zones {
>>> + cpu_thermal: cpu-thermal {
>>> + cooling-maps {
>>> + map0 {
>>> + /* Corresponds to 500MHz */
>>> + cooling-device = <&cpu0 5 5>;
>>> + };
>>> + map1 {
>>> + /* Corresponds to 200MHz */
>>> + cooling-device = <&cpu0 8 8>;
>>> + };
>>> + };
>>> + };
>>> + };
>>> };
>>>
>>> &adc {
>>> diff --git a/arch/arm/boot/dts/exynos3250.dtsi b/arch/arm/boot/dts/exynos3250.dtsi
>>> index e0f3b2ed41a3..a4931b660ddb 100644
>>> --- a/arch/arm/boot/dts/exynos3250.dtsi
>>> +++ b/arch/arm/boot/dts/exynos3250.dtsi
>>> @@ -55,6 +55,7 @@
>>> clock-frequency = <1000000000>;
>>> clocks = <&cmu CLK_ARM_CLK>;
>>> clock-names = "cpu";
>>> + #cooling-cells = <2>;
>>>
>>
>> Don't you need also cooling-{min,max}-state properties?
>
> Yes, it is well working without cooling-{min,max}-state or cooling-{min,max}-level.
>
> I look for the some code to parse "cooling-{min,max}-state or cooling-{min,max}-level"
> in drivers/thermal/*. But, there are no any code to parse it.
>
> But, Documentation/devicetree/bindings/thermal/thermal.txt contains just the 'cooling-{min,max}-state.
>
> I think that there are mismatch between document and thermal core driver.
Thanks for explanation, looks good.
Acked-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Best regards,
Krzysztof
next prev parent reply other threads:[~2015-07-02 7:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 5:37 [PATCH] ARM: dts: Add CPU cooling binding for Exynos3250-based Rinato/Monk board Chanwoo Choi
2015-07-02 5:37 ` Chanwoo Choi
2015-07-02 5:54 ` Krzysztof Kozlowski
2015-07-02 5:54 ` Krzysztof Kozlowski
2015-07-02 6:11 ` Chanwoo Choi
2015-07-02 6:11 ` Chanwoo Choi
2015-07-02 7:17 ` Krzysztof Kozlowski [this message]
2015-07-02 7:17 ` Krzysztof Kozlowski
2015-07-06 1:08 ` Krzysztof Kozlowski
2015-07-06 1:08 ` Krzysztof Kozlowski
2015-07-07 14:40 ` Kukjin Kim
2015-07-07 14:40 ` Kukjin Kim
2015-07-08 0:19 ` Krzysztof Kozlowski
2015-07-08 0:19 ` Krzysztof Kozlowski
2015-07-29 6:35 ` Chanwoo Choi
2015-07-29 6:35 ` Chanwoo Choi
2015-07-30 14:03 ` Kukjin Kim
2015-07-30 14:03 ` Kukjin Kim
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=5594E57C.2010300@samsung.com \
--to=k.kozlowski@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=kgene@kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=l.majewski@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.