drivers/pinctrl/freescale/pinctrl-mxs.h
Source file repositories/reference/linux-study-clean/drivers/pinctrl/freescale/pinctrl-mxs.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/pinctrl/freescale/pinctrl-mxs.h- Extension
.h- Size
- 1719 bytes
- Lines
- 85
- Domain
- Driver Families
- Bucket
- drivers/pinctrl
- Inferred role
- Driver Families: implementation source
- Status
- source implementation candidate
Why This File Exists
Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/platform_device.hlinux/pinctrl/pinctrl.h
Detected Declarations
struct mxs_functionstruct mxs_groupstruct mxs_regsstruct mxs_pinctrl_soc_data
Annotated Snippet
struct mxs_function {
const char *name;
const char **groups;
unsigned ngroups;
};
struct mxs_group {
const char *name;
unsigned int *pins;
unsigned npins;
u8 *muxsel;
u8 config;
};
struct mxs_regs {
u16 muxsel;
u16 drive;
u16 pull;
};
struct mxs_pinctrl_soc_data {
const struct mxs_regs *regs;
const struct pinctrl_pin_desc *pins;
unsigned npins;
struct mxs_function *functions;
unsigned nfunctions;
struct mxs_group *groups;
unsigned ngroups;
};
int mxs_pinctrl_probe(struct platform_device *pdev,
struct mxs_pinctrl_soc_data *soc);
#endif /* __PINCTRL_MXS_H */
Annotation
- Immediate include surface: `linux/platform_device.h`, `linux/pinctrl/pinctrl.h`.
- Detected declarations: `struct mxs_function`, `struct mxs_group`, `struct mxs_regs`, `struct mxs_pinctrl_soc_data`.
- Atlas domain: Driver Families / drivers/pinctrl.
- 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.