arch/arm64/boot/dts/blaize/blaize-blzp1600-som.dtsi

File Facts

System

Linux kernel

Corpus path

arch/arm64/boot/dts/blaize/blaize-blzp1600-som.dtsi

Extension

.dtsi

Size

362 bytes

Lines

24

Domain

Architecture Layer

Bucket

arch/arm64

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

• blaize-blzp1600.dtsi

Detected Declarations

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

Annotated Snippet

// SPDX-License-Identifier: GPL-2.0+
/*
 * Copyright (c) 2024 Blaize, Inc. All rights reserved.
 */

#include "blaize-blzp1600.dtsi"

/ {
	memory@0 {
		device_type = "memory";
		reg = <0x0 0x0 0x1 0x0>;
	};
};

/* i2c4 bus is available only on the SoM, not on the board */
&i2c4 {
	clock-frequency = <100000>;
	status = "okay";
};

&uart0 {
	status = "okay";
};

Annotation

• Immediate include surface: `blaize-blzp1600.dtsi`.
• Atlas domain: Architecture Layer / arch/arm64.
• 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.