arch/arm/mach-imx/cpu-imx31.c

File Facts

System

Linux kernel

Corpus path

arch/arm/mach-imx/cpu-imx31.c

Extension

.c

Size

1855 bytes

Lines

73

Domain

Architecture Layer

Bucket

arch/arm

Inferred role

Architecture Layer: exported/initcall integration point

Status

integration 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.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/module.h
• linux/of_address.h
• linux/io.h
• common.h
• hardware.h
• iim.h

Detected Declarations

• function mx31_read_cpu_rev
• function mx31_revision
• export mx31_revision

Annotated Snippet

if (srev == mx31_cpu_type[i].srev) {
			rev = mx31_cpu_type[i].rev;
			imx_print_silicon_rev(mx31_cpu_type[i].name,
						mx31_cpu_type[i].rev);
			goto out;
		}

	imx_print_silicon_rev("i.MX31", IMX_CHIP_REVISION_UNKNOWN);

out:
	iounmap(iim_base);
	return rev;
}

int mx31_revision(void)
{
	if (mx31_cpu_rev == -1)
		mx31_cpu_rev = mx31_read_cpu_rev();

	return mx31_cpu_rev;
}
EXPORT_SYMBOL(mx31_revision);

Annotation

• Immediate include surface: `linux/module.h`, `linux/of_address.h`, `linux/io.h`, `common.h`, `hardware.h`, `iim.h`.
• Detected declarations: `function mx31_read_cpu_rev`, `function mx31_revision`, `export mx31_revision`.
• Atlas domain: Architecture Layer / arch/arm.
• Implementation status: integration 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.