diff options
Diffstat (limited to 'Documentation/thermal/sysfs-api.txt')
-rw-r--r-- | Documentation/thermal/sysfs-api.txt | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/Documentation/thermal/sysfs-api.txt b/Documentation/thermal/sysfs-api.txt index cb3d15bc1aeb..b61e46f449aa 100644 --- a/Documentation/thermal/sysfs-api.txt +++ b/Documentation/thermal/sysfs-api.txt | |||
@@ -278,3 +278,15 @@ method, the sys I/F structure will be built like this: | |||
278 | |---name: acpitz | 278 | |---name: acpitz |
279 | |---temp1_input: 37000 | 279 | |---temp1_input: 37000 |
280 | |---temp1_crit: 100000 | 280 | |---temp1_crit: 100000 |
281 | |||
282 | 4. Event Notification | ||
283 | |||
284 | The framework includes a simple notification mechanism, in the form of a | ||
285 | netlink event. Netlink socket initialization is done during the _init_ | ||
286 | of the framework. Drivers which intend to use the notification mechanism | ||
287 | just need to call generate_netlink_event() with two arguments viz | ||
288 | (originator, event). Typically the originator will be an integer assigned | ||
289 | to a thermal_zone_device when it registers itself with the framework. The | ||
290 | event will be one of:{THERMAL_AUX0, THERMAL_AUX1, THERMAL_CRITICAL, | ||
291 | THERMAL_DEV_FAULT}. Notification can be sent when the current temperature | ||
292 | crosses any of the configured thresholds. | ||