drivers/soc/atmel/Kconfig

Source file repositories/reference/linux-study-clean/drivers/soc/atmel/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/soc/atmel/Kconfig
Extension: [no extension]
Size: 611 bytes
Lines: 19
Domain: Driver Families
Bucket: drivers/soc
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
config AT91_SOC_ID
	bool "SoC bus for Atmel ARM SoCs"
	depends on ARCH_AT91 || COMPILE_TEST
	default ARCH_AT91
	help
	  Include support for the SoC bus on the Atmel ARM SoCs.

config AT91_SOC_SFR
	tristate "Special Function Registers support"
	depends on ARCH_AT91 || COMPILE_TEST
	help
	  This is a driver for the Special Function Registers available on
	  Atmel SAMA5Dx SoCs, providing access to specific aspects of the
	  integrated memory, bridge implementations, processor etc.

	  This driver can also be built as a module. If so, the module
	  will be called sfr.

Annotation

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