arch/arm64/boot/dts/qcom/sc7180-trogdor-quackingstick-r0-lte.dts
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/qcom/sc7180-trogdor-quackingstick-r0-lte.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/qcom/sc7180-trogdor-quackingstick-r0-lte.dts- Extension
.dts- Size
- 887 bytes
- Lines
- 39
- 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-r0.dtssc7180-trogdor-lte-sku.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: 0x600 => 1536
* - bits 11..8: Panel ID: 0x6 (AUO)
*/
#include "sc7180-trogdor-quackingstick-r0.dts"
#include "sc7180-trogdor-lte-sku.dtsi"
/ {
model = "Google Quackingstick (rev0+) with LTE";
compatible = "google,quackingstick-sku1536", "qcom,sc7180";
};
&ap_sar_sensor {
compatible = "semtech,sx9324";
semtech,ph0-pin = <3 1 3>;
semtech,ph1-pin = <2 1 2>;
semtech,ph2-pin = <3 3 1>;
semtech,ph3-pin = <1 3 3>;
semtech,ph01-resolution = <1024>;
semtech,ph23-resolution = <1024>;
semtech,startup-sensor = <1>;
semtech,ph01-proxraw-strength = <3>;
semtech,ph23-proxraw-strength = <3>;
semtech,avg-pos-strength = <256>;
/delete-property/ svdd-supply;
vdd-supply = <&pp1800_prox>;
};
&ap_sar_sensor_i2c {
status = "okay";
};
Annotation
- Immediate include surface: `sc7180-trogdor-quackingstick-r0.dts`, `sc7180-trogdor-lte-sku.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.