1 What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/kbd_backlight_mode
4 Contact: Azael Avalos <coproscefalo@gmail.com>
5 Description: This file controls the keyboard backlight operation mode, valid
9 * 0x2 -> AUTO (also called TIMER)
13 Note that from kernel 3.16 onwards this file accepts all listed
14 parameters, kernel 3.15 only accepts the first two (FN-Z and
16 Also note that toggling this value on type 1 devices, requires
17 a reboot for changes to take effect.
20 What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/kbd_backlight_timeout
23 Contact: Azael Avalos <coproscefalo@gmail.com>
24 Description: This file controls the timeout of the keyboard backlight
25 whenever the operation mode is set to AUTO (or TIMER),
26 valid values range from 0-60.
27 Note that the kernel 3.15 only had support for the first
28 keyboard type, the kernel 3.16 added support for the second
29 type and the range accepted for type 2 is 1-60.
30 See the entry named "kbd_type"
33 What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/position
36 Contact: Azael Avalos <coproscefalo@gmail.com>
37 Description: This file shows the absolute position of the built-in
40 What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/touchpad
43 Contact: Azael Avalos <coproscefalo@gmail.com>
44 Description: This files controls the status of the touchpad and pointing
45 stick (if available), valid values are:
52 What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/available_kbd_modes
55 Contact: Azael Avalos <coproscefalo@gmail.com>
56 Description: This file shows the supported keyboard backlight modes
57 the system supports, which can be:
60 * 0x2 -> AUTO (also called TIMER)
64 Note that not all keyboard types support the listed modes.
65 See the entry named "available_kbd_modes"
68 What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/kbd_type
71 Contact: Azael Avalos <coproscefalo@gmail.com>
72 Description: This file shows the current keyboard backlight type,
75 * 1 -> Type 1, supporting modes FN-Z and AUTO
76 * 2 -> Type 2, supporting modes TIMER, ON and OFF
79 What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/usb_sleep_charge
80 Date: January 23, 2015
82 Contact: Azael Avalos <coproscefalo@gmail.com>
83 Description: This file controls the USB Sleep & Charge charging mode, which
86 * 0 -> Disabled (0x00)
87 * 1 -> Alternate (0x09)
91 Note that from kernel 4.1 onwards this file accepts all listed
92 values, kernel 4.0 only supports the first three.
93 Note that this feature only works when connected to power, if
94 you want to use it under battery, see the entry named
95 "sleep_functions_on_battery"
98 What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/sleep_functions_on_battery
99 Date: January 23, 2015
101 Contact: Azael Avalos <coproscefalo@gmail.com>
102 Description: This file controls the USB Sleep Functions under battery, and
103 set the level at which point they will be disabled, accepted
107 * 1-100 -> Battery level to disable sleep functions
109 Currently it prints two values, the first one indicates if the
110 feature is enabled or disabled, while the second one shows the
111 current battery level set.
112 Note that when the value is set to disabled, the sleep function
113 will only work when connected to power.
116 What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/usb_rapid_charge
117 Date: January 23, 2015
119 Contact: Azael Avalos <coproscefalo@gmail.com>
120 Description: This file controls the USB Rapid Charge state, which can be:
125 Note that toggling this value requires a reboot for changes to
129 What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/usb_sleep_music
130 Date: January 23, 2015
132 Contact: Azael Avalos <coproscefalo@gmail.com>
133 Description: This file controls the Sleep & Music state, which values can be:
138 Note that this feature only works when connected to power, if
139 you want to use it under battery, see the entry named
140 "sleep_functions_on_battery"
143 What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/version
144 Date: February 12, 2015
146 Contact: Azael Avalos <coproscefalo@gmail.com>
147 Description: This file shows the current version of the driver
150 What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/fan
151 Date: February 12, 2015
153 Contact: Azael Avalos <coproscefalo@gmail.com>
154 Description: This file controls the state of the internal fan, valid
160 What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/kbd_function_keys
161 Date: February 12, 2015
163 Contact: Azael Avalos <coproscefalo@gmail.com>
164 Description: This file controls the Special Functions (hotkeys) operation
165 mode, valid values are:
167 * 0 -> Normal Operation
168 * 1 -> Special Functions
170 In the "Normal Operation" mode, the F{1-12} keys are as usual
171 and the hotkeys are accessed via FN-F{1-12}.
172 In the "Special Functions" mode, the F{1-12} keys trigger the
173 hotkey and the F{1-12} keys are accessed via FN-F{1-12}.
174 Note that toggling this value requires a reboot for changes to
178 What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/panel_power_on
179 Date: February 12, 2015
181 Contact: Azael Avalos <coproscefalo@gmail.com>
182 Description: This file controls whether the laptop should turn ON whenever
183 the LID is opened, valid values are:
188 Note that toggling this value requires a reboot for changes to
192 What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/usb_three
193 Date: February 12, 2015
195 Contact: Azael Avalos <coproscefalo@gmail.com>
196 Description: This file controls the USB 3 functionality, valid values are:
198 * 0 -> Disabled (Acts as a regular USB 2)
199 * 1 -> Enabled (Full USB 3 functionality)
201 Note that toggling this value requires a reboot for changes to
205 What: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS{1900,620{0,7,8}}:00/cooling_method
208 Contact: Azael Avalos <coproscefalo@gmail.com>
209 Description: This file controls the Cooling Method feature.
210 Reading this file prints two values, the first is the actual cooling method
211 and the second is the maximum cooling method supported.
212 When the maximum cooling method is ONE, valid values are:
214 * 0 -> Maximum Performance
215 * 1 -> Battery Optimized
217 When the maximum cooling method is TWO, valid values are:
219 * 0 -> Maximum Performance
221 * 2 -> Battery Optimized