diff options
| author | Eduardo Valentin <eduardo.valentin@ti.com> | 2013-01-02 15:29:39 +0000 |
|---|---|---|
| committer | Zhang Rui <rui.zhang@intel.com> | 2013-01-16 10:46:46 +0800 |
| commit | 8ab3e6a08a98f7ff18c6814065eb30ba2e000233 (patch) | |
| tree | 79653389ffbff8e748815ca13a7a925e585ca2a9 /Documentation/thermal | |
| parent | c076fc42a4d6c51d6422aaf9f6626bf1adf983e7 (diff) | |
thermal: Use thermal zone device id in netlink messages
This patch changes the function thermal_generate_netlink_event
to receive a thermal zone device instead of a originator id.
This way, the messages will always be bound to a thermal zone.
Signed-off-by: Eduardo Valentin <eduardo.valentin@ti.com>
Reviewed-by: Durgadoss R <durgadoss.r@intel.com>
Signed-off-by: Zhang Rui <rui.zhang@intel.com>
Diffstat (limited to 'Documentation/thermal')
| -rw-r--r-- | Documentation/thermal/sysfs-api.txt | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/Documentation/thermal/sysfs-api.txt b/Documentation/thermal/sysfs-api.txt index 88c02334e356..526d4b90d6c1 100644 --- a/Documentation/thermal/sysfs-api.txt +++ b/Documentation/thermal/sysfs-api.txt @@ -329,8 +329,9 @@ The framework includes a simple notification mechanism, in the form of a netlink event. Netlink socket initialization is done during the _init_ of the framework. Drivers which intend to use the notification mechanism just need to call thermal_generate_netlink_event() with two arguments viz -(originator, event). Typically the originator will be an integer assigned -to a thermal_zone_device when it registers itself with the framework. The +(originator, event). The originator is a pointer to struct thermal_zone_device +from where the event has been originated. An integer which represents the +thermal zone device will be used in the message to identify the zone. The event will be one of:{THERMAL_AUX0, THERMAL_AUX1, THERMAL_CRITICAL, THERMAL_DEV_FAULT}. Notification can be sent when the current temperature crosses any of the configured thresholds. |