arch/arm/mach-imx/mxc.h

File Facts

System

Linux kernel

Corpus path

arch/arm/mach-imx/mxc.h

Extension

.h

Size

1576 bytes

Lines

88

Domain

Architecture Layer

Bucket

arch/arm

Inferred role

Architecture Layer: implementation source

Status

source implementation candidate

Why This File Exists

CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.

• CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/types.h
• soc/imx/cpu.h

Detected Declarations

• struct cpu_op
• function Copyright
• function cpu_is_imx6sl
• function cpu_is_imx6dl
• function cpu_is_imx6sx
• function cpu_is_imx6ul
• function cpu_is_imx6ull
• function cpu_is_imx6ulz
• function cpu_is_imx6sll
• function cpu_is_imx6q
• function cpu_is_imx7d

Annotated Snippet

struct cpu_op {
	u32 cpu_rate;
};

int tzic_enable_wake(void);

extern struct cpu_op *(*get_cpu_op)(int *op);
#endif

#define imx_readl	readl_relaxed
#define imx_readw	readw_relaxed
#define imx_writel	writel_relaxed
#define imx_writew	writew_relaxed

#endif /*  __ASM_ARCH_MXC_H__ */

Annotation

• Immediate include surface: `linux/types.h`, `soc/imx/cpu.h`.
• Detected declarations: `struct cpu_op`, `function Copyright`, `function cpu_is_imx6sl`, `function cpu_is_imx6dl`, `function cpu_is_imx6sx`, `function cpu_is_imx6ul`, `function cpu_is_imx6ull`, `function cpu_is_imx6ulz`, `function cpu_is_imx6sll`, `function cpu_is_imx6q`.
• Atlas domain: Architecture Layer / arch/arm.
• 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.