drivers/connector/Kconfig

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

File Facts

System: Linux kernel
Corpus path: drivers/connector/Kconfig
Extension: [no extension]
Size: 628 bytes
Lines: 24
Domain: Driver Families
Bucket: drivers/connector
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 CONNECTOR
	tristate "Connector - unified userspace <-> kernelspace linker"
	depends on NET
	help
	  This is unified userspace <-> kernelspace connector working on top
	  of the netlink socket protocol.

	  Connector support can also be built as a module.  If so, the module
	  will be called cn.

if CONNECTOR

config PROC_EVENTS
	bool "Report process events to userspace"
	depends on CONNECTOR=y
	default y
	help
	  Provide a connector that reports process events to userspace. Send
	  events such as fork, exec, id change (uid, gid, suid, etc), and exit.

endif # CONNECTOR

Annotation

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