arch/arm64/boot/dts/qcom/sm4250.dtsi
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/qcom/sm4250.dtsi
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/qcom/sm4250.dtsi- Extension
.dtsi- Size
- 1137 bytes
- Lines
- 78
- 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
sm6115.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+ OR BSD-3-Clause)
/*
* Copyright (c) 2021, Iskren Chernev <iskren.chernev@gmail.com>
*/
#include "sm6115.dtsi"
&cpu0 {
compatible = "qcom,kryo240";
};
&cpu1 {
compatible = "qcom,kryo240";
};
&cpu2 {
compatible = "qcom,kryo240";
};
&cpu3 {
compatible = "qcom,kryo240";
};
&cpu4 {
compatible = "qcom,kryo240";
};
&cpu5 {
compatible = "qcom,kryo240";
};
&cpu6 {
compatible = "qcom,kryo240";
};
&cpu7 {
compatible = "qcom,kryo240";
};
&lpass_tlmm {
compatible = "qcom,sm4250-lpass-lpi-pinctrl";
gpio-ranges = <&lpass_tlmm 0 0 27>;
lpi_i2s2_active: lpi-i2s2-active-state {
sck-pins {
pins = "gpio10";
function = "i2s2_clk";
bias-disable;
drive-strength = <8>;
output-high;
};
ws-pins {
pins = "gpio11";
function = "i2s2_ws";
bias-disable;
drive-strength = <8>;
output-high;
};
data-pins {
pins = "gpio12";
function = "i2s2_data";
bias-disable;
drive-strength = <8>;
output-high;
};
ext-mclk1-pins {
pins = "gpio18";
Annotation
- Immediate include surface: `sm6115.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.