From: Wei Ni <wni@nvidia.com>
To: "rui.zhang@intel.com" <rui.zhang@intel.com>
Cc: "durgadoss.r@intel.com" <durgadoss.r@intel.com>,
"eduardo.valentin@ti.com" <eduardo.valentin@ti.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
Wei Ni <wni@nvidia.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Thermal: Allow first update of cooling device state
Date: Mon, 24 Feb 2014 15:13:56 +0800 [thread overview]
Message-ID: <530AF134.4000505@nvidia.com> (raw)
In-Reply-To: <1392606175-19635-1-git-send-email-wni@nvidia.com>
Hi, Rui
Do you have any comment for it ?
Thanks.
Wei.
On 02/17/2014 11:02 AM, Wei Ni wrote:
> In initialization, if the cooling device is initialized at
> max cooling state, and the thermal zone temperature is below
> the first trip point, then the cooling state can't be updated
> to the right state, untill the first trip point be triggered.
>
> To fix this issue, allow first update of cooling device state
> during registration, initialized "updated" device field as
> "false" (instead of "true").
>
> Signed-off-by: Wei Ni <wni@nvidia.com>
> ---
> drivers/thermal/thermal_core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/thermal/thermal_core.c b/drivers/thermal/thermal_core.c
> index 338a88b..02f57af 100644
> --- a/drivers/thermal/thermal_core.c
> +++ b/drivers/thermal/thermal_core.c
> @@ -1107,7 +1107,7 @@ __thermal_cooling_device_register(struct device_node *np,
> INIT_LIST_HEAD(&cdev->thermal_instances);
> cdev->np = np;
> cdev->ops = ops;
> - cdev->updated = true;
> + cdev->updated = false;
> cdev->device.class = &thermal_class;
> cdev->devdata = devdata;
> dev_set_name(&cdev->device, "cooling_device%d", cdev->id);
>
next prev parent reply other threads:[~2014-02-24 7:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 3:02 [PATCH] Thermal: Allow first update of cooling device state Wei Ni
2014-02-24 7:13 ` Wei Ni [this message]
2014-02-27 6:49 ` 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=530AF134.4000505@nvidia.com \
--to=wni@nvidia.com \
--cc=durgadoss.r@intel.com \
--cc=eduardo.valentin@ti.com \
--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 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.