include/linux/mfd/atc260x/core.h
Source file repositories/reference/linux-study-clean/include/linux/mfd/atc260x/core.h
File Facts
- System
- Linux kernel
- Corpus path
include/linux/mfd/atc260x/core.h- Extension
.h- Size
- 1230 bytes
- Lines
- 59
- 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/mfd/atc260x/atc2603c.hlinux/mfd/atc260x/atc2609a.h
Detected Declarations
struct atc260xstruct regmap_configenum atc260x_typeenum atc260x_ver
Annotated Snippet
struct atc260x {
struct device *dev;
struct regmap *regmap;
const struct regmap_irq_chip *regmap_irq_chip;
struct regmap_irq_chip_data *irq_data;
struct mutex *regmap_mutex; /* mutex for custom regmap locking */
const struct mfd_cell *cells;
int nr_cells;
int irq;
enum atc260x_type ic_type;
enum atc260x_ver ic_ver;
const char *type_name;
unsigned int rev_reg;
const struct atc260x_init_regs *init_regs; /* regs for device init */
};
struct regmap_config;
int atc260x_match_device(struct atc260x *atc260x, struct regmap_config *regmap_cfg);
int atc260x_device_probe(struct atc260x *atc260x);
#endif /* __LINUX_MFD_ATC260X_CORE_H */
Annotation
- Immediate include surface: `linux/mfd/atc260x/atc2603c.h`, `linux/mfd/atc260x/atc2609a.h`.
- Detected declarations: `struct atc260x`, `struct regmap_config`, `enum atc260x_type`, `enum atc260x_ver`.
- 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.