drivers/reset/amlogic/Kconfig

Source file repositories/reference/linux-study-clean/drivers/reset/amlogic/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/reset/amlogic/Kconfig
Extension: [no extension]
Size: 702 bytes
Lines: 28
Domain: Driver Families
Bucket: drivers/reset
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

config RESET_MESON_COMMON
	tristate
	select REGMAP

config RESET_MESON
	tristate "Meson Reset Driver"
	depends on ARCH_MESON || COMPILE_TEST
	default ARCH_MESON
	select REGMAP_MMIO
	select RESET_MESON_COMMON
	help
	  This enables the reset driver for Amlogic SoCs.

config RESET_MESON_AUX
	tristate "Meson Reset Auxiliary Driver"
	depends on ARCH_MESON || COMPILE_TEST
	select AUXILIARY_BUS
	select RESET_MESON_COMMON
	help
	  This enables the reset auxiliary driver for Amlogic SoCs.

config RESET_MESON_AUDIO_ARB
	tristate "Meson Audio Memory Arbiter Reset Driver"
	depends on ARCH_MESON || COMPILE_TEST
	help
	  This enables the reset driver for Audio Memory Arbiter of
	  Amlogic's A113 based SoCs

Annotation

Atlas domain: Driver Families / drivers/reset.
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.