arch/arm/boot/dts/qcom/msm8926.dtsi

File Facts

System

Linux kernel

Corpus path

arch/arm/boot/dts/qcom/msm8926.dtsi

Extension

.dtsi

Size

220 bytes

Lines

12

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

• qcom-msm8226.dtsi

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) 2025, Luca Weiss <luca@lucaweiss.eu>
 */

#include "qcom-msm8226.dtsi"

&modem {
	compatible = "qcom,msm8926-mss-pil";
	/delete-property/ qcom,ext-bhs-reg;
};

Annotation

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