arch/arm64/boot/dts/nvidia/tegra264-p3834.dtsi

File Facts

System

Linux kernel

Corpus path

arch/arm64/boot/dts/nvidia/tegra264-p3834.dtsi

Extension

.dtsi

Size

457 bytes

Lines

39

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

• tegra264.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-only OR BSD-2-Clause

#include "tegra264.dtsi"

/ {
	compatible = "nvidia,p3834", "nvidia,tegra264";

	aliases {
	};

	bus@0 {
		serial@c4e0000 {
			status = "okay";
		};

		serial@c5a0000 {
			status = "okay";
		};
	};

	bus@8100000000 {
		iommu@5000000 {
			status = "okay";
		};

		cmdqv@5200000 {
			status = "okay";
		};

		iommu@6000000 {
			status = "okay";
		};

		cmdqv@6200000 {
			status = "okay";
		};
	};
};

Annotation

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