drivers/platform/goldfish/Kconfig

Source file repositories/reference/linux-study-clean/drivers/platform/goldfish/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/platform/goldfish/Kconfig
Extension: [no extension]
Size: 590 bytes
Lines: 21
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-only
menuconfig GOLDFISH
	bool "Platform support for Goldfish virtual devices"
	depends on HAS_IOMEM && HAS_DMA
	default X86_GOLDFISH
	help
	  Say Y here to get to see options for the Goldfish virtual platform.
	  This option alone does not add any kernel code.

	  Unless you are building for the Android Goldfish emulator say N here.

if GOLDFISH

config GOLDFISH_PIPE
	tristate "Goldfish virtual device for QEMU pipes"
	help
	  This is a virtual device to drive the QEMU pipe interface used by
	  the Goldfish Android Virtual Device.

endif # GOLDFISH

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.