From: Laxman Dewangan <ldewangan@nvidia.com>
To: rui.zhang@intel.com, eduardo.valentin@ti.com
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Laxman Dewangan <ldewangan@nvidia.com>
Subject: [PATCH] thermal: of: look for sensor driver parent node if device node missing
Date: Mon, 14 Jul 2014 16:42:34 +0530 [thread overview]
Message-ID: <1405336354-31310-1-git-send-email-ldewangan@nvidia.com> (raw)
There are some mfd devices which supports junction thermal interrupt
like ams,AS3722. The DT binding of these devices are defined as the
flat and drivers for sub module of such devices are registered as
the mfd_add_devices. In this method, the sub devices registered as
platform driver and these do not have the of_node pointer on their
device structure. In this case, use the parent of_node pointer to
get the required of_node pointer.
Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
---
drivers/thermal/of-thermal.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/thermal/of-thermal.c b/drivers/thermal/of-thermal.c
index 04b1be7..85a7d71 100644
--- a/drivers/thermal/of-thermal.c
+++ b/drivers/thermal/of-thermal.c
@@ -396,6 +396,8 @@ thermal_zone_of_sensor_register(struct device *dev, int sensor_id,
return ERR_PTR(-EINVAL);
sensor_np = dev->of_node;
+ if (!sensor_np && dev->parent)
+ sensor_np = dev->parent->of_node;
for_each_child_of_node(np, child) {
struct of_phandle_args sensor_specs;
--
1.8.1.5
next reply other threads:[~2014-07-14 11:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 11:12 Laxman Dewangan [this message]
2014-07-14 12:04 ` [PATCH] thermal: of: look for sensor driver parent node if device node missing Lucas Stach
2014-07-30 13:18 ` Eduardo Valentin
2014-07-30 13:39 ` Laxman Dewangan
2014-07-30 14:26 ` Eduardo Valentin
2014-07-24 9:49 ` Laxman Dewangan
2014-07-24 15:15 ` Zhang, Rui
2014-07-24 16:38 ` Eduardo Valentin
2014-07-25 8:22 ` Laxman Dewangan
2014-07-25 8:35 ` Javi Merino
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=1405336354-31310-1-git-send-email-ldewangan@nvidia.com \
--to=ldewangan@nvidia.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 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).