include/linux/mfd/max77686-private.h

File Facts

System

Linux kernel

Corpus path

include/linux/mfd/max77686-private.h

Extension

.h

Size

12658 bytes

Lines

445

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/i2c.h
• linux/regmap.h
• linux/module.h

Detected Declarations

• struct max77686_dev
• enum max77686_pmic_reg
• enum max77686_rtc_reg
• enum max77802_pmic_reg
• enum max77802_rtc_reg
• enum max77686_irq_source
• enum max77686_irq
• enum max77686_types

Annotated Snippet

struct max77686_dev {
	struct device *dev;
	struct i2c_client *i2c; /* 0xcc / PMIC, Battery Control, and FLASH */

	unsigned long type;

	struct regmap *regmap;		/* regmap for mfd */
	struct regmap_irq_chip_data *irq_data;

	int irq;
	struct mutex irqlock;
	int irq_masks_cur[MAX77686_IRQ_GROUP_NR];
	int irq_masks_cache[MAX77686_IRQ_GROUP_NR];
};

enum max77686_types {
	TYPE_MAX77686,
	TYPE_MAX77802,
};

#endif /*  __LINUX_MFD_MAX77686_PRIV_H */

Annotation

• Immediate include surface: `linux/i2c.h`, `linux/regmap.h`, `linux/module.h`.
• Detected declarations: `struct max77686_dev`, `enum max77686_pmic_reg`, `enum max77686_rtc_reg`, `enum max77802_pmic_reg`, `enum max77802_rtc_reg`, `enum max77686_irq_source`, `enum max77686_irq`, `enum max77686_types`.
• 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.