From: Eduardo Valentin <edubezval@gmail.com>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: rui.zhang@intel.com, eduardo.valentin@gmail.com,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
javi.merino@arm.com
Subject: Re: [PATCH] thermal: add support to disable thermal zone from DTS
Date: Tue, 29 Jul 2014 09:47:19 -0400 [thread overview]
Message-ID: <20140729134719.GD3336@developer> (raw)
In-Reply-To: <1406282518-31266-1-git-send-email-ldewangan@nvidia.com>
On Fri, Jul 25, 2014 at 03:31:58PM +0530, Laxman Dewangan wrote:
> Add support to check status of the thermal zone before registering the
> zone. This will help on disabling some non-existing thermal zone from
> the top level DTS file out of common dtsi thermalzone file.
>
> For example,
> we have 3 platforms almost same but thermal zones on this platform are
> little bit different. Platform 1 and 2 have three thermal zones and
> platform 3 has two thermal zones. To avoid duplication of the thermal
> zones entries on each DTS file of platforms,we created one common
> dtsi file for thermal zone and included this dtsi file from these
> 3 platform's top level dts file.
>
> On common thermal zone com dtsi file, all thermal zone are enabled and
> need to disable one of thermal zone on platform 3 dts file. For this, we
> just added entry status = "disabled" for that thermal zone on platform 3
> dts file and along with this change to make it work.
>
> This way, we reuse the common file and control the enable/disable of the
> thermal zone from top level dts file.
>
> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
This patch looks sane to me.
Applied. Thanks.
> ---
> drivers/thermal/of-thermal.c | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/drivers/thermal/of-thermal.c b/drivers/thermal/of-thermal.c
> index 4b2b999..f8eb625 100644
> --- a/drivers/thermal/of-thermal.c
> +++ b/drivers/thermal/of-thermal.c
> @@ -401,6 +401,10 @@ thermal_zone_of_sensor_register(struct device *dev, int sensor_id,
> struct of_phandle_args sensor_specs;
> int ret, id;
>
> + /* Check whether child is enabled or not */
> + if (!of_device_is_available(child))
> + continue;
> +
> /* For now, thermal framework supports only 1 sensor per zone */
> ret = of_parse_phandle_with_args(child, "thermal-sensors",
> "#thermal-sensor-cells",
> @@ -771,6 +775,10 @@ int __init of_parse_thermal_zones(void)
> struct thermal_zone_device *zone;
> struct thermal_zone_params *tzp;
>
> + /* Check whether child is enabled or not */
> + if (!of_device_is_available(child))
> + continue;
> +
> tz = thermal_of_build_thermal_zone(child);
> if (IS_ERR(tz)) {
> pr_err("failed to build thermal zone %s: %ld\n",
> @@ -838,6 +846,10 @@ void of_thermal_destroy_zones(void)
> for_each_child_of_node(np, child) {
> struct thermal_zone_device *zone;
>
> + /* Check whether child is enabled or not */
> + if (!of_device_is_available(child))
> + continue;
> +
> zone = thermal_zone_get_zone_by_name(child->name);
> if (IS_ERR(zone))
> continue;
> --
> 1.8.1.5
>
prev parent reply other threads:[~2014-07-29 13:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 10:01 [PATCH] thermal: add support to disable thermal zone from DTS Laxman Dewangan
2014-07-29 13:47 ` Eduardo Valentin [this message]
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=20140729134719.GD3336@developer \
--to=edubezval@gmail.com \
--cc=eduardo.valentin@gmail.com \
--cc=javi.merino@arm.com \
--cc=ldewangan@nvidia.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 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).