Kconfig 41 KB

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