arch/arm64/boot/dts/qcom/monaco-el2.dtso

File Facts

System

Linux kernel

Corpus path

arch/arm64/boot/dts/qcom/monaco-el2.dtso

Extension

.dtso

Size

456 bytes

Lines

30

Domain

Architecture Layer

Bucket

arch/arm64

Inferred role

Architecture Layer: arch/arm64

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

• No C-style include directives detected by the generator.

Detected Declarations

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

Annotated Snippet

// SPDX-License-Identifier: BSD-3-Clause
/*
 * Copyright (c) Qualcomm Technologies, Inc. and/or its subsidiaries.
 *
 * Monaco specific modifications required to boot in EL2.
 */

/dts-v1/;
/plugin/;

&gpu_zap_shader {
	status = "disabled";
};

&iris {
	status = "disabled";
};

&remoteproc_adsp {
	iommus = <&apps_smmu 0x2000 0x0>;
};

&remoteproc_cdsp {
	iommus = <&apps_smmu 0x19c0 0x0400>;
};

&remoteproc_gpdsp {
	iommus = <&apps_smmu 0x28a0 0x0>;
};

Annotation

• 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.