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_OAKTRAIL 61 tristate "Intel Oaktrail Platform Extras" 62 depends on ACPI 63 depends on ACPI_VIDEO || ACPI_VIDEO=n 64 depends on RFKILL && BACKLIGHT_CLASS_DEVICE && ACPI 65 help 66 Intel Oaktrail platform need this driver to provide interfaces to 67 enable/disable the Camera, WiFi, BT etc. devices. If in doubt, say Y 68 here; it will only load on supported platforms. 69 70config INTEL_BXTWC_PMIC_TMU 71 tristate "Intel Broxton Whiskey Cove TMU Driver" 72 depends on INTEL_SOC_PMIC_BXTWC 73 depends on MFD_INTEL_PMC_BXT 74 select REGMAP 75 help 76 Select this driver to use Intel Broxton Whiskey Cove PMIC TMU feature. 77 This driver enables the alarm wakeup functionality in the TMU unit of 78 Whiskey Cove PMIC. 79 80config INTEL_CHTDC_TI_PWRBTN 81 tristate "Intel Cherry Trail Dollar Cove TI power button driver" 82 depends on INTEL_SOC_PMIC_CHTDC_TI 83 depends on INPUT 84 help 85 This option adds a power button driver for Dollar Cove TI 86 PMIC on Intel Cherry Trail devices. 87 88 To compile this driver as a module, choose M here: the module 89 will be called intel_chtdc_ti_pwrbtn. 90 91config INTEL_MRFLD_PWRBTN 92 tristate "Intel Merrifield Basin Cove power button driver" 93 depends on INTEL_SOC_PMIC_MRFLD 94 depends on INPUT 95 help 96 This option adds a power button driver for Basin Cove PMIC 97 on Intel Merrifield devices. 98 99 To compile this driver as a module, choose M here: the module 100 will be called intel_mrfld_pwrbtn. 101 102config INTEL_PUNIT_IPC 103 tristate "Intel P-Unit IPC Driver" 104 help 105 This driver provides support for Intel P-Unit Mailbox IPC mechanism, 106 which is used to bridge the communications between kernel and P-Unit. 107 108config INTEL_RST 109 tristate "Intel Rapid Start Technology Driver" 110 depends on ACPI 111 help 112 This driver provides support for modifying parameters on systems 113 equipped with Intel's Rapid Start Technology. When put in an ACPI 114 sleep state, these devices will wake after either a configured 115 timeout or when the system battery reaches a critical state, 116 automatically copying memory contents to disk. On resume, the 117 firmware will copy the memory contents back to RAM and resume the OS 118 as usual. 119 120config INTEL_SMARTCONNECT 121 tristate "Intel Smart Connect disabling driver" 122 depends on ACPI 123 help 124 Intel Smart Connect is a technology intended to permit devices to 125 update state by resuming for a short period of time at regular 126 intervals. If a user enables this functionality under Windows and 127 then reboots into Linux, the system may remain configured to resume 128 on suspend. In the absence of any userspace to support it, the system 129 will then remain awake until something triggers another suspend. 130 131 This driver checks to determine whether the device has Intel Smart 132 Connect enabled, and if so disables it. 133 134config INTEL_TURBO_MAX_3 135 bool "Intel Turbo Boost Max Technology 3.0 enumeration driver" 136 depends on X86_64 && SCHED_MC_PRIO 137 help 138 This driver reads maximum performance ratio of each CPU and set up 139 the scheduler priority metrics. In this way scheduler can prefer 140 CPU with higher performance to schedule tasks. 141 142 This driver is only required when the system is not using Hardware 143 P-States (HWP). In HWP mode, priority can be read from ACPI tables. 144 145config INTEL_UNCORE_FREQ_CONTROL 146 tristate "Intel Uncore frequency control driver" 147 depends on X86_64 148 help 149 This driver allows control of Uncore frequency limits on 150 supported server platforms. 151 152 Uncore frequency controls RING/LLC (last-level cache) clocks. 153 154 To compile this driver as a module, choose M here: the module 155 will be called intel-uncore-frequency. 156 157endif # X86_PLATFORM_DRIVERS_INTEL 158