arch/arm64/boot/dts/qcom/x1p42100-hp-omnibook-x14.dts

File Facts

System

Linux kernel

Corpus path

arch/arm64/boot/dts/qcom/x1p42100-hp-omnibook-x14.dts

Extension

.dts

Size

724 bytes

Lines

34

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

• purwa.dtsi
• hamoa-pmics.dtsi
• x1-hp-omnibook-x14.dtsi

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 "purwa.dtsi"
#include "hamoa-pmics.dtsi"
#include "x1-hp-omnibook-x14.dtsi"
/delete-node/ &pmc8380_6;
/delete-node/ &pmc8380_6_thermal;

/ {
	model = "HP Omnibook X 14-fe1";
	compatible = "hp,omnibook-x14-fe1", "qcom,x1p42100";
	chassis-type = "laptop";
};

&gpu_zap_shader {
	firmware-name = "qcom/x1p42100/hp/omnibook-x14/qcdxkmsucpurwa.mbn";
};

&remoteproc_adsp {
	firmware-name = "qcom/x1p42100/hp/omnibook-x14/qcadsp8380.mbn",
			"qcom/x1p42100/hp/omnibook-x14/adsp_dtbs.elf";

	status = "okay";
};

&remoteproc_cdsp {
	firmware-name = "qcom/x1p42100/hp/omnibook-x14/qccdsp8380.mbn",
			"qcom/x1p42100/hp/omnibook-x14/cdsp_dtbs.elf";

	status = "okay";
};

Annotation

• Immediate include surface: `purwa.dtsi`, `hamoa-pmics.dtsi`, `x1-hp-omnibook-x14.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.