include/linux/mfd/da9063/core.h
Source file repositories/reference/linux-study-clean/include/linux/mfd/da9063/core.h
File Facts
- System
- Linux kernel
- Corpus path
include/linux/mfd/da9063/core.h- Extension
.h- Size
- 2048 bytes
- Lines
- 96
- 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/interrupt.hlinux/mfd/da9063/registers.h
Detected Declarations
struct da9063enum da9063_typeenum da9063_variant_codesenum da9063_irqs
Annotated Snippet
struct da9063 {
/* Device */
struct device *dev;
enum da9063_type type;
unsigned char variant_code;
unsigned int flags;
bool use_sw_pm;
/* Control interface */
struct regmap *regmap;
/* Interrupts */
int chip_irq;
unsigned int irq_base;
struct regmap_irq_chip_data *regmap_irq;
};
int da9063_device_init(struct da9063 *da9063, unsigned int irq);
int da9063_irq_init(struct da9063 *da9063);
#endif /* __MFD_DA9063_CORE_H__ */
Annotation
- Immediate include surface: `linux/interrupt.h`, `linux/mfd/da9063/registers.h`.
- Detected declarations: `struct da9063`, `enum da9063_type`, `enum da9063_variant_codes`, `enum da9063_irqs`.
- 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.