include/linux/mfd/madera/pdata.h
Source file repositories/reference/linux-study-clean/include/linux/mfd/madera/pdata.h
File Facts
- System
- Linux kernel
- Corpus path
include/linux/mfd/madera/pdata.h- Extension
.h- Size
- 1576 bytes
- Lines
- 60
- 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/arizona-ldo1.hlinux/regulator/arizona-micsupp.hlinux/regulator/machine.hlinux/types.hsound/madera-pdata.h
Detected Declarations
struct gpio_descstruct pinctrl_mapstruct madera_pdata
Annotated Snippet
struct madera_pdata {
struct gpio_desc *reset;
struct arizona_ldo1_pdata ldo1;
struct arizona_micsupp_pdata micvdd;
unsigned int irq_flags;
int gpio_base;
const struct pinctrl_map *gpio_configs;
int n_gpio_configs;
u32 gpsw[MADERA_MAX_GPSW];
struct madera_codec_pdata codec;
};
#endif
Annotation
- Immediate include surface: `linux/regulator/arizona-ldo1.h`, `linux/regulator/arizona-micsupp.h`, `linux/regulator/machine.h`, `linux/types.h`, `sound/madera-pdata.h`.
- Detected declarations: `struct gpio_desc`, `struct pinctrl_map`, `struct madera_pdata`.
- 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.