include/linux/mfd/pf1550.h

File Facts

System

Linux kernel

Corpus path

include/linux/mfd/pf1550.h

Extension

.h

Size

7808 bytes

Lines

274

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

Detected Declarations

• struct pf1550_ddata
• enum pf1550_pmic_reg
• enum pf1550_otp_reg
• enum pf1550_irq
• enum pf1550_pmic_irq
• enum pf1550_onkey_irq
• enum pf1550_charg_irq
• enum pf1550_regulators

Annotated Snippet

struct pf1550_ddata {
	struct regmap_irq_chip_data *irq_data_regulator;
	struct regmap_irq_chip_data *irq_data_charger;
	struct regmap_irq_chip_data *irq_data_onkey;
	struct regmap_irq_chip_data *irq_data;
	struct regmap *regmap;
	struct device *dev;
	bool dvs1_enable;
	bool dvs2_enable;
	int irq;
};

#endif /* __LINUX_MFD_PF1550_H */

Annotation

• Immediate include surface: `linux/i2c.h`, `linux/regmap.h`.
• Detected declarations: `struct pf1550_ddata`, `enum pf1550_pmic_reg`, `enum pf1550_otp_reg`, `enum pf1550_irq`, `enum pf1550_pmic_irq`, `enum pf1550_onkey_irq`, `enum pf1550_charg_irq`, `enum pf1550_regulators`.
• 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.