arch/arm64/boot/dts/qcom/apq8094-sony-xperia-kitakami-karin_windy.dts
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/qcom/apq8094-sony-xperia-kitakami-karin_windy.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/qcom/apq8094-sony-xperia-kitakami-karin_windy.dts- Extension
.dts- Size
- 611 bytes
- Lines
- 25
- 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
msm8994-sony-xperia-kitakami-karin.dts
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) 2020, Konrad Dybcio <konrad.dybcio@somainline.org>
*/
/dts-v1/;
/* As the names may imply, there is quite a bunch of duplication there. */
#include "msm8994-sony-xperia-kitakami-karin.dts"
/ {
model = "Sony Xperia Z4 Tablet (Wi-Fi)";
compatible = "sony,karin_windy", "qcom,apq8094";
chassis-type = "tablet";
/*
* This model uses the APQ variant of MSM8994 (APQ8094).
* The v1/v2/v2.1 story (from kitakami.dtsi) also applies here.
*/
qcom,msm-id = <253 0x20000>, <253 0x20001>;
};
/delete-node/ &pm8994_l1;
/delete-node/ &pm8994_l19;
Annotation
- Immediate include surface: `msm8994-sony-xperia-kitakami-karin.dts`.
- 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.