include/linux/mfd/mxs-lradc.h
Source file repositories/reference/linux-study-clean/include/linux/mfd/mxs-lradc.h
File Facts
- System
- Linux kernel
- Corpus path
include/linux/mfd/mxs-lradc.h- Extension
.h- Size
- 5736 bytes
- Lines
- 179
- 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/bitops.hlinux/io.hlinux/stmp_device.h
Detected Declarations
struct mxs_lradcenum mxs_lradc_idenum mxs_lradc_ts_wiresfunction mxs_lradc_irq_mask
Annotated Snippet
struct mxs_lradc {
enum mxs_lradc_id soc;
struct clk *clk;
u8 buffer_vchans;
enum mxs_lradc_ts_wires touchscreen_wire;
bool use_touchbutton;
};
static inline u32 mxs_lradc_irq_mask(struct mxs_lradc *lradc)
{
switch (lradc->soc) {
case IMX23_LRADC:
return LRADC_CTRL1_MX23_LRADC_IRQ_MASK;
case IMX28_LRADC:
return LRADC_CTRL1_MX28_LRADC_IRQ_MASK;
default:
return 0;
}
}
#endif /* __MXS_LRADC_H */
Annotation
- Immediate include surface: `linux/bitops.h`, `linux/io.h`, `linux/stmp_device.h`.
- Detected declarations: `struct mxs_lradc`, `enum mxs_lradc_id`, `enum mxs_lradc_ts_wires`, `function mxs_lradc_irq_mask`.
- 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.