include/linux/mfd/adp5585.h

File Facts

System

Linux kernel

Corpus path

include/linux/mfd/adp5585.h

Extension

.h

Size

7040 bytes

Lines

227

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/bits.h
• linux/notifier.h

Detected Declarations

• struct regmap
• struct adp5585_regs
• struct adp5585_dev
• enum adp5585_variant

Annotated Snippet

struct adp5585_regs {
	unsigned int gen_cfg;
	unsigned int ext_cfg;
	unsigned int int_en;
	unsigned int poll_ptime_cfg;
	unsigned int reset_cfg;
	unsigned int reset1_event_a;
	unsigned int reset2_event_a;
	unsigned int pin_cfg_a;
};

struct adp5585_dev {
	struct device *dev;
	struct regmap *regmap;
	const struct adp5585_regs *regs;
	struct blocking_notifier_head event_notifier;
	unsigned long *pin_usage;
	unsigned int n_pins;
	unsigned int reset2_out;
	enum adp5585_variant variant;
	unsigned int id;
	bool has_unlock;
	bool has_pin6;
	int irq;
	unsigned int ev_poll_time;
	unsigned int unlock_time;
	unsigned int unlock_keys[2];
	unsigned int nkeys_unlock;
	unsigned int reset1_keys[3];
	unsigned int nkeys_reset1;
	unsigned int reset2_keys[2];
	unsigned int nkeys_reset2;
	u8 reset_cfg;
};

#endif

Annotation

• Immediate include surface: `linux/bits.h`, `linux/notifier.h`.
• Detected declarations: `struct regmap`, `struct adp5585_regs`, `struct adp5585_dev`, `enum adp5585_variant`.
• 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.