arch/arm64/boot/dts/qcom/x1e80100-hp-elitebook-ultra-g1q.dts
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/qcom/x1e80100-hp-elitebook-ultra-g1q.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/qcom/x1e80100-hp-elitebook-ultra-g1q.dts- Extension
.dts- Size
- 651 bytes
- Lines
- 29
- 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
x1e80100-hp-omnibook-x14.dts
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
// SPDX-License-Identifier: BSD-3-Clause
/dts-v1/;
#include "x1e80100-hp-omnibook-x14.dts"
/ {
model = "HP EliteBook Ultra G1q";
compatible = "hp,elitebook-ultra-g1q", "qcom,x1e80100";
};
&gpu_zap_shader {
firmware-name = "qcom/x1e80100/hp/elitebook-ultra-g1q/qcdxkmsuc8380.mbn";
};
&remoteproc_adsp {
firmware-name = "qcom/x1e80100/hp/elitebook-ultra-g1q/qcadsp8380.mbn",
"qcom/x1e80100/hp/elitebook-ultra-g1q/adsp_dtbs.elf";
};
&remoteproc_cdsp {
firmware-name = "qcom/x1e80100/hp/elitebook-ultra-g1q/qccdsp8380.mbn",
"qcom/x1e80100/hp/elitebook-ultra-g1q/cdsp_dtbs.elf";
};
&sound {
model = "X1E80100-HP-ELITEBOOK-ULTRA-G1Q";
};
Annotation
- Immediate include surface: `x1e80100-hp-omnibook-x14.dts`.
- 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.