arch/arm64/boot/dts/qcom/sm8650.dtsi
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/qcom/sm8650.dtsi
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/qcom/sm8650.dtsi- Extension
.dtsi- Size
- 203719 bytes
- Lines
- 8609
- 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
dt-bindings/clock/qcom,dsi-phy-28nm.hdt-bindings/clock/qcom,rpmh.hdt-bindings/clock/qcom,sm8650-camcc.hdt-bindings/clock/qcom,sm8650-dispcc.hdt-bindings/clock/qcom,sm8650-gcc.hdt-bindings/clock/qcom,sm8650-gpucc.hdt-bindings/clock/qcom,sm8650-tcsr.hdt-bindings/clock/qcom,sm8650-videocc.hdt-bindings/dma/qcom-gpi.hdt-bindings/firmware/qcom,scm.hdt-bindings/gpio/gpio.hdt-bindings/interconnect/qcom,icc.hdt-bindings/interconnect/qcom,sm8650-rpmh.hdt-bindings/interconnect/qcom,osm-l3.hdt-bindings/interrupt-controller/arm-gic.hdt-bindings/mailbox/qcom-ipcc.hdt-bindings/phy/phy-qcom-qmp.hdt-bindings/power/qcom,rpmhpd.hdt-bindings/power/qcom-rpmpd.hdt-bindings/reset/qcom,sm8650-gpucc.hdt-bindings/soc/qcom,gpr.hdt-bindings/soc/qcom,rpmh-rsc.hdt-bindings/sound/qcom,q6dsp-lpass-ports.hdt-bindings/thermal/thermal.h
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, Linaro Limited
*/
#include <dt-bindings/clock/qcom,dsi-phy-28nm.h>
#include <dt-bindings/clock/qcom,rpmh.h>
#include <dt-bindings/clock/qcom,sm8650-camcc.h>
#include <dt-bindings/clock/qcom,sm8650-dispcc.h>
#include <dt-bindings/clock/qcom,sm8650-gcc.h>
#include <dt-bindings/clock/qcom,sm8650-gpucc.h>
#include <dt-bindings/clock/qcom,sm8650-tcsr.h>
#include <dt-bindings/clock/qcom,sm8650-videocc.h>
#include <dt-bindings/dma/qcom-gpi.h>
#include <dt-bindings/firmware/qcom,scm.h>
#include <dt-bindings/gpio/gpio.h>
#include <dt-bindings/interconnect/qcom,icc.h>
#include <dt-bindings/interconnect/qcom,sm8650-rpmh.h>
#include <dt-bindings/interconnect/qcom,osm-l3.h>
#include <dt-bindings/interrupt-controller/arm-gic.h>
#include <dt-bindings/mailbox/qcom-ipcc.h>
#include <dt-bindings/phy/phy-qcom-qmp.h>
#include <dt-bindings/power/qcom,rpmhpd.h>
#include <dt-bindings/power/qcom-rpmpd.h>
#include <dt-bindings/reset/qcom,sm8650-gpucc.h>
#include <dt-bindings/soc/qcom,gpr.h>
#include <dt-bindings/soc/qcom,rpmh-rsc.h>
#include <dt-bindings/sound/qcom,q6dsp-lpass-ports.h>
#include <dt-bindings/thermal/thermal.h>
/ {
interrupt-parent = <&intc>;
#address-cells = <2>;
#size-cells = <2>;
chosen { };
clocks {
xo_board: xo-board {
compatible = "fixed-clock";
#clock-cells = <0>;
};
sleep_clk: sleep-clk {
compatible = "fixed-clock";
#clock-cells = <0>;
};
bi_tcxo_div2: bi-tcxo-div2-clk {
compatible = "fixed-factor-clock";
#clock-cells = <0>;
clocks = <&rpmhcc RPMH_CXO_CLK>;
clock-mult = <1>;
clock-div = <2>;
};
bi_tcxo_ao_div2: bi-tcxo-ao-div2-clk {
compatible = "fixed-factor-clock";
#clock-cells = <0>;
clocks = <&rpmhcc RPMH_CXO_CLK_A>;
clock-mult = <1>;
clock-div = <2>;
};
};
cpus {
#address-cells = <2>;
Annotation
- Immediate include surface: `dt-bindings/clock/qcom,dsi-phy-28nm.h`, `dt-bindings/clock/qcom,rpmh.h`, `dt-bindings/clock/qcom,sm8650-camcc.h`, `dt-bindings/clock/qcom,sm8650-dispcc.h`, `dt-bindings/clock/qcom,sm8650-gcc.h`, `dt-bindings/clock/qcom,sm8650-gpucc.h`, `dt-bindings/clock/qcom,sm8650-tcsr.h`, `dt-bindings/clock/qcom,sm8650-videocc.h`.
- 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.