From: Laxman Dewangan <ldewangan@nvidia.com>
To: <edubezval@gmail.com>, <rui.zhang@intel.com>,
<robh+dt@kernel.org>, <mark.rutland@arm.com>, <corbet@lwn.net>
Cc: <linux-pm@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-doc@vger.kernel.org>,
<rklein@nvidia.com>, Laxman Dewangan <ldewangan@nvidia.com>
Subject: [PATCH V2 4/6] thermal: doc: Add details of devm_thermal_zone_of_sensor_{register,unregister}
Date: Wed, 9 Mar 2016 18:40:08 +0530 [thread overview]
Message-ID: <1457529010-6538-5-git-send-email-ldewangan@nvidia.com> (raw)
In-Reply-To: <1457529010-6538-1-git-send-email-ldewangan@nvidia.com>
Add details of the interface devm_thermal_zone_of_sensor_register()
and devm_thermal_zone_of_sensor_unregister() in the
<thermal/sysfs-api.txt>.
Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
---
Changes from V1:
- New in series.
Documentation/thermal/sysfs-api.txt | 23 +++++++++++++++++++++++
1 file changed, 23 insertions(+)
diff --git a/Documentation/thermal/sysfs-api.txt b/Documentation/thermal/sysfs-api.txt
index 18a3a5e..ed419d6 100644
--- a/Documentation/thermal/sysfs-api.txt
+++ b/Documentation/thermal/sysfs-api.txt
@@ -117,6 +117,29 @@ temperature) and throttle appropriate devices.
interface. It will also silent the zone by remove the .get_temp() and
get_trend() thermal zone device callbacks.
+1.1.5 struct thermal_zone_device *devm_thermal_zone_of_sensor_register(
+ struct device *dev, int sensor_id,
+ void *data, const struct thermal_zone_of_device_ops *ops)
+
+ This interface is resource managed version of
+ thermal_zone_of_sensor_register().
+ All details of thermal_zone_of_sensor_register() described in
+ section 1.1.3 is applicable here.
+ The benefit of using this interface to register sensor is that it
+ is not require to explicitly call thermal_zone_of_sensor_unregister()
+ in error path or during driver unbinding as this is done by driver
+ resource manager.
+
+1.1.6 void devm_thermal_zone_of_sensor_unregister(struct device *dev,
+ struct thermal_zone_device *tzd)
+
+ This interface is resource managed version of
+ thermal_zone_of_sensor_unregister().
+ All details of thermal_zone_of_sensor_unregister() described in
+ section 1.1.4 is applicable here.
+ Normally this function will not need to be called and the resource
+ management code will ensure that the resource is freed.
+
1.2 thermal cooling device interface
1.2.1 struct thermal_cooling_device *thermal_cooling_device_register(char *name,
void *devdata, struct thermal_cooling_device_ops *)
--
2.1.4
next prev parent reply other threads:[~2016-03-09 13:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 13:10 [PATCH V2 0/6] thermal: add devm_ version of thermal_zone register and driver for max77620 Laxman Dewangan
2016-03-09 13:10 ` [PATCH V2 1/6] thermal: doc: Add details of thermal_zone_of_sensor_{register,unregister} Laxman Dewangan
2016-03-09 13:10 ` [PATCH V2 2/6] thermal: of-thermal: Add devm version of thermal_zone_of_sensor_register Laxman Dewangan
2016-03-09 13:10 ` [PATCH V2 3/6] thermal: Add devm_thermal_zone_of_sensor_register() in managed devices list Laxman Dewangan
2016-03-09 19:31 ` Eduardo Valentin
2016-03-09 13:10 ` Laxman Dewangan [this message]
2016-03-09 13:10 ` [PATCH V2 5/6] thermal: max77620: Add thermal driver for reporting junction temp Laxman Dewangan
2016-03-09 19:27 ` Eduardo Valentin
2016-03-10 6:56 ` Laxman Dewangan
2016-03-09 13:10 ` [PATCH V2 6/6] thermal: Add DT binding doc for thermal of PMIC max77620 Laxman Dewangan
2016-03-09 19:29 ` Eduardo Valentin
2016-03-09 18:29 ` [PATCH V2 0/6] thermal: add devm_ version of thermal_zone register and driver for max77620 Eduardo Valentin
2016-03-09 19:32 ` Eduardo Valentin
2016-03-10 6:55 ` Laxman Dewangan
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=1457529010-6538-5-git-send-email-ldewangan@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=edubezval@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=rklein@nvidia.com \
--cc=robh+dt@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
Powered by JetHome