From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Leo Yan <leo.yan@linaro.org>
Cc: Zhang Rui <rui.zhang@intel.com>,
edubezval@gmail.com,
"open list:THERMAL" <linux-pm@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
kong.kongxinwei@hisilicon.com
Subject: Re: [PATCH] thermal/drivers/hisi: Remove confusing error message
Date: Tue, 22 Aug 2017 10:25:07 +0200 [thread overview]
Message-ID: <12e90c78-d8dc-5184-17aa-281cd0ad5417@linaro.org> (raw)
In-Reply-To: <20170822080427.GB13910@leoy-ThinkPad-T440>
On 22/08/2017 10:04, Leo Yan wrote:
> Hi Daniel,
>
> On Mon, Aug 21, 2017 at 12:06:17PM +0200, Daniel Lezcano wrote:
>
> [...]
>
>> Hi Leo,
>>
>> a cleanest solution would be either:
>>
>> - add the 3 missing thermal sensors in the DT and default to the id 2
>
> Yeah, so do you think below change works for you?
Isn't it possible to set the delay also ? so we don't have to send
another patch if we want to use one of those instead of 2.
> ---8<---
>
> ARM64: dts: hisilicon: add missed thermal sensors for Hi6220
>
> The thermal driver tries to register four sensors but the DT only binds
> one sensor (sensor ID 2) with thermal zone, as result the thermal driver
> reports failure for missed thermal sensor binding.
>
> This patch adds missed thermal sensor for Hi6220, so can dismiss the
> booting failure log.
>
> diff --git a/arch/arm64/boot/dts/hisilicon/hi6220.dtsi b/arch/arm64/boot/dts/hisilicon/hi6220.dtsi
> index eacbe0d..44c2bc7 100644
> --- a/arch/arm64/boot/dts/hisilicon/hi6220.dtsi
> +++ b/arch/arm64/boot/dts/hisilicon/hi6220.dtsi
> @@ -833,6 +833,18 @@
>
> thermal-zones {
>
> + local: local {
> + polling-delay = <0>;
> + polling-delay-passive = <0>;
> + thermal-sensors = <&tsensor 0>;
> + };
> +
> + cls1: cls1 {
> + polling-delay = <0>;
> + polling-delay-passive = <0>;
> + thermal-sensors = <&tsensor 1>;
> + };
> +
> cls0: cls0 {
> polling-delay = <1000>;
> polling-delay-passive = <100>;
> @@ -862,6 +874,12 @@
> };
> };
> };
> +
> + gpu: gpu {
> + polling-delay = <0>;
> + polling-delay-passive = <0>;
> + thermal-sensors = <&tsensor 3>;
> + };
> };
>
>
>> or
>>
>> - remove all the code assuming 4 sensors and deal with the one unique
>> sensor
>
> I personally prefer to avoid doing this, if only register one unique
> sensor this will let us have no flexiblity for trying multiple sensors
> on this platform.
Ok, I will on the other side give a cleanup in the driver to optimize
the sensors lookup.
Thanks
-- Daniel
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2017-08-22 8:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-07 15:03 [PATCH] thermal/drivers/hisi: Remove confusing error message Daniel Lezcano
2017-08-08 7:55 ` Zhang Rui
2017-08-08 10:15 ` Daniel Lezcano
2017-08-08 12:48 ` Zhang Rui
2017-08-08 13:29 ` Leo Yan
2017-08-11 3:14 ` Zhang Rui
2017-08-21 10:06 ` Daniel Lezcano
2017-08-22 8:04 ` Leo Yan
2017-08-22 8:25 ` Daniel Lezcano [this message]
2017-08-23 6:13 ` Leo Yan
2017-12-05 1:52 ` Eduardo Valentin
2017-12-05 6:48 ` Daniel Lezcano
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=12e90c78-d8dc-5184-17aa-281cd0ad5417@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=edubezval@gmail.com \
--cc=kong.kongxinwei@hisilicon.com \
--cc=leo.yan@linaro.org \
--cc=linux-kernel@vger.kernel.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).