arch/arm64/boot/dts/qcom/sc7180-trogdor-lazor-r9-kb.dts
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/qcom/sc7180-trogdor-lazor-r9-kb.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/qcom/sc7180-trogdor-lazor-r9-kb.dts- Extension
.dts- Size
- 469 bytes
- Lines
- 24
- 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.dtsisc7180-trogdor-parade-ps8640.dtsisc7180-trogdor-lazor.dtsisc7180-trogdor-rt5682i-sku.dtsisc7180-lite.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 Lazor board device tree source
*
* Copyright 2020 Google LLC.
*/
/dts-v1/;
#include "sc7180-trogdor.dtsi"
#include "sc7180-trogdor-parade-ps8640.dtsi"
#include "sc7180-trogdor-lazor.dtsi"
#include "sc7180-trogdor-rt5682i-sku.dtsi"
#include "sc7180-lite.dtsi"
/ {
model = "Google Lazor (rev9) with KB Backlight";
compatible = "google,lazor-rev9-sku2", "qcom,sc7180";
};
&pwmleds {
status = "okay";
};
Annotation
- Immediate include surface: `sc7180-trogdor.dtsi`, `sc7180-trogdor-parade-ps8640.dtsi`, `sc7180-trogdor-lazor.dtsi`, `sc7180-trogdor-rt5682i-sku.dtsi`, `sc7180-lite.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.