xref: /openbmc/linux/drivers/platform/x86/Kconfig (revision e15a5365)
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 NEW_LEDS
473	select LEDS_CLASS
474	help
475	  This is a driver for laptops built by Fujitsu:
476
477	    * P2xxx/P5xxx/S6xxx/S7xxx series Lifebooks
478	    * Possibly other Fujitsu laptop models
479	    * Tested with S6410 and S7020
480
481	  It adds support for LCD brightness control and some hotkeys.
482
483	  If you have a Fujitsu laptop, say Y or M here.
484
485config FUJITSU_TABLET
486       tristate "Fujitsu Tablet Extras"
487       depends on ACPI
488       depends on INPUT
489	help
490         This is a driver for tablets built by Fujitsu:
491
492           * Lifebook P1510/P1610/P1620/Txxxx
493           * Stylistic ST5xxx
494           * Possibly other Fujitsu tablet models
495
496         It adds support for the panel buttons, docking station detection,
497         tablet/notebook mode detection for convertible and
498         orientation detection for docked slates.
499
500         If you have a Fujitsu convertible or slate, say Y or M here.
501
502config GPD_POCKET_FAN
503	tristate "GPD Pocket Fan Controller support"
504	depends on ACPI
505	depends on THERMAL
506	help
507	  Driver for the GPD Pocket vendor specific FAN02501 ACPI device
508	  which controls the fan speed on the GPD Pocket.
509
510	  Without this driver the fan on the Pocket will stay off independent
511	  of the CPU temperature. Say Y or M if the kernel may be used on a
512	  GPD pocket.
513
514config HP_ACCEL
515	tristate "HP laptop accelerometer"
516	depends on INPUT && ACPI
517	depends on SERIO_I8042
518	select SENSORS_LIS3LV02D
519	select NEW_LEDS
520	select LEDS_CLASS
521	help
522	  This driver provides support for the "Mobile Data Protection System 3D"
523	  or "3D DriveGuard" feature of HP laptops. On such systems the driver
524	  should load automatically (via ACPI alias).
525
526	  Support for a led indicating disk protection will be provided as
527	  hp::hddprotect. For more information on the feature, refer to
528	  Documentation/misc-devices/lis3lv02d.rst.
529
530	  To compile this driver as a module, choose M here: the module will
531	  be called hp_accel.
532
533config HP_WIRELESS
534	tristate "HP wireless button"
535	depends on ACPI
536	depends on INPUT
537	help
538	 This driver provides supports for new HP wireless button for Windows 8.
539	 On such systems the driver should load automatically (via ACPI alias).
540
541	 To compile this driver as a module, choose M here: the module will
542	 be called hp-wireless.
543
544config HP_WMI
545	tristate "HP WMI extras"
546	depends on ACPI_WMI
547	depends on INPUT
548	depends on RFKILL || RFKILL = n
549	select INPUT_SPARSEKMAP
550	help
551	 Say Y here if you want to support WMI-based hotkeys on HP laptops and
552	 to read data from WMI such as docking or ambient light sensor state.
553
554	 To compile this driver as a module, choose M here: the module will
555	 be called hp-wmi.
556
557config TC1100_WMI
558	tristate "HP Compaq TC1100 Tablet WMI Extras"
559	depends on !X86_64
560	depends on ACPI
561	depends on ACPI_WMI
562	help
563	  This is a driver for the WMI extensions (wireless and bluetooth power
564	  control) of the HP Compaq TC1100 tablet.
565
566config IBM_RTL
567	tristate "Device driver to enable PRTL support"
568	depends on PCI
569	help
570	 Enable support for IBM Premium Real Time Mode (PRTM).
571	 This module will allow you the enter and exit PRTM in the BIOS via
572	 sysfs on platforms that support this feature.  System in PRTM will
573	 not receive CPU-generated SMIs for recoverable errors.  Use of this
574	 feature without proper support may void your hardware warranty.
575
576	 If the proper BIOS support is found the driver will load and create
577	 /sys/devices/system/ibm_rtl/.  The "state" variable will indicate
578	 whether or not the BIOS is in PRTM.
579	 state = 0 (BIOS SMIs on)
580	 state = 1 (BIOS SMIs off)
581
582config IDEAPAD_LAPTOP
583	tristate "Lenovo IdeaPad Laptop Extras"
584	depends on ACPI
585	depends on RFKILL && INPUT
586	depends on SERIO_I8042
587	depends on BACKLIGHT_CLASS_DEVICE
588	depends on ACPI_VIDEO || ACPI_VIDEO = n
589	depends on ACPI_WMI || ACPI_WMI = n
590	select INPUT_SPARSEKMAP
591	help
592	  This is a driver for Lenovo IdeaPad netbooks contains drivers for
593	  rfkill switch, hotkey, fan control and backlight control.
594
595config SENSORS_HDAPS
596	tristate "Thinkpad Hard Drive Active Protection System (hdaps)"
597	depends on INPUT
598	help
599	  This driver provides support for the IBM Hard Drive Active Protection
600	  System (hdaps), which provides an accelerometer and other misc. data.
601	  ThinkPads starting with the R50, T41, and X40 are supported.  The
602	  accelerometer data is readable via sysfs.
603
604	  This driver also provides an absolute input class device, allowing
605	  the laptop to act as a pinball machine-esque joystick.
606
607	  If your ThinkPad is not recognized by the driver, please update to latest
608	  BIOS. This is especially the case for some R52 ThinkPads.
609
610	  Say Y here if you have an applicable laptop and want to experience
611	  the awesome power of hdaps.
612
613config THINKPAD_ACPI
614	tristate "ThinkPad ACPI Laptop Extras"
615	depends on ACPI
616	depends on ACPI_BATTERY
617	depends on INPUT
618	depends on RFKILL || RFKILL = n
619	depends on ACPI_VIDEO || ACPI_VIDEO = n
620	depends on BACKLIGHT_CLASS_DEVICE
621	select HWMON
622	select NVRAM
623	select NEW_LEDS
624	select LEDS_CLASS
625	select LEDS_TRIGGERS
626	select LEDS_TRIGGER_AUDIO
627	help
628	  This is a driver for the IBM and Lenovo ThinkPad laptops. It adds
629	  support for Fn-Fx key combinations, Bluetooth control, video
630	  output switching, ThinkLight control, UltraBay eject and more.
631	  For more information about this driver see
632	  <file:Documentation/admin-guide/laptops/thinkpad-acpi.rst> and
633	  <http://ibm-acpi.sf.net/> .
634
635	  This driver was formerly known as ibm-acpi.
636
637	  Extra functionality will be available if the rfkill (CONFIG_RFKILL)
638	  and/or ALSA (CONFIG_SND) subsystems are available in the kernel.
639	  Note that if you want ThinkPad-ACPI to be built-in instead of
640	  modular, ALSA and rfkill will also have to be built-in.
641
642	  If you have an IBM or Lenovo ThinkPad laptop, say Y or M here.
643
644config THINKPAD_ACPI_ALSA_SUPPORT
645	bool "Console audio control ALSA interface"
646	depends on THINKPAD_ACPI
647	depends on SND
648	depends on SND = y || THINKPAD_ACPI = SND
649	default y
650	help
651	  Enables monitoring of the built-in console audio output control
652	  (headphone and speakers), which is operated by the mute and (in
653	  some ThinkPad models) volume hotkeys.
654
655	  If this option is enabled, ThinkPad-ACPI will export an ALSA card
656	  with a single read-only mixer control, which should be used for
657	  on-screen-display feedback purposes by the Desktop Environment.
658
659	  Optionally, the driver will also allow software control (the
660	  ALSA mixer will be made read-write).  Please refer to the driver
661	  documentation for details.
662
663	  All IBM models have both volume and mute control.  Newer Lenovo
664	  models only have mute control (the volume hotkeys are just normal
665	  keys and volume control is done through the main HDA mixer).
666
667config THINKPAD_ACPI_DEBUGFACILITIES
668	bool "Maintainer debug facilities"
669	depends on THINKPAD_ACPI
670	help
671	  Enables extra stuff in the thinkpad-acpi which is completely useless
672	  for normal use.  Read the driver source to find out what it does.
673
674	  Say N here, unless you were told by a kernel maintainer to do
675	  otherwise.
676
677config THINKPAD_ACPI_DEBUG
678	bool "Verbose debug mode"
679	depends on THINKPAD_ACPI
680	help
681	  Enables extra debugging information, at the expense of a slightly
682	  increase in driver size.
683
684	  If you are not sure, say N here.
685
686config THINKPAD_ACPI_UNSAFE_LEDS
687	bool "Allow control of important LEDs (unsafe)"
688	depends on THINKPAD_ACPI
689	help
690	  Overriding LED state on ThinkPads can mask important
691	  firmware alerts (like critical battery condition), or misled
692	  the user into damaging the hardware (undocking or ejecting
693	  the bay while buses are still active), etc.
694
695	  LED control on the ThinkPad is write-only (with very few
696	  exceptions on very ancient models), which makes it
697	  impossible to know beforehand if important information will
698	  be lost when one changes LED state.
699
700	  Users that know what they are doing can enable this option
701	  and the driver will allow control of every LED, including
702	  the ones on the dock stations.
703
704	  Never enable this option on a distribution kernel.
705
706	  Say N here, unless you are building a kernel for your own
707	  use, and need to control the important firmware LEDs.
708
709config THINKPAD_ACPI_VIDEO
710	bool "Video output control support"
711	depends on THINKPAD_ACPI
712	default y
713	help
714	  Allows the thinkpad_acpi driver to provide an interface to control
715	  the various video output ports.
716
717	  This feature often won't work well, depending on ThinkPad model,
718	  display state, video output devices in use, whether there is a X
719	  server running, phase of the moon, and the current mood of
720	  Schroedinger's cat.  If you can use X.org's RandR to control
721	  your ThinkPad's video output ports instead of this feature,
722	  don't think twice: do it and say N here to save memory and avoid
723	  bad interactions with X.org.
724
725	  NOTE: access to this feature is limited to processes with the
726	  CAP_SYS_ADMIN capability, to avoid local DoS issues in platforms
727	  where it interacts badly with X.org.
728
729	  If you are not sure, say Y here but do try to check if you could
730	  be using X.org RandR instead.
731
732config THINKPAD_ACPI_HOTKEY_POLL
733	bool "Support NVRAM polling for hot keys"
734	depends on THINKPAD_ACPI
735	default y
736	help
737	  Some thinkpad models benefit from NVRAM polling to detect a few of
738	  the hot key press events.  If you know your ThinkPad model does not
739	  need to do NVRAM polling to support any of the hot keys you use,
740	  unselecting this option will save about 1kB of memory.
741
742	  ThinkPads T40 and newer, R52 and newer, and X31 and newer are
743	  unlikely to need NVRAM polling in their latest BIOS versions.
744
745	  NVRAM polling can detect at most the following keys: ThinkPad/Access
746	  IBM, Zoom, Switch Display (fn+F7), ThinkLight, Volume up/down/mute,
747	  Brightness up/down, Display Expand (fn+F8), Hibernate (fn+F12).
748
749	  If you are not sure, say Y here.  The driver enables polling only if
750	  it is strictly necessary to do so.
751
752config INTEL_ATOMISP2_LED
753	tristate "Intel AtomISP2 camera LED driver"
754	depends on GPIOLIB && LEDS_GPIO
755	help
756	  Many Bay Trail and Cherry Trail devices come with a camera attached
757	  to Intel's Image Signal Processor. Linux currently does not have a
758	  driver for these, so they do not work as a camera. Some of these
759	  camera's have a LED which is controlled through a GPIO.
760
761	  Some of these devices have a firmware issue where the LED gets turned
762	  on at boot. This driver will turn the LED off at boot and also allows
763	  controlling the LED (repurposing it) through the sysfs LED interface.
764
765	  Which GPIO is attached to the LED is usually not described in the
766	  ACPI tables, so this driver contains per-system info about the GPIO
767	  inside the driver, this means that this driver only works on systems
768	  the driver knows about.
769
770	  To compile this driver as a module, choose M here: the module
771	  will be called intel_atomisp2_led.
772
773config INTEL_ATOMISP2_PM
774	tristate "Intel AtomISP2 dummy / power-management driver"
775	depends on PCI && IOSF_MBI && PM
776	depends on !INTEL_ATOMISP
777	help
778	  Power-management driver for Intel's Image Signal Processor found on
779	  Bay Trail and Cherry Trail devices. This dummy driver's sole purpose
780	  is to turn the ISP off (put it in D3) to save power and to allow
781	  entering of S0ix modes.
782
783	  To compile this driver as a module, choose M here: the module
784	  will be called intel_atomisp2_pm.
785
786config INTEL_CHT_INT33FE
787	tristate "Intel Cherry Trail ACPI INT33FE Driver"
788	depends on X86 && ACPI && I2C && REGULATOR
789	depends on CHARGER_BQ24190=y || (CHARGER_BQ24190=m && m)
790	depends on USB_ROLES_INTEL_XHCI=y || (USB_ROLES_INTEL_XHCI=m && m)
791	depends on TYPEC_MUX_PI3USB30532=y || (TYPEC_MUX_PI3USB30532=m && m)
792	help
793	  This driver add support for the INT33FE ACPI device found on
794	  some Intel Cherry Trail devices.
795
796	  There are two kinds of INT33FE ACPI device possible: for hardware
797	  with USB Type-C and Micro-B connectors. This driver supports both.
798
799	  The INT33FE ACPI device has a CRS table with I2cSerialBusV2
800	  resources for Fuel Gauge Controller and (in the Type-C variant)
801	  FUSB302 USB Type-C Controller and PI3USB30532 USB switch.
802	  This driver instantiates i2c-clients for these, so that standard
803	  i2c drivers for these chips can bind to the them.
804
805	  If you enable this driver it is advised to also select
806	  CONFIG_BATTERY_BQ27XXX=m or CONFIG_BATTERY_BQ27XXX_I2C=m for Micro-B
807	  device and CONFIG_TYPEC_FUSB302=m and CONFIG_BATTERY_MAX17042=m
808	  for Type-C device.
809
810config INTEL_HID_EVENT
811	tristate "INTEL HID Event"
812	depends on ACPI
813	depends on INPUT
814	select INPUT_SPARSEKMAP
815	help
816	  This driver provides support for the Intel HID Event hotkey interface.
817	  Some laptops require this driver for hotkey support.
818
819	  To compile this driver as a module, choose M here: the module will
820	  be called intel_hid.
821
822config INTEL_INT0002_VGPIO
823	tristate "Intel ACPI INT0002 Virtual GPIO driver"
824	depends on GPIOLIB && ACPI
825	select GPIOLIB_IRQCHIP
826	help
827	  Some peripherals on Bay Trail and Cherry Trail platforms signal a
828	  Power Management Event (PME) to the Power Management Controller (PMC)
829	  to wakeup the system. When this happens software needs to explicitly
830	  clear the PME bus 0 status bit in the GPE0a_STS register to avoid an
831	  IRQ storm on IRQ 9.
832
833	  This is modelled in ACPI through the INT0002 ACPI device, which is
834	  called a "Virtual GPIO controller" in ACPI because it defines the
835	  event handler to call when the PME triggers through _AEI and _L02
836	  methods as would be done for a real GPIO interrupt in ACPI.
837
838	  To compile this driver as a module, choose M here: the module will
839	  be called intel_int0002_vgpio.
840
841config INTEL_MENLOW
842	tristate "Thermal Management driver for Intel menlow platform"
843	depends on ACPI_THERMAL
844	select THERMAL
845	help
846	  ACPI thermal management enhancement driver on
847	  Intel Menlow platform.
848
849	  If unsure, say N.
850
851config INTEL_OAKTRAIL
852	tristate "Intel Oaktrail Platform Extras"
853	depends on ACPI
854	depends on ACPI_VIDEO || ACPI_VIDEO = n
855	depends on RFKILL && BACKLIGHT_CLASS_DEVICE && ACPI
856	help
857	  Intel Oaktrail platform need this driver to provide interfaces to
858	  enable/disable the Camera, WiFi, BT etc. devices. If in doubt, say Y
859	  here; it will only load on supported platforms.
860
861config INTEL_VBTN
862	tristate "INTEL VIRTUAL BUTTON"
863	depends on ACPI
864	depends on INPUT
865	select INPUT_SPARSEKMAP
866	help
867	  This driver provides support for the Intel Virtual Button interface.
868	  Some laptops require this driver for power button support.
869
870	  To compile this driver as a module, choose M here: the module will
871	  be called intel_vbtn.
872
873config SURFACE3_WMI
874	tristate "Surface 3 WMI Driver"
875	depends on ACPI_WMI
876	depends on DMI
877	depends on INPUT
878	depends on SPI
879	help
880	  Say Y here if you have a Surface 3.
881
882	  To compile this driver as a module, choose M here: the module will
883	  be called surface3-wmi.
884
885config SURFACE_3_BUTTON
886	tristate "Power/home/volume buttons driver for Microsoft Surface 3 tablet"
887	depends on ACPI && KEYBOARD_GPIO && I2C
888	help
889	  This driver handles the power/home/volume buttons on the Microsoft Surface 3 tablet.
890
891config SURFACE_3_POWER_OPREGION
892	tristate "Surface 3 battery platform operation region support"
893	depends on ACPI && I2C
894	help
895	  This driver provides support for ACPI operation
896	  region of the Surface 3 battery platform driver.
897
898config SURFACE_PRO3_BUTTON
899	tristate "Power/home/volume buttons driver for Microsoft Surface Pro 3/4 tablet"
900	depends on ACPI && INPUT
901	help
902	  This driver handles the power/home/volume buttons on the Microsoft Surface Pro 3/4 tablet.
903
904config MSI_LAPTOP
905	tristate "MSI Laptop Extras"
906	depends on ACPI
907	depends on BACKLIGHT_CLASS_DEVICE
908	depends on ACPI_VIDEO || ACPI_VIDEO = n
909	depends on RFKILL
910	depends on INPUT && SERIO_I8042
911	select INPUT_SPARSEKMAP
912	help
913	  This is a driver for laptops built by MSI (MICRO-STAR
914	  INTERNATIONAL):
915
916	  MSI MegaBook S270 (MS-1013)
917	  Cytron/TCM/Medion/Tchibo MD96100/SAM2000
918
919	  It adds support for Bluetooth, WLAN and LCD brightness control.
920
921	  More information about this driver is available at
922	  <http://0pointer.de/lennart/tchibo.html>.
923
924	  If you have an MSI S270 laptop, say Y or M here.
925
926config MSI_WMI
927	tristate "MSI WMI extras"
928	depends on ACPI_WMI
929	depends on INPUT
930	depends on BACKLIGHT_CLASS_DEVICE
931	depends on ACPI_VIDEO || ACPI_VIDEO = n
932	select INPUT_SPARSEKMAP
933	help
934	 Say Y here if you want to support WMI-based hotkeys on MSI laptops.
935
936	 To compile this driver as a module, choose M here: the module will
937	 be called msi-wmi.
938
939config XO15_EBOOK
940	tristate "OLPC XO-1.5 ebook switch"
941	depends on OLPC || COMPILE_TEST
942	depends on ACPI && INPUT
943	help
944	  Support for the ebook switch on the OLPC XO-1.5 laptop.
945
946	  This switch is triggered as the screen is rotated and folded down to
947	  convert the device into ebook form.
948
949config XO1_RFKILL
950	tristate "OLPC XO-1 software RF kill switch"
951	depends on OLPC || COMPILE_TEST
952	depends on RFKILL
953	help
954	  Support for enabling/disabling the WLAN interface on the OLPC XO-1
955	  laptop.
956
957config PCENGINES_APU2
958	tristate "PC Engines APUv2/3 front button and LEDs driver"
959	depends on INPUT && INPUT_KEYBOARD && GPIOLIB
960	depends on LEDS_CLASS
961	select GPIO_AMD_FCH
962	select KEYBOARD_GPIO_POLLED
963	select LEDS_GPIO
964	help
965	  This driver provides support for the front button and LEDs on
966	  PC Engines APUv2/APUv3 board.
967
968	  To compile this driver as a module, choose M here: the module
969	  will be called pcengines-apuv2.
970
971config SAMSUNG_LAPTOP
972	tristate "Samsung Laptop driver"
973	depends on RFKILL || RFKILL = n
974	depends on ACPI_VIDEO || ACPI_VIDEO = n
975	depends on BACKLIGHT_CLASS_DEVICE
976	select LEDS_CLASS
977	select NEW_LEDS
978	help
979	  This module implements a driver for a wide range of different
980	  Samsung laptops.  It offers control over the different
981	  function keys, wireless LED, LCD backlight level.
982
983	  It may also provide some sysfs files described in
984	  <file:Documentation/ABI/testing/sysfs-driver-samsung-laptop>
985
986	  To compile this driver as a module, choose M here: the module
987	  will be called samsung-laptop.
988
989config SAMSUNG_Q10
990	tristate "Samsung Q10 Extras"
991	depends on ACPI
992	select BACKLIGHT_CLASS_DEVICE
993	help
994	  This driver provides support for backlight control on Samsung Q10
995	  and related laptops, including Dell Latitude X200.
996
997config ACPI_TOSHIBA
998	tristate "Toshiba Laptop Extras"
999	depends on ACPI
1000	depends on ACPI_WMI
1001	select LEDS_CLASS
1002	select NEW_LEDS
1003	depends on BACKLIGHT_CLASS_DEVICE
1004	depends on INPUT
1005	depends on SERIO_I8042 || SERIO_I8042 = n
1006	depends on ACPI_VIDEO || ACPI_VIDEO = n
1007	depends on RFKILL || RFKILL = n
1008	depends on IIO
1009	select INPUT_SPARSEKMAP
1010	help
1011	  This driver adds support for access to certain system settings
1012	  on "legacy free" Toshiba laptops.  These laptops can be recognized by
1013	  their lack of a BIOS setup menu and APM support.
1014
1015	  On these machines, all system configuration is handled through the
1016	  ACPI.  This driver is required for access to controls not covered
1017	  by the general ACPI drivers, such as LCD brightness, video output,
1018	  etc.
1019
1020	  This driver differs from the non-ACPI Toshiba laptop driver (located
1021	  under "Processor type and features") in several aspects.
1022	  Configuration is accessed by reading and writing text files in the
1023	  /proc tree instead of by program interface to /dev.  Furthermore, no
1024	  power management functions are exposed, as those are handled by the
1025	  general ACPI drivers.
1026
1027	  More information about this driver is available at
1028	  <http://memebeam.org/toys/ToshibaAcpiDriver>.
1029
1030	  If you have a legacy free Toshiba laptop (such as the Libretto L1
1031	  series), say Y.
1032
1033config TOSHIBA_BT_RFKILL
1034	tristate "Toshiba Bluetooth RFKill switch support"
1035	depends on ACPI
1036	depends on RFKILL || RFKILL = n
1037	help
1038	  This driver adds support for Bluetooth events for the RFKill
1039	  switch on modern Toshiba laptops with full ACPI support and
1040	  an RFKill switch.
1041
1042	  This driver handles RFKill events for the TOS6205 Bluetooth,
1043	  and re-enables it when the switch is set back to the 'on'
1044	  position.
1045
1046	  If you have a modern Toshiba laptop with a Bluetooth and an
1047	  RFKill switch (such as the Portege R500), say Y.
1048
1049config TOSHIBA_HAPS
1050	tristate "Toshiba HDD Active Protection Sensor"
1051	depends on ACPI
1052	help
1053	  This driver adds support for the built-in accelerometer
1054	  found on recent Toshiba laptops equipped with HID TOS620A
1055	  device.
1056
1057	  This driver receives ACPI notify events 0x80 when the sensor
1058	  detects a sudden move or a harsh vibration, as well as an
1059	  ACPI notify event 0x81 whenever the movement or vibration has
1060	  been stabilized.
1061
1062	  Also provides sysfs entries to get/set the desired protection
1063	  level and resetting the HDD protection interface.
1064
1065	  If you have a recent Toshiba laptop with a built-in accelerometer
1066	  device, say Y.
1067
1068config TOSHIBA_WMI
1069	tristate "Toshiba WMI Hotkeys Driver (EXPERIMENTAL)"
1070	depends on ACPI_WMI
1071	depends on INPUT
1072	select INPUT_SPARSEKMAP
1073	help
1074	  This driver adds hotkey monitoring support to some Toshiba models
1075	  that manage the hotkeys via WMI events.
1076
1077	  WARNING: This driver is incomplete as it lacks a proper keymap and the
1078	  *notify function only prints the ACPI event type value. Be warned that
1079	  you will need to provide some information if you have a Toshiba model
1080	  with WMI event hotkeys and want to help with the development of this
1081	  driver.
1082
1083	  If you have a WMI-based hotkeys Toshiba laptop, say Y or M here.
1084
1085config ACPI_CMPC
1086	tristate "CMPC Laptop Extras"
1087	depends on ACPI && INPUT
1088	depends on RFKILL || RFKILL=n
1089	select BACKLIGHT_CLASS_DEVICE
1090	help
1091	  Support for Intel Classmate PC ACPI devices, including some
1092	  keys as input device, backlight device, tablet and accelerometer
1093	  devices.
1094
1095config COMPAL_LAPTOP
1096	tristate "Compal (and others) Laptop Extras"
1097	depends on ACPI
1098	depends on BACKLIGHT_CLASS_DEVICE
1099	depends on ACPI_VIDEO || ACPI_VIDEO = n
1100	depends on RFKILL
1101	depends on HWMON
1102	depends on POWER_SUPPLY
1103	help
1104	  This is a driver for laptops built by Compal, and some models by
1105	  other brands (e.g. Dell, Toshiba).
1106
1107	  It adds support for rfkill, Bluetooth, WLAN, LCD brightness, hwmon
1108	  and battery charging level control.
1109
1110config LG_LAPTOP
1111	tristate "LG Laptop Extras"
1112	depends on ACPI
1113	depends on ACPI_WMI
1114	depends on INPUT
1115	select INPUT_SPARSEKMAP
1116	select NEW_LEDS
1117	select LEDS_CLASS
1118	help
1119	 This driver adds support for hotkeys as well as control of keyboard
1120	 backlight, battery maximum charge level and various other ACPI
1121	 features.
1122
1123	 If you have an LG Gram laptop, say Y or M here.
1124
1125config PANASONIC_LAPTOP
1126	tristate "Panasonic Laptop Extras"
1127	depends on INPUT && ACPI
1128	depends on BACKLIGHT_CLASS_DEVICE
1129	select INPUT_SPARSEKMAP
1130	help
1131	  This driver adds support for access to backlight control and hotkeys
1132	  on Panasonic Let's Note laptops.
1133
1134	  If you have a Panasonic Let's note laptop (such as the R1(N variant),
1135	  R2, R3, R5, T2, W2 and Y2 series), say Y.
1136
1137config SONY_LAPTOP
1138	tristate "Sony Laptop Extras"
1139	depends on ACPI
1140	depends on ACPI_VIDEO || ACPI_VIDEO = n
1141	depends on BACKLIGHT_CLASS_DEVICE
1142	depends on INPUT
1143	depends on RFKILL
1144	help
1145	  This mini-driver drives the SNC and SPIC devices present in the ACPI
1146	  BIOS of the Sony Vaio laptops.
1147
1148	  It gives access to some extra laptop functionalities like Bluetooth,
1149	  screen brightness control, Fn keys and allows powering on/off some
1150	  devices.
1151
1152	  Read <file:Documentation/admin-guide/laptops/sony-laptop.rst> for more information.
1153
1154config SONYPI_COMPAT
1155	bool "Sonypi compatibility"
1156	depends on SONY_LAPTOP
1157	help
1158	  Build the sonypi driver compatibility code into the sony-laptop driver.
1159
1160config SYSTEM76_ACPI
1161	tristate "System76 ACPI Driver"
1162	depends on ACPI
1163	select NEW_LEDS
1164	select LEDS_CLASS
1165	select LEDS_TRIGGERS
1166	help
1167	  This is a driver for System76 laptops running open firmware. It adds
1168	  support for Fn-Fx key combinations, keyboard backlight, and airplane mode
1169	  LEDs.
1170
1171	  If you have a System76 laptop running open firmware, say Y or M here.
1172
1173config TOPSTAR_LAPTOP
1174	tristate "Topstar Laptop Extras"
1175	depends on ACPI
1176	depends on INPUT
1177	select INPUT_SPARSEKMAP
1178	select LEDS_CLASS
1179	select NEW_LEDS
1180	help
1181	  This driver adds support for hotkeys found on Topstar laptops.
1182
1183	  If you have a Topstar laptop, say Y or M here.
1184
1185config I2C_MULTI_INSTANTIATE
1186	tristate "I2C multi instantiate pseudo device driver"
1187	depends on I2C && ACPI
1188	help
1189	  Some ACPI-based systems list multiple i2c-devices in a single ACPI
1190	  firmware-node. This driver will instantiate separate i2c-clients
1191	  for each device in the firmware-node.
1192
1193	  To compile this driver as a module, choose M here: the module
1194	  will be called i2c-multi-instantiate.
1195
1196config MLX_PLATFORM
1197	tristate "Mellanox Technologies platform support"
1198	depends on I2C && REGMAP
1199	help
1200	  This option enables system support for the Mellanox Technologies
1201	  platform. The Mellanox systems provide data center networking
1202	  solutions based on Virtual Protocol Interconnect (VPI) technology
1203	  enable seamless connectivity to 56/100Gb/s InfiniBand or 10/40/56GbE
1204	  connection.
1205
1206	  If you have a Mellanox system, say Y or M here.
1207
1208config TOUCHSCREEN_DMI
1209	bool "DMI based touchscreen configuration info"
1210	depends on ACPI && DMI && I2C=y && TOUCHSCREEN_SILEAD
1211	select EFI_EMBEDDED_FIRMWARE if EFI
1212	help
1213	  Certain ACPI based tablets with e.g. Silead or Chipone touchscreens
1214	  do not have enough data in ACPI tables for the touchscreen driver to
1215	  handle the touchscreen properly, as OEMs expect the data to be baked
1216	  into the tablet model specific version of the driver shipped with the
1217	  the OS-image for the device. This option supplies the missing info.
1218	  Enable this for x86 tablets with Silead or Chipone touchscreens.
1219
1220config INTEL_IMR
1221	bool "Intel Isolated Memory Region support"
1222	depends on X86_INTEL_QUARK && IOSF_MBI
1223	help
1224	  This option provides a means to manipulate Isolated Memory Regions.
1225	  IMRs are a set of registers that define read and write access masks
1226	  to prohibit certain system agents from accessing memory with 1 KiB
1227	  granularity.
1228
1229	  IMRs make it possible to control read/write access to an address
1230	  by hardware agents inside the SoC. Read and write masks can be
1231	  defined for:
1232		- eSRAM flush
1233		- Dirty CPU snoop (write only)
1234		- RMU access
1235		- PCI Virtual Channel 0/Virtual Channel 1
1236		- SMM mode
1237		- Non SMM mode
1238
1239	  Quark contains a set of eight IMR registers and makes use of those
1240	  registers during its bootup process.
1241
1242	  If you are running on a Galileo/Quark say Y here.
1243
1244config INTEL_IPS
1245	tristate "Intel Intelligent Power Sharing"
1246	depends on ACPI && PCI
1247	help
1248	  Intel Calpella platforms support dynamic power sharing between the
1249	  CPU and GPU, maximizing performance in a given TDP.  This driver,
1250	  along with the CPU frequency and i915 drivers, provides that
1251	  functionality.  If in doubt, say Y here; it will only load on
1252	  supported platforms.
1253
1254config INTEL_RST
1255        tristate "Intel Rapid Start Technology Driver"
1256	depends on ACPI
1257	help
1258	  This driver provides support for modifying parameters on systems
1259	  equipped with Intel's Rapid Start Technology. When put in an ACPI
1260	  sleep state, these devices will wake after either a configured
1261	  timeout or when the system battery reaches a critical state,
1262	  automatically copying memory contents to disk. On resume, the
1263	  firmware will copy the memory contents back to RAM and resume the OS
1264	  as usual.
1265
1266config INTEL_SMARTCONNECT
1267        tristate "Intel Smart Connect disabling driver"
1268	depends on ACPI
1269	help
1270	  Intel Smart Connect is a technology intended to permit devices to
1271	  update state by resuming for a short period of time at regular
1272	  intervals. If a user enables this functionality under Windows and
1273	  then reboots into Linux, the system may remain configured to resume
1274	  on suspend. In the absence of any userspace to support it, the system
1275	  will then remain awake until something triggers another suspend.
1276
1277	  This driver checks to determine whether the device has Intel Smart
1278	  Connect enabled, and if so disables it.
1279
1280source "drivers/platform/x86/intel_speed_select_if/Kconfig"
1281
1282config INTEL_TURBO_MAX_3
1283	bool "Intel Turbo Boost Max Technology 3.0 enumeration driver"
1284	depends on X86_64 && SCHED_MC_PRIO
1285	help
1286	  This driver reads maximum performance ratio of each CPU and set up
1287	  the scheduler priority metrics. In this way scheduler can prefer
1288	  CPU with higher performance to schedule tasks.
1289	  This driver is only required when the system is not using Hardware
1290	  P-States (HWP). In HWP mode, priority can be read from ACPI tables.
1291
1292config INTEL_UNCORE_FREQ_CONTROL
1293	tristate "Intel Uncore frequency control driver"
1294	depends on X86_64
1295	help
1296	  This driver allows control of uncore frequency limits on
1297	  supported server platforms.
1298	  Uncore frequency controls RING/LLC (last-level cache) clocks.
1299
1300	  To compile this driver as a module, choose M here: the module
1301	  will be called intel-uncore-frequency.
1302
1303config INTEL_BXTWC_PMIC_TMU
1304	tristate "Intel BXT Whiskey Cove TMU Driver"
1305	depends on REGMAP
1306	depends on MFD_INTEL_PMC_BXT
1307	depends on INTEL_SOC_PMIC_BXTWC
1308	help
1309	  Select this driver to use Intel BXT Whiskey Cove PMIC TMU feature.
1310	  This driver enables the alarm wakeup functionality in the TMU unit
1311	  of Whiskey Cove PMIC.
1312
1313config INTEL_CHTDC_TI_PWRBTN
1314	tristate "Intel Cherry Trail Dollar Cove TI power button driver"
1315	depends on INTEL_SOC_PMIC_CHTDC_TI
1316	depends on INPUT
1317	help
1318	  This option adds a power button driver driver for Dollar Cove TI
1319	  PMIC on Intel Cherry Trail devices.
1320
1321	  To compile this driver as a module, choose M here: the module
1322	  will be called intel_chtdc_ti_pwrbtn.
1323
1324config INTEL_MFLD_THERMAL
1325       tristate "Thermal driver for Intel Medfield platform"
1326       depends on MFD_INTEL_MSIC && THERMAL
1327       help
1328         Say Y here to enable thermal driver support for the  Intel Medfield
1329         platform.
1330
1331config INTEL_MID_POWER_BUTTON
1332	tristate "power button driver for Intel MID platforms"
1333	depends on INTEL_SCU && INPUT
1334	help
1335	  This driver handles the power button on the Intel MID platforms.
1336
1337	  If unsure, say N.
1338
1339config INTEL_MRFLD_PWRBTN
1340	tristate "Intel Merrifield Basin Cove power button driver"
1341	depends on INTEL_SOC_PMIC_MRFLD
1342	depends on INPUT
1343	help
1344	  This option adds a power button driver for Basin Cove PMIC
1345	  on Intel Merrifield devices.
1346
1347	  To compile this driver as a module, choose M here: the module
1348	  will be called intel_mrfld_pwrbtn.
1349
1350config INTEL_PMC_CORE
1351	tristate "Intel PMC Core driver"
1352	depends on PCI
1353	help
1354	  The Intel Platform Controller Hub for Intel Core SoCs provides access
1355	  to Power Management Controller registers via a PCI interface. This
1356	  driver can utilize debugging capabilities and supported features as
1357	  exposed by the Power Management Controller.
1358
1359	  Supported features:
1360		- SLP_S0_RESIDENCY counter
1361		- PCH IP Power Gating status
1362		- LTR Ignore
1363		- MPHY/PLL gating status (Sunrisepoint PCH only)
1364
1365config INTEL_PUNIT_IPC
1366	tristate "Intel P-Unit IPC Driver"
1367	help
1368	  This driver provides support for Intel P-Unit Mailbox IPC mechanism,
1369	  which is used to bridge the communications between kernel and P-Unit.
1370
1371config INTEL_SCU_IPC
1372	bool
1373
1374config INTEL_SCU
1375	bool
1376	select INTEL_SCU_IPC
1377
1378config INTEL_SCU_PCI
1379	bool "Intel SCU PCI driver"
1380	depends on PCI
1381	select INTEL_SCU
1382	help
1383	  This driver is used to bridge the communications between kernel
1384	  and SCU on some embedded Intel x86 platforms. It also creates
1385	  devices that are connected to the SoC through the SCU.
1386	  Platforms supported:
1387	    Medfield
1388	    Clovertrail
1389	    Merrifield
1390	    Broxton
1391	    Apollo Lake
1392
1393config INTEL_SCU_PLATFORM
1394	tristate "Intel SCU platform driver"
1395	depends on ACPI
1396	select INTEL_SCU
1397	help
1398	  This driver is used to bridge the communications between kernel
1399	  and SCU (sometimes called PMC as well). The driver currently
1400	  supports Intel Elkhart Lake and compatible platforms.
1401
1402config INTEL_SCU_IPC_UTIL
1403	tristate "Intel SCU IPC utility driver"
1404	depends on INTEL_SCU
1405	help
1406	  The IPC Util driver provides an interface with the SCU enabling
1407	  low level access for debug work and updating the firmware. Say
1408	  N unless you will be doing this on an Intel MID platform.
1409
1410config INTEL_TELEMETRY
1411	tristate "Intel SoC Telemetry Driver"
1412	depends on X86_64
1413	depends on MFD_INTEL_PMC_BXT
1414	depends on INTEL_PUNIT_IPC
1415	help
1416	  This driver provides interfaces to configure and use
1417	  telemetry for INTEL SoC from APL onwards. It is also
1418	  used to get various SoC events and parameters
1419	  directly via debugfs files. Various tools may use
1420	  this interface for SoC state monitoring.
1421
1422endif # X86_PLATFORM_DEVICES
1423
1424config PMC_ATOM
1425       def_bool y
1426       depends on PCI
1427       select COMMON_CLK
1428