1# SPDX-License-Identifier: GPL-2.0-only
2#
3# Intel x86 Platform Specific Drivers
4#
5
6source "drivers/platform/x86/intel/atomisp2/Kconfig"
7source "drivers/platform/x86/intel/ifs/Kconfig"
8source "drivers/platform/x86/intel/int1092/Kconfig"
9source "drivers/platform/x86/intel/int3472/Kconfig"
10source "drivers/platform/x86/intel/pmc/Kconfig"
11source "drivers/platform/x86/intel/pmt/Kconfig"
12source "drivers/platform/x86/intel/speed_select_if/Kconfig"
13source "drivers/platform/x86/intel/telemetry/Kconfig"
14source "drivers/platform/x86/intel/wmi/Kconfig"
15source "drivers/platform/x86/intel/uncore-frequency/Kconfig"
16
17
18config INTEL_HID_EVENT
19	tristate "Intel HID Event"
20	depends on ACPI
21	depends on INPUT
22	depends on I2C
23	select INPUT_SPARSEKMAP
24	help
25	  This driver provides support for the Intel HID Event hotkey interface.
26	  Some laptops require this driver for hotkey support.
27
28	  To compile this driver as a module, choose M here: the module will
29	  be called intel_hid.
30
31config INTEL_VBTN
32	tristate "Intel Virtual Button"
33	depends on ACPI
34	depends on INPUT
35	depends on I2C
36	select INPUT_SPARSEKMAP
37	help
38	  This driver provides support for the Intel Virtual Button interface.
39	  Some laptops require this driver for power button support.
40
41	  To compile this driver as a module, choose M here: the module will
42	  be called intel_vbtn.
43
44config INTEL_INT0002_VGPIO
45	tristate "Intel ACPI INT0002 Virtual GPIO driver"
46	depends on GPIOLIB && ACPI && PM_SLEEP
47	select GPIOLIB_IRQCHIP
48	help
49	  Some peripherals on Bay Trail and Cherry Trail platforms signal a
50	  Power Management Event (PME) to the Power Management Controller (PMC)
51	  to wakeup the system. When this happens software needs to explicitly
52	  clear the PME bus 0 status bit in the GPE0a_STS register to avoid an
53	  IRQ storm on IRQ 9.
54
55	  This is modelled in ACPI through the INT0002 ACPI device, which is
56	  called a "Virtual GPIO controller" in ACPI because it defines the
57	  event handler to call when the PME triggers through _AEI and _L02
58	  methods as would be done for a real GPIO interrupt in ACPI.
59
60	  To compile this driver as a module, choose M here: the module will
61	  be called intel_int0002_vgpio.
62
63config INTEL_OAKTRAIL
64	tristate "Intel Oaktrail Platform Extras"
65	depends on ACPI
66	depends on ACPI_VIDEO || ACPI_VIDEO=n
67	depends on RFKILL && BACKLIGHT_CLASS_DEVICE && ACPI
68	help
69	  Intel Oaktrail platform need this driver to provide interfaces to
70	  enable/disable the Camera, WiFi, BT etc. devices. If in doubt, say Y
71	  here; it will only load on supported platforms.
72
73config INTEL_BXTWC_PMIC_TMU
74	tristate "Intel Broxton Whiskey Cove TMU Driver"
75	depends on INTEL_SOC_PMIC_BXTWC
76	depends on MFD_INTEL_PMC_BXT
77	select REGMAP
78	help
79	  Select this driver to use Intel Broxton Whiskey Cove PMIC TMU feature.
80	  This driver enables the alarm wakeup functionality in the TMU unit of
81	  Whiskey Cove PMIC.
82
83config INTEL_CHTDC_TI_PWRBTN
84	tristate "Intel Cherry Trail Dollar Cove TI power button driver"
85	depends on INTEL_SOC_PMIC_CHTDC_TI
86	depends on INPUT
87	help
88	  This option adds a power button driver for Dollar Cove TI
89	  PMIC on Intel Cherry Trail devices.
90
91	  To compile this driver as a module, choose M here: the module
92	  will be called intel_chtdc_ti_pwrbtn.
93
94config INTEL_CHTWC_INT33FE
95	tristate "Intel Cherry Trail Whiskey Cove ACPI INT33FE Driver"
96	depends on X86 && ACPI && I2C && REGULATOR
97	depends on CHARGER_BQ24190=y || (CHARGER_BQ24190=m && m)
98	depends on USB_ROLES_INTEL_XHCI=y || (USB_ROLES_INTEL_XHCI=m && m)
99	depends on TYPEC_MUX_PI3USB30532=y || (TYPEC_MUX_PI3USB30532=m && m)
100	help
101	  This driver add support for the Intel Cherry Trail Whiskey Cove
102	  INT33FE ACPI device found on the GPD win and the GPD pocket.
103
104	  The INT33FE ACPI device on these mini laptops contains I2cSerialBusV2
105	  resources for a MAX17042 Fuel Gauge, FUSB302 USB Type-C Controller
106	  and PI3USB30532 USB switch.
107	  This driver instantiates i2c-clients for these, so that standard
108	  i2c drivers for these chips can bind to the them.
109
110	  If you enable this driver it is advised to also select
111	  CONFIG_TYPEC_FUSB302=m, CONFIG_TYPEC_MUX_PI3USB30532=m and
112	  CONFIG_BATTERY_MAX17042=m.
113
114config INTEL_ISHTP_ECLITE
115	tristate "Intel ISHTP eclite controller Driver"
116	depends on INTEL_ISH_HID
117	depends on ACPI
118	help
119	  This driver is for accessing the PSE (Programmable Service Engine) -
120	  an Embedded Controller like IP - using ISHTP (Integrated Sensor Hub
121	  Transport Protocol) to get battery, thermal and UCSI (USB Type-C
122	  Connector System Software Interface) related data from the platform.
123	  Users who don't want to use discrete Embedded Controller on Intel's
124	  Elkhartlake platform can leverage this integrated solution of
125	  ECLite which is part of PSE subsystem.
126
127	  To compile this driver as a module, choose M here: the module
128	  will be called intel_ishtp_eclite.
129
130config INTEL_MRFLD_PWRBTN
131	tristate "Intel Merrifield Basin Cove power button driver"
132	depends on INTEL_SOC_PMIC_MRFLD
133	depends on INPUT
134	help
135	  This option adds a power button driver for Basin Cove PMIC
136	  on Intel Merrifield devices.
137
138	  To compile this driver as a module, choose M here: the module
139	  will be called intel_mrfld_pwrbtn.
140
141config INTEL_PUNIT_IPC
142	tristate "Intel P-Unit IPC Driver"
143	help
144	  This driver provides support for Intel P-Unit Mailbox IPC mechanism,
145	  which is used to bridge the communications between kernel and P-Unit.
146
147config INTEL_RST
148	tristate "Intel Rapid Start Technology Driver"
149	depends on ACPI
150	help
151	  This driver provides support for modifying parameters on systems
152	  equipped with Intel's Rapid Start Technology. When put in an ACPI
153	  sleep state, these devices will wake after either a configured
154	  timeout or when the system battery reaches a critical state,
155	  automatically copying memory contents to disk. On resume, the
156	  firmware will copy the memory contents back to RAM and resume the OS
157	  as usual.
158
159config INTEL_SDSI
160	tristate "Intel On Demand (Software Defined Silicon) Driver"
161	depends on INTEL_VSEC
162	depends on X86_64
163	help
164	  This driver enables access to the Intel On Demand (formerly Software
165	  Defined Silicon) interface used to provision silicon features with an
166	  authentication certificate and capability license.
167
168	  To compile this driver as a module, choose M here: the module will
169	  be called intel_sdsi.
170
171config INTEL_SMARTCONNECT
172	tristate "Intel Smart Connect disabling driver"
173	depends on ACPI
174	help
175	  Intel Smart Connect is a technology intended to permit devices to
176	  update state by resuming for a short period of time at regular
177	  intervals. If a user enables this functionality under Windows and
178	  then reboots into Linux, the system may remain configured to resume
179	  on suspend. In the absence of any userspace to support it, the system
180	  will then remain awake until something triggers another suspend.
181
182	  This driver checks to determine whether the device has Intel Smart
183	  Connect enabled, and if so disables it.
184
185config INTEL_TPMI
186	tristate "Intel Topology Aware Register and PM Capsule Interface (TPMI)"
187	depends on INTEL_VSEC
188	depends on X86_64
189	help
190	  The Intel Topology Aware Register and PM Capsule Interface (TPMI),
191	  provides enumerable MMIO interface for power management features.
192	  This driver creates devices, so that other PM feature driver can
193	  be loaded for PM specific feature operation.
194
195	  To compile this driver as a module, choose M here: the module will
196	  be called intel_vsec_tpmi.
197
198config INTEL_TURBO_MAX_3
199	bool "Intel Turbo Boost Max Technology 3.0 enumeration driver"
200	depends on X86_64 && SCHED_MC_PRIO
201	help
202	  This driver reads maximum performance ratio of each CPU and set up
203	  the scheduler priority metrics. In this way scheduler can prefer
204	  CPU with higher performance to schedule tasks.
205
206	  This driver is only required when the system is not using Hardware
207	  P-States (HWP). In HWP mode, priority can be read from ACPI tables.
208
209config INTEL_VSEC
210	tristate "Intel Vendor Specific Extended Capabilities Driver"
211	depends on PCI
212	select AUXILIARY_BUS
213	help
214	  Adds support for feature drivers exposed using Intel PCIe VSEC and
215	  DVSEC.
216
217	  To compile this driver as a module, choose M here: the module will
218	  be called intel_vsec.
219