arch/arm64/boot/dts/qcom/sc7280-herobrine-villager-r1-lte.dts

File Facts

System

Linux kernel

Corpus path

arch/arm64/boot/dts/qcom/sc7280-herobrine-villager-r1-lte.dts

Extension

.dts

Size

336 bytes

Lines

17

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

• sc7280-herobrine-villager-r1.dtsi
• sc7280-herobrine-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 Villager board device tree source
 *
 * Copyright 2022 Google LLC.
 */

/dts-v1/;

#include "sc7280-herobrine-villager-r1.dtsi"
#include "sc7280-herobrine-lte-sku.dtsi"

/ {
	model = "Google Villager (rev1+) with LTE";
	compatible = "google,villager-sku512", "qcom,sc7280";
};

Annotation

• Immediate include surface: `sc7280-herobrine-villager-r1.dtsi`, `sc7280-herobrine-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.