include/linux/mfd/cs40l50.h
Source file repositories/reference/linux-study-clean/include/linux/mfd/cs40l50.h
File Facts
- System
- Linux kernel
- Corpus path
include/linux/mfd/cs40l50.h- Extension
.h- Size
- 4196 bytes
- Lines
- 138
- 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/firmware/cirrus/cs_dsp.hlinux/gpio/consumer.hlinux/pm.hlinux/regmap.h
Detected Declarations
struct cs40l50enum cs40l50_irq_listenum cs40l50_wseqs
Annotated Snippet
struct cs40l50 {
struct device *dev;
struct regmap *regmap;
struct mutex lock;
struct cs_dsp dsp;
struct gpio_desc *reset_gpio;
struct regmap_irq_chip_data *irq_data;
const struct firmware *fw;
const struct firmware *bin;
struct cs_dsp_wseq wseqs[CS40L50_NUM_WSEQS];
int irq;
u32 devid;
u32 revid;
};
int cs40l50_dsp_write(struct device *dev, struct regmap *regmap, u32 val);
int cs40l50_probe(struct cs40l50 *cs40l50);
int cs40l50_remove(struct cs40l50 *cs40l50);
extern const struct regmap_config cs40l50_regmap;
extern const struct dev_pm_ops cs40l50_pm_ops;
#endif /* __MFD_CS40L50_H__ */
Annotation
- Immediate include surface: `linux/firmware/cirrus/cs_dsp.h`, `linux/gpio/consumer.h`, `linux/pm.h`, `linux/regmap.h`.
- Detected declarations: `struct cs40l50`, `enum cs40l50_irq_list`, `enum cs40l50_wseqs`.
- 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.