1 ThinkPad ACPI Extras Driver
6 Borislav Deianov <borislav@users.sf.net>
7 Henrique de Moraes Holschuh <hmh@hmh.eng.br>
8 http://ibm-acpi.sf.net/
11 This is a Linux driver for the IBM and Lenovo ThinkPad laptops. It
12 supports various features of these laptops which are accessible
13 through the ACPI and ACPI EC framework, but not otherwise fully
14 supported by the generic Linux ACPI drivers.
16 This driver used to be named ibm-acpi until kernel 2.6.21 and release
17 0.13-20070314. It used to be in the drivers/acpi tree, but it was
18 moved to the drivers/misc tree and renamed to thinkpad-acpi for kernel
19 2.6.22, and release 0.14. It was moved to drivers/platform/x86 for
20 kernel 2.6.29 and release 0.22.
22 The driver is named "thinkpad-acpi". In some places, like module
23 names and log messages, "thinkpad_acpi" is used because of userspace
26 "tpacpi" is used as a shorthand where "thinkpad-acpi" would be too
27 long due to length limitations on some Linux kernel versions.
32 The features currently supported are the following (see below for
33 detailed description):
36 - Bluetooth enable and disable
37 - video output switching, expansion control
38 - ThinkLight on and off
39 - limited docking and undocking
45 - Experimental: embedded controller register dump
46 - LCD brightness control
48 - Fan control and monitoring: fan speed, fan enable/disable
49 - WAN enable and disable
50 - UWB enable and disable
52 A compatibility table by model and feature is maintained on the web
53 site, http://ibm-acpi.sf.net/. I appreciate any success or failure
54 reports, especially if they add to or correct the compatibility table.
55 Please include the following information in your report:
58 - a copy of your ACPI tables, using the "acpidump" utility
59 - a copy of the output of dmidecode, with serial numbers
61 - which driver features work and which don't
62 - the observed behavior of non-working features
64 Any other comments or patches are also more than welcome.
70 If you are compiling this driver as included in the Linux kernel
71 sources, look for the CONFIG_THINKPAD_ACPI Kconfig option.
72 It is located on the menu path: "Device Drivers" -> "X86 Platform
73 Specific Device Drivers" -> "ThinkPad ACPI Laptop Extras".
79 The driver exports two different interfaces to userspace, which can be
80 used to access the features it provides. One is a legacy procfs-based
81 interface, which will be removed at some time in the future. The other
82 is a new sysfs-based interface which is not complete yet.
84 The procfs interface creates the /proc/acpi/ibm directory. There is a
85 file under that directory for each feature it supports. The procfs
86 interface is mostly frozen, and will change very little if at all: it
87 will not be extended to add any new functionality in the driver, instead
88 all new functionality will be implemented on the sysfs interface.
90 The sysfs interface tries to blend in the generic Linux sysfs subsystems
91 and classes as much as possible. Since some of these subsystems are not
92 yet ready or stabilized, it is expected that this interface will change,
93 and any and all userspace programs must deal with it.
96 Notes about the sysfs interface:
98 Unlike what was done with the procfs interface, correctness when talking
99 to the sysfs interfaces will be enforced, as will correctness in the
100 thinkpad-acpi's implementation of sysfs interfaces.
102 Also, any bugs in the thinkpad-acpi sysfs driver code or in the
103 thinkpad-acpi's implementation of the sysfs interfaces will be fixed for
104 maximum correctness, even if that means changing an interface in
105 non-compatible ways. As these interfaces mature both in the kernel and
106 in thinkpad-acpi, such changes should become quite rare.
108 Applications interfacing to the thinkpad-acpi sysfs interfaces must
109 follow all sysfs guidelines and correctly process all errors (the sysfs
110 interface makes extensive use of errors). File descriptors and open /
111 close operations to the sysfs inodes must also be properly implemented.
113 The version of thinkpad-acpi's sysfs interface is exported by the driver
114 as a driver attribute (see below).
116 Sysfs driver attributes are on the driver's sysfs attribute space,
117 for 2.6.23+ this is /sys/bus/platform/drivers/thinkpad_acpi/ and
118 /sys/bus/platform/drivers/thinkpad_hwmon/
120 Sysfs device attributes are on the thinkpad_acpi device sysfs attribute
121 space, for 2.6.23+ this is /sys/devices/platform/thinkpad_acpi/.
123 Sysfs device attributes for the sensors and fan are on the
124 thinkpad_hwmon device's sysfs attribute space, but you should locate it
125 looking for a hwmon device with the name attribute of "thinkpad", or
126 better yet, through libsensors.
132 procfs: /proc/acpi/ibm/driver
133 sysfs driver attribute: version
135 The driver name and version. No commands can be written to this file.
138 Sysfs interface version
139 -----------------------
141 sysfs driver attribute: interface_version
143 Version of the thinkpad-acpi sysfs interface, as an unsigned long
144 (output in hex format: 0xAAAABBCC), where:
145 AAAA - major revision
149 The sysfs interface version changelog for the driver can be found at the
150 end of this document. Changes to the sysfs interface done by the kernel
151 subsystems are not documented here, nor are they tracked by this
154 Changes to the thinkpad-acpi sysfs interface are only considered
155 non-experimental when they are submitted to Linux mainline, at which
156 point the changes in this interface are documented and interface_version
157 may be updated. If you are using any thinkpad-acpi features not yet
158 sent to mainline for merging, you do so on your own risk: these features
159 may disappear, or be implemented in a different and incompatible way by
160 the time they are merged in Linux mainline.
162 Changes that are backwards-compatible by nature (e.g. the addition of
163 attributes that do not change the way the other attributes work) do not
164 always warrant an update of interface_version. Therefore, one must
165 expect that an attribute might not be there, and deal with it properly
166 (an attribute not being there *is* a valid way to make it clear that a
167 feature is not available in sysfs).
173 procfs: /proc/acpi/ibm/hotkey
174 sysfs device attribute: hotkey_*
176 In a ThinkPad, the ACPI HKEY handler is responsible for communicating
177 some important events and also keyboard hot key presses to the operating
178 system. Enabling the hotkey functionality of thinkpad-acpi signals the
179 firmware that such a driver is present, and modifies how the ThinkPad
180 firmware will behave in many situations.
182 The driver enables the HKEY ("hot key") event reporting automatically
183 when loaded, and disables it when it is removed.
185 The driver will report HKEY events in the following format:
187 ibm/hotkey HKEY 00000080 0000xxxx
189 Some of these events refer to hot key presses, but not all of them.
191 The driver will generate events over the input layer for hot keys and
192 radio switches, and over the ACPI netlink layer for other events. The
193 input layer support accepts the standard IOCTLs to remap the keycodes
194 assigned to each hot key.
196 The hot key bit mask allows some control over which hot keys generate
197 events. If a key is "masked" (bit set to 0 in the mask), the firmware
198 will handle it. If it is "unmasked", it signals the firmware that
199 thinkpad-acpi would prefer to handle it, if the firmware would be so
200 kind to allow it (and it often doesn't!).
202 Not all bits in the mask can be modified. Not all bits that can be
203 modified do anything. Not all hot keys can be individually controlled
204 by the mask. Some models do not support the mask at all, and in those
205 models, hot keys cannot be controlled individually. The behaviour of
206 the mask is, therefore, highly dependent on the ThinkPad model.
208 Note that unmasking some keys prevents their default behavior. For
209 example, if Fn+F5 is unmasked, that key will no longer enable/disable
212 Note also that not all Fn key combinations are supported through ACPI.
213 For example, on the X40, the brightness, volume and "Access IBM" buttons
214 do not generate ACPI events even with this driver. They *can* be used
215 through the "ThinkPad Buttons" utility, see http://www.nongnu.org/tpb/
219 The following commands can be written to the /proc/acpi/ibm/hotkey file:
221 echo 0xffffffff > /proc/acpi/ibm/hotkey -- enable all hot keys
222 echo 0 > /proc/acpi/ibm/hotkey -- disable all possible hot keys
223 ... any other 8-hex-digit mask ...
224 echo reset > /proc/acpi/ibm/hotkey -- restore the original mask
226 The following commands have been deprecated and will cause the kernel
229 echo enable > /proc/acpi/ibm/hotkey -- does nothing
230 echo disable > /proc/acpi/ibm/hotkey -- returns an error
232 The procfs interface does not support NVRAM polling control. So as to
233 maintain maximum bug-to-bug compatibility, it does not report any masks,
234 nor does it allow one to manipulate the hot key mask when the firmware
235 does not support masks at all, even if NVRAM polling is in use.
240 DEPRECATED, WILL BE REMOVED SOON.
245 Returns the hot keys mask when thinkpad-acpi was loaded.
246 Upon module unload, the hot keys mask will be restored
250 DEPRECATED, WILL BE REMOVED SOON.
256 bit mask to enable driver-handling (and depending on
257 the firmware, ACPI event generation) for each hot key
258 (see above). Returns the current status of the hot keys
259 mask, and allows one to modify it.
261 Note: when NVRAM polling is active, the firmware mask
262 will be different from the value returned by
263 hotkey_mask. The driver will retain enabled bits for
264 hotkeys that are under NVRAM polling even if the
265 firmware refuses them, and will not set these bits on
266 the firmware hot key mask.
269 bit mask that should enable event reporting for all
270 supported hot keys, when echoed to hotkey_mask above.
271 Unless you know which events need to be handled
272 passively (because the firmware *will* handle them
273 anyway), do *not* use hotkey_all_mask. Use
274 hotkey_recommended_mask, instead. You have been warned.
276 hotkey_recommended_mask:
277 bit mask that should enable event reporting for all
278 supported hot keys, except those which are always
279 handled by the firmware anyway. Echo it to
280 hotkey_mask above, to use.
283 bit mask that selects which hot keys will the driver
284 poll the NVRAM for. This is auto-detected by the driver
285 based on the capabilities reported by the ACPI firmware,
286 but it can be overridden at runtime.
288 Hot keys whose bits are set in both hotkey_source_mask
289 and also on hotkey_mask are polled for in NVRAM. Only a
290 few hot keys are available through CMOS NVRAM polling.
292 Warning: when in NVRAM mode, the volume up/down/mute
293 keys are synthesized according to changes in the mixer,
294 so you have to use volume up or volume down to unmute,
295 as per the ThinkPad volume mixer user interface. When
296 in ACPI event mode, volume up/down/mute are reported as
297 separate events, but this behaviour may be corrected in
298 future releases of this driver, in which case the
299 ThinkPad volume mixer user interface semantics will be
303 frequency in Hz for hot key polling. It must be between
304 0 and 25 Hz. Polling is only carried out when strictly
307 Setting hotkey_poll_freq to zero disables polling, and
308 will cause hot key presses that require NVRAM polling
309 to never be reported.
311 Setting hotkey_poll_freq too low will cause repeated
312 pressings of the same hot key to be misreported as a
313 single key press, or to not even be detected at all.
314 The recommended polling frequency is 10Hz.
317 If the ThinkPad has a hardware radio switch, this
318 attribute will read 0 if the switch is in the "radios
319 disabled" position, and 1 if the switch is in the
320 "radios enabled" position.
322 This attribute has poll()/select() support.
325 If the ThinkPad has tablet capabilities, this attribute
326 will read 0 if the ThinkPad is in normal mode, and
327 1 if the ThinkPad is in tablet mode.
329 This attribute has poll()/select() support.
332 Returns the state of the procfs ACPI event report mode
333 filter for hot keys. If it is set to 1 (the default),
334 all hot key presses are reported both through the input
335 layer and also as ACPI events through procfs (but not
336 through netlink). If it is set to 2, hot key presses
337 are reported only through the input layer.
339 This attribute is read-only in kernels 2.6.23 or later,
340 and read-write on earlier kernels.
342 May return -EPERM (write access locked out by module
343 parameter) or -EACCES (read-only).
346 Set to 1 if the system is waking up because the user
347 requested a bay ejection. Set to 2 if the system is
348 waking up because the user requested the system to
349 undock. Set to zero for normal wake-ups or wake-ups
350 due to unknown reasons.
352 This attribute has poll()/select() support.
354 wakeup_hotunplug_complete:
355 Set to 1 if the system was waken up because of an
356 undock or bay ejection request, and that request
357 was successfully completed. At this point, it might
358 be useful to send the system back to sleep, at the
359 user's choice. Refer to HKEY events 0x4003 and
362 This attribute has poll()/select() support.
366 A Hot key is mapped to a single input layer EV_KEY event, possibly
367 followed by an EV_MSC MSC_SCAN event that shall contain that key's scan
368 code. An EV_SYN event will always be generated to mark the end of the
371 Do not use the EV_MSC MSC_SCAN events to process keys. They are to be
372 used as a helper to remap keys, only. They are particularly useful when
373 remapping KEY_UNKNOWN keys.
375 The events are available in an input device, with the following id:
378 vendor: 0x1014 (PCI_VENDOR_ID_IBM) or
379 0x17aa (PCI_VENDOR_ID_LENOVO)
380 product: 0x5054 ("TP")
383 The version will have its LSB incremented if the keymap changes in a
384 backwards-compatible way. The MSB shall always be 0x41 for this input
385 device. If the MSB is not 0x41, do not use the device as described in
386 this section, as it is either something else (e.g. another input device
387 exported by a thinkpad driver, such as HDAPS) or its functionality has
388 been changed in a non-backwards compatible way.
390 Adding other event types for other functionalities shall be considered a
391 backwards-compatible change for this input device.
393 Thinkpad-acpi Hot Key event map (version 0x4101):
399 0x1002 0x01 FN+F2 IBM: battery (rare)
402 0x1003 0x02 FN+F3 Many IBM models always report
403 this hot key, even with hot keys
404 disabled or with Fn+F3 masked
409 0x1004 0x03 FN+F4 Sleep button (ACPI sleep button
410 semantics, i.e. sleep-to-RAM).
411 It is always generate some kind
412 of event, either the hot key
413 event or a ACPI sleep button
414 event. The firmware may
415 refuse to generate further FN+F4
416 key presses until a S3 or S4 ACPI
417 sleep cycle is performed or some
420 0x1005 0x04 FN+F5 Radio. Enables/disables
421 the internal Bluetooth hardware
422 and W-WAN card if left in control
423 of the firmware. Does not affect
425 Should be used to turn on/off all
426 radios (Bluetooth+W-WAN+WLAN),
431 0x1007 0x06 FN+F7 Video output cycle.
432 Do you feel lucky today?
434 0x1008 0x07 FN+F8 IBM: toggle screen expand
435 Lenovo: configure UltraNav
441 0x100C 0x0B FN+F12 Sleep to disk. You are always
442 supposed to handle it yourself,
443 either through the ACPI event,
444 or through a hotkey event.
445 The firmware may refuse to
446 generate further FN+F4 key
447 press events until a S3 or S4
448 ACPI sleep cycle is performed,
451 0x100D 0x0C FN+BACKSPACE -
452 0x100E 0x0D FN+INSERT -
453 0x100F 0x0E FN+DELETE -
455 0x1010 0x0F FN+HOME Brightness up. This key is
456 always handled by the firmware
457 in IBM ThinkPads, even when
458 unmasked. Just leave it alone.
459 For Lenovo ThinkPads with a new
460 BIOS, it has to be handled either
461 by the ACPI OSI, or by userspace.
462 0x1011 0x10 FN+END Brightness down. See brightness
465 0x1012 0x11 FN+PGUP ThinkLight toggle. This key is
466 always handled by the firmware,
469 0x1013 0x12 FN+PGDOWN -
471 0x1014 0x13 FN+SPACE Zoom key
473 0x1015 0x14 VOLUME UP Internal mixer volume up. This
474 key is always handled by the
475 firmware, even when unmasked.
476 NOTE: Lenovo seems to be changing
478 0x1016 0x15 VOLUME DOWN Internal mixer volume up. This
479 key is always handled by the
480 firmware, even when unmasked.
481 NOTE: Lenovo seems to be changing
483 0x1017 0x16 MUTE Mute internal mixer. This
484 key is always handled by the
485 firmware, even when unmasked.
487 0x1018 0x17 THINKPAD ThinkPad/Access IBM/Lenovo key
493 The ThinkPad firmware does not allow one to differentiate when most hot
494 keys are pressed or released (either that, or we don't know how to, yet).
495 For these keys, the driver generates a set of events for a key press and
496 immediately issues the same set of events for a key release. It is
497 unknown by the driver if the ThinkPad firmware triggered these events on
498 hot key press or release, but the firmware will do it for either one, not
501 If a key is mapped to KEY_RESERVED, it generates no input events at all.
502 If a key is mapped to KEY_UNKNOWN, it generates an input event that
503 includes an scan code. If a key is mapped to anything else, it will
504 generate input device EV_KEY events.
506 In addition to the EV_KEY events, thinkpad-acpi may also issue EV_SW
509 SW_RFKILL_ALL T60 and later hardare rfkill rocker switch
510 SW_TABLET_MODE Tablet ThinkPads HKEY events 0x5009 and 0x500A
512 Non hot-key ACPI HKEY event map:
515 0x5009 Tablet swivel: switched to tablet mode
516 0x500A Tablet swivel: switched to normal mode
517 0x7000 Radio Switch may have changed state
519 The above events are not propagated by the driver, except for legacy
520 compatibility purposes when hotkey_report_mode is set to 1.
522 0x2304 System is waking up from suspend to undock
523 0x2305 System is waking up from suspend to eject bay
524 0x2404 System is waking up from hibernation to undock
525 0x2405 System is waking up from hibernation to eject bay
527 The above events are never propagated by the driver.
529 0x3003 Bay ejection (see 0x2x05) complete, can sleep again
530 0x4003 Undocked (see 0x2x04), can sleep again
531 0x500B Tablet pen inserted into its storage bay
532 0x500C Tablet pen removed from its storage bay
533 0x5010 Brightness level changed (newer Lenovo BIOSes)
535 The above events are propagated by the driver.
539 ibm-acpi and thinkpad-acpi 0.15 (mainline kernels before 2.6.23) never
540 supported the input layer, and sent events over the procfs ACPI event
543 To avoid sending duplicate events over the input layer and the ACPI
544 event interface, thinkpad-acpi 0.16 implements a module parameter
545 (hotkey_report_mode), and also a sysfs device attribute with the same
548 Make no mistake here: userspace is expected to switch to using the input
549 layer interface of thinkpad-acpi, together with the ACPI netlink event
550 interface in kernels 2.6.23 and later, or with the ACPI procfs event
551 interface in kernels 2.6.22 and earlier.
553 If no hotkey_report_mode module parameter is specified (or it is set to
554 zero), the driver defaults to mode 1 (see below), and on kernels 2.6.22
555 and earlier, also allows one to change the hotkey_report_mode through
556 sysfs. In kernels 2.6.23 and later, where the netlink ACPI event
557 interface is available, hotkey_report_mode cannot be changed through
558 sysfs (it is read-only).
560 If the hotkey_report_mode module parameter is set to 1 or 2, it cannot
561 be changed later through sysfs (any writes will return -EPERM to signal
562 that hotkey_report_mode was locked. On 2.6.23 and later, where
563 hotkey_report_mode cannot be changed at all, writes will return -EACCES).
565 hotkey_report_mode set to 1 makes the driver export through the procfs
566 ACPI event interface all hot key presses (which are *also* sent to the
567 input layer). This is a legacy compatibility behaviour, and it is also
568 the default mode of operation for the driver.
570 hotkey_report_mode set to 2 makes the driver filter out the hot key
571 presses from the procfs ACPI event interface, so these events will only
572 be sent through the input layer. Userspace that has been updated to use
573 the thinkpad-acpi input layer interface should set hotkey_report_mode to
576 Hot key press events are never sent to the ACPI netlink event interface.
577 Really up-to-date userspace under kernel 2.6.23 and later is to use the
578 netlink interface and the input layer interface, and don't bother at all
579 with hotkey_report_mode.
582 Brightness hotkey notes:
584 These are the current sane choices for brightness key mapping in
587 For IBM and Lenovo models *without* ACPI backlight control (the ones on
588 which thinkpad-acpi will autoload its backlight interface by default,
589 and on which ACPI video does not export a backlight interface):
591 1. Don't enable or map the brightness hotkeys in thinkpad-acpi, as
592 these older firmware versions unfortunately won't respect the hotkey
593 mask for brightness keys anyway, and always reacts to them. This
594 usually work fine, unless X.org drivers are doing something to block
595 the BIOS. In that case, use (3) below. This is the default mode of
598 2. Enable the hotkeys, but map them to something else that is NOT
599 KEY_BRIGHTNESS_UP/DOWN or any other keycode that would cause
600 userspace to try to change the backlight level, and use that as an
601 on-screen-display hint.
603 3. IF AND ONLY IF X.org drivers find a way to block the firmware from
604 automatically changing the brightness, enable the hotkeys and map
605 them to KEY_BRIGHTNESS_UP and KEY_BRIGHTNESS_DOWN, and feed that to
606 something that calls xbacklight. thinkpad-acpi will not be able to
607 change brightness in that case either, so you should disable its
610 For Lenovo models *with* ACPI backlight control:
612 1. Load up ACPI video and use that. ACPI video will report ACPI
613 events for brightness change keys. Do not mess with thinkpad-acpi
614 defaults in this case. thinkpad-acpi should not have anything to do
615 with backlight events in a scenario where ACPI video is loaded:
616 brightness hotkeys must be disabled, and the backlight interface is
617 to be kept disabled as well. This is the default mode of operation.
619 2. Do *NOT* load up ACPI video, enable the hotkeys in thinkpad-acpi,
620 and map them to KEY_BRIGHTNESS_UP and KEY_BRIGHTNESS_DOWN. Process
621 these keys on userspace somehow (e.g. by calling xbacklight).
627 procfs: /proc/acpi/ibm/bluetooth
628 sysfs device attribute: bluetooth_enable (deprecated)
629 sysfs rfkill class: switch "tpacpi_bluetooth_sw"
631 This feature shows the presence and current state of a ThinkPad
632 Bluetooth device in the internal ThinkPad CDC slot.
634 If the ThinkPad supports it, the Bluetooth state is stored in NVRAM,
635 so it is kept across reboots and power-off.
639 If Bluetooth is installed, the following commands can be used:
641 echo enable > /proc/acpi/ibm/bluetooth
642 echo disable > /proc/acpi/ibm/bluetooth
646 If the Bluetooth CDC card is installed, it can be enabled /
647 disabled through the "bluetooth_enable" thinkpad-acpi device
648 attribute, and its current status can also be queried.
651 0: disables Bluetooth / Bluetooth is disabled
652 1: enables Bluetooth / Bluetooth is enabled.
654 Note: this interface has been superseded by the generic rfkill
655 class. It has been deprecated, and it will be removed in year
658 rfkill controller switch "tpacpi_bluetooth_sw": refer to
659 Documentation/rfkill.txt for details.
662 Video output control -- /proc/acpi/ibm/video
663 --------------------------------------------
665 This feature allows control over the devices used for video output -
666 LCD, CRT or DVI (if available). The following commands are available:
668 echo lcd_enable > /proc/acpi/ibm/video
669 echo lcd_disable > /proc/acpi/ibm/video
670 echo crt_enable > /proc/acpi/ibm/video
671 echo crt_disable > /proc/acpi/ibm/video
672 echo dvi_enable > /proc/acpi/ibm/video
673 echo dvi_disable > /proc/acpi/ibm/video
674 echo auto_enable > /proc/acpi/ibm/video
675 echo auto_disable > /proc/acpi/ibm/video
676 echo expand_toggle > /proc/acpi/ibm/video
677 echo video_switch > /proc/acpi/ibm/video
679 Each video output device can be enabled or disabled individually.
680 Reading /proc/acpi/ibm/video shows the status of each device.
682 Automatic video switching can be enabled or disabled. When automatic
683 video switching is enabled, certain events (e.g. opening the lid,
684 docking or undocking) cause the video output device to change
685 automatically. While this can be useful, it also causes flickering
686 and, on the X40, video corruption. By disabling automatic switching,
687 the flickering or video corruption can be avoided.
689 The video_switch command cycles through the available video outputs
690 (it simulates the behavior of Fn-F7).
692 Video expansion can be toggled through this feature. This controls
693 whether the display is expanded to fill the entire LCD screen when a
694 mode with less than full resolution is used. Note that the current
695 video expansion status cannot be determined through this feature.
697 Note that on many models (particularly those using Radeon graphics
698 chips) the X driver configures the video card in a way which prevents
699 Fn-F7 from working. This also disables the video output switching
700 features of this driver, as it uses the same ACPI methods as
701 Fn-F7. Video switching on the console should still work.
703 UPDATE: refer to https://bugs.freedesktop.org/show_bug.cgi?id=2000
709 procfs: /proc/acpi/ibm/light
710 sysfs attributes: as per LED class, for the "tpacpi::thinklight" LED
714 The ThinkLight status can be read and set through the procfs interface. A
715 few models which do not make the status available will show the ThinkLight
716 status as "unknown". The available commands are:
718 echo on > /proc/acpi/ibm/light
719 echo off > /proc/acpi/ibm/light
723 The ThinkLight sysfs interface is documented by the LED class
724 documentation, in Documentation/leds-class.txt. The ThinkLight LED name
725 is "tpacpi::thinklight".
727 Due to limitations in the sysfs LED class, if the status of the ThinkLight
728 cannot be read or if it is unknown, thinkpad-acpi will report it as "off".
729 It is impossible to know if the status returned through sysfs is valid.
732 Docking / undocking -- /proc/acpi/ibm/dock
733 ------------------------------------------
735 Docking and undocking (e.g. with the X4 UltraBase) requires some
736 actions to be taken by the operating system to safely make or break
737 the electrical connections with the dock.
739 The docking feature of this driver generates the following ACPI events:
741 ibm/dock GDCK 00000003 00000001 -- eject request
742 ibm/dock GDCK 00000003 00000002 -- undocked
743 ibm/dock GDCK 00000000 00000003 -- docked
745 NOTE: These events will only be generated if the laptop was docked
746 when originally booted. This is due to the current lack of support for
747 hot plugging of devices in the Linux ACPI framework. If the laptop was
748 booted while not in the dock, the following message is shown in the
751 Mar 17 01:42:34 aero kernel: thinkpad_acpi: dock device not present
753 In this case, no dock-related events are generated but the dock and
754 undock commands described below still work. They can be executed
755 manually or triggered by Fn key combinations (see the example acpid
756 configuration files included in the driver tarball package available
759 When the eject request button on the dock is pressed, the first event
760 above is generated. The handler for this event should issue the
763 echo undock > /proc/acpi/ibm/dock
765 After the LED on the dock goes off, it is safe to eject the laptop.
766 Note: if you pressed this key by mistake, go ahead and eject the
767 laptop, then dock it back in. Otherwise, the dock may not function as
770 When the laptop is docked, the third event above is generated. The
771 handler for this event should issue the following command to fully
774 echo dock > /proc/acpi/ibm/dock
776 The contents of the /proc/acpi/ibm/dock file shows the current status
777 of the dock, as provided by the ACPI framework.
779 The docking support in this driver does not take care of enabling or
780 disabling any other devices you may have attached to the dock. For
781 example, a CD drive plugged into the UltraBase needs to be disabled or
782 enabled separately. See the provided example acpid configuration files
783 for how this can be accomplished.
785 There is no support yet for PCI devices that may be attached to a
786 docking station, e.g. in the ThinkPad Dock II. The driver currently
787 does not recognize, enable or disable such devices. This means that
788 the only docking stations currently supported are the X-series
789 UltraBase docks and "dumb" port replicators like the Mini Dock (the
790 latter don't need any ACPI support, actually).
793 UltraBay eject -- /proc/acpi/ibm/bay
794 ------------------------------------
796 Inserting or ejecting an UltraBay device requires some actions to be
797 taken by the operating system to safely make or break the electrical
798 connections with the device.
800 This feature generates the following ACPI events:
802 ibm/bay MSTR 00000003 00000000 -- eject request
803 ibm/bay MSTR 00000001 00000000 -- eject lever inserted
805 NOTE: These events will only be generated if the UltraBay was present
806 when the laptop was originally booted (on the X series, the UltraBay
807 is in the dock, so it may not be present if the laptop was undocked).
808 This is due to the current lack of support for hot plugging of devices
809 in the Linux ACPI framework. If the laptop was booted without the
810 UltraBay, the following message is shown in the logs:
812 Mar 17 01:42:34 aero kernel: thinkpad_acpi: bay device not present
814 In this case, no bay-related events are generated but the eject
815 command described below still works. It can be executed manually or
816 triggered by a hot key combination.
818 Sliding the eject lever generates the first event shown above. The
819 handler for this event should take whatever actions are necessary to
820 shut down the device in the UltraBay (e.g. call idectl), then issue
821 the following command:
823 echo eject > /proc/acpi/ibm/bay
825 After the LED on the UltraBay goes off, it is safe to pull out the
828 When the eject lever is inserted, the second event above is
829 generated. The handler for this event should take whatever actions are
830 necessary to enable the UltraBay device (e.g. call idectl).
832 The contents of the /proc/acpi/ibm/bay file shows the current status
833 of the UltraBay, as provided by the ACPI framework.
835 EXPERIMENTAL warm eject support on the 600e/x, A22p and A3x (To use
836 this feature, you need to supply the experimental=1 parameter when
839 These models do not have a button near the UltraBay device to request
840 a hot eject but rather require the laptop to be put to sleep
841 (suspend-to-ram) before the bay device is ejected or inserted).
842 The sequence of steps to eject the device is as follows:
844 echo eject > /proc/acpi/ibm/bay
845 put the ThinkPad to sleep
848 cat /proc/acpi/ibm/bay should show that the drive was removed
850 On the A3x, both the UltraBay 2000 and UltraBay Plus devices are
851 supported. Use "eject2" instead of "eject" for the second bay.
853 Note: the UltraBay eject support on the 600e/x, A22p and A3x is
854 EXPERIMENTAL and may not work as expected. USE WITH CAUTION!
860 procfs: /proc/acpi/ibm/cmos
861 sysfs device attribute: cmos_command
863 This feature is mostly used internally by the ACPI firmware to keep the legacy
864 CMOS NVRAM bits in sync with the current machine state, and to record this
865 state so that the ThinkPad will retain such settings across reboots.
867 Some of these commands actually perform actions in some ThinkPad models, but
868 this is expected to disappear more and more in newer models. As an example, in
869 a T43 and in a X40, commands 12 and 13 still control the ThinkLight state for
870 real, but commands 0 to 2 don't control the mixer anymore (they have been
871 phased out) and just update the NVRAM.
873 The range of valid cmos command numbers is 0 to 21, but not all have an
874 effect and the behavior varies from model to model. Here is the behavior
875 on the X40 (tpb is the ThinkPad Buttons utility):
877 0 - Related to "Volume down" key press
878 1 - Related to "Volume up" key press
879 2 - Related to "Mute on" key press
880 3 - Related to "Access IBM" key press
881 4 - Related to "LCD brightness up" key press
882 5 - Related to "LCD brightness down" key press
883 11 - Related to "toggle screen expansion" key press/function
884 12 - Related to "ThinkLight on"
885 13 - Related to "ThinkLight off"
886 14 - Related to "ThinkLight" key press (toggle ThinkLight)
888 The cmos command interface is prone to firmware split-brain problems, as
889 in newer ThinkPads it is just a compatibility layer. Do not use it, it is
890 exported just as a debug tool.
896 procfs: /proc/acpi/ibm/led
897 sysfs attributes: as per LED class, see below for names
899 Some of the LED indicators can be controlled through this feature. On
900 some older ThinkPad models, it is possible to query the status of the
901 LED indicators as well. Newer ThinkPads cannot query the real status
902 of the LED indicators.
904 Because misuse of the LEDs could induce an unaware user to perform
905 dangerous actions (like undocking or ejecting a bay device while the
906 buses are still active), or mask an important alarm (such as a nearly
907 empty battery, or a broken battery), access to most LEDs is
910 Unrestricted access to all LEDs requires that thinkpad-acpi be
911 compiled with the CONFIG_THINKPAD_ACPI_UNSAFE_LEDS option enabled.
912 Distributions must never enable this option. Individual users that
913 are aware of the consequences are welcome to enabling it.
917 The available commands are:
919 echo '<LED number> on' >/proc/acpi/ibm/led
920 echo '<LED number> off' >/proc/acpi/ibm/led
921 echo '<LED number> blink' >/proc/acpi/ibm/led
923 The <LED number> range is 0 to 7. The set of LEDs that can be
924 controlled varies from model to model. Here is the common ThinkPad
932 5 - UltraBase battery slot
936 All of the above can be turned on and off and can be made to blink.
940 The ThinkPad LED sysfs interface is described in detail by the LED class
941 documentation, in Documentation/leds-class.txt.
943 The leds are named (in LED ID order, from 0 to 7):
944 "tpacpi::power", "tpacpi:orange:batt", "tpacpi:green:batt",
945 "tpacpi::dock_active", "tpacpi::bay_active", "tpacpi::dock_batt",
946 "tpacpi::unknown_led", "tpacpi::standby".
948 Due to limitations in the sysfs LED class, if the status of the LED
949 indicators cannot be read due to an error, thinkpad-acpi will report it as
950 a brightness of zero (same as LED off).
952 If the thinkpad firmware doesn't support reading the current status,
953 trying to read the current LED brightness will just return whatever
954 brightness was last written to that attribute.
956 These LEDs can blink using hardware acceleration. To request that a
957 ThinkPad indicator LED should blink in hardware accelerated mode, use the
958 "timer" trigger, and leave the delay_on and delay_off parameters set to
959 zero (to request hardware acceleration autodetection).
962 ACPI sounds -- /proc/acpi/ibm/beep
963 ----------------------------------
965 The BEEP method is used internally by the ACPI firmware to provide
966 audible alerts in various situations. This feature allows the same
967 sounds to be triggered manually.
969 The commands are non-negative integer numbers:
971 echo <number> >/proc/acpi/ibm/beep
973 The valid <number> range is 0 to 17. Not all numbers trigger sounds
974 and the sounds vary from model to model. Here is the behavior on the
977 0 - stop a sound in progress (but use 17 to stop 16)
978 2 - two beeps, pause, third beep ("low battery")
980 4 - high, followed by low-pitched beep ("unable")
982 6 - very high, followed by high-pitched beep ("AC/DC")
983 7 - high-pitched beep
984 9 - three short beeps
986 12 - low-pitched beep
987 15 - three high-pitched beeps repeating constantly, stop with 0
988 16 - one medium-pitched beep repeating constantly, stop with 17
995 procfs: /proc/acpi/ibm/thermal
996 sysfs device attributes: (hwmon "thinkpad") temp*_input
998 Most ThinkPads include six or more separate temperature sensors but only
999 expose the CPU temperature through the standard ACPI methods. This
1000 feature shows readings from up to eight different sensors on older
1001 ThinkPads, and up to sixteen different sensors on newer ThinkPads.
1003 For example, on the X40, a typical output may be:
1004 temperatures: 42 42 45 41 36 -128 33 -128
1006 On the T43/p, a typical output may be:
1007 temperatures: 48 48 36 52 38 -128 31 -128 48 52 48 -128 -128 -128 -128 -128
1009 The mapping of thermal sensors to physical locations varies depending on
1010 system-board model (and thus, on ThinkPad model).
1012 http://thinkwiki.org/wiki/Thermal_Sensors is a public wiki page that
1013 tries to track down these locations for various models.
1015 Most (newer?) models seem to follow this pattern:
1018 2: (depends on model)
1019 3: (depends on model)
1021 5: Main battery: main sensor
1022 6: Bay battery: main sensor
1023 7: Main battery: secondary sensor
1024 8: Bay battery: secondary sensor
1025 9-15: (depends on model)
1027 For the R51 (source: Thomas Gruber):
1031 For the T43, T43/p (source: Shmidoax/Thinkwiki.org)
1032 http://thinkwiki.org/wiki/Thermal_Sensors#ThinkPad_T43.2C_T43p
1033 2: System board, left side (near PCMCIA slot), reported as HDAPS temp
1035 9: MCH (northbridge) to DRAM Bus
1036 10: Clock-generator, mini-pci card and ICH (southbridge), under Mini-PCI
1037 card, under touchpad
1038 11: Power regulator, underside of system board, below F2 key
1040 The A31 has a very atypical layout for the thermal sensors
1041 (source: Milos Popovic, http://thinkwiki.org/wiki/Thermal_Sensors#ThinkPad_A31)
1043 2: Main Battery: main sensor
1045 4: Bay Battery: main sensor
1046 5: MCH (northbridge)
1048 7: Main Battery: secondary sensor
1049 8: Bay Battery: secondary sensor
1053 Readings from sensors that are not available return -128.
1054 No commands can be written to this file.
1057 Sensors that are not available return the ENXIO error. This
1058 status may change at runtime, as there are hotplug thermal
1059 sensors, like those inside the batteries and docks.
1061 thinkpad-acpi thermal sensors are reported through the hwmon
1062 subsystem, and follow all of the hwmon guidelines at
1063 Documentation/hwmon.
1066 EXPERIMENTAL: Embedded controller register dump -- /proc/acpi/ibm/ecdump
1067 ------------------------------------------------------------------------
1069 This feature is marked EXPERIMENTAL because the implementation
1070 directly accesses hardware registers and may not work as expected. USE
1071 WITH CAUTION! To use this feature, you need to supply the
1072 experimental=1 parameter when loading the module.
1074 This feature dumps the values of 256 embedded controller
1075 registers. Values which have changed since the last time the registers
1076 were dumped are marked with a star:
1078 [root@x40 ibm-acpi]# cat /proc/acpi/ibm/ecdump
1079 EC +00 +01 +02 +03 +04 +05 +06 +07 +08 +09 +0a +0b +0c +0d +0e +0f
1080 EC 0x00: a7 47 87 01 fe 96 00 08 01 00 cb 00 00 00 40 00
1081 EC 0x10: 00 00 ff ff f4 3c 87 09 01 ff 42 01 ff ff 0d 00
1082 EC 0x20: 00 00 00 00 00 00 00 00 00 00 00 03 43 00 00 80
1083 EC 0x30: 01 07 1a 00 30 04 00 00 *85 00 00 10 00 50 00 00
1084 EC 0x40: 00 00 00 00 00 00 14 01 00 04 00 00 00 00 00 00
1085 EC 0x50: 00 c0 02 0d 00 01 01 02 02 03 03 03 03 *bc *02 *bc
1086 EC 0x60: *02 *bc *02 00 00 00 00 00 00 00 00 00 00 00 00 00
1087 EC 0x70: 00 00 00 00 00 12 30 40 *24 *26 *2c *27 *20 80 *1f 80
1088 EC 0x80: 00 00 00 06 *37 *0e 03 00 00 00 0e 07 00 00 00 00
1089 EC 0x90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1090 EC 0xa0: *ff 09 ff 09 ff ff *64 00 *00 *00 *a2 41 *ff *ff *e0 00
1091 EC 0xb0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1092 EC 0xc0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1093 EC 0xd0: 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1094 EC 0xe0: 00 00 00 00 00 00 00 00 11 20 49 04 24 06 55 03
1095 EC 0xf0: 31 55 48 54 35 38 57 57 08 2f 45 73 07 65 6c 1a
1097 This feature can be used to determine the register holding the fan
1098 speed on some models. To do that, do the following:
1100 - make sure the battery is fully charged
1101 - make sure the fan is running
1102 - run 'cat /proc/acpi/ibm/ecdump' several times, once per second or so
1104 The first step makes sure various charging-related values don't
1105 vary. The second ensures that the fan-related values do vary, since
1106 the fan speed fluctuates a bit. The third will (hopefully) mark the
1107 fan register with a star:
1109 [root@x40 ibm-acpi]# cat /proc/acpi/ibm/ecdump
1110 EC +00 +01 +02 +03 +04 +05 +06 +07 +08 +09 +0a +0b +0c +0d +0e +0f
1111 EC 0x00: a7 47 87 01 fe 96 00 08 01 00 cb 00 00 00 40 00
1112 EC 0x10: 00 00 ff ff f4 3c 87 09 01 ff 42 01 ff ff 0d 00
1113 EC 0x20: 00 00 00 00 00 00 00 00 00 00 00 03 43 00 00 80
1114 EC 0x30: 01 07 1a 00 30 04 00 00 85 00 00 10 00 50 00 00
1115 EC 0x40: 00 00 00 00 00 00 14 01 00 04 00 00 00 00 00 00
1116 EC 0x50: 00 c0 02 0d 00 01 01 02 02 03 03 03 03 bc 02 bc
1117 EC 0x60: 02 bc 02 00 00 00 00 00 00 00 00 00 00 00 00 00
1118 EC 0x70: 00 00 00 00 00 12 30 40 24 27 2c 27 21 80 1f 80
1119 EC 0x80: 00 00 00 06 *be 0d 03 00 00 00 0e 07 00 00 00 00
1120 EC 0x90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1121 EC 0xa0: ff 09 ff 09 ff ff 64 00 00 00 a2 41 ff ff e0 00
1122 EC 0xb0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1123 EC 0xc0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1124 EC 0xd0: 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1125 EC 0xe0: 00 00 00 00 00 00 00 00 11 20 49 04 24 06 55 03
1126 EC 0xf0: 31 55 48 54 35 38 57 57 08 2f 45 73 07 65 6c 1a
1128 Another set of values that varies often is the temperature
1129 readings. Since temperatures don't change vary fast, you can take
1130 several quick dumps to eliminate them.
1132 You can use a similar method to figure out the meaning of other
1133 embedded controller registers - e.g. make sure nothing else changes
1134 except the charging or discharging battery to determine which
1135 registers contain the current battery capacity, etc. If you experiment
1136 with this, do send me your results (including some complete dumps with
1137 a description of the conditions when they were taken.)
1140 LCD brightness control
1141 ----------------------
1143 procfs: /proc/acpi/ibm/brightness
1144 sysfs backlight device "thinkpad_screen"
1146 This feature allows software control of the LCD brightness on ThinkPad
1147 models which don't have a hardware brightness slider.
1149 It has some limitations: the LCD backlight cannot be actually turned
1150 on or off by this interface, it just controls the backlight brightness
1153 On IBM (and some of the earlier Lenovo) ThinkPads, the backlight control
1154 has eight brightness levels, ranging from 0 to 7. Some of the levels
1155 may not be distinct. Later Lenovo models that implement the ACPI
1156 display backlight brightness control methods have 16 levels, ranging
1159 There are two interfaces to the firmware for direct brightness control,
1160 EC and UCMS (or CMOS). To select which one should be used, use the
1161 brightness_mode module parameter: brightness_mode=1 selects EC mode,
1162 brightness_mode=2 selects UCMS mode, brightness_mode=3 selects EC
1163 mode with NVRAM backing (so that brightness changes are remembered
1164 across shutdown/reboot).
1166 The driver tries to select which interface to use from a table of
1167 defaults for each ThinkPad model. If it makes a wrong choice, please
1168 report this as a bug, so that we can fix it.
1170 When display backlight brightness controls are available through the
1171 standard ACPI interface, it is best to use it instead of this direct
1172 ThinkPad-specific interface. The driver will disable its native
1173 backlight brightness control interface if it detects that the standard
1174 ACPI interface is available in the ThinkPad.
1176 The brightness_enable module parameter can be used to control whether
1177 the LCD brightness control feature will be enabled when available.
1178 brightness_enable=0 forces it to be disabled. brightness_enable=1
1179 forces it to be enabled when available, even if the standard ACPI
1180 interface is also available.
1184 The available commands are:
1186 echo up >/proc/acpi/ibm/brightness
1187 echo down >/proc/acpi/ibm/brightness
1188 echo 'level <level>' >/proc/acpi/ibm/brightness
1192 The interface is implemented through the backlight sysfs class, which is
1193 poorly documented at this time.
1195 Locate the thinkpad_screen device under /sys/class/backlight, and inside
1196 it there will be the following attributes:
1199 Reads the maximum brightness the hardware can be set to.
1200 The minimum is always zero.
1203 Reads what brightness the screen is set to at this instant.
1206 Writes request the driver to change brightness to the
1207 given value. Reads will tell you what brightness the
1208 driver is trying to set the display to when "power" is set
1209 to zero and the display has not been dimmed by a kernel
1210 power management event.
1213 power management mode, where 0 is "display on", and 1 to 3
1214 will dim the display backlight to brightness level 0
1215 because thinkpad-acpi cannot really turn the backlight
1216 off. Kernel power management events can temporarily
1217 increase the current power management level, i.e. they can
1223 Whatever you do, do NOT ever call thinkpad-acpi backlight-level change
1224 interface and the ACPI-based backlight level change interface
1225 (available on newer BIOSes, and driven by the Linux ACPI video driver)
1226 at the same time. The two will interact in bad ways, do funny things,
1227 and maybe reduce the life of the backlight lamps by needlessly kicking
1228 its level up and down at every change.
1231 Volume control -- /proc/acpi/ibm/volume
1232 ---------------------------------------
1234 This feature allows volume control on ThinkPad models which don't have
1235 a hardware volume knob. The available commands are:
1237 echo up >/proc/acpi/ibm/volume
1238 echo down >/proc/acpi/ibm/volume
1239 echo mute >/proc/acpi/ibm/volume
1240 echo 'level <level>' >/proc/acpi/ibm/volume
1242 The <level> number range is 0 to 15 although not all of them may be
1243 distinct. The unmute the volume after the mute command, use either the
1244 up or down command (the level command will not unmute the volume).
1245 The current volume level and mute state is shown in the file.
1247 The ALSA mixer interface to this feature is still missing, but patches
1248 to add it exist. That problem should be addressed in the not so
1252 Fan control and monitoring: fan speed, fan enable/disable
1253 ---------------------------------------------------------
1255 procfs: /proc/acpi/ibm/fan
1256 sysfs device attributes: (hwmon "thinkpad") fan1_input, pwm1,
1258 sysfs hwmon driver attributes: fan_watchdog
1260 NOTE NOTE NOTE: fan control operations are disabled by default for
1261 safety reasons. To enable them, the module parameter "fan_control=1"
1262 must be given to thinkpad-acpi.
1264 This feature attempts to show the current fan speed, control mode and
1265 other fan data that might be available. The speed is read directly
1266 from the hardware registers of the embedded controller. This is known
1267 to work on later R, T, X and Z series ThinkPads but may show a bogus
1268 value on other models.
1272 Most ThinkPad fans work in "levels" at the firmware interface. Level 0
1273 stops the fan. The higher the level, the higher the fan speed, although
1274 adjacent levels often map to the same fan speed. 7 is the highest
1275 level, where the fan reaches the maximum recommended speed.
1277 Level "auto" means the EC changes the fan level according to some
1278 internal algorithm, usually based on readings from the thermal sensors.
1280 There is also a "full-speed" level, also known as "disengaged" level.
1281 In this level, the EC disables the speed-locked closed-loop fan control,
1282 and drives the fan as fast as it can go, which might exceed hardware
1283 limits, so use this level with caution.
1285 The fan usually ramps up or down slowly from one speed to another, and
1286 it is normal for the EC to take several seconds to react to fan
1287 commands. The full-speed level may take up to two minutes to ramp up to
1288 maximum speed, and in some ThinkPads, the tachometer readings go stale
1289 while the EC is transitioning to the full-speed level.
1291 WARNING WARNING WARNING: do not leave the fan disabled unless you are
1292 monitoring all of the temperature sensor readings and you are ready to
1293 enable it if necessary to avoid overheating.
1295 An enabled fan in level "auto" may stop spinning if the EC decides the
1296 ThinkPad is cool enough and doesn't need the extra airflow. This is
1297 normal, and the EC will spin the fan up if the various thermal readings
1300 On the X40, this seems to depend on the CPU and HDD temperatures.
1301 Specifically, the fan is turned on when either the CPU temperature
1302 climbs to 56 degrees or the HDD temperature climbs to 46 degrees. The
1303 fan is turned off when the CPU temperature drops to 49 degrees and the
1304 HDD temperature drops to 41 degrees. These thresholds cannot
1305 currently be controlled.
1307 The ThinkPad's ACPI DSDT code will reprogram the fan on its own when
1308 certain conditions are met. It will override any fan programming done
1309 through thinkpad-acpi.
1311 The thinkpad-acpi kernel driver can be programmed to revert the fan
1312 level to a safe setting if userspace does not issue one of the procfs
1313 fan commands: "enable", "disable", "level" or "watchdog", or if there
1314 are no writes to pwm1_enable (or to pwm1 *if and only if* pwm1_enable is
1315 set to 1, manual mode) within a configurable amount of time of up to
1316 120 seconds. This functionality is called fan safety watchdog.
1318 Note that the watchdog timer stops after it enables the fan. It will be
1319 rearmed again automatically (using the same interval) when one of the
1320 above mentioned fan commands is received. The fan watchdog is,
1321 therefore, not suitable to protect against fan mode changes made through
1322 means other than the "enable", "disable", and "level" procfs fan
1323 commands, or the hwmon fan control sysfs interface.
1327 The fan may be enabled or disabled with the following commands:
1329 echo enable >/proc/acpi/ibm/fan
1330 echo disable >/proc/acpi/ibm/fan
1332 Placing a fan on level 0 is the same as disabling it. Enabling a fan
1333 will try to place it in a safe level if it is too slow or disabled.
1335 The fan level can be controlled with the command:
1337 echo 'level <level>' > /proc/acpi/ibm/fan
1339 Where <level> is an integer from 0 to 7, or one of the words "auto" or
1340 "full-speed" (without the quotes). Not all ThinkPads support the "auto"
1341 and "full-speed" levels. The driver accepts "disengaged" as an alias for
1342 "full-speed", and reports it as "disengaged" for backwards
1345 On the X31 and X40 (and ONLY on those models), the fan speed can be
1346 controlled to a certain degree. Once the fan is running, it can be
1347 forced to run faster or slower with the following command:
1349 echo 'speed <speed>' > /proc/acpi/ibm/fan
1351 The sustainable range of fan speeds on the X40 appears to be from about
1352 3700 to about 7350. Values outside this range either do not have any
1353 effect or the fan speed eventually settles somewhere in that range. The
1354 fan cannot be stopped or started with this command. This functionality
1355 is incomplete, and not available through the sysfs interface.
1357 To program the safety watchdog, use the "watchdog" command.
1359 echo 'watchdog <interval in seconds>' > /proc/acpi/ibm/fan
1361 If you want to disable the watchdog, use 0 as the interval.
1365 The sysfs interface follows the hwmon subsystem guidelines for the most
1366 part, and the exception is the fan safety watchdog.
1368 Writes to any of the sysfs attributes may return the EINVAL error if
1369 that operation is not supported in a given ThinkPad or if the parameter
1370 is out-of-bounds, and EPERM if it is forbidden. They may also return
1371 EINTR (interrupted system call), and EIO (I/O error while trying to talk
1374 Features not yet implemented by the driver return ENOSYS.
1376 hwmon device attribute pwm1_enable:
1377 0: PWM offline (fan is set to full-speed mode)
1378 1: Manual PWM control (use pwm1 to set fan level)
1379 2: Hardware PWM control (EC "auto" mode)
1380 3: reserved (Software PWM control, not implemented yet)
1382 Modes 0 and 2 are not supported by all ThinkPads, and the
1383 driver is not always able to detect this. If it does know a
1384 mode is unsupported, it will return -EINVAL.
1386 hwmon device attribute pwm1:
1387 Fan level, scaled from the firmware values of 0-7 to the hwmon
1388 scale of 0-255. 0 means fan stopped, 255 means highest normal
1391 This attribute only commands the fan if pmw1_enable is set to 1
1392 (manual PWM control).
1394 hwmon device attribute fan1_input:
1395 Fan tachometer reading, in RPM. May go stale on certain
1396 ThinkPads while the EC transitions the PWM to offline mode,
1397 which can take up to two minutes. May return rubbish on older
1400 hwmon driver attribute fan_watchdog:
1401 Fan safety watchdog timer interval, in seconds. Minimum is
1402 1 second, maximum is 120 seconds. 0 disables the watchdog.
1404 To stop the fan: set pwm1 to zero, and pwm1_enable to 1.
1406 To start the fan in a safe mode: set pwm1_enable to 2. If that fails
1407 with EINVAL, try to set pwm1_enable to 1 and pwm1 to at least 128 (255
1408 would be the safest choice, though).
1414 procfs: /proc/acpi/ibm/wan
1415 sysfs device attribute: wwan_enable (deprecated)
1416 sysfs rfkill class: switch "tpacpi_wwan_sw"
1418 This feature shows the presence and current state of the built-in
1419 Wireless WAN device.
1421 If the ThinkPad supports it, the WWAN state is stored in NVRAM,
1422 so it is kept across reboots and power-off.
1424 It was tested on a Lenovo ThinkPad X60. It should probably work on other
1425 ThinkPad models which come with this module installed.
1429 If the W-WAN card is installed, the following commands can be used:
1431 echo enable > /proc/acpi/ibm/wan
1432 echo disable > /proc/acpi/ibm/wan
1436 If the W-WAN card is installed, it can be enabled /
1437 disabled through the "wwan_enable" thinkpad-acpi device
1438 attribute, and its current status can also be queried.
1441 0: disables WWAN card / WWAN card is disabled
1442 1: enables WWAN card / WWAN card is enabled.
1444 Note: this interface has been superseded by the generic rfkill
1445 class. It has been deprecated, and it will be removed in year
1448 rfkill controller switch "tpacpi_wwan_sw": refer to
1449 Documentation/rfkill.txt for details.
1455 This feature is marked EXPERIMENTAL because it has not been extensively
1456 tested and validated in various ThinkPad models yet. The feature may not
1457 work as expected. USE WITH CAUTION! To use this feature, you need to supply
1458 the experimental=1 parameter when loading the module.
1460 sysfs rfkill class: switch "tpacpi_uwb_sw"
1462 This feature exports an rfkill controller for the UWB device, if one is
1463 present and enabled in the BIOS.
1467 rfkill controller switch "tpacpi_uwb_sw": refer to
1468 Documentation/rfkill.txt for details.
1471 Multiple Commands, Module Parameters
1472 ------------------------------------
1474 Multiple commands can be written to the proc files in one shot by
1475 separating them with commas, for example:
1477 echo enable,0xffff > /proc/acpi/ibm/hotkey
1478 echo lcd_disable,crt_enable > /proc/acpi/ibm/video
1480 Commands can also be specified when loading the thinkpad-acpi module,
1483 modprobe thinkpad_acpi hotkey=enable,0xffff video=auto_disable
1486 Enabling debugging output
1487 -------------------------
1489 The module takes a debug parameter which can be used to selectively
1490 enable various classes of debugging output, for example:
1492 modprobe thinkpad_acpi debug=0xffff
1494 will enable all debugging output classes. It takes a bitmask, so
1495 to enable more than one output class, just add their values.
1497 Debug bitmask Description
1498 0x8000 Disclose PID of userspace programs
1499 accessing some functions of the driver
1500 0x0001 Initialization and probing
1502 0x0004 RF Transmitter control (RFKILL)
1503 (bluetooth, WWAN, UWB...)
1504 0x0008 HKEY event interface, hotkeys
1506 0x0020 Backlight brightness
1508 There is also a kernel build option to enable more debugging
1509 information, which may be necessary to debug driver problems.
1511 The level of debugging information output by the driver can be changed
1512 at runtime through sysfs, using the driver attribute debug_level. The
1513 attribute takes the same bitmask as the debug module parameter above.
1516 Force loading of module
1517 -----------------------
1519 If thinkpad-acpi refuses to detect your ThinkPad, you can try to specify
1520 the module parameter force_load=1. Regardless of whether this works or
1521 not, please contact ibm-acpi-devel@lists.sourceforge.net with a report.
1524 Sysfs interface changelog:
1526 0x000100: Initial sysfs support, as a single platform driver and
1528 0x000200: Hot key support for 32 hot keys, and radio slider switch
1530 0x010000: Hot keys are now handled by default over the input
1531 layer, the radio switch generates input event EV_RADIO,
1532 and the driver enables hot key handling by default in
1535 0x020000: ABI fix: added a separate hwmon platform device and
1536 driver, which must be located by name (thinkpad)
1537 and the hwmon class for libsensors4 (lm-sensors 3)
1538 compatibility. Moved all hwmon attributes to this
1539 new platform device.
1541 0x020100: Marker for thinkpad-acpi with hot key NVRAM polling
1542 support. If you must, use it to know you should not
1543 start a userspace NVRAM poller (allows to detect when
1544 NVRAM is compiled out by the user because it is
1545 unneeded/undesired in the first place).
1546 0x020101: Marker for thinkpad-acpi with hot key NVRAM polling
1547 and proper hotkey_mask semantics (version 8 of the
1548 NVRAM polling patch). Some development snapshots of
1549 0.18 had an earlier version that did strange things
1552 0x020200: Add poll()/select() support to the following attributes:
1553 hotkey_radio_sw, wakeup_hotunplug_complete, wakeup_reason
1555 0x020300: hotkey enable/disable support removed, attributes
1556 hotkey_bios_enabled and hotkey_enable deprecated and
git.openpandora.org / pandora-kernel.git / blob