arch/arm64/boot/dts/qcom/sc7180-trogdor-quackingstick-r0.dts
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/qcom/sc7180-trogdor-quackingstick-r0.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/qcom/sc7180-trogdor-quackingstick-r0.dts- Extension
.dts- Size
- 602 bytes
- Lines
- 27
- 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
sc7180-trogdor-quackingstick.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 MIT)
/*
* Google Quackingstick board device tree source
*
* Copyright 2021 Google LLC.
*
* SKU: 0x601 => 1537
* - bits 11..8: Panel ID: 0x6 (AUO)
*/
#include "sc7180-trogdor-quackingstick.dtsi"
/ {
model = "Google Quackingstick (rev0+)";
compatible = "google,quackingstick-sku1537", "qcom,sc7180";
};
&mdss_dsi0_phy {
qcom,phy-rescode-offset-top = /bits/ 8 <(-13) (-13) (-13) (-13) (-13)>;
qcom,phy-rescode-offset-bot = /bits/ 8 <(-13) (-13) (-13) (-13) (-13)>;
qcom,phy-drive-ldo-level = <375>;
};
&panel {
compatible = "auo,b101uan08.3";
};
Annotation
- Immediate include surface: `sc7180-trogdor-quackingstick.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.