1# SPDX-License-Identifier: GPL-2.0-only 2# 3# X86 Platform Specific Drivers 4# 5 6menuconfig X86_PLATFORM_DEVICES 7 bool "X86 Platform Specific Device Drivers" 8 default y 9 depends on X86 10 help 11 Say Y here to get to see options for device drivers for various 12 x86 platforms, including vendor-specific laptop extension drivers. 13 This option alone does not add any kernel code. 14 15 If you say N, all options in this submenu will be skipped and disabled. 16 17if X86_PLATFORM_DEVICES 18 19config ACPI_WMI 20 tristate "WMI" 21 depends on ACPI 22 help 23 This driver adds support for the ACPI-WMI (Windows Management 24 Instrumentation) mapper device (PNP0C14) found on some systems. 25 26 ACPI-WMI is a proprietary extension to ACPI to expose parts of the 27 ACPI firmware to userspace - this is done through various vendor 28 defined methods and data blocks in a PNP0C14 device, which are then 29 made available for userspace to call. 30 31 The implementation of this in Linux currently only exposes this to 32 other kernel space drivers. 33 34 This driver is a required dependency to build the firmware specific 35 drivers needed on many machines, including Acer and HP laptops. 36 37 It is safe to enable this driver even if your DSDT doesn't define 38 any ACPI-WMI devices. 39 40config WMI_BMOF 41 tristate "WMI embedded Binary MOF driver" 42 depends on ACPI_WMI 43 default ACPI_WMI 44 help 45 Say Y here if you want to be able to read a firmware-embedded 46 WMI Binary MOF data. Using this requires userspace tools and may be 47 rather tedious. 48 49 To compile this driver as a module, choose M here: the module will 50 be called wmi-bmof. 51 52config HUAWEI_WMI 53 tristate "Huawei WMI laptop extras driver" 54 depends on ACPI_BATTERY 55 depends on ACPI_WMI 56 depends on INPUT 57 select INPUT_SPARSEKMAP 58 select LEDS_CLASS 59 select LEDS_TRIGGERS 60 select LEDS_TRIGGER_AUDIO 61 select NEW_LEDS 62 help 63 This driver provides support for Huawei WMI hotkeys, battery charge 64 control, fn-lock, mic-mute LED, and other extra features. 65 66 To compile this driver as a module, choose M here: the module 67 will be called huawei-wmi. 68 69config UV_SYSFS 70 tristate "Sysfs structure for UV systems" 71 depends on X86_UV 72 depends on SYSFS 73 help 74 This driver supports a sysfs tree describing information about 75 UV systems at /sys/firmware/sgi_uv/. 76 77 To compile this driver as a module, choose M here: the module will 78 be called uv_sysfs. 79 80config INTEL_WMI_SBL_FW_UPDATE 81 tristate "Intel WMI Slim Bootloader firmware update signaling driver" 82 depends on ACPI_WMI 83 help 84 Say Y here if you want to be able to use the WMI interface to signal 85 Slim Bootloader to trigger update on next reboot. 86 87 To compile this driver as a module, choose M here: the module will 88 be called intel-wmi-sbl-fw-update. 89 90config INTEL_WMI_THUNDERBOLT 91 tristate "Intel WMI thunderbolt force power driver" 92 depends on ACPI_WMI 93 help 94 Say Y here if you want to be able to use the WMI interface on select 95 systems to force the power control of Intel Thunderbolt controllers. 96 This is useful for updating the firmware when devices are not plugged 97 into the controller. 98 99 To compile this driver as a module, choose M here: the module will 100 be called intel-wmi-thunderbolt. 101 102config MXM_WMI 103 tristate "WMI support for MXM Laptop Graphics" 104 depends on ACPI_WMI 105 help 106 MXM is a standard for laptop graphics cards, the WMI interface 107 is required for switchable nvidia graphics machines 108 109config PEAQ_WMI 110 tristate "PEAQ 2-in-1 WMI hotkey driver" 111 depends on ACPI_WMI 112 depends on INPUT 113 help 114 Say Y here if you want to support WMI-based hotkeys on PEAQ 2-in-1s. 115 116config XIAOMI_WMI 117 tristate "Xiaomi WMI key driver" 118 depends on ACPI_WMI 119 depends on INPUT 120 help 121 Say Y here if you want to support WMI-based keys on Xiaomi notebooks. 122 123 To compile this driver as a module, choose M here: the module will 124 be called xiaomi-wmi. 125 126config ACERHDF 127 tristate "Acer Aspire One temperature and fan driver" 128 depends on ACPI && THERMAL 129 select THERMAL_GOV_BANG_BANG 130 help 131 This is a driver for Acer Aspire One netbooks. It allows to access 132 the temperature sensor and to control the fan. 133 134 After loading this driver the BIOS is still in control of the fan. 135 To let the kernel handle the fan, do: 136 echo -n enabled > /sys/class/thermal/thermal_zoneN/mode 137 where N=0,1,2... depending on the number of thermal nodes and the 138 detection order of your particular system. The "type" parameter 139 in the same node directory will tell you if it is "acerhdf". 140 141 For more information about this driver see 142 <https://piie.net/files/acerhdf_README.txt> 143 144 If you have an Acer Aspire One netbook, say Y or M 145 here. 146 147config ACER_WIRELESS 148 tristate "Acer Wireless Radio Control Driver" 149 depends on ACPI 150 depends on INPUT 151 help 152 The Acer Wireless Radio Control handles the airplane mode hotkey 153 present on new Acer laptops. 154 155 Say Y or M here if you have an Acer notebook with an airplane mode 156 hotkey. 157 158 If you choose to compile this driver as a module the module will be 159 called acer-wireless. 160 161config ACER_WMI 162 tristate "Acer WMI Laptop Extras" 163 depends on ACPI 164 select LEDS_CLASS 165 select NEW_LEDS 166 depends on BACKLIGHT_CLASS_DEVICE 167 depends on SERIO_I8042 168 depends on INPUT 169 depends on RFKILL || RFKILL = n 170 depends on ACPI_WMI 171 select INPUT_SPARSEKMAP 172 # Acer WMI depends on ACPI_VIDEO when ACPI is enabled 173 select ACPI_VIDEO if ACPI 174 help 175 This is a driver for newer Acer (and Wistron) laptops. It adds 176 wireless radio and bluetooth control, and on some laptops, 177 exposes the mail LED and LCD backlight. 178 179 If you have an ACPI-WMI compatible Acer/ Wistron laptop, say Y or M 180 here. 181 182config AMD_PMC 183 tristate "AMD SoC PMC driver" 184 depends on ACPI && PCI 185 help 186 The driver provides support for AMD Power Management Controller 187 primarily responsible for S2Idle transactions that are driven from 188 a platform firmware running on SMU. This driver also provides a debug 189 mechanism to investigate the S2Idle transactions and failures. 190 191 Say Y or M here if you have a notebook powered by AMD RYZEN CPU/APU. 192 193 If you choose to compile this driver as a module the module will be 194 called amd-pmc. 195 196config APPLE_GMUX 197 tristate "Apple Gmux Driver" 198 depends on ACPI && PCI 199 depends on PNP 200 depends on BACKLIGHT_CLASS_DEVICE 201 depends on BACKLIGHT_APPLE=n || BACKLIGHT_APPLE 202 depends on ACPI_VIDEO=n || ACPI_VIDEO 203 help 204 This driver provides support for the gmux device found on many 205 Apple laptops, which controls the display mux for the hybrid 206 graphics as well as the backlight. Currently only backlight 207 control is supported by the driver. 208 209config ASUS_LAPTOP 210 tristate "Asus Laptop Extras" 211 depends on ACPI 212 select LEDS_CLASS 213 select NEW_LEDS 214 depends on BACKLIGHT_CLASS_DEVICE 215 depends on INPUT 216 depends on RFKILL || RFKILL = n 217 depends on ACPI_VIDEO || ACPI_VIDEO = n 218 select INPUT_SPARSEKMAP 219 help 220 This is a driver for Asus laptops, Lenovo SL and the Pegatron 221 Lucid tablet. It may also support some MEDION, JVC or VICTOR 222 laptops. It makes all the extra buttons generate standard 223 ACPI events and input events, and on the Lucid the built-in 224 accelerometer appears as an input device. It also adds 225 support for video output switching, LCD backlight control, 226 Bluetooth and Wlan control, and most importantly, allows you 227 to blink those fancy LEDs. 228 229 For more information see <http://acpi4asus.sf.net>. 230 231 If you have an ACPI-compatible ASUS laptop, say Y or M here. 232 233config ASUS_WIRELESS 234 tristate "Asus Wireless Radio Control Driver" 235 depends on ACPI 236 depends on INPUT 237 select NEW_LEDS 238 select LEDS_CLASS 239 help 240 The Asus Wireless Radio Control handles the airplane mode hotkey 241 present on some Asus laptops. 242 243 Say Y or M here if you have an ASUS notebook with an airplane mode 244 hotkey. 245 246 If you choose to compile this driver as a module the module will be 247 called asus-wireless. 248 249config ASUS_WMI 250 tristate "ASUS WMI Driver" 251 depends on ACPI_WMI 252 depends on ACPI_BATTERY 253 depends on INPUT 254 depends on HWMON 255 depends on BACKLIGHT_CLASS_DEVICE 256 depends on RFKILL || RFKILL = n 257 depends on HOTPLUG_PCI 258 depends on ACPI_VIDEO || ACPI_VIDEO = n 259 select INPUT_SPARSEKMAP 260 select LEDS_CLASS 261 select NEW_LEDS 262 help 263 Say Y here if you have a WMI aware Asus laptop (like Eee PCs or new 264 Asus Notebooks). 265 266 To compile this driver as a module, choose M here: the module will 267 be called asus-wmi. 268 269config ASUS_NB_WMI 270 tristate "Asus Notebook WMI Driver" 271 depends on ASUS_WMI 272 depends on SERIO_I8042 || SERIO_I8042 = n 273 help 274 This is a driver for newer Asus notebooks. It adds extra features 275 like wireless radio and bluetooth control, leds, hotkeys, backlight... 276 277 For more information, see 278 <file:Documentation/ABI/testing/sysfs-platform-asus-wmi> 279 280 If you have an ACPI-WMI compatible Asus Notebook, say Y or M 281 here. 282 283config EEEPC_LAPTOP 284 tristate "Eee PC Hotkey Driver" 285 depends on ACPI 286 depends on INPUT 287 depends on RFKILL || RFKILL = n 288 depends on ACPI_VIDEO || ACPI_VIDEO = n 289 depends on HOTPLUG_PCI 290 depends on BACKLIGHT_CLASS_DEVICE 291 select HWMON 292 select LEDS_CLASS 293 select NEW_LEDS 294 select INPUT_SPARSEKMAP 295 help 296 This driver supports the Fn-Fx keys on Eee PC laptops. 297 298 It also gives access to some extra laptop functionalities like 299 Bluetooth, backlight and allows powering on/off some other 300 devices. 301 302 If you have an Eee PC laptop, say Y or M here. If this driver 303 doesn't work on your Eee PC, try eeepc-wmi instead. 304 305config EEEPC_WMI 306 tristate "Eee PC WMI Driver" 307 depends on ASUS_WMI 308 help 309 This is a driver for newer Eee PC laptops. It adds extra features 310 like wireless radio and bluetooth control, leds, hotkeys, backlight... 311 312 For more information, see 313 <file:Documentation/ABI/testing/sysfs-platform-asus-wmi> 314 315 If you have an ACPI-WMI compatible Eee PC laptop (>= 1000), say Y or M 316 here. 317 318source "drivers/platform/x86/dell/Kconfig" 319 320config AMILO_RFKILL 321 tristate "Fujitsu-Siemens Amilo rfkill support" 322 depends on RFKILL 323 depends on SERIO_I8042 324 help 325 This is a driver for enabling wifi on some Fujitsu-Siemens Amilo 326 laptops. 327 328config FUJITSU_LAPTOP 329 tristate "Fujitsu Laptop Extras" 330 depends on ACPI 331 depends on INPUT 332 depends on BACKLIGHT_CLASS_DEVICE 333 depends on ACPI_VIDEO || ACPI_VIDEO = n 334 select INPUT_SPARSEKMAP 335 select NEW_LEDS 336 select LEDS_CLASS 337 help 338 This is a driver for laptops built by Fujitsu: 339 340 * P2xxx/P5xxx/S6xxx/S7xxx series Lifebooks 341 * Possibly other Fujitsu laptop models 342 * Tested with S6410 and S7020 343 344 It adds support for LCD brightness control and some hotkeys. 345 346 If you have a Fujitsu laptop, say Y or M here. 347 348config FUJITSU_TABLET 349 tristate "Fujitsu Tablet Extras" 350 depends on ACPI 351 depends on INPUT 352 help 353 This is a driver for tablets built by Fujitsu: 354 355 * Lifebook P1510/P1610/P1620/Txxxx 356 * Stylistic ST5xxx 357 * Possibly other Fujitsu tablet models 358 359 It adds support for the panel buttons, docking station detection, 360 tablet/notebook mode detection for convertible and 361 orientation detection for docked slates. 362 363 If you have a Fujitsu convertible or slate, say Y or M here. 364 365config GPD_POCKET_FAN 366 tristate "GPD Pocket Fan Controller support" 367 depends on ACPI 368 depends on THERMAL 369 help 370 Driver for the GPD Pocket vendor specific FAN02501 ACPI device 371 which controls the fan speed on the GPD Pocket. 372 373 Without this driver the fan on the Pocket will stay off independent 374 of the CPU temperature. Say Y or M if the kernel may be used on a 375 GPD pocket. 376 377config HP_ACCEL 378 tristate "HP laptop accelerometer" 379 depends on INPUT && ACPI 380 depends on SERIO_I8042 381 select SENSORS_LIS3LV02D 382 select NEW_LEDS 383 select LEDS_CLASS 384 help 385 This driver provides support for the "Mobile Data Protection System 3D" 386 or "3D DriveGuard" feature of HP laptops. On such systems the driver 387 should load automatically (via ACPI alias). 388 389 Support for a led indicating disk protection will be provided as 390 hp::hddprotect. For more information on the feature, refer to 391 Documentation/misc-devices/lis3lv02d.rst. 392 393 To compile this driver as a module, choose M here: the module will 394 be called hp_accel. 395 396config HP_WIRELESS 397 tristate "HP wireless button" 398 depends on ACPI 399 depends on INPUT 400 help 401 This driver provides supports for new HP wireless button for Windows 8. 402 On such systems the driver should load automatically (via ACPI alias). 403 404 To compile this driver as a module, choose M here: the module will 405 be called hp-wireless. 406 407config HP_WMI 408 tristate "HP WMI extras" 409 depends on ACPI_WMI 410 depends on INPUT 411 depends on RFKILL || RFKILL = n 412 select INPUT_SPARSEKMAP 413 help 414 Say Y here if you want to support WMI-based hotkeys on HP laptops and 415 to read data from WMI such as docking or ambient light sensor state. 416 417 To compile this driver as a module, choose M here: the module will 418 be called hp-wmi. 419 420config TC1100_WMI 421 tristate "HP Compaq TC1100 Tablet WMI Extras" 422 depends on !X86_64 423 depends on ACPI 424 depends on ACPI_WMI 425 help 426 This is a driver for the WMI extensions (wireless and bluetooth power 427 control) of the HP Compaq TC1100 tablet. 428 429config IBM_RTL 430 tristate "Device driver to enable PRTL support" 431 depends on PCI 432 help 433 Enable support for IBM Premium Real Time Mode (PRTM). 434 This module will allow you the enter and exit PRTM in the BIOS via 435 sysfs on platforms that support this feature. System in PRTM will 436 not receive CPU-generated SMIs for recoverable errors. Use of this 437 feature without proper support may void your hardware warranty. 438 439 If the proper BIOS support is found the driver will load and create 440 /sys/devices/system/ibm_rtl/. The "state" variable will indicate 441 whether or not the BIOS is in PRTM. 442 state = 0 (BIOS SMIs on) 443 state = 1 (BIOS SMIs off) 444 445config IDEAPAD_LAPTOP 446 tristate "Lenovo IdeaPad Laptop Extras" 447 depends on ACPI 448 depends on RFKILL && INPUT 449 depends on SERIO_I8042 450 depends on BACKLIGHT_CLASS_DEVICE 451 depends on ACPI_VIDEO || ACPI_VIDEO = n 452 depends on ACPI_WMI || ACPI_WMI = n 453 select ACPI_PLATFORM_PROFILE 454 select INPUT_SPARSEKMAP 455 select NEW_LEDS 456 select LEDS_CLASS 457 help 458 This is a driver for Lenovo IdeaPad netbooks contains drivers for 459 rfkill switch, hotkey, fan control and backlight control. 460 461config SENSORS_HDAPS 462 tristate "Thinkpad Hard Drive Active Protection System (hdaps)" 463 depends on INPUT 464 help 465 This driver provides support for the IBM Hard Drive Active Protection 466 System (hdaps), which provides an accelerometer and other misc. data. 467 ThinkPads starting with the R50, T41, and X40 are supported. The 468 accelerometer data is readable via sysfs. 469 470 This driver also provides an absolute input class device, allowing 471 the laptop to act as a pinball machine-esque joystick. 472 473 If your ThinkPad is not recognized by the driver, please update to latest 474 BIOS. This is especially the case for some R52 ThinkPads. 475 476 Say Y here if you have an applicable laptop and want to experience 477 the awesome power of hdaps. 478 479config THINKPAD_ACPI 480 tristate "ThinkPad ACPI Laptop Extras" 481 depends on ACPI 482 depends on ACPI_BATTERY 483 depends on INPUT 484 depends on RFKILL || RFKILL = n 485 depends on ACPI_VIDEO || ACPI_VIDEO = n 486 depends on BACKLIGHT_CLASS_DEVICE 487 select ACPI_PLATFORM_PROFILE 488 select HWMON 489 select NVRAM 490 select NEW_LEDS 491 select LEDS_CLASS 492 select LEDS_TRIGGERS 493 select LEDS_TRIGGER_AUDIO 494 help 495 This is a driver for the IBM and Lenovo ThinkPad laptops. It adds 496 support for Fn-Fx key combinations, Bluetooth control, video 497 output switching, ThinkLight control, UltraBay eject and more. 498 For more information about this driver see 499 <file:Documentation/admin-guide/laptops/thinkpad-acpi.rst> and 500 <http://ibm-acpi.sf.net/> . 501 502 This driver was formerly known as ibm-acpi. 503 504 Extra functionality will be available if the rfkill (CONFIG_RFKILL) 505 and/or ALSA (CONFIG_SND) subsystems are available in the kernel. 506 Note that if you want ThinkPad-ACPI to be built-in instead of 507 modular, ALSA and rfkill will also have to be built-in. 508 509 If you have an IBM or Lenovo ThinkPad laptop, say Y or M here. 510 511config THINKPAD_ACPI_ALSA_SUPPORT 512 bool "Console audio control ALSA interface" 513 depends on THINKPAD_ACPI 514 depends on SND 515 depends on SND = y || THINKPAD_ACPI = SND 516 default y 517 help 518 Enables monitoring of the built-in console audio output control 519 (headphone and speakers), which is operated by the mute and (in 520 some ThinkPad models) volume hotkeys. 521 522 If this option is enabled, ThinkPad-ACPI will export an ALSA card 523 with a single read-only mixer control, which should be used for 524 on-screen-display feedback purposes by the Desktop Environment. 525 526 Optionally, the driver will also allow software control (the 527 ALSA mixer will be made read-write). Please refer to the driver 528 documentation for details. 529 530 All IBM models have both volume and mute control. Newer Lenovo 531 models only have mute control (the volume hotkeys are just normal 532 keys and volume control is done through the main HDA mixer). 533 534config THINKPAD_ACPI_DEBUGFACILITIES 535 bool "Maintainer debug facilities" 536 depends on THINKPAD_ACPI 537 help 538 Enables extra stuff in the thinkpad-acpi which is completely useless 539 for normal use. Read the driver source to find out what it does. 540 541 Say N here, unless you were told by a kernel maintainer to do 542 otherwise. 543 544config THINKPAD_ACPI_DEBUG 545 bool "Verbose debug mode" 546 depends on THINKPAD_ACPI 547 help 548 Enables extra debugging information, at the expense of a slightly 549 increase in driver size. 550 551 If you are not sure, say N here. 552 553config THINKPAD_ACPI_UNSAFE_LEDS 554 bool "Allow control of important LEDs (unsafe)" 555 depends on THINKPAD_ACPI 556 help 557 Overriding LED state on ThinkPads can mask important 558 firmware alerts (like critical battery condition), or misled 559 the user into damaging the hardware (undocking or ejecting 560 the bay while buses are still active), etc. 561 562 LED control on the ThinkPad is write-only (with very few 563 exceptions on very ancient models), which makes it 564 impossible to know beforehand if important information will 565 be lost when one changes LED state. 566 567 Users that know what they are doing can enable this option 568 and the driver will allow control of every LED, including 569 the ones on the dock stations. 570 571 Never enable this option on a distribution kernel. 572 573 Say N here, unless you are building a kernel for your own 574 use, and need to control the important firmware LEDs. 575 576config THINKPAD_ACPI_VIDEO 577 bool "Video output control support" 578 depends on THINKPAD_ACPI 579 default y 580 help 581 Allows the thinkpad_acpi driver to provide an interface to control 582 the various video output ports. 583 584 This feature often won't work well, depending on ThinkPad model, 585 display state, video output devices in use, whether there is a X 586 server running, phase of the moon, and the current mood of 587 Schroedinger's cat. If you can use X.org's RandR to control 588 your ThinkPad's video output ports instead of this feature, 589 don't think twice: do it and say N here to save memory and avoid 590 bad interactions with X.org. 591 592 NOTE: access to this feature is limited to processes with the 593 CAP_SYS_ADMIN capability, to avoid local DoS issues in platforms 594 where it interacts badly with X.org. 595 596 If you are not sure, say Y here but do try to check if you could 597 be using X.org RandR instead. 598 599config THINKPAD_ACPI_HOTKEY_POLL 600 bool "Support NVRAM polling for hot keys" 601 depends on THINKPAD_ACPI 602 default y 603 help 604 Some thinkpad models benefit from NVRAM polling to detect a few of 605 the hot key press events. If you know your ThinkPad model does not 606 need to do NVRAM polling to support any of the hot keys you use, 607 unselecting this option will save about 1kB of memory. 608 609 ThinkPads T40 and newer, R52 and newer, and X31 and newer are 610 unlikely to need NVRAM polling in their latest BIOS versions. 611 612 NVRAM polling can detect at most the following keys: ThinkPad/Access 613 IBM, Zoom, Switch Display (fn+F7), ThinkLight, Volume up/down/mute, 614 Brightness up/down, Display Expand (fn+F8), Hibernate (fn+F12). 615 616 If you are not sure, say Y here. The driver enables polling only if 617 it is strictly necessary to do so. 618 619config INTEL_ATOMISP2_LED 620 tristate "Intel AtomISP2 camera LED driver" 621 depends on GPIOLIB && LEDS_GPIO 622 help 623 Many Bay Trail and Cherry Trail devices come with a camera attached 624 to Intel's Image Signal Processor. Linux currently does not have a 625 driver for these, so they do not work as a camera. Some of these 626 camera's have a LED which is controlled through a GPIO. 627 628 Some of these devices have a firmware issue where the LED gets turned 629 on at boot. This driver will turn the LED off at boot and also allows 630 controlling the LED (repurposing it) through the sysfs LED interface. 631 632 Which GPIO is attached to the LED is usually not described in the 633 ACPI tables, so this driver contains per-system info about the GPIO 634 inside the driver, this means that this driver only works on systems 635 the driver knows about. 636 637 To compile this driver as a module, choose M here: the module 638 will be called intel_atomisp2_led. 639 640config INTEL_ATOMISP2_PM 641 tristate "Intel AtomISP2 dummy / power-management driver" 642 depends on PCI && IOSF_MBI && PM 643 depends on !INTEL_ATOMISP 644 help 645 Power-management driver for Intel's Image Signal Processor found on 646 Bay Trail and Cherry Trail devices. This dummy driver's sole purpose 647 is to turn the ISP off (put it in D3) to save power and to allow 648 entering of S0ix modes. 649 650 To compile this driver as a module, choose M here: the module 651 will be called intel_atomisp2_pm. 652 653config INTEL_CHT_INT33FE 654 tristate "Intel Cherry Trail ACPI INT33FE Driver" 655 depends on X86 && ACPI && I2C && REGULATOR 656 depends on CHARGER_BQ24190=y || (CHARGER_BQ24190=m && m) 657 depends on USB_ROLES_INTEL_XHCI=y || (USB_ROLES_INTEL_XHCI=m && m) 658 depends on TYPEC_MUX_PI3USB30532=y || (TYPEC_MUX_PI3USB30532=m && m) 659 help 660 This driver add support for the INT33FE ACPI device found on 661 some Intel Cherry Trail devices. 662 663 There are two kinds of INT33FE ACPI device possible: for hardware 664 with USB Type-C and Micro-B connectors. This driver supports both. 665 666 The INT33FE ACPI device has a CRS table with I2cSerialBusV2 667 resources for Fuel Gauge Controller and (in the Type-C variant) 668 FUSB302 USB Type-C Controller and PI3USB30532 USB switch. 669 This driver instantiates i2c-clients for these, so that standard 670 i2c drivers for these chips can bind to the them. 671 672 If you enable this driver it is advised to also select 673 CONFIG_BATTERY_BQ27XXX=m or CONFIG_BATTERY_BQ27XXX_I2C=m for Micro-B 674 device and CONFIG_TYPEC_FUSB302=m and CONFIG_BATTERY_MAX17042=m 675 for Type-C device. 676 677config INTEL_HID_EVENT 678 tristate "INTEL HID Event" 679 depends on ACPI 680 depends on INPUT 681 select INPUT_SPARSEKMAP 682 help 683 This driver provides support for the Intel HID Event hotkey interface. 684 Some laptops require this driver for hotkey support. 685 686 To compile this driver as a module, choose M here: the module will 687 be called intel_hid. 688 689config INTEL_INT0002_VGPIO 690 tristate "Intel ACPI INT0002 Virtual GPIO driver" 691 depends on GPIOLIB && ACPI 692 select GPIOLIB_IRQCHIP 693 help 694 Some peripherals on Bay Trail and Cherry Trail platforms signal a 695 Power Management Event (PME) to the Power Management Controller (PMC) 696 to wakeup the system. When this happens software needs to explicitly 697 clear the PME bus 0 status bit in the GPE0a_STS register to avoid an 698 IRQ storm on IRQ 9. 699 700 This is modelled in ACPI through the INT0002 ACPI device, which is 701 called a "Virtual GPIO controller" in ACPI because it defines the 702 event handler to call when the PME triggers through _AEI and _L02 703 methods as would be done for a real GPIO interrupt in ACPI. 704 705 To compile this driver as a module, choose M here: the module will 706 be called intel_int0002_vgpio. 707 708config INTEL_MENLOW 709 tristate "Thermal Management driver for Intel menlow platform" 710 depends on ACPI_THERMAL 711 select THERMAL 712 help 713 ACPI thermal management enhancement driver on 714 Intel Menlow platform. 715 716 If unsure, say N. 717 718config INTEL_OAKTRAIL 719 tristate "Intel Oaktrail Platform Extras" 720 depends on ACPI 721 depends on ACPI_VIDEO || ACPI_VIDEO = n 722 depends on RFKILL && BACKLIGHT_CLASS_DEVICE && ACPI 723 help 724 Intel Oaktrail platform need this driver to provide interfaces to 725 enable/disable the Camera, WiFi, BT etc. devices. If in doubt, say Y 726 here; it will only load on supported platforms. 727 728config INTEL_VBTN 729 tristate "INTEL VIRTUAL BUTTON" 730 depends on ACPI 731 depends on INPUT 732 select INPUT_SPARSEKMAP 733 help 734 This driver provides support for the Intel Virtual Button interface. 735 Some laptops require this driver for power button support. 736 737 To compile this driver as a module, choose M here: the module will 738 be called intel_vbtn. 739 740config MSI_LAPTOP 741 tristate "MSI Laptop Extras" 742 depends on ACPI 743 depends on BACKLIGHT_CLASS_DEVICE 744 depends on ACPI_VIDEO || ACPI_VIDEO = n 745 depends on RFKILL 746 depends on INPUT && SERIO_I8042 747 select INPUT_SPARSEKMAP 748 help 749 This is a driver for laptops built by MSI (MICRO-STAR 750 INTERNATIONAL): 751 752 MSI MegaBook S270 (MS-1013) 753 Cytron/TCM/Medion/Tchibo MD96100/SAM2000 754 755 It adds support for Bluetooth, WLAN and LCD brightness control. 756 757 More information about this driver is available at 758 <http://0pointer.de/lennart/tchibo.html>. 759 760 If you have an MSI S270 laptop, say Y or M here. 761 762config MSI_WMI 763 tristate "MSI WMI extras" 764 depends on ACPI_WMI 765 depends on INPUT 766 depends on BACKLIGHT_CLASS_DEVICE 767 depends on ACPI_VIDEO || ACPI_VIDEO = n 768 select INPUT_SPARSEKMAP 769 help 770 Say Y here if you want to support WMI-based hotkeys on MSI laptops. 771 772 To compile this driver as a module, choose M here: the module will 773 be called msi-wmi. 774 775config XO15_EBOOK 776 tristate "OLPC XO-1.5 ebook switch" 777 depends on OLPC || COMPILE_TEST 778 depends on ACPI && INPUT 779 help 780 Support for the ebook switch on the OLPC XO-1.5 laptop. 781 782 This switch is triggered as the screen is rotated and folded down to 783 convert the device into ebook form. 784 785config XO1_RFKILL 786 tristate "OLPC XO-1 software RF kill switch" 787 depends on OLPC || COMPILE_TEST 788 depends on RFKILL 789 help 790 Support for enabling/disabling the WLAN interface on the OLPC XO-1 791 laptop. 792 793config PCENGINES_APU2 794 tristate "PC Engines APUv2/3 front button and LEDs driver" 795 depends on INPUT && INPUT_KEYBOARD && GPIOLIB 796 depends on LEDS_CLASS 797 select GPIO_AMD_FCH 798 select KEYBOARD_GPIO_POLLED 799 select LEDS_GPIO 800 help 801 This driver provides support for the front button and LEDs on 802 PC Engines APUv2/APUv3 board. 803 804 To compile this driver as a module, choose M here: the module 805 will be called pcengines-apuv2. 806 807config SAMSUNG_LAPTOP 808 tristate "Samsung Laptop driver" 809 depends on RFKILL || RFKILL = n 810 depends on ACPI_VIDEO || ACPI_VIDEO = n 811 depends on BACKLIGHT_CLASS_DEVICE 812 select LEDS_CLASS 813 select NEW_LEDS 814 help 815 This module implements a driver for a wide range of different 816 Samsung laptops. It offers control over the different 817 function keys, wireless LED, LCD backlight level. 818 819 It may also provide some sysfs files described in 820 <file:Documentation/ABI/testing/sysfs-driver-samsung-laptop> 821 822 To compile this driver as a module, choose M here: the module 823 will be called samsung-laptop. 824 825config SAMSUNG_Q10 826 tristate "Samsung Q10 Extras" 827 depends on ACPI 828 select BACKLIGHT_CLASS_DEVICE 829 help 830 This driver provides support for backlight control on Samsung Q10 831 and related laptops, including Dell Latitude X200. 832 833config ACPI_TOSHIBA 834 tristate "Toshiba Laptop Extras" 835 depends on ACPI 836 depends on ACPI_WMI 837 select LEDS_CLASS 838 select NEW_LEDS 839 depends on BACKLIGHT_CLASS_DEVICE 840 depends on INPUT 841 depends on SERIO_I8042 || SERIO_I8042 = n 842 depends on ACPI_VIDEO || ACPI_VIDEO = n 843 depends on RFKILL || RFKILL = n 844 depends on IIO 845 select INPUT_SPARSEKMAP 846 help 847 This driver adds support for access to certain system settings 848 on "legacy free" Toshiba laptops. These laptops can be recognized by 849 their lack of a BIOS setup menu and APM support. 850 851 On these machines, all system configuration is handled through the 852 ACPI. This driver is required for access to controls not covered 853 by the general ACPI drivers, such as LCD brightness, video output, 854 etc. 855 856 This driver differs from the non-ACPI Toshiba laptop driver (located 857 under "Processor type and features") in several aspects. 858 Configuration is accessed by reading and writing text files in the 859 /proc tree instead of by program interface to /dev. Furthermore, no 860 power management functions are exposed, as those are handled by the 861 general ACPI drivers. 862 863 More information about this driver is available at 864 <http://memebeam.org/toys/ToshibaAcpiDriver>. 865 866 If you have a legacy free Toshiba laptop (such as the Libretto L1 867 series), say Y. 868 869config TOSHIBA_BT_RFKILL 870 tristate "Toshiba Bluetooth RFKill switch support" 871 depends on ACPI 872 depends on RFKILL || RFKILL = n 873 help 874 This driver adds support for Bluetooth events for the RFKill 875 switch on modern Toshiba laptops with full ACPI support and 876 an RFKill switch. 877 878 This driver handles RFKill events for the TOS6205 Bluetooth, 879 and re-enables it when the switch is set back to the 'on' 880 position. 881 882 If you have a modern Toshiba laptop with a Bluetooth and an 883 RFKill switch (such as the Portege R500), say Y. 884 885config TOSHIBA_HAPS 886 tristate "Toshiba HDD Active Protection Sensor" 887 depends on ACPI 888 help 889 This driver adds support for the built-in accelerometer 890 found on recent Toshiba laptops equipped with HID TOS620A 891 device. 892 893 This driver receives ACPI notify events 0x80 when the sensor 894 detects a sudden move or a harsh vibration, as well as an 895 ACPI notify event 0x81 whenever the movement or vibration has 896 been stabilized. 897 898 Also provides sysfs entries to get/set the desired protection 899 level and resetting the HDD protection interface. 900 901 If you have a recent Toshiba laptop with a built-in accelerometer 902 device, say Y. 903 904config TOSHIBA_WMI 905 tristate "Toshiba WMI Hotkeys Driver (EXPERIMENTAL)" 906 depends on ACPI_WMI 907 depends on INPUT 908 select INPUT_SPARSEKMAP 909 help 910 This driver adds hotkey monitoring support to some Toshiba models 911 that manage the hotkeys via WMI events. 912 913 WARNING: This driver is incomplete as it lacks a proper keymap and the 914 *notify function only prints the ACPI event type value. Be warned that 915 you will need to provide some information if you have a Toshiba model 916 with WMI event hotkeys and want to help with the development of this 917 driver. 918 919 If you have a WMI-based hotkeys Toshiba laptop, say Y or M here. 920 921config ACPI_CMPC 922 tristate "CMPC Laptop Extras" 923 depends on ACPI && INPUT 924 depends on RFKILL || RFKILL=n 925 select BACKLIGHT_CLASS_DEVICE 926 help 927 Support for Intel Classmate PC ACPI devices, including some 928 keys as input device, backlight device, tablet and accelerometer 929 devices. 930 931config COMPAL_LAPTOP 932 tristate "Compal (and others) Laptop Extras" 933 depends on ACPI 934 depends on BACKLIGHT_CLASS_DEVICE 935 depends on ACPI_VIDEO || ACPI_VIDEO = n 936 depends on RFKILL 937 depends on HWMON 938 depends on POWER_SUPPLY 939 help 940 This is a driver for laptops built by Compal, and some models by 941 other brands (e.g. Dell, Toshiba). 942 943 It adds support for rfkill, Bluetooth, WLAN, LCD brightness, hwmon 944 and battery charging level control. 945 946config LG_LAPTOP 947 tristate "LG Laptop Extras" 948 depends on ACPI 949 depends on ACPI_WMI 950 depends on INPUT 951 select INPUT_SPARSEKMAP 952 select NEW_LEDS 953 select LEDS_CLASS 954 help 955 This driver adds support for hotkeys as well as control of keyboard 956 backlight, battery maximum charge level and various other ACPI 957 features. 958 959 If you have an LG Gram laptop, say Y or M here. 960 961config PANASONIC_LAPTOP 962 tristate "Panasonic Laptop Extras" 963 depends on INPUT && ACPI 964 depends on BACKLIGHT_CLASS_DEVICE 965 select INPUT_SPARSEKMAP 966 help 967 This driver adds support for access to backlight control and hotkeys 968 on Panasonic Let's Note laptops. 969 970 If you have a Panasonic Let's note laptop (such as the R1(N variant), 971 R2, R3, R5, T2, W2 and Y2 series), say Y. 972 973config SONY_LAPTOP 974 tristate "Sony Laptop Extras" 975 depends on ACPI 976 depends on ACPI_VIDEO || ACPI_VIDEO = n 977 depends on BACKLIGHT_CLASS_DEVICE 978 depends on INPUT 979 depends on RFKILL 980 help 981 This mini-driver drives the SNC and SPIC devices present in the ACPI 982 BIOS of the Sony Vaio laptops. 983 984 It gives access to some extra laptop functionalities like Bluetooth, 985 screen brightness control, Fn keys and allows powering on/off some 986 devices. 987 988 Read <file:Documentation/admin-guide/laptops/sony-laptop.rst> for more information. 989 990config SONYPI_COMPAT 991 bool "Sonypi compatibility" 992 depends on SONY_LAPTOP 993 help 994 Build the sonypi driver compatibility code into the sony-laptop driver. 995 996config SYSTEM76_ACPI 997 tristate "System76 ACPI Driver" 998 depends on ACPI 999 select NEW_LEDS 1000 select LEDS_CLASS 1001 select LEDS_TRIGGERS 1002 help 1003 This is a driver for System76 laptops running open firmware. It adds 1004 support for Fn-Fx key combinations, keyboard backlight, and airplane mode 1005 LEDs. 1006 1007 If you have a System76 laptop running open firmware, say Y or M here. 1008 1009config TOPSTAR_LAPTOP 1010 tristate "Topstar Laptop Extras" 1011 depends on ACPI 1012 depends on INPUT 1013 select INPUT_SPARSEKMAP 1014 select LEDS_CLASS 1015 select NEW_LEDS 1016 help 1017 This driver adds support for hotkeys found on Topstar laptops. 1018 1019 If you have a Topstar laptop, say Y or M here. 1020 1021config I2C_MULTI_INSTANTIATE 1022 tristate "I2C multi instantiate pseudo device driver" 1023 depends on I2C && ACPI 1024 help 1025 Some ACPI-based systems list multiple i2c-devices in a single ACPI 1026 firmware-node. This driver will instantiate separate i2c-clients 1027 for each device in the firmware-node. 1028 1029 To compile this driver as a module, choose M here: the module 1030 will be called i2c-multi-instantiate. 1031 1032config MLX_PLATFORM 1033 tristate "Mellanox Technologies platform support" 1034 depends on I2C && REGMAP 1035 help 1036 This option enables system support for the Mellanox Technologies 1037 platform. The Mellanox systems provide data center networking 1038 solutions based on Virtual Protocol Interconnect (VPI) technology 1039 enable seamless connectivity to 56/100Gb/s InfiniBand or 10/40/56GbE 1040 connection. 1041 1042 If you have a Mellanox system, say Y or M here. 1043 1044config TOUCHSCREEN_DMI 1045 bool "DMI based touchscreen configuration info" 1046 depends on ACPI && DMI && I2C=y && TOUCHSCREEN_SILEAD 1047 select EFI_EMBEDDED_FIRMWARE if EFI 1048 help 1049 Certain ACPI based tablets with e.g. Silead or Chipone touchscreens 1050 do not have enough data in ACPI tables for the touchscreen driver to 1051 handle the touchscreen properly, as OEMs expect the data to be baked 1052 into the tablet model specific version of the driver shipped with the 1053 the OS-image for the device. This option supplies the missing info. 1054 Enable this for x86 tablets with Silead or Chipone touchscreens. 1055 1056config INTEL_IMR 1057 bool "Intel Isolated Memory Region support" 1058 depends on X86_INTEL_QUARK && IOSF_MBI 1059 help 1060 This option provides a means to manipulate Isolated Memory Regions. 1061 IMRs are a set of registers that define read and write access masks 1062 to prohibit certain system agents from accessing memory with 1 KiB 1063 granularity. 1064 1065 IMRs make it possible to control read/write access to an address 1066 by hardware agents inside the SoC. Read and write masks can be 1067 defined for: 1068 - eSRAM flush 1069 - Dirty CPU snoop (write only) 1070 - RMU access 1071 - PCI Virtual Channel 0/Virtual Channel 1 1072 - SMM mode 1073 - Non SMM mode 1074 1075 Quark contains a set of eight IMR registers and makes use of those 1076 registers during its bootup process. 1077 1078 If you are running on a Galileo/Quark say Y here. 1079 1080config INTEL_IPS 1081 tristate "Intel Intelligent Power Sharing" 1082 depends on ACPI && PCI 1083 help 1084 Intel Calpella platforms support dynamic power sharing between the 1085 CPU and GPU, maximizing performance in a given TDP. This driver, 1086 along with the CPU frequency and i915 drivers, provides that 1087 functionality. If in doubt, say Y here; it will only load on 1088 supported platforms. 1089 1090config INTEL_RST 1091 tristate "Intel Rapid Start Technology Driver" 1092 depends on ACPI 1093 help 1094 This driver provides support for modifying parameters on systems 1095 equipped with Intel's Rapid Start Technology. When put in an ACPI 1096 sleep state, these devices will wake after either a configured 1097 timeout or when the system battery reaches a critical state, 1098 automatically copying memory contents to disk. On resume, the 1099 firmware will copy the memory contents back to RAM and resume the OS 1100 as usual. 1101 1102config INTEL_SMARTCONNECT 1103 tristate "Intel Smart Connect disabling driver" 1104 depends on ACPI 1105 help 1106 Intel Smart Connect is a technology intended to permit devices to 1107 update state by resuming for a short period of time at regular 1108 intervals. If a user enables this functionality under Windows and 1109 then reboots into Linux, the system may remain configured to resume 1110 on suspend. In the absence of any userspace to support it, the system 1111 will then remain awake until something triggers another suspend. 1112 1113 This driver checks to determine whether the device has Intel Smart 1114 Connect enabled, and if so disables it. 1115 1116source "drivers/platform/x86/intel_speed_select_if/Kconfig" 1117 1118config INTEL_TURBO_MAX_3 1119 bool "Intel Turbo Boost Max Technology 3.0 enumeration driver" 1120 depends on X86_64 && SCHED_MC_PRIO 1121 help 1122 This driver reads maximum performance ratio of each CPU and set up 1123 the scheduler priority metrics. In this way scheduler can prefer 1124 CPU with higher performance to schedule tasks. 1125 This driver is only required when the system is not using Hardware 1126 P-States (HWP). In HWP mode, priority can be read from ACPI tables. 1127 1128config INTEL_UNCORE_FREQ_CONTROL 1129 tristate "Intel Uncore frequency control driver" 1130 depends on X86_64 1131 help 1132 This driver allows control of uncore frequency limits on 1133 supported server platforms. 1134 Uncore frequency controls RING/LLC (last-level cache) clocks. 1135 1136 To compile this driver as a module, choose M here: the module 1137 will be called intel-uncore-frequency. 1138 1139config INTEL_BXTWC_PMIC_TMU 1140 tristate "Intel BXT Whiskey Cove TMU Driver" 1141 depends on REGMAP 1142 depends on MFD_INTEL_PMC_BXT 1143 depends on INTEL_SOC_PMIC_BXTWC 1144 help 1145 Select this driver to use Intel BXT Whiskey Cove PMIC TMU feature. 1146 This driver enables the alarm wakeup functionality in the TMU unit 1147 of Whiskey Cove PMIC. 1148 1149config INTEL_CHTDC_TI_PWRBTN 1150 tristate "Intel Cherry Trail Dollar Cove TI power button driver" 1151 depends on INTEL_SOC_PMIC_CHTDC_TI 1152 depends on INPUT 1153 help 1154 This option adds a power button driver driver for Dollar Cove TI 1155 PMIC on Intel Cherry Trail devices. 1156 1157 To compile this driver as a module, choose M here: the module 1158 will be called intel_chtdc_ti_pwrbtn. 1159 1160config INTEL_MRFLD_PWRBTN 1161 tristate "Intel Merrifield Basin Cove power button driver" 1162 depends on INTEL_SOC_PMIC_MRFLD 1163 depends on INPUT 1164 help 1165 This option adds a power button driver for Basin Cove PMIC 1166 on Intel Merrifield devices. 1167 1168 To compile this driver as a module, choose M here: the module 1169 will be called intel_mrfld_pwrbtn. 1170 1171config INTEL_PMC_CORE 1172 tristate "Intel PMC Core driver" 1173 depends on PCI 1174 help 1175 The Intel Platform Controller Hub for Intel Core SoCs provides access 1176 to Power Management Controller registers via a PCI interface. This 1177 driver can utilize debugging capabilities and supported features as 1178 exposed by the Power Management Controller. 1179 1180 Supported features: 1181 - SLP_S0_RESIDENCY counter 1182 - PCH IP Power Gating status 1183 - LTR Ignore 1184 - MPHY/PLL gating status (Sunrisepoint PCH only) 1185 1186config INTEL_PMT_CLASS 1187 tristate 1188 help 1189 The Intel Platform Monitoring Technology (PMT) class driver provides 1190 the basic sysfs interface and file hierarchy uses by PMT devices. 1191 1192 For more information, see: 1193 <file:Documentation/ABI/testing/sysfs-class-intel_pmt> 1194 1195 To compile this driver as a module, choose M here: the module 1196 will be called intel_pmt_class. 1197 1198config INTEL_PMT_TELEMETRY 1199 tristate "Intel Platform Monitoring Technology (PMT) Telemetry driver" 1200 depends on MFD_INTEL_PMT 1201 select INTEL_PMT_CLASS 1202 help 1203 The Intel Platform Monitory Technology (PMT) Telemetry driver provides 1204 access to hardware telemetry metrics on devices that support the 1205 feature. 1206 1207 To compile this driver as a module, choose M here: the module 1208 will be called intel_pmt_telemetry. 1209 1210config INTEL_PMT_CRASHLOG 1211 tristate "Intel Platform Monitoring Technology (PMT) Crashlog driver" 1212 depends on MFD_INTEL_PMT 1213 select INTEL_PMT_CLASS 1214 help 1215 The Intel Platform Monitoring Technology (PMT) crashlog driver provides 1216 access to hardware crashlog capabilities on devices that support the 1217 feature. 1218 1219 To compile this driver as a module, choose M here: the module 1220 will be called intel_pmt_crashlog. 1221 1222config INTEL_PUNIT_IPC 1223 tristate "Intel P-Unit IPC Driver" 1224 help 1225 This driver provides support for Intel P-Unit Mailbox IPC mechanism, 1226 which is used to bridge the communications between kernel and P-Unit. 1227 1228config INTEL_SCU_IPC 1229 bool 1230 1231config INTEL_SCU 1232 bool 1233 select INTEL_SCU_IPC 1234 1235config INTEL_SCU_PCI 1236 bool "Intel SCU PCI driver" 1237 depends on PCI 1238 select INTEL_SCU 1239 help 1240 This driver is used to bridge the communications between kernel 1241 and SCU on some embedded Intel x86 platforms. It also creates 1242 devices that are connected to the SoC through the SCU. 1243 Platforms supported: 1244 Medfield 1245 Clovertrail 1246 Merrifield 1247 Broxton 1248 Apollo Lake 1249 1250config INTEL_SCU_PLATFORM 1251 tristate "Intel SCU platform driver" 1252 depends on ACPI 1253 select INTEL_SCU 1254 help 1255 This driver is used to bridge the communications between kernel 1256 and SCU (sometimes called PMC as well). The driver currently 1257 supports Intel Elkhart Lake and compatible platforms. 1258 1259config INTEL_SCU_WDT 1260 bool 1261 default INTEL_SCU_PCI 1262 depends on INTEL_MID_WATCHDOG 1263 help 1264 This is a specific platform code to instantiate watchdog device 1265 on ACPI-based Intel MID platforms. 1266 1267config INTEL_SCU_IPC_UTIL 1268 tristate "Intel SCU IPC utility driver" 1269 depends on INTEL_SCU 1270 help 1271 The IPC Util driver provides an interface with the SCU enabling 1272 low level access for debug work and updating the firmware. Say 1273 N unless you will be doing this on an Intel MID platform. 1274 1275config INTEL_TELEMETRY 1276 tristate "Intel SoC Telemetry Driver" 1277 depends on X86_64 1278 depends on MFD_INTEL_PMC_BXT 1279 depends on INTEL_PUNIT_IPC 1280 help 1281 This driver provides interfaces to configure and use 1282 telemetry for INTEL SoC from APL onwards. It is also 1283 used to get various SoC events and parameters 1284 directly via debugfs files. Various tools may use 1285 this interface for SoC state monitoring. 1286 1287endif # X86_PLATFORM_DEVICES 1288 1289config PMC_ATOM 1290 def_bool y 1291 depends on PCI 1292 select COMMON_CLK 1293