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