2 # X86 Platform Specific Drivers
5 menuconfig X86_PLATFORM_DEVICES
6 bool "X86 Platform Specific Device Drivers"
10 Say Y here to get to see options for device drivers for various
11 x86 platforms, including vendor-specific laptop extension drivers.
12 This option alone does not add any kernel code.
14 If you say N, all options in this submenu will be skipped and disabled.
16 if X86_PLATFORM_DEVICES
19 tristate "Acer WMI Laptop Extras"
23 depends on BACKLIGHT_CLASS_DEVICE
24 depends on SERIO_I8042
26 depends on RFKILL || RFKILL = n
28 select INPUT_SPARSEKMAP
29 # Acer WMI depends on ACPI_VIDEO when ACPI is enabled
30 select ACPI_VIDEO if ACPI
32 This is a driver for newer Acer (and Wistron) laptops. It adds
33 wireless radio and bluetooth control, and on some laptops,
34 exposes the mail LED and LCD backlight.
36 If you have an ACPI-WMI compatible Acer/ Wistron laptop, say Y or M
40 tristate "Acer Wireless Radio Control Driver"
44 The Acer Wireless Radio Control handles the airplane mode hotkey
45 present on new Acer laptops.
47 Say Y or M here if you have an Acer notebook with an airplane mode
50 If you choose to compile this driver as a module the module will be
54 tristate "Acer Aspire One temperature and fan driver"
55 depends on ACPI && THERMAL
56 select THERMAL_GOV_BANG_BANG
58 This is a driver for Acer Aspire One netbooks. It allows to access
59 the temperature sensor and to control the fan.
61 After loading this driver the BIOS is still in control of the fan.
62 To let the kernel handle the fan, do:
63 echo -n enabled > /sys/class/thermal/thermal_zoneN/mode
64 where N=0,1,2... depending on the number of thermal nodes and the
65 detection order of your particular system. The "type" parameter
66 in the same node directory will tell you if it is "acerhdf".
68 For more information about this driver see
69 <http://piie.net/files/acerhdf_README.txt>
71 If you have an Acer Aspire One netbook, say Y or M
75 tristate "Alienware Special feature control"
81 This is a driver for controlling Alienware BIOS driven
82 features. It exposes an interface for controlling the AlienFX
83 zones on Alienware machines that don't contain a dedicated AlienFX
84 USB MCU such as the X51 and X51-R2.
87 tristate "Asus Laptop Extras"
91 depends on BACKLIGHT_CLASS_DEVICE
93 depends on RFKILL || RFKILL = n
94 depends on ACPI_VIDEO || ACPI_VIDEO = n
95 select INPUT_SPARSEKMAP
98 This is a driver for Asus laptops, Lenovo SL and the Pegatron
99 Lucid tablet. It may also support some MEDION, JVC or VICTOR
100 laptops. It makes all the extra buttons generate standard
101 ACPI events and input events, and on the Lucid the built-in
102 accelerometer appears as an input device. It also adds
103 support for video output switching, LCD backlight control,
104 Bluetooth and Wlan control, and most importantly, allows you
105 to blink those fancy LEDs.
107 For more information see <http://acpi4asus.sf.net>.
109 If you have an ACPI-compatible ASUS laptop, say Y or M here.
112 # The DELL_SMBIOS driver depends on ACPI_WMI and/or DCDBAS if those
113 # backends are selected. The "depends" line prevents a configuration
114 # where DELL_SMBIOS=y while either of those dependencies =m.
117 tristate "Dell SMBIOS driver"
118 depends on DCDBAS || DCDBAS=n
119 depends on ACPI_WMI || ACPI_WMI=n
121 This provides support for the Dell SMBIOS calling interface.
122 If you have a Dell computer you should enable this option.
124 Be sure to select at least one backend for it to work properly.
126 config DELL_SMBIOS_WMI
127 bool "Dell SMBIOS driver WMI backend"
130 select DELL_WMI_DESCRIPTOR
131 depends on DELL_SMBIOS
133 This provides an implementation for the Dell SMBIOS calling interface
134 communicated over ACPI-WMI.
136 If you have a Dell computer from >2007 you should say Y here.
137 If you aren't sure and this module doesn't work for your computer
140 config DELL_SMBIOS_SMM
141 bool "Dell SMBIOS driver SMM backend"
144 depends on DELL_SMBIOS
146 This provides an implementation for the Dell SMBIOS calling interface
147 communicated over SMI/SMM.
149 If you have a Dell computer from <=2017 you should say Y here.
150 If you aren't sure and this module doesn't work for your computer
154 tristate "Dell Laptop Extras"
156 depends on BACKLIGHT_CLASS_DEVICE
157 depends on ACPI_VIDEO || ACPI_VIDEO = n
158 depends on RFKILL || RFKILL = n
159 depends on SERIO_I8042
160 depends on DELL_SMBIOS
165 This driver adds support for rfkill and backlight control to Dell
166 laptops (except for some models covered by the Compal driver).
169 tristate "Dell WMI notifications"
173 depends on ACPI_VIDEO || ACPI_VIDEO = n
174 depends on DELL_SMBIOS
175 select DELL_WMI_DESCRIPTOR
176 select INPUT_SPARSEKMAP
178 Say Y here if you want to support WMI-based hotkeys on Dell laptops.
180 To compile this driver as a module, choose M here: the module will
183 config DELL_WMI_DESCRIPTOR
188 tristate "WMI Hotkeys for Dell All-In-One series"
191 select INPUT_SPARSEKMAP
193 Say Y here if you want to support WMI-based hotkeys on Dell
196 To compile this driver as a module, choose M here: the module will
197 be called dell-wmi-aio.
200 tristate "External LED on Dell Business Netbooks"
201 depends on LEDS_CLASS
204 This adds support for the Latitude 2100 and similar
205 notebooks that have an external LED.
208 tristate "Dell Latitude freefall driver (ACPI SMO88XX)"
211 Say Y here if you want to support SMO88XX freefall devices
212 on Dell Latitude laptops.
214 To compile this driver as a module, choose M here: the module will
215 be called dell-smo8800.
218 tristate "Dell Airplane Mode Switch driver"
223 Say Y here if you want to support Dell Airplane Mode Switch ACPI
224 device on Dell laptops. Sometimes it has names: DELLABCE or DELRBTN.
225 This driver register rfkill device or input hotkey device depending
226 on hardware type (hw switch slider or keyboard toggle button). For
227 rfkill devices it receive HW switch events and set correct hard
230 To compile this driver as a module, choose M here: the module will
234 tristate "BIOS update support for DELL systems via sysfs"
237 select FW_LOADER_USER_HELPER
239 Say m if you want to have the option of updating the BIOS for your
240 DELL system. Note you need a Dell OpenManage or Dell Update package (DUP)
241 supporting application to communicate with the BIOS regarding the new
242 image for the image update to take effect.
243 See <file:Documentation/dell_rbu.txt> for more details on the driver.
246 config FUJITSU_LAPTOP
247 tristate "Fujitsu Laptop Extras"
250 depends on BACKLIGHT_CLASS_DEVICE
251 depends on ACPI_VIDEO || ACPI_VIDEO = n
252 select INPUT_SPARSEKMAP
255 This is a driver for laptops built by Fujitsu:
257 * P2xxx/P5xxx/S6xxx/S7xxx series Lifebooks
258 * Possibly other Fujitsu laptop models
259 * Tested with S6410 and S7020
261 It adds support for LCD brightness control and some hotkeys.
263 If you have a Fujitsu laptop, say Y or M here.
265 config FUJITSU_TABLET
266 tristate "Fujitsu Tablet Extras"
270 This is a driver for tablets built by Fujitsu:
272 * Lifebook P1510/P1610/P1620/Txxxx
274 * Possibly other Fujitsu tablet models
276 It adds support for the panel buttons, docking station detection,
277 tablet/notebook mode detection for convertible and
278 orientation detection for docked slates.
280 If you have a Fujitsu convertible or slate, say Y or M here.
283 tristate "Fujitsu-Siemens Amilo rfkill support"
285 depends on SERIO_I8042
287 This is a driver for enabling wifi on some Fujitsu-Siemens Amilo
290 config GPD_POCKET_FAN
291 tristate "GPD Pocket Fan Controller support"
295 Driver for the GPD Pocket vendor specific FAN02501 ACPI device
296 which controls the fan speed on the GPD Pocket.
298 Without this driver the fan on the Pocket will stay off independent
299 of the CPU temperature. Say Y or M if the kernel may be used on a
303 tristate "HP Compaq TC1100 Tablet WMI Extras"
308 This is a driver for the WMI extensions (wireless and bluetooth power
309 control) of the HP Compaq TC1100 tablet.
312 tristate "HP laptop accelerometer"
313 depends on INPUT && ACPI
314 depends on SERIO_I8042
315 select SENSORS_LIS3LV02D
319 This driver provides support for the "Mobile Data Protection System 3D"
320 or "3D DriveGuard" feature of HP laptops. On such systems the driver
321 should load automatically (via ACPI alias).
323 Support for a led indicating disk protection will be provided as
324 hp::hddprotect. For more information on the feature, refer to
325 Documentation/misc-devices/lis3lv02d.
327 To compile this driver as a module, choose M here: the module will
331 tristate "HP wireless button"
335 This driver provides supports for new HP wireless button for Windows 8.
336 On such systems the driver should load automatically (via ACPI alias).
338 To compile this driver as a module, choose M here: the module will
339 be called hp-wireless.
342 tristate "HP WMI extras"
345 depends on RFKILL || RFKILL = n
346 select INPUT_SPARSEKMAP
348 Say Y here if you want to support WMI-based hotkeys on HP laptops and
349 to read data from WMI such as docking or ambient light sensor state.
351 To compile this driver as a module, choose M here: the module will
355 tristate "MSI Laptop Extras"
357 depends on BACKLIGHT_CLASS_DEVICE
358 depends on ACPI_VIDEO || ACPI_VIDEO = n
360 depends on INPUT && SERIO_I8042
361 select INPUT_SPARSEKMAP
363 This is a driver for laptops built by MSI (MICRO-STAR
366 MSI MegaBook S270 (MS-1013)
367 Cytron/TCM/Medion/Tchibo MD96100/SAM2000
369 It adds support for Bluetooth, WLAN and LCD brightness control.
371 More information about this driver is available at
372 <http://0pointer.de/lennart/tchibo.html>.
374 If you have an MSI S270 laptop, say Y or M here.
376 config PANASONIC_LAPTOP
377 tristate "Panasonic Laptop Extras"
378 depends on INPUT && ACPI
379 depends on BACKLIGHT_CLASS_DEVICE
380 select INPUT_SPARSEKMAP
382 This driver adds support for access to backlight control and hotkeys
383 on Panasonic Let's Note laptops.
385 If you have a Panasonic Let's note laptop (such as the R1(N variant),
386 R2, R3, R5, T2, W2 and Y2 series), say Y.
389 tristate "Compal (and others) Laptop Extras"
391 depends on BACKLIGHT_CLASS_DEVICE
392 depends on ACPI_VIDEO || ACPI_VIDEO = n
395 depends on POWER_SUPPLY
397 This is a driver for laptops built by Compal, and some models by
398 other brands (e.g. Dell, Toshiba).
400 It adds support for rfkill, Bluetooth, WLAN, LCD brightness, hwmon
401 and battery charging level control.
403 For a (possibly incomplete) list of supported laptops, please refer
404 to: Documentation/platform/x86-laptop-drivers.txt
407 tristate "Sony Laptop Extras"
409 depends on ACPI_VIDEO || ACPI_VIDEO = n
410 depends on BACKLIGHT_CLASS_DEVICE
414 This mini-driver drives the SNC and SPIC devices present in the ACPI
415 BIOS of the Sony Vaio laptops.
417 It gives access to some extra laptop functionalities like Bluetooth,
418 screen brightness control, Fn keys and allows powering on/off some
421 Read <file:Documentation/laptops/sony-laptop.txt> for more information.
424 bool "Sonypi compatibility"
425 depends on SONY_LAPTOP
427 Build the sonypi driver compatibility code into the sony-laptop driver.
429 config IDEAPAD_LAPTOP
430 tristate "Lenovo IdeaPad Laptop Extras"
432 depends on RFKILL && INPUT
433 depends on SERIO_I8042
434 depends on BACKLIGHT_CLASS_DEVICE
435 depends on ACPI_VIDEO || ACPI_VIDEO = n
436 depends on ACPI_WMI || ACPI_WMI = n
437 select INPUT_SPARSEKMAP
439 This is a driver for Lenovo IdeaPad netbooks contains drivers for
440 rfkill switch, hotkey, fan control and backlight control.
443 tristate "Surface 3 WMI Driver"
449 Say Y here if you have a Surface 3.
451 To compile this driver as a module, choose M here: the module will
452 be called surface3-wmi.
455 tristate "ThinkPad ACPI Laptop Extras"
457 depends on ACPI_BATTERY
459 depends on RFKILL || RFKILL = n
460 depends on ACPI_VIDEO || ACPI_VIDEO = n
461 depends on BACKLIGHT_CLASS_DEVICE
467 This is a driver for the IBM and Lenovo ThinkPad laptops. It adds
468 support for Fn-Fx key combinations, Bluetooth control, video
469 output switching, ThinkLight control, UltraBay eject and more.
470 For more information about this driver see
471 <file:Documentation/laptops/thinkpad-acpi.txt> and
472 <http://ibm-acpi.sf.net/> .
474 This driver was formerly known as ibm-acpi.
476 Extra functionality will be available if the rfkill (CONFIG_RFKILL)
477 and/or ALSA (CONFIG_SND) subsystems are available in the kernel.
478 Note that if you want ThinkPad-ACPI to be built-in instead of
479 modular, ALSA and rfkill will also have to be built-in.
481 If you have an IBM or Lenovo ThinkPad laptop, say Y or M here.
483 config THINKPAD_ACPI_ALSA_SUPPORT
484 bool "Console audio control ALSA interface"
485 depends on THINKPAD_ACPI
487 depends on SND = y || THINKPAD_ACPI = SND
490 Enables monitoring of the built-in console audio output control
491 (headphone and speakers), which is operated by the mute and (in
492 some ThinkPad models) volume hotkeys.
494 If this option is enabled, ThinkPad-ACPI will export an ALSA card
495 with a single read-only mixer control, which should be used for
496 on-screen-display feedback purposes by the Desktop Environment.
498 Optionally, the driver will also allow software control (the
499 ALSA mixer will be made read-write). Please refer to the driver
500 documentation for details.
502 All IBM models have both volume and mute control. Newer Lenovo
503 models only have mute control (the volume hotkeys are just normal
504 keys and volume control is done through the main HDA mixer).
506 config THINKPAD_ACPI_DEBUGFACILITIES
507 bool "Maintainer debug facilities"
508 depends on THINKPAD_ACPI
510 Enables extra stuff in the thinkpad-acpi which is completely useless
511 for normal use. Read the driver source to find out what it does.
513 Say N here, unless you were told by a kernel maintainer to do
516 config THINKPAD_ACPI_DEBUG
517 bool "Verbose debug mode"
518 depends on THINKPAD_ACPI
520 Enables extra debugging information, at the expense of a slightly
521 increase in driver size.
523 If you are not sure, say N here.
525 config THINKPAD_ACPI_UNSAFE_LEDS
526 bool "Allow control of important LEDs (unsafe)"
527 depends on THINKPAD_ACPI
529 Overriding LED state on ThinkPads can mask important
530 firmware alerts (like critical battery condition), or misled
531 the user into damaging the hardware (undocking or ejecting
532 the bay while buses are still active), etc.
534 LED control on the ThinkPad is write-only (with very few
535 exceptions on very ancient models), which makes it
536 impossible to know beforehand if important information will
537 be lost when one changes LED state.
539 Users that know what they are doing can enable this option
540 and the driver will allow control of every LED, including
541 the ones on the dock stations.
543 Never enable this option on a distribution kernel.
545 Say N here, unless you are building a kernel for your own
546 use, and need to control the important firmware LEDs.
548 config THINKPAD_ACPI_VIDEO
549 bool "Video output control support"
550 depends on THINKPAD_ACPI
553 Allows the thinkpad_acpi driver to provide an interface to control
554 the various video output ports.
556 This feature often won't work well, depending on ThinkPad model,
557 display state, video output devices in use, whether there is a X
558 server running, phase of the moon, and the current mood of
559 Schroedinger's cat. If you can use X.org's RandR to control
560 your ThinkPad's video output ports instead of this feature,
561 don't think twice: do it and say N here to save memory and avoid
562 bad interactions with X.org.
564 NOTE: access to this feature is limited to processes with the
565 CAP_SYS_ADMIN capability, to avoid local DoS issues in platforms
566 where it interacts badly with X.org.
568 If you are not sure, say Y here but do try to check if you could
569 be using X.org RandR instead.
571 config THINKPAD_ACPI_HOTKEY_POLL
572 bool "Support NVRAM polling for hot keys"
573 depends on THINKPAD_ACPI
576 Some thinkpad models benefit from NVRAM polling to detect a few of
577 the hot key press events. If you know your ThinkPad model does not
578 need to do NVRAM polling to support any of the hot keys you use,
579 unselecting this option will save about 1kB of memory.
581 ThinkPads T40 and newer, R52 and newer, and X31 and newer are
582 unlikely to need NVRAM polling in their latest BIOS versions.
584 NVRAM polling can detect at most the following keys: ThinkPad/Access
585 IBM, Zoom, Switch Display (fn+F7), ThinkLight, Volume up/down/mute,
586 Brightness up/down, Display Expand (fn+F8), Hibernate (fn+F12).
588 If you are not sure, say Y here. The driver enables polling only if
589 it is strictly necessary to do so.
592 tristate "Thinkpad Hard Drive Active Protection System (hdaps)"
596 This driver provides support for the IBM Hard Drive Active Protection
597 System (hdaps), which provides an accelerometer and other misc. data.
598 ThinkPads starting with the R50, T41, and X40 are supported. The
599 accelerometer data is readable via sysfs.
601 This driver also provides an absolute input class device, allowing
602 the laptop to act as a pinball machine-esque joystick.
604 If your ThinkPad is not recognized by the driver, please update to latest
605 BIOS. This is especially the case for some R52 ThinkPads.
607 Say Y here if you have an applicable laptop and want to experience
608 the awesome power of hdaps.
611 tristate "Thermal Management driver for Intel menlow platform"
612 depends on ACPI_THERMAL
615 ACPI thermal management enhancement driver on
616 Intel Menlow platform.
621 tristate "Eee PC Hotkey Driver"
624 depends on RFKILL || RFKILL = n
625 depends on ACPI_VIDEO || ACPI_VIDEO = n
626 depends on HOTPLUG_PCI
627 depends on BACKLIGHT_CLASS_DEVICE
631 select INPUT_SPARSEKMAP
633 This driver supports the Fn-Fx keys on Eee PC laptops.
635 It also gives access to some extra laptop functionalities like
636 Bluetooth, backlight and allows powering on/off some other
639 If you have an Eee PC laptop, say Y or M here. If this driver
640 doesn't work on your Eee PC, try eeepc-wmi instead.
643 tristate "ASUS WMI Driver"
647 depends on BACKLIGHT_CLASS_DEVICE
648 depends on RFKILL || RFKILL = n
649 depends on HOTPLUG_PCI
650 depends on ACPI_VIDEO || ACPI_VIDEO = n
651 select INPUT_SPARSEKMAP
655 Say Y here if you have a WMI aware Asus laptop (like Eee PCs or new
658 To compile this driver as a module, choose M here: the module will
662 tristate "Asus Notebook WMI Driver"
664 depends on SERIO_I8042 || SERIO_I8042 = n
666 This is a driver for newer Asus notebooks. It adds extra features
667 like wireless radio and bluetooth control, leds, hotkeys, backlight...
669 For more information, see
670 <file:Documentation/ABI/testing/sysfs-platform-asus-wmi>
672 If you have an ACPI-WMI compatible Asus Notebook, say Y or M
676 tristate "Eee PC WMI Driver"
679 This is a driver for newer Eee PC laptops. It adds extra features
680 like wireless radio and bluetooth control, leds, hotkeys, backlight...
682 For more information, see
683 <file:Documentation/ABI/testing/sysfs-platform-asus-wmi>
685 If you have an ACPI-WMI compatible Eee PC laptop (>= 1000), say Y or M
689 tristate "Asus Wireless Radio Control Driver"
695 The Asus Wireless Radio Control handles the airplane mode hotkey
696 present on some Asus laptops.
698 Say Y or M here if you have an ASUS notebook with an airplane mode
701 If you choose to compile this driver as a module the module will be
702 called asus-wireless.
708 This driver adds support for the ACPI-WMI (Windows Management
709 Instrumentation) mapper device (PNP0C14) found on some systems.
711 ACPI-WMI is a proprietary extension to ACPI to expose parts of the
712 ACPI firmware to userspace - this is done through various vendor
713 defined methods and data blocks in a PNP0C14 device, which are then
714 made available for userspace to call.
716 The implementation of this in Linux currently only exposes this to
717 other kernel space drivers.
719 This driver is a required dependency to build the firmware specific
720 drivers needed on many machines, including Acer and HP laptops.
722 It is safe to enable this driver even if your DSDT doesn't define
723 any ACPI-WMI devices.
726 tristate "WMI embedded Binary MOF driver"
730 Say Y here if you want to be able to read a firmware-embedded
731 WMI Binary MOF data. Using this requires userspace tools and may be
734 To compile this driver as a module, choose M here: the module will
737 config INTEL_WMI_THUNDERBOLT
738 tristate "Intel WMI thunderbolt force power driver"
741 Say Y here if you want to be able to use the WMI interface on select
742 systems to force the power control of Intel Thunderbolt controllers.
743 This is useful for updating the firmware when devices are not plugged
746 To compile this driver as a module, choose M here: the module will
747 be called intel-wmi-thunderbolt.
750 tristate "MSI WMI extras"
753 depends on BACKLIGHT_CLASS_DEVICE
754 depends on ACPI_VIDEO || ACPI_VIDEO = n
755 select INPUT_SPARSEKMAP
757 Say Y here if you want to support WMI-based hotkeys on MSI laptops.
759 To compile this driver as a module, choose M here: the module will
763 tristate "PEAQ 2-in-1 WMI hotkey driver"
768 Say Y here if you want to support WMI-based hotkeys on PEAQ 2-in-1s.
770 config TOPSTAR_LAPTOP
771 tristate "Topstar Laptop Extras"
774 select INPUT_SPARSEKMAP
778 This driver adds support for hotkeys found on Topstar laptops.
780 If you have a Topstar laptop, say Y or M here.
783 tristate "Toshiba Laptop Extras"
788 depends on BACKLIGHT_CLASS_DEVICE
790 depends on SERIO_I8042 || SERIO_I8042 = n
791 depends on ACPI_VIDEO || ACPI_VIDEO = n
792 depends on RFKILL || RFKILL = n
795 select INPUT_SPARSEKMAP
797 This driver adds support for access to certain system settings
798 on "legacy free" Toshiba laptops. These laptops can be recognized by
799 their lack of a BIOS setup menu and APM support.
801 On these machines, all system configuration is handled through the
802 ACPI. This driver is required for access to controls not covered
803 by the general ACPI drivers, such as LCD brightness, video output,
806 This driver differs from the non-ACPI Toshiba laptop driver (located
807 under "Processor type and features") in several aspects.
808 Configuration is accessed by reading and writing text files in the
809 /proc tree instead of by program interface to /dev. Furthermore, no
810 power management functions are exposed, as those are handled by the
811 general ACPI drivers.
813 More information about this driver is available at
814 <http://memebeam.org/toys/ToshibaAcpiDriver>.
816 If you have a legacy free Toshiba laptop (such as the Libretto L1
819 config TOSHIBA_BT_RFKILL
820 tristate "Toshiba Bluetooth RFKill switch support"
822 depends on RFKILL || RFKILL = n
824 This driver adds support for Bluetooth events for the RFKill
825 switch on modern Toshiba laptops with full ACPI support and
828 This driver handles RFKill events for the TOS6205 Bluetooth,
829 and re-enables it when the switch is set back to the 'on'
832 If you have a modern Toshiba laptop with a Bluetooth and an
833 RFKill switch (such as the Portege R500), say Y.
836 tristate "Toshiba HDD Active Protection Sensor"
839 This driver adds support for the built-in accelerometer
840 found on recent Toshiba laptops equipped with HID TOS620A
843 This driver receives ACPI notify events 0x80 when the sensor
844 detects a sudden move or a harsh vibration, as well as an
845 ACPI notify event 0x81 whenever the movement or vibration has
848 Also provides sysfs entries to get/set the desired protection
849 level and resetting the HDD protection interface.
851 If you have a recent Toshiba laptop with a built-in accelerometer
855 tristate "Toshiba WMI Hotkeys Driver (EXPERIMENTAL)"
858 select INPUT_SPARSEKMAP
860 This driver adds hotkey monitoring support to some Toshiba models
861 that manage the hotkeys via WMI events.
863 WARNING: This driver is incomplete as it lacks a proper keymap and the
864 *notify function only prints the ACPI event type value. Be warned that
865 you will need to provide some information if you have a Toshiba model
866 with WMI event hotkeys and want to help with the development of this
869 If you have a WMI-based hotkeys Toshiba laptop, say Y or M here.
872 tristate "CMPC Laptop Extras"
873 depends on ACPI && INPUT
874 depends on RFKILL || RFKILL=n
875 select BACKLIGHT_CLASS_DEVICE
877 Support for Intel Classmate PC ACPI devices, including some
878 keys as input device, backlight device, tablet and accelerometer
881 config INTEL_CHT_INT33FE
882 tristate "Intel Cherry Trail ACPI INT33FE Driver"
883 depends on X86 && ACPI && I2C && REGULATOR
884 depends on CHARGER_BQ24190=y || (CHARGER_BQ24190=m && m)
886 This driver add support for the INT33FE ACPI device found on
887 some Intel Cherry Trail devices.
889 The INT33FE ACPI device has a CRS table with I2cSerialBusV2
890 resources for 3 devices: Maxim MAX17047 Fuel Gauge Controller,
891 FUSB302 USB Type-C Controller and PI3USB30532 USB switch.
892 This driver instantiates i2c-clients for these, so that standard
893 i2c drivers for these chips can bind to the them.
895 If you enable this driver it is advised to also select
896 CONFIG_TYPEC_FUSB302=m and CONFIG_BATTERY_MAX17042=m.
898 config INTEL_INT0002_VGPIO
899 tristate "Intel ACPI INT0002 Virtual GPIO driver"
900 depends on GPIOLIB && ACPI
901 select GPIOLIB_IRQCHIP
903 Some peripherals on Bay Trail and Cherry Trail platforms signal a
904 Power Management Event (PME) to the Power Management Controller (PMC)
905 to wakeup the system. When this happens software needs to explicitly
906 clear the PME bus 0 status bit in the GPE0a_STS register to avoid an
909 This is modelled in ACPI through the INT0002 ACPI device, which is
910 called a "Virtual GPIO controller" in ACPI because it defines the
911 event handler to call when the PME triggers through _AEI and _L02
912 methods as would be done for a real GPIO interrupt in ACPI.
914 To compile this driver as a module, choose M here: the module will
915 be called intel_int0002_vgpio.
917 config INTEL_HID_EVENT
918 tristate "INTEL HID Event"
921 select INPUT_SPARSEKMAP
923 This driver provides support for the Intel HID Event hotkey interface.
924 Some laptops require this driver for hotkey support.
926 To compile this driver as a module, choose M here: the module will
930 tristate "INTEL VIRTUAL BUTTON"
933 select INPUT_SPARSEKMAP
935 This driver provides support for the Intel Virtual Button interface.
936 Some laptops require this driver for power button support.
938 To compile this driver as a module, choose M here: the module will
939 be called intel_vbtn.
942 bool "Intel SCU IPC Support"
943 depends on X86_INTEL_MID
946 IPC is used to bridge the communications between kernel and SCU on
947 some embedded Intel x86 platforms. This is not needed for PC-type
950 config INTEL_SCU_IPC_UTIL
951 tristate "Intel SCU IPC utility driver"
952 depends on INTEL_SCU_IPC
955 The IPC Util driver provides an interface with the SCU enabling
956 low level access for debug work and updating the firmware. Say
957 N unless you will be doing this on an Intel MID platform.
959 config INTEL_MID_POWER_BUTTON
960 tristate "power button driver for Intel MID platforms"
961 depends on INTEL_SCU_IPC && INPUT
963 This driver handles the power button on the Intel MID platforms.
967 config INTEL_MFLD_THERMAL
968 tristate "Thermal driver for Intel Medfield platform"
969 depends on MFD_INTEL_MSIC && THERMAL
971 Say Y here to enable thermal driver support for the Intel Medfield
975 tristate "Intel Intelligent Power Sharing"
978 Intel Calpella platforms support dynamic power sharing between the
979 CPU and GPU, maximizing performance in a given TDP. This driver,
980 along with the CPU frequency and i915 drivers, provides that
981 functionality. If in doubt, say Y here; it will only load on
985 bool "Intel Isolated Memory Region support"
986 depends on X86_INTEL_QUARK && IOSF_MBI
988 This option provides a means to manipulate Isolated Memory Regions.
989 IMRs are a set of registers that define read and write access masks
990 to prohibit certain system agents from accessing memory with 1 KiB
993 IMRs make it possible to control read/write access to an address
994 by hardware agents inside the SoC. Read and write masks can be
997 - Dirty CPU snoop (write only)
999 - PCI Virtual Channel 0/Virtual Channel 1
1003 Quark contains a set of eight IMR registers and makes use of those
1004 registers during its bootup process.
1006 If you are running on a Galileo/Quark say Y here.
1008 config INTEL_PMC_CORE
1009 tristate "Intel PMC Core driver"
1012 The Intel Platform Controller Hub for Intel Core SoCs provides access
1013 to Power Management Controller registers via a PCI interface. This
1014 driver can utilize debugging capabilities and supported features as
1015 exposed by the Power Management Controller.
1018 - SLP_S0_RESIDENCY counter
1019 - PCH IP Power Gating status
1021 - MPHY/PLL gating status (Sunrisepoint PCH only)
1024 tristate "Device driver to enable PRTL support"
1027 Enable support for IBM Premium Real Time Mode (PRTM).
1028 This module will allow you the enter and exit PRTM in the BIOS via
1029 sysfs on platforms that support this feature. System in PRTM will
1030 not receive CPU-generated SMIs for recoverable errors. Use of this
1031 feature without proper support may void your hardware warranty.
1033 If the proper BIOS support is found the driver will load and create
1034 /sys/devices/system/ibm_rtl/. The "state" variable will indicate
1035 whether or not the BIOS is in PRTM.
1036 state = 0 (BIOS SMIs on)
1037 state = 1 (BIOS SMIs off)
1040 tristate "OLPC XO-1 software RF kill switch"
1041 depends on OLPC || COMPILE_TEST
1044 Support for enabling/disabling the WLAN interface on the OLPC XO-1
1048 tristate "OLPC XO-1.5 ebook switch"
1049 depends on OLPC || COMPILE_TEST
1050 depends on ACPI && INPUT
1052 Support for the ebook switch on the OLPC XO-1.5 laptop.
1054 This switch is triggered as the screen is rotated and folded down to
1055 convert the device into ebook form.
1057 config SAMSUNG_LAPTOP
1058 tristate "Samsung Laptop driver"
1059 depends on RFKILL || RFKILL = n
1060 depends on ACPI_VIDEO || ACPI_VIDEO = n
1061 depends on BACKLIGHT_CLASS_DEVICE
1065 This module implements a driver for a wide range of different
1066 Samsung laptops. It offers control over the different
1067 function keys, wireless LED, LCD backlight level.
1069 It may also provide some sysfs files described in
1070 <file:Documentation/ABI/testing/sysfs-driver-samsung-laptop>
1072 To compile this driver as a module, choose M here: the module
1073 will be called samsung-laptop.
1076 tristate "WMI support for MXM Laptop Graphics"
1079 MXM is a standard for laptop graphics cards, the WMI interface
1080 is required for switchable nvidia graphics machines
1082 config INTEL_OAKTRAIL
1083 tristate "Intel Oaktrail Platform Extras"
1085 depends on ACPI_VIDEO || ACPI_VIDEO = n
1086 depends on RFKILL && BACKLIGHT_CLASS_DEVICE && ACPI
1088 Intel Oaktrail platform need this driver to provide interfaces to
1089 enable/disable the Camera, WiFi, BT etc. devices. If in doubt, say Y
1090 here; it will only load on supported platforms.
1093 tristate "Samsung Q10 Extras"
1095 select BACKLIGHT_CLASS_DEVICE
1097 This driver provides support for backlight control on Samsung Q10
1098 and related laptops, including Dell Latitude X200.
1101 tristate "Apple Gmux Driver"
1104 depends on BACKLIGHT_CLASS_DEVICE
1105 depends on BACKLIGHT_APPLE=n || BACKLIGHT_APPLE
1106 depends on ACPI_VIDEO=n || ACPI_VIDEO
1108 This driver provides support for the gmux device found on many
1109 Apple laptops, which controls the display mux for the hybrid
1110 graphics as well as the backlight. Currently only backlight
1111 control is supported by the driver.
1114 tristate "Intel Rapid Start Technology Driver"
1117 This driver provides support for modifying paramaters on systems
1118 equipped with Intel's Rapid Start Technology. When put in an ACPI
1119 sleep state, these devices will wake after either a configured
1120 timeout or when the system battery reaches a critical state,
1121 automatically copying memory contents to disk. On resume, the
1122 firmware will copy the memory contents back to RAM and resume the OS
1125 config INTEL_SMARTCONNECT
1126 tristate "Intel Smart Connect disabling driver"
1129 Intel Smart Connect is a technology intended to permit devices to
1130 update state by resuming for a short period of time at regular
1131 intervals. If a user enables this functionality under Windows and
1132 then reboots into Linux, the system may remain configured to resume
1133 on suspend. In the absence of any userspace to support it, the system
1134 will then remain awake until something triggers another suspend.
1136 This driver checks to determine whether the device has Intel Smart
1137 Connect enabled, and if so disables it.
1140 tristate "pvpanic device support"
1143 This driver provides support for the pvpanic device. pvpanic is
1144 a paravirtualized device provided by QEMU; it lets a virtual machine
1145 (guest) communicate panic events to the host.
1147 config INTEL_PMC_IPC
1148 tristate "Intel PMC IPC Driver"
1151 This driver provides support for PMC control on some Intel platforms.
1152 The PMC is an ARC processor which defines IPC commands for communication
1153 with other entities in the CPU.
1155 config INTEL_BXTWC_PMIC_TMU
1156 tristate "Intel BXT Whiskey Cove TMU Driver"
1158 depends on INTEL_SOC_PMIC_BXTWC && INTEL_PMC_IPC
1160 Select this driver to use Intel BXT Whiskey Cove PMIC TMU feature.
1161 This driver enables the alarm wakeup functionality in the TMU unit
1162 of Whiskey Cove PMIC.
1164 config SURFACE_PRO3_BUTTON
1165 tristate "Power/home/volume buttons driver for Microsoft Surface Pro 3/4 tablet"
1166 depends on ACPI && INPUT
1168 This driver handles the power/home/volume buttons on the Microsoft Surface Pro 3/4 tablet.
1170 config SURFACE_3_BUTTON
1171 tristate "Power/home/volume buttons driver for Microsoft Surface 3 tablet"
1172 depends on ACPI && KEYBOARD_GPIO && I2C
1174 This driver handles the power/home/volume buttons on the Microsoft Surface 3 tablet.
1176 config INTEL_PUNIT_IPC
1177 tristate "Intel P-Unit IPC Driver"
1179 This driver provides support for Intel P-Unit Mailbox IPC mechanism,
1180 which is used to bridge the communications between kernel and P-Unit.
1182 config INTEL_TELEMETRY
1183 tristate "Intel SoC Telemetry Driver"
1184 depends on INTEL_PMC_IPC && INTEL_PUNIT_IPC && X86_64
1186 This driver provides interfaces to configure and use
1187 telemetry for INTEL SoC from APL onwards. It is also
1188 used to get various SoC events and parameters
1189 directly via debugfs files. Various tools may use
1190 this interface for SoC state monitoring.
1193 tristate "Mellanox Technologies platform support"
1194 depends on I2C && REGMAP
1196 This option enables system support for the Mellanox Technologies
1197 platform. The Mellanox systems provide data center networking
1198 solutions based on Virtual Protocol Interconnect (VPI) technology
1199 enable seamless connectivity to 56/100Gb/s InfiniBand or 10/40/56GbE
1202 If you have a Mellanox system, say Y or M here.
1204 config INTEL_TURBO_MAX_3
1205 bool "Intel Turbo Boost Max Technology 3.0 enumeration driver"
1206 depends on X86_64 && SCHED_MC_PRIO
1208 This driver reads maximum performance ratio of each CPU and set up
1209 the scheduler priority metrics. In this way scheduler can prefer
1210 CPU with higher performance to schedule tasks.
1211 This driver is only required when the system is not using Hardware
1212 P-States (HWP). In HWP mode, priority can be read from ACPI tables.
1214 config TOUCHSCREEN_DMI
1215 bool "DMI based touchscreen configuration info"
1216 depends on ACPI && DMI && I2C=y && TOUCHSCREEN_SILEAD
1218 Certain ACPI based tablets with e.g. Silead or Chipone touchscreens
1219 do not have enough data in ACPI tables for the touchscreen driver to
1220 handle the touchscreen properly, as OEMs expect the data to be baked
1221 into the tablet model specific version of the driver shipped with the
1222 the OS-image for the device. This option supplies the missing info.
1223 Enable this for x86 tablets with Silead or Chipone touchscreens.
1225 config INTEL_CHTDC_TI_PWRBTN
1226 tristate "Intel Cherry Trail Dollar Cove TI power button driver"
1227 depends on INTEL_SOC_PMIC_CHTDC_TI
1230 This option adds a power button driver driver for Dollar Cove TI
1231 PMIC on Intel Cherry Trail devices.
1233 To compile this driver as a module, choose M here: the module
1234 will be called intel_chtdc_ti_pwrbtn.
1236 config I2C_MULTI_INSTANTIATE
1237 tristate "I2C multi instantiate pseudo device driver"
1238 depends on I2C && ACPI
1240 Some ACPI-based systems list multiple i2c-devices in a single ACPI
1241 firmware-node. This driver will instantiate separate i2c-clients
1242 for each device in the firmware-node.
1244 To compile this driver as a module, choose M here: the module
1245 will be called i2c-multi-instantiate.
1247 endif # X86_PLATFORM_DEVICES