]>
Commit | Line | Data |
---|---|---|
203d3d4a | 1 | Generic Thermal Sysfs driver How To |
38bb0849 | 2 | =================================== |
203d3d4a ZR |
3 | |
4 | Written by Sujith Thomas <sujith.thomas@intel.com>, Zhang Rui <rui.zhang@intel.com> | |
5 | ||
6 | Updated: 2 January 2008 | |
7 | ||
8 | Copyright (c) 2008 Intel Corporation | |
9 | ||
10 | ||
11 | 0. Introduction | |
12 | ||
38bb0849 FP |
13 | The generic thermal sysfs provides a set of interfaces for thermal zone |
14 | devices (sensors) and thermal cooling devices (fan, processor...) to register | |
15 | with the thermal management solution and to be a part of it. | |
203d3d4a | 16 | |
38bb0849 FP |
17 | This how-to focuses on enabling new thermal zone and cooling devices to |
18 | participate in thermal management. | |
19 | This solution is platform independent and any type of thermal zone devices | |
20 | and cooling devices should be able to make use of the infrastructure. | |
203d3d4a | 21 | |
38bb0849 FP |
22 | The main task of the thermal sysfs driver is to expose thermal zone attributes |
23 | as well as cooling device attributes to the user space. | |
24 | An intelligent thermal management application can make decisions based on | |
25 | inputs from thermal zone attributes (the current temperature and trip point | |
26 | temperature) and throttle appropriate devices. | |
203d3d4a ZR |
27 | |
28 | [0-*] denotes any positive number starting from 0 | |
29 | [1-*] denotes any positive number starting from 1 | |
30 | ||
31 | 1. thermal sysfs driver interface functions | |
32 | ||
33 | 1.1 thermal zone device interface | |
38bb0849 | 34 | 1.1.1 struct thermal_zone_device *thermal_zone_device_register(char *name, |
c56f5c03 D |
35 | int trips, int mask, void *devdata, |
36 | struct thermal_zone_device_ops *ops) | |
38bb0849 FP |
37 | |
38 | This interface function adds a new thermal zone device (sensor) to | |
39 | /sys/class/thermal folder as thermal_zone[0-*]. It tries to bind all the | |
40 | thermal cooling devices registered at the same time. | |
41 | ||
42 | name: the thermal zone name. | |
43 | trips: the total number of trip points this thermal zone supports. | |
c56f5c03 | 44 | mask: Bit string: If 'n'th bit is set, then trip point 'n' is writeable. |
38bb0849 FP |
45 | devdata: device private data |
46 | ops: thermal zone device call-backs. | |
47 | .bind: bind the thermal zone device with a thermal cooling device. | |
48 | .unbind: unbind the thermal zone device with a thermal cooling device. | |
49 | .get_temp: get the current temperature of the thermal zone. | |
8eaa8d6c ZR |
50 | .get_mode: get the current mode (enabled/disabled) of the thermal zone. |
51 | - "enabled" means the kernel thermal management is enabled. | |
52 | - "disabled" will prevent kernel thermal driver action upon trip points | |
38bb0849 | 53 | so that user applications can take charge of thermal management. |
8eaa8d6c | 54 | .set_mode: set the mode (enabled/disabled) of the thermal zone. |
38bb0849 FP |
55 | .get_trip_type: get the type of certain trip point. |
56 | .get_trip_temp: get the temperature above which the certain trip point | |
57 | will be fired. | |
e6e238c3 ADK |
58 | .set_emul_temp: set the emulation temperature which helps in debugging |
59 | different threshold temperature points. | |
203d3d4a ZR |
60 | |
61 | 1.1.2 void thermal_zone_device_unregister(struct thermal_zone_device *tz) | |
62 | ||
38bb0849 FP |
63 | This interface function removes the thermal zone device. |
64 | It deletes the corresponding entry form /sys/class/thermal folder and | |
65 | unbind all the thermal cooling devices it uses. | |
203d3d4a ZR |
66 | |
67 | 1.2 thermal cooling device interface | |
68 | 1.2.1 struct thermal_cooling_device *thermal_cooling_device_register(char *name, | |
38bb0849 FP |
69 | void *devdata, struct thermal_cooling_device_ops *) |
70 | ||
71 | This interface function adds a new thermal cooling device (fan/processor/...) | |
72 | to /sys/class/thermal/ folder as cooling_device[0-*]. It tries to bind itself | |
73 | to all the thermal zone devices register at the same time. | |
74 | name: the cooling device name. | |
75 | devdata: device private data. | |
76 | ops: thermal cooling devices call-backs. | |
77 | .get_max_state: get the Maximum throttle state of the cooling device. | |
78 | .get_cur_state: get the Current throttle state of the cooling device. | |
79 | .set_cur_state: set the Current throttle state of the cooling device. | |
203d3d4a ZR |
80 | |
81 | 1.2.2 void thermal_cooling_device_unregister(struct thermal_cooling_device *cdev) | |
82 | ||
38bb0849 FP |
83 | This interface function remove the thermal cooling device. |
84 | It deletes the corresponding entry form /sys/class/thermal folder and | |
85 | unbind itself from all the thermal zone devices using it. | |
203d3d4a ZR |
86 | |
87 | 1.3 interface for binding a thermal zone device with a thermal cooling device | |
88 | 1.3.1 int thermal_zone_bind_cooling_device(struct thermal_zone_device *tz, | |
9d99842f ZR |
89 | int trip, struct thermal_cooling_device *cdev, |
90 | unsigned long upper, unsigned long lower); | |
203d3d4a | 91 | |
38bb0849 FP |
92 | This interface function bind a thermal cooling device to the certain trip |
93 | point of a thermal zone device. | |
94 | This function is usually called in the thermal zone device .bind callback. | |
95 | tz: the thermal zone device | |
96 | cdev: thermal cooling device | |
97 | trip: indicates which trip point the cooling devices is associated with | |
98 | in this thermal zone. | |
9d99842f ZR |
99 | upper:the Maximum cooling state for this trip point. |
100 | THERMAL_NO_LIMIT means no upper limit, | |
101 | and the cooling device can be in max_state. | |
102 | lower:the Minimum cooling state can be used for this trip point. | |
103 | THERMAL_NO_LIMIT means no lower limit, | |
104 | and the cooling device can be in cooling state 0. | |
203d3d4a ZR |
105 | |
106 | 1.3.2 int thermal_zone_unbind_cooling_device(struct thermal_zone_device *tz, | |
38bb0849 | 107 | int trip, struct thermal_cooling_device *cdev); |
203d3d4a | 108 | |
38bb0849 FP |
109 | This interface function unbind a thermal cooling device from the certain |
110 | trip point of a thermal zone device. This function is usually called in | |
111 | the thermal zone device .unbind callback. | |
112 | tz: the thermal zone device | |
113 | cdev: thermal cooling device | |
114 | trip: indicates which trip point the cooling devices is associated with | |
115 | in this thermal zone. | |
203d3d4a | 116 | |
6ea083b1 D |
117 | 1.4 Thermal Zone Parameters |
118 | 1.4.1 struct thermal_bind_params | |
119 | This structure defines the following parameters that are used to bind | |
120 | a zone with a cooling device for a particular trip point. | |
121 | .cdev: The cooling device pointer | |
122 | .weight: The 'influence' of a particular cooling device on this zone. | |
123 | This is on a percentage scale. The sum of all these weights | |
124 | (for a particular zone) cannot exceed 100. | |
125 | .trip_mask:This is a bit mask that gives the binding relation between | |
126 | this thermal zone and cdev, for a particular trip point. | |
127 | If nth bit is set, then the cdev and thermal zone are bound | |
128 | for trip point n. | |
129 | .match: This call back returns success(0) if the 'tz and cdev' need to | |
130 | be bound, as per platform data. | |
131 | 1.4.2 struct thermal_zone_params | |
132 | This structure defines the platform level parameters for a thermal zone. | |
133 | This data, for each thermal zone should come from the platform layer. | |
134 | This is an optional feature where some platforms can choose not to | |
135 | provide this data. | |
136 | .governor_name: Name of the thermal governor used for this zone | |
137 | .num_tbps: Number of thermal_bind_params entries for this zone | |
138 | .tbp: thermal_bind_params entries | |
139 | ||
203d3d4a ZR |
140 | 2. sysfs attributes structure |
141 | ||
142 | RO read only value | |
143 | RW read/write value | |
144 | ||
e9ae7107 ZR |
145 | Thermal sysfs attributes will be represented under /sys/class/thermal. |
146 | Hwmon sysfs I/F extension is also available under /sys/class/hwmon | |
147 | if hwmon is compiled in or built as a module. | |
203d3d4a ZR |
148 | |
149 | Thermal zone device sys I/F, created once it's registered: | |
e9ae7107 | 150 | /sys/class/thermal/thermal_zone[0-*]: |
38bb0849 FP |
151 | |---type: Type of the thermal zone |
152 | |---temp: Current temperature | |
153 | |---mode: Working mode of the thermal zone | |
6ea083b1 | 154 | |---policy: Thermal governor used for this zone |
38bb0849 FP |
155 | |---trip_point_[0-*]_temp: Trip point temperature |
156 | |---trip_point_[0-*]_type: Trip point type | |
27365a6c | 157 | |---trip_point_[0-*]_hyst: Hysteresis value for this trip point |
e6e238c3 | 158 | |---emul_temp: Emulated temperature set node |
203d3d4a ZR |
159 | |
160 | Thermal cooling device sys I/F, created once it's registered: | |
e9ae7107 | 161 | /sys/class/thermal/cooling_device[0-*]: |
38bb0849 FP |
162 | |---type: Type of the cooling device(processor/fan/...) |
163 | |---max_state: Maximum cooling state of the cooling device | |
164 | |---cur_state: Current cooling state of the cooling device | |
203d3d4a ZR |
165 | |
166 | ||
38bb0849 FP |
167 | Then next two dynamic attributes are created/removed in pairs. They represent |
168 | the relationship between a thermal zone and its associated cooling device. | |
169 | They are created/removed for each successful execution of | |
170 | thermal_zone_bind_cooling_device/thermal_zone_unbind_cooling_device. | |
203d3d4a | 171 | |
38bb0849 FP |
172 | /sys/class/thermal/thermal_zone[0-*]: |
173 | |---cdev[0-*]: [0-*]th cooling device in current thermal zone | |
174 | |---cdev[0-*]_trip_point: Trip point that cdev[0-*] is associated with | |
203d3d4a | 175 | |
e9ae7107 | 176 | Besides the thermal zone device sysfs I/F and cooling device sysfs I/F, |
38bb0849 FP |
177 | the generic thermal driver also creates a hwmon sysfs I/F for each _type_ |
178 | of thermal zone device. E.g. the generic thermal driver registers one hwmon | |
179 | class device and build the associated hwmon sysfs I/F for all the registered | |
180 | ACPI thermal zones. | |
181 | ||
e9ae7107 | 182 | /sys/class/hwmon/hwmon[0-*]: |
38bb0849 FP |
183 | |---name: The type of the thermal zone devices |
184 | |---temp[1-*]_input: The current temperature of thermal zone [1-*] | |
185 | |---temp[1-*]_critical: The critical trip point of thermal zone [1-*] | |
186 | ||
e9ae7107 | 187 | Please read Documentation/hwmon/sysfs-interface for additional information. |
203d3d4a ZR |
188 | |
189 | *************************** | |
190 | * Thermal zone attributes * | |
191 | *************************** | |
192 | ||
38bb0849 FP |
193 | type |
194 | Strings which represent the thermal zone type. | |
195 | This is given by thermal zone driver as part of registration. | |
196 | E.g: "acpitz" indicates it's an ACPI thermal device. | |
197 | In order to keep it consistent with hwmon sys attribute; this should | |
198 | be a short, lowercase string, not containing spaces nor dashes. | |
199 | RO, Required | |
200 | ||
201 | temp | |
202 | Current temperature as reported by thermal zone (sensor). | |
203 | Unit: millidegree Celsius | |
204 | RO, Required | |
205 | ||
206 | mode | |
8eaa8d6c | 207 | One of the predefined values in [enabled, disabled]. |
38bb0849 FP |
208 | This file gives information about the algorithm that is currently |
209 | managing the thermal zone. It can be either default kernel based | |
210 | algorithm or user space application. | |
8eaa8d6c ZR |
211 | enabled = enable Kernel Thermal management. |
212 | disabled = Preventing kernel thermal zone driver actions upon | |
213 | trip points so that user application can take full | |
214 | charge of the thermal management. | |
38bb0849 FP |
215 | RW, Optional |
216 | ||
6ea083b1 D |
217 | policy |
218 | One of the various thermal governors used for a particular zone. | |
219 | RW, Required | |
220 | ||
38bb0849 FP |
221 | trip_point_[0-*]_temp |
222 | The temperature above which trip point will be fired. | |
223 | Unit: millidegree Celsius | |
224 | RO, Optional | |
225 | ||
226 | trip_point_[0-*]_type | |
227 | Strings which indicate the type of the trip point. | |
228 | E.g. it can be one of critical, hot, passive, active[0-*] for ACPI | |
229 | thermal zone. | |
230 | RO, Optional | |
231 | ||
27365a6c D |
232 | trip_point_[0-*]_hyst |
233 | The hysteresis value for a trip point, represented as an integer | |
234 | Unit: Celsius | |
235 | RW, Optional | |
236 | ||
38bb0849 FP |
237 | cdev[0-*] |
238 | Sysfs link to the thermal cooling device node where the sys I/F | |
239 | for cooling device throttling control represents. | |
240 | RO, Optional | |
241 | ||
242 | cdev[0-*]_trip_point | |
243 | The trip point with which cdev[0-*] is associated in this thermal | |
244 | zone; -1 means the cooling device is not associated with any trip | |
245 | point. | |
246 | RO, Optional | |
29226ed3 FP |
247 | |
248 | passive | |
249 | Attribute is only present for zones in which the passive cooling | |
250 | policy is not supported by native thermal driver. Default is zero | |
251 | and can be set to a temperature (in millidegrees) to enable a | |
252 | passive trip point for the zone. Activation is done by polling with | |
253 | an interval of 1 second. | |
254 | Unit: millidegrees Celsius | |
3d8e3ad8 | 255 | Valid values: 0 (disabled) or greater than 1000 |
29226ed3 | 256 | RW, Optional |
38bb0849 | 257 | |
e6e238c3 ADK |
258 | emul_temp |
259 | Interface to set the emulated temperature method in thermal zone | |
260 | (sensor). After setting this temperature, the thermal zone may pass | |
261 | this temperature to platform emulation function if registered or | |
262 | cache it locally. This is useful in debugging different temperature | |
263 | threshold and its associated cooling action. This is write only node | |
264 | and writing 0 on this node should disable emulation. | |
265 | Unit: millidegree Celsius | |
266 | WO, Optional | |
267 | ||
8837295a EV |
268 | WARNING: Be careful while enabling this option on production systems, |
269 | because userland can easily disable the thermal policy by simply | |
270 | flooding this sysfs node with low temperature values. | |
271 | ||
38bb0849 FP |
272 | ***************************** |
273 | * Cooling device attributes * | |
274 | ***************************** | |
275 | ||
276 | type | |
277 | String which represents the type of device, e.g: | |
278 | - for generic ACPI: should be "Fan", "Processor" or "LCD" | |
279 | - for memory controller device on intel_menlow platform: | |
280 | should be "Memory controller". | |
281 | RO, Required | |
282 | ||
283 | max_state | |
284 | The maximum permissible cooling state of this cooling device. | |
285 | RO, Required | |
286 | ||
287 | cur_state | |
288 | The current cooling state of this cooling device. | |
289 | The value can any integer numbers between 0 and max_state: | |
290 | - cur_state == 0 means no cooling | |
291 | - cur_state == max_state means the maximum cooling. | |
292 | RW, Required | |
203d3d4a ZR |
293 | |
294 | 3. A simple implementation | |
295 | ||
38bb0849 FP |
296 | ACPI thermal zone may support multiple trip points like critical, hot, |
297 | passive, active. If an ACPI thermal zone supports critical, passive, | |
298 | active[0] and active[1] at the same time, it may register itself as a | |
299 | thermal_zone_device (thermal_zone1) with 4 trip points in all. | |
300 | It has one processor and one fan, which are both registered as | |
301 | thermal_cooling_device. | |
302 | ||
303 | If the processor is listed in _PSL method, and the fan is listed in _AL0 | |
304 | method, the sys I/F structure will be built like this: | |
203d3d4a ZR |
305 | |
306 | /sys/class/thermal: | |
307 | ||
308 | |thermal_zone1: | |
38bb0849 FP |
309 | |---type: acpitz |
310 | |---temp: 37000 | |
8eaa8d6c | 311 | |---mode: enabled |
6ea083b1 | 312 | |---policy: step_wise |
38bb0849 FP |
313 | |---trip_point_0_temp: 100000 |
314 | |---trip_point_0_type: critical | |
315 | |---trip_point_1_temp: 80000 | |
316 | |---trip_point_1_type: passive | |
317 | |---trip_point_2_temp: 70000 | |
318 | |---trip_point_2_type: active0 | |
319 | |---trip_point_3_temp: 60000 | |
320 | |---trip_point_3_type: active1 | |
321 | |---cdev0: --->/sys/class/thermal/cooling_device0 | |
322 | |---cdev0_trip_point: 1 /* cdev0 can be used for passive */ | |
323 | |---cdev1: --->/sys/class/thermal/cooling_device3 | |
324 | |---cdev1_trip_point: 2 /* cdev1 can be used for active[0]*/ | |
203d3d4a ZR |
325 | |
326 | |cooling_device0: | |
38bb0849 FP |
327 | |---type: Processor |
328 | |---max_state: 8 | |
329 | |---cur_state: 0 | |
203d3d4a ZR |
330 | |
331 | |cooling_device3: | |
38bb0849 FP |
332 | |---type: Fan |
333 | |---max_state: 2 | |
334 | |---cur_state: 0 | |
e9ae7107 ZR |
335 | |
336 | /sys/class/hwmon: | |
337 | ||
338 | |hwmon0: | |
38bb0849 FP |
339 | |---name: acpitz |
340 | |---temp1_input: 37000 | |
341 | |---temp1_crit: 100000 | |
4cb18728 D |
342 | |
343 | 4. Event Notification | |
344 | ||
345 | The framework includes a simple notification mechanism, in the form of a | |
346 | netlink event. Netlink socket initialization is done during the _init_ | |
347 | of the framework. Drivers which intend to use the notification mechanism | |
2d58d7ea | 348 | just need to call thermal_generate_netlink_event() with two arguments viz |
8ab3e6a0 EV |
349 | (originator, event). The originator is a pointer to struct thermal_zone_device |
350 | from where the event has been originated. An integer which represents the | |
351 | thermal zone device will be used in the message to identify the zone. The | |
4cb18728 D |
352 | event will be one of:{THERMAL_AUX0, THERMAL_AUX1, THERMAL_CRITICAL, |
353 | THERMAL_DEV_FAULT}. Notification can be sent when the current temperature | |
354 | crosses any of the configured thresholds. | |
6ea083b1 D |
355 | |
356 | 5. Export Symbol APIs: | |
357 | ||
358 | 5.1: get_tz_trend: | |
359 | This function returns the trend of a thermal zone, i.e the rate of change | |
360 | of temperature of the thermal zone. Ideally, the thermal sensor drivers | |
361 | are supposed to implement the callback. If they don't, the thermal | |
362 | framework calculated the trend by comparing the previous and the current | |
363 | temperature values. | |
364 | ||
365 | 5.2:get_thermal_instance: | |
366 | This function returns the thermal_instance corresponding to a given | |
367 | {thermal_zone, cooling_device, trip_point} combination. Returns NULL | |
368 | if such an instance does not exist. | |
369 | ||
7b73c993 | 370 | 5.3:thermal_notify_framework: |
6ea083b1 D |
371 | This function handles the trip events from sensor drivers. It starts |
372 | throttling the cooling devices according to the policy configured. | |
373 | For CRITICAL and HOT trip points, this notifies the respective drivers, | |
374 | and does actual throttling for other trip points i.e ACTIVE and PASSIVE. | |
375 | The throttling policy is based on the configured platform data; if no | |
376 | platform data is provided, this uses the step_wise throttling policy. | |
377 | ||
378 | 5.4:thermal_cdev_update: | |
379 | This function serves as an arbitrator to set the state of a cooling | |
380 | device. It sets the cooling device to the deepest cooling state if | |
381 | possible. |