arch/arm/boot/dts/qcom/qcom-msm8226-microsoft-moneypenny.dts
Source file repositories/reference/linux-study-clean/arch/arm/boot/dts/qcom/qcom-msm8226-microsoft-moneypenny.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/arm/boot/dts/qcom/qcom-msm8226-microsoft-moneypenny.dts- Extension
.dts- Size
- 649 bytes
- Lines
- 28
- 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.dtsiqcom-msm8226-microsoft-common.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) 2023, Jack Matthews <jm5112356@gmail.com>
* Copyright (c) 2023, Ivaylo Ivanov <ivo.ivanov.ivanov1@gmail.com>
* Copyright (c) 2023, Dominik Kobinski <dominikkobinski314@gmail.com>
* Copyright (c) 2023, Rayyan Ansari <rayyan@ansari.sh>
*/
/dts-v1/;
#include "qcom-msm8226.dtsi"
#include "qcom-msm8226-microsoft-common.dtsi"
/* This device has no magnetometer */
/delete-node/ &magnetometer;
/ {
model = "Nokia Lumia 630";
compatible = "microsoft,moneypenny", "qcom,msm8226";
chassis-type = "handset";
};
&framebuffer {
width = <480>;
height = <854>;
stride = <(480 * 4)>;
};
Annotation
- Immediate include surface: `qcom-msm8226.dtsi`, `qcom-msm8226-microsoft-common.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.