arch/arm64/boot/dts/qcom/sm7225.dtsi

File Facts

System

Linux kernel

Corpus path

arch/arm64/boot/dts/qcom/sm7225.dtsi

Extension

.dtsi

Size

893 bytes

Lines

36

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

• sm6350.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) 2021, Luca Weiss <luca@z3ntu.xyz>
 */

#include "sm6350.dtsi"

/* SM7225 uses Kryo 570 instead of Kryo 560 */
&cpu0 { compatible = "qcom,kryo570"; };
&cpu1 { compatible = "qcom,kryo570"; };
&cpu2 { compatible = "qcom,kryo570"; };
&cpu3 { compatible = "qcom,kryo570"; };
&cpu4 { compatible = "qcom,kryo570"; };
&cpu5 { compatible = "qcom,kryo570"; };
&cpu6 { compatible = "qcom,kryo570"; };
&cpu7 { compatible = "qcom,kryo570"; };

&cpu0_opp_table {
	opp-1804800000 {
		opp-hz = /bits/ 64 <1804800000>;
		opp-peak-kBps = <(1804000 * 4 * 2 * 2) (1459200 * 16 * 2)>;
	};
};

&cpu6_opp_table {
	opp-2131200000 {
		opp-hz = /bits/ 64 <2131200000>;
		opp-peak-kBps = <(2092000 * 4 * 2 * 2) (1459200 * 16 * 2)>;
	};

	opp-2208000000 {
		opp-hz = /bits/ 64 <2208000000>;
		opp-peak-kBps = <(2092000 * 4 * 2 * 2) (1459200 * 16 * 2)>;
	};
};

Annotation

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