drivers/dpll/Kconfig

Source file repositories/reference/linux-study-clean/drivers/dpll/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/dpll/Kconfig
Extension: [no extension]
Size: 679 bytes
Lines: 29
Domain: Driver Families
Bucket: drivers/dpll
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
#
# Generic DPLL drivers configuration
#

menu "DPLL device support"

config DPLL
	bool

config DPLL_REFCNT_TRACKER
	bool "DPLL reference count tracking"
	depends on DEBUG_KERNEL && STACKTRACE_SUPPORT && DPLL
	select REF_TRACKER
	help
	  Enable reference count tracking for DPLL devices and pins.
	  This helps debugging reference leaks and use-after-free bugs
	  by recording stack traces for each get/put operation.

	  The tracking information is exposed via debugfs at:
	    /sys/kernel/debug/ref_tracker/dpll_device_*
	    /sys/kernel/debug/ref_tracker/dpll_pin_*

	  If unsure, say N.

source "drivers/dpll/zl3073x/Kconfig"

endmenu

Annotation

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