1# SPDX-License-Identifier: GPL-2.0-only 2# 3# Intel x86 Platform Specific Drivers 4# 5 6menuconfig X86_PLATFORM_DRIVERS_INTEL 7 bool "Intel x86 Platform Specific Device Drivers" 8 default y 9 help 10 Say Y here to get to see options for device drivers for 11 various Intel x86 platforms, including vendor-specific 12 drivers. This option alone does not add any kernel code. 13 14 If you say N, all options in this submenu will be skipped 15 and disabled. 16 17if X86_PLATFORM_DRIVERS_INTEL 18 19source "drivers/platform/x86/intel/atomisp2/Kconfig" 20source "drivers/platform/x86/intel/int1092/Kconfig" 21source "drivers/platform/x86/intel/int33fe/Kconfig" 22source "drivers/platform/x86/intel/int3472/Kconfig" 23source "drivers/platform/x86/intel/pmc/Kconfig" 24source "drivers/platform/x86/intel/pmt/Kconfig" 25source "drivers/platform/x86/intel/speed_select_if/Kconfig" 26source "drivers/platform/x86/intel/telemetry/Kconfig" 27 28config INTEL_HID_EVENT 29 tristate "Intel HID Event" 30 depends on ACPI 31 depends on INPUT 32 depends on I2C 33 select INPUT_SPARSEKMAP 34 help 35 This driver provides support for the Intel HID Event hotkey interface. 36 Some laptops require this driver for hotkey support. 37 38 To compile this driver as a module, choose M here: the module will 39 be called intel_hid. 40 41config INTEL_INT0002_VGPIO 42 tristate "Intel ACPI INT0002 Virtual GPIO driver" 43 depends on GPIOLIB && ACPI && PM_SLEEP 44 select GPIOLIB_IRQCHIP 45 help 46 Some peripherals on Bay Trail and Cherry Trail platforms signal a 47 Power Management Event (PME) to the Power Management Controller (PMC) 48 to wakeup the system. When this happens software needs to explicitly 49 clear the PME bus 0 status bit in the GPE0a_STS register to avoid an 50 IRQ storm on IRQ 9. 51 52 This is modelled in ACPI through the INT0002 ACPI device, which is 53 called a "Virtual GPIO controller" in ACPI because it defines the 54 event handler to call when the PME triggers through _AEI and _L02 55 methods as would be done for a real GPIO interrupt in ACPI. 56 57 To compile this driver as a module, choose M here: the module will 58 be called intel_int0002_vgpio. 59 60config INTEL_BXTWC_PMIC_TMU 61 tristate "Intel Broxton Whiskey Cove TMU Driver" 62 depends on INTEL_SOC_PMIC_BXTWC 63 depends on MFD_INTEL_PMC_BXT 64 select REGMAP 65 help 66 Select this driver to use Intel Broxton Whiskey Cove PMIC TMU feature. 67 This driver enables the alarm wakeup functionality in the TMU unit of 68 Whiskey Cove PMIC. 69 70config INTEL_CHTDC_TI_PWRBTN 71 tristate "Intel Cherry Trail Dollar Cove TI power button driver" 72 depends on INTEL_SOC_PMIC_CHTDC_TI 73 depends on INPUT 74 help 75 This option adds a power button driver for Dollar Cove TI 76 PMIC on Intel Cherry Trail devices. 77 78 To compile this driver as a module, choose M here: the module 79 will be called intel_chtdc_ti_pwrbtn. 80 81config INTEL_MRFLD_PWRBTN 82 tristate "Intel Merrifield Basin Cove power button driver" 83 depends on INTEL_SOC_PMIC_MRFLD 84 depends on INPUT 85 help 86 This option adds a power button driver for Basin Cove PMIC 87 on Intel Merrifield devices. 88 89 To compile this driver as a module, choose M here: the module 90 will be called intel_mrfld_pwrbtn. 91 92config INTEL_PUNIT_IPC 93 tristate "Intel P-Unit IPC Driver" 94 help 95 This driver provides support for Intel P-Unit Mailbox IPC mechanism, 96 which is used to bridge the communications between kernel and P-Unit. 97 98config INTEL_RST 99 tristate "Intel Rapid Start Technology Driver" 100 depends on ACPI 101 help 102 This driver provides support for modifying parameters on systems 103 equipped with Intel's Rapid Start Technology. When put in an ACPI 104 sleep state, these devices will wake after either a configured 105 timeout or when the system battery reaches a critical state, 106 automatically copying memory contents to disk. On resume, the 107 firmware will copy the memory contents back to RAM and resume the OS 108 as usual. 109 110config INTEL_SMARTCONNECT 111 tristate "Intel Smart Connect disabling driver" 112 depends on ACPI 113 help 114 Intel Smart Connect is a technology intended to permit devices to 115 update state by resuming for a short period of time at regular 116 intervals. If a user enables this functionality under Windows and 117 then reboots into Linux, the system may remain configured to resume 118 on suspend. In the absence of any userspace to support it, the system 119 will then remain awake until something triggers another suspend. 120 121 This driver checks to determine whether the device has Intel Smart 122 Connect enabled, and if so disables it. 123 124config INTEL_TURBO_MAX_3 125 bool "Intel Turbo Boost Max Technology 3.0 enumeration driver" 126 depends on X86_64 && SCHED_MC_PRIO 127 help 128 This driver reads maximum performance ratio of each CPU and set up 129 the scheduler priority metrics. In this way scheduler can prefer 130 CPU with higher performance to schedule tasks. 131 132 This driver is only required when the system is not using Hardware 133 P-States (HWP). In HWP mode, priority can be read from ACPI tables. 134 135config INTEL_UNCORE_FREQ_CONTROL 136 tristate "Intel Uncore frequency control driver" 137 depends on X86_64 138 help 139 This driver allows control of Uncore frequency limits on 140 supported server platforms. 141 142 Uncore frequency controls RING/LLC (last-level cache) clocks. 143 144 To compile this driver as a module, choose M here: the module 145 will be called intel-uncore-frequency. 146 147endif # X86_PLATFORM_DRIVERS_INTEL 148