arch/arm64/boot/dts/exynos/google/gs101-raven.dts
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/exynos/google/gs101-raven.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/exynos/google/gs101-raven.dts- Extension
.dts- Size
- 784 bytes
- Lines
- 48
- 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
gs101-pixel-common.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-only
/*
* Raven Device Tree
*
* Copyright 2021-2023 Google LLC
* Copyright 2023-2025 Linaro Ltd
*/
/dts-v1/;
#include "gs101-pixel-common.dtsi"
/ {
model = "Raven";
compatible = "google,gs101-raven", "google,gs101";
};
&acpm_ipc {
pmic-2 {
regulators {
ldo4s {
regulator-name = "vdd2_uwb";
regulator-min-microvolt = <2500000>;
regulator-max-microvolt = <3300000>;
};
ldo14s {
regulator-name = "vdd3_uwb";
regulator-min-microvolt = <1600000>;
regulator-max-microvolt = <1950000>;
};
};
};
};
&cont_splash_mem {
reg = <0x0 0xfac00000 (1440 * 3120 * 4)>;
status = "okay";
};
&framebuffer0 {
width = <1440>;
height = <3120>;
stride = <(1440 * 4)>;
format = "a8r8g8b8";
status = "okay";
};
Annotation
- Immediate include surface: `gs101-pixel-common.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.