From: Wei Ni <wni@nvidia.com>
To: Eduardo Valentin <eduardo.valentin@ti.com>,
"swarren@wwwdotorg.org" <swarren@wwwdotorg.org>,
"pawel.moll@arm.com" <pawel.moll@arm.com>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"ian.campbell@citrix.com" <ian.campbell@citrix.com>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
"linux@roeck-us.net" <linux@roeck-us.net>,
"rui.zhang@intel.com" <rui.zhang@intel.com>
Cc: "grant.likely@linaro.org" <grant.likely@linaro.org>,
"durgadoss.r@intel.com" <durgadoss.r@intel.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"lm-sensors@lm-sensors.org" <lm-sensors@lm-sensors.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCHv4 02/18] thermal: core: allow binding via .bind when tzp is present
Date: Wed, 6 Nov 2013 10:56:48 +0800 [thread overview]
Message-ID: <5279AFF0.1080105@nvidia.com> (raw)
In-Reply-To: <1380251605-3804-3-git-send-email-eduardo.valentin@ti.com>
On 09/27/2013 11:13 AM, Eduardo Valentin wrote:
> This patch allows drivers register thermal zone devices
> with thermal zone params and .bind callbacks. In this case,
> it will use the .bind callback.
>
> Cc: Zhang Rui <rui.zhang@intel.com>
> Cc: linux-pm@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
> Signed-off-by: Eduardo Valentin <eduardo.valentin@ti.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 8a94300..f7a9f4f 100644
> --- a/drivers/thermal/thermal_core.c
> +++ b/drivers/thermal/thermal_core.c
> @@ -247,7 +247,7 @@ static void bind_cdev(struct thermal_cooling_device *cdev)
> if (!pos->tzp && !pos->ops->bind)
> continue;
>
> - if (!pos->tzp && pos->ops->bind) {
> + if (pos->ops->bind) {
Hi, Eduardo
In bind_tz() routine, it also has same problem.
I had sent out similar patch "[PATCHv4 02/18] thermal: core: allow
binding via .bind when tzp is present" to fix it, but no response yet.
I think you can add my changes in your series :)
Thanks.
Wei.
> ret = pos->ops->bind(pos, cdev);
> if (ret)
> print_bind_err_msg(pos, cdev, ret);
>
next prev parent reply other threads:[~2013-11-06 2:56 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-27 3:13 [PATCHv4 00/18] device thermal limits represented in device tree nodes (v4) Eduardo Valentin
2013-09-27 3:13 ` [PATCHv4 01/18] thermal: allow registering without .get_temp Eduardo Valentin
2013-09-27 3:13 ` [PATCHv4 02/18] thermal: core: allow binding via .bind when tzp is present Eduardo Valentin
2013-11-06 2:56 ` Wei Ni [this message]
2013-09-27 3:13 ` [PATCHv7 03/18] thermal: introduce device tree parser Eduardo Valentin
2013-09-30 15:36 ` Mark Rutland
[not found] ` <20130930153614.GA22259-NuALmloUBlrZROr8t4l/smS4ubULX0JqMm0uRHvK7Nw@public.gmane.org>
2013-09-30 20:47 ` Eduardo Valentin
[not found] ` <1380251605-3804-4-git-send-email-eduardo.valentin-l0cyMroinI0@public.gmane.org>
2013-10-01 2:39 ` [PATCHv8 " Eduardo Valentin
2013-10-07 20:51 ` Mark Rutland
2013-10-08 14:59 ` Eduardo Valentin
2013-11-05 18:08 ` Eduardo Valentin
2013-09-27 3:13 ` [PATCHv4 05/18] thermal: cpu_cooling: introduce of_cpufreq_cooling_register Eduardo Valentin
2013-09-27 3:13 ` [PATCHv4 06/18] cpufreq: cpufreq-cpu0: add dt node parsing for cooling device properties Eduardo Valentin
2013-09-27 3:13 ` [PATCHv4 07/18] hwmon: lm75: expose to thermal fw via DT nodes Eduardo Valentin
2013-09-27 3:13 ` [PATCHv4 09/18] thermal: ti-soc-thermal: use thermal DT infrastructure Eduardo Valentin
2013-09-27 3:13 ` [PATCHv4 10/18] arm: dts: add omap4 CPU thermal data Eduardo Valentin
2013-09-27 3:13 ` [PATCHv4 11/18] arm: dts: add omap4430 " Eduardo Valentin
2013-09-27 12:24 ` Nishanth Menon
2013-09-27 13:20 ` Eduardo Valentin
2013-09-27 13:26 ` Nishanth Menon
2013-09-27 13:42 ` Eduardo Valentin
2013-09-27 3:13 ` [PATCHv4 12/18] arm: dts: add omap4460 " Eduardo Valentin
[not found] ` <1380251605-3804-1-git-send-email-eduardo.valentin-l0cyMroinI0@public.gmane.org>
2013-09-27 3:13 ` [PATCHv4 04/18] thermal: core: introduce thermal_of_cooling_device_register Eduardo Valentin
2013-09-27 3:13 ` [PATCHv4 08/18] hwmon: tmp102: expose to thermal fw via DT nodes Eduardo Valentin
2013-09-27 3:13 ` [PATCHv4 13/18] arm: dts: add cooling properties on omap4430 cpu node Eduardo Valentin
2013-09-27 3:13 ` [PATCHv4 17/18] arm: dts: add omap5 thermal data Eduardo Valentin
2013-09-27 3:13 ` [PATCHv4 18/18] arm: dts: add cooling properties on omap5 cpu node Eduardo Valentin
2013-09-27 3:13 ` [PATCHv4 14/18] arm: dts: add cooling properties on omap4460 " Eduardo Valentin
2013-09-27 3:13 ` [PATCHv4 15/18] arm: dts: add omap5 GPU thermal data Eduardo Valentin
2013-09-27 3:13 ` [PATCHv4 16/18] arm: dts: add omap5 CORE " Eduardo Valentin
2013-09-27 3:15 ` [PATCHv4 00/18] device thermal limits represented in device tree nodes (v4) 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=5279AFF0.1080105@nvidia.com \
--to=wni@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=durgadoss.r@intel.com \
--cc=eduardo.valentin@ti.com \
--cc=grant.likely@linaro.org \
--cc=ian.campbell@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lm-sensors@lm-sensors.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=rui.zhang@intel.com \
--cc=swarren@wwwdotorg.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).