platform/x86: intel_int0002_vgpio: Move to intel sub-directory
JIRA: https://issues.redhat.com/browse/RHEL-25415 Conflicts: Minor drift issues. commit daef4c5a042302a047e56e8985f8d50d85f45802 Author: Kate Hsuan <hpa@redhat.com> Date: Fri Aug 20 14:04:54 2021 +0300 platform/x86: intel_int0002_vgpio: Move to intel sub-directory Move Intel vGPIO (INT0002) driver to intel sub-directory to improve readability. Signed-off-by: Kate Hsuan <hpa@redhat.com> Reviewed-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> Link: https://lore.kernel.org/r/20210820110458.73018-17-andriy.shevchenko@linux.intel.com Signed-off-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Prarit Bhargava <prarit@redhat.com>
This commit is contained in:
parent
8e59d2113f
commit
3798108d13
|
@ -636,25 +636,6 @@ config THINKPAD_LMI
|
|||
|
||||
source "drivers/platform/x86/intel/Kconfig"
|
||||
|
||||
config INTEL_INT0002_VGPIO
|
||||
tristate "Intel ACPI INT0002 Virtual GPIO driver"
|
||||
depends on GPIOLIB && ACPI && PM_SLEEP
|
||||
select GPIOLIB_IRQCHIP
|
||||
help
|
||||
Some peripherals on Bay Trail and Cherry Trail platforms signal a
|
||||
Power Management Event (PME) to the Power Management Controller (PMC)
|
||||
to wakeup the system. When this happens software needs to explicitly
|
||||
clear the PME bus 0 status bit in the GPE0a_STS register to avoid an
|
||||
IRQ storm on IRQ 9.
|
||||
|
||||
This is modelled in ACPI through the INT0002 ACPI device, which is
|
||||
called a "Virtual GPIO controller" in ACPI because it defines the
|
||||
event handler to call when the PME triggers through _AEI and _L02
|
||||
methods as would be done for a real GPIO interrupt in ACPI.
|
||||
|
||||
To compile this driver as a module, choose M here: the module will
|
||||
be called intel_int0002_vgpio.
|
||||
|
||||
config INTEL_MENLOW
|
||||
tristate "Thermal Management driver for Intel menlow platform"
|
||||
depends on ACPI_THERMAL
|
||||
|
|
|
@ -67,7 +67,6 @@ obj-$(CONFIG_THINKPAD_LMI) += think-lmi.o
|
|||
# Intel
|
||||
obj-$(CONFIG_X86_PLATFORM_DRIVERS_INTEL) += intel/
|
||||
|
||||
obj-$(CONFIG_INTEL_INT0002_VGPIO) += intel_int0002_vgpio.o
|
||||
obj-$(CONFIG_INTEL_MENLOW) += intel_menlow.o
|
||||
obj-$(CONFIG_INTEL_OAKTRAIL) += intel_oaktrail.o
|
||||
obj-$(CONFIG_INTEL_VBTN) += intel-vbtn.o
|
||||
|
|
|
@ -41,6 +41,25 @@ config INTEL_HID_EVENT
|
|||
To compile this driver as a module, choose M here: the module will
|
||||
be called intel_hid.
|
||||
|
||||
config INTEL_INT0002_VGPIO
|
||||
tristate "Intel ACPI INT0002 Virtual GPIO driver"
|
||||
depends on GPIOLIB && ACPI && PM_SLEEP
|
||||
select GPIOLIB_IRQCHIP
|
||||
help
|
||||
Some peripherals on Bay Trail and Cherry Trail platforms signal a
|
||||
Power Management Event (PME) to the Power Management Controller (PMC)
|
||||
to wakeup the system. When this happens software needs to explicitly
|
||||
clear the PME bus 0 status bit in the GPE0a_STS register to avoid an
|
||||
IRQ storm on IRQ 9.
|
||||
|
||||
This is modelled in ACPI through the INT0002 ACPI device, which is
|
||||
called a "Virtual GPIO controller" in ACPI because it defines the
|
||||
event handler to call when the PME triggers through _AEI and _L02
|
||||
methods as would be done for a real GPIO interrupt in ACPI.
|
||||
|
||||
To compile this driver as a module, choose M here: the module will
|
||||
be called intel_int0002_vgpio.
|
||||
|
||||
config INTEL_SDSI
|
||||
tristate "Intel On Demand (Software Defined Silicon) Driver"
|
||||
depends on INTEL_VSEC
|
||||
|
|
|
@ -38,3 +38,7 @@ obj-$(CONFIG_INTEL_TPMI) += intel_vsec_tpmi.o
|
|||
# Intel input drivers
|
||||
intel-hid-y := hid.o
|
||||
obj-$(CONFIG_INTEL_HID_EVENT) += intel-hid.o
|
||||
|
||||
# Intel miscellaneous drivers
|
||||
intel_int0002_vgpio-y := int0002_vgpio.o
|
||||
obj-$(CONFIG_INTEL_INT0002_VGPIO) += intel_int0002_vgpio.o
|
||||
|
|
Loading…
Reference in New Issue