arch/arm/boot/dts/nxp/vf/vf610m4.dtsi

File Facts

System

Linux kernel

Corpus path

arch/arm/boot/dts/nxp/vf/vf610m4.dtsi

Extension

.dtsi

Size

2238 bytes

Lines

62

Domain

Architecture Layer

Bucket

arch/arm

Inferred role

Architecture Layer: configuration, schema, or hardware description

Status

atlas-only

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.

Dependency Surface

• ../../armv7-m.dtsi
• vfxxx.dtsi

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

#include "../../armv7-m.dtsi"
#include "vfxxx.dtsi"

/ {
	#address-cells = <1>;
	#size-cells = <1>;
	chosen { };
	aliases { };
};

&mscm_ir {
	interrupt-parent = <&nvic>;
};

&nvic {
	arm,num-irq-priority-bits = <4>;
};

Annotation

• Immediate include surface: `../../armv7-m.dtsi`, `vfxxx.dtsi`.
• Atlas domain: Architecture Layer / arch/arm.
• Implementation status: atlas-only.

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.