include/linux/extcon.h

File Facts

System

Linux kernel

Corpus path

include/linux/extcon.h

Extension

.h

Size

10230 bytes

Lines

332

Domain

Core OS

Bucket

Core Kernel Interface

Inferred role

Core OS: implementation source

Status

source implementation candidate

Why This File Exists

Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.

• Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/device.h

Detected Declarations

• struct extcon_dev
• struct extcon_specific_cable_nb
• function extcon_get_state
• function extcon_get_property
• function extcon_get_property_capability
• function extcon_register_notifier
• function extcon_unregister_notifier
• function devm_extcon_register_notifier
• function devm_extcon_unregister_notifier
• function extcon_unregister_notifier_all
• function devm_extcon_register_notifier_all
• function devm_extcon_unregister_notifier_all

Annotated Snippet

struct extcon_specific_cable_nb {
       struct notifier_block *user_nb;
       int cable_index;
       struct extcon_dev *edev;
       unsigned long previous_value;
};
#endif /* __LINUX_EXTCON_H__ */

Annotation

• Immediate include surface: `linux/device.h`.
• Detected declarations: `struct extcon_dev`, `struct extcon_specific_cable_nb`, `function extcon_get_state`, `function extcon_get_property`, `function extcon_get_property_capability`, `function extcon_register_notifier`, `function extcon_unregister_notifier`, `function devm_extcon_register_notifier`, `function devm_extcon_unregister_notifier`, `function extcon_unregister_notifier_all`.
• Atlas domain: Core OS / Core Kernel Interface.
• Implementation status: source implementation candidate.

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.