drivers/platform/x86/x86-android-tablets/Kconfig

Source file repositories/reference/linux-study-clean/drivers/platform/x86/x86-android-tablets/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/platform/x86/x86-android-tablets/Kconfig
Extension: [no extension]
Size: 958 bytes
Lines: 27
Domain: Driver Families
Bucket: drivers/platform
Inferred role: Driver Families: build/configuration rule
Status: atlas-only

Why This File Exists

Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

Dependency Surface

No C-style include directives detected by the generator.

Detected Declarations

No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

# SPDX-License-Identifier: GPL-2.0-or-later
#
# X86 Android tablet support Kconfig
#

config X86_ANDROID_TABLETS
	tristate "X86 Android tablet support"
	depends on I2C && SPI && SERIAL_DEV_BUS
	depends on GPIOLIB && PMIC_OPREGION
	depends on ACPI && EFI && PCI
	select NEW_LEDS
	select LEDS_CLASS
	select POWER_SUPPLY
	help
	  X86 tablets which ship with Android as (part of) the factory image
	  typically have various problems with their DSDTs. The factory kernels
	  shipped on these devices typically have device addresses and GPIOs
	  hardcoded in the kernel, rather than specified in their DSDT.

	  With the DSDT containing a random collection of devices which may or
	  may not actually be present. This driver contains various fixes for
	  such tablets, including instantiating kernel devices for devices which
	  are missing from the DSDT.

	  If you have a x86 Android tablet say Y or M here, for a generic x86
	  distro configuration say M here.

Annotation

Atlas domain: Driver Families / drivers/platform.
Implementation status: atlas-only.

Implementation Notes

This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.