CONFIG_INTEL_INT0002_VGPIO: Intel ACPI INT0002 Virtual GPIO driver

General informations

The Linux kernel configuration item CONFIG_INTEL_INT0002_VGPIO has multiple definitions:

Intel ACPI INT0002 Virtual GPIO driver found in drivers/platform/x86/intel/Kconfig

The configuration item CONFIG_INTEL_INT0002_VGPIO:

• prompt: Intel ACPI INT0002 Virtual GPIO driver
• type: tristate
• depends on: CONFIG_GPIOLIB && CONFIG_ACPI && CONFIG_PM_SLEEP
• defined in drivers/platform/x86/intel/Kconfig
• found in Linux kernels: 5.15, 5.16-rc+HEAD
• modules built: intel_int0002_vgpio, intel_int0002_vgpio

Help text

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.

Intel ACPI INT0002 Virtual GPIO driver found in drivers/platform/x86/Kconfig

The configuration item CONFIG_INTEL_INT0002_VGPIO:

• prompt: Intel ACPI INT0002 Virtual GPIO driver
• type: tristate
• depends on: CONFIG_GPIOLIB && CONFIG_ACPI && CONFIG_PM_SLEEP
• defined in drivers/platform/x86/Kconfig
• found in Linux kernels: 4.13–4.20, 5.0–5.14, 5.14+HEAD
• modules built: intel_int0002_vgpio, intel_int0002_vgpio

Help text

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.

Hardware

LKDDb

Raw data from LKDDb:

• lkddb acpi "INT0002" : CONFIG_INTEL_INT0002_VGPIO CONFIG_X86 : drivers/platform/x86/intel_int0002_vgpio.c # in 4.13–4.20, 5.0–5.14, 5.14+HEAD
• lkddb acpi "INT0002" : CONFIG_INTEL_INT0002_VGPIO CONFIG_X86 CONFIG_X86_PLATFORM_DRIVERS_INTEL : drivers/platform/x86/intel/int0002_vgpio.c # in 5.15, 5.16-rc+HEAD
• lkddb module intel_int0002_vgpio CONFIG_INTEL_INT0002_VGPIO : drivers/platform/x86/Kconfig : "Intel ACPI INT0002 Virtual GPIO driver" # in 4.13–4.20, 5.0–5.14, 5.14+HEAD
• lkddb module intel_int0002_vgpio CONFIG_INTEL_INT0002_VGPIO : drivers/platform/x86/intel/Kconfig : "Intel ACPI INT0002 Virtual GPIO driver" # in 5.15, 5.16-rc+HEAD
• lkddb platform "INT0002 Virtual GPIO" : CONFIG_INTEL_INT0002_VGPIO CONFIG_X86 : drivers/platform/x86/intel_int0002_vgpio.c # in 4.13–4.20, 5.0–5.14, 5.14+HEAD
• lkddb platform "INT0002 Virtual GPIO" : CONFIG_INTEL_INT0002_VGPIO CONFIG_X86 CONFIG_X86_PLATFORM_DRIVERS_INTEL : drivers/platform/x86/intel/int0002_vgpio.c # in 5.15, 5.16-rc+HEAD

Sources

This page is automaticly generated with free (libre, open) software lkddb(see lkddb-sources).

The data is retrived from:

• Linux kernel
• Linux Kernel Driver DataBase (LKDDb)

Automatic links from Google (and ads)

Custom Search

Popular queries: