include/linux/mfd/rk808.h
Source file repositories/reference/linux-study-clean/include/linux/mfd/rk808.h
File Facts
- System
- Linux kernel
- Corpus path
include/linux/mfd/rk808.h- Extension
.h- Size
- 42660 bytes
- Lines
- 1477
- 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/regulator/machine.hlinux/regmap.h
Detected Declarations
struct rk808enum rk808_regenum rk816_regenum rk816_irqsenum rk818_regenum rk801_regenum rk805_regenum rk806_reg_idenum rk806_irqsenum rk806_lv_selenum rk806_uv_selenum rk806_pwrctrl_funenum rk806_pin_levelenum rk806_vsel_ctr_selenum rk806_dvs_ctr_selenum rk806_pin_dr_selenum rk806_int_funenum rk806_dvs_modeenum rk817_reg_idenum rk809_reg_id
Annotated Snippet
struct rk808 {
struct device *dev;
struct regmap_irq_chip_data *irq_data;
struct regmap *regmap;
long variant;
const struct regmap_config *regmap_cfg;
const struct regmap_irq_chip *regmap_irq_chip;
};
void rk8xx_shutdown(struct device *dev);
int rk8xx_probe(struct device *dev, int variant, unsigned int irq, struct regmap *regmap);
int rk8xx_suspend(struct device *dev);
int rk8xx_resume(struct device *dev);
#endif /* __LINUX_REGULATOR_RK808_H */
Annotation
- Immediate include surface: `linux/regulator/machine.h`, `linux/regmap.h`.
- Detected declarations: `struct rk808`, `enum rk808_reg`, `enum rk816_reg`, `enum rk816_irqs`, `enum rk818_reg`, `enum rk801_reg`, `enum rk805_reg`, `enum rk806_reg_id`, `enum rk806_irqs`, `enum rk806_lv_sel`.
- 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.