arch/arm64/boot/dts/bst/bstc1200-cdcu1.0-adas_4c2g.dts

File Facts

System

Linux kernel

Corpus path

arch/arm64/boot/dts/bst/bstc1200-cdcu1.0-adas_4c2g.dts

Extension

.dts

Size

734 bytes

Lines

44

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

• bstc1200.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
/dts-v1/;

#include "bstc1200.dtsi"

/ {
	model = "BST C1200-96 CDCU1.0 4C2G";
	compatible = "bst,c1200-cdcu1.0-adas-4c2g", "bst,c1200";

	chosen {
		stdout-path = "serial0:115200n8";
	};

	memory@810000000 {
		device_type = "memory";
		reg = <0x8 0x10000000 0x0 0x30000000>,
		      <0x8 0xc0000000 0x1 0x0>,
		      <0xc 0x00000000 0x0 0x40000000>;
	};

	reserved-memory {
		#address-cells = <2>;
		#size-cells = <2>;
		ranges;

		mmc0_reserved: mmc0-reserved@5160000 {
			compatible = "shared-dma-pool";
			reg = <0x0 0x5160000 0x0 0x10000>;
			no-map;
		};
	};
};

&mmc0 {
	bus-width = <8>;
	memory-region = <&mmc0_reserved>;
	non-removable;
	status = "okay";
};

&uart0 {
	status = "okay";
};

Annotation

• Immediate include surface: `bstc1200.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.