arch/arm64/boot/dts/qcom/msm8998-asus-novago-tp370ql.dts

File Facts

System

Linux kernel

Corpus path

arch/arm64/boot/dts/qcom/msm8998-asus-novago-tp370ql.dts

Extension

.dts

Size

749 bytes

Lines

42

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

• msm8998-clamshell.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
/* Copyright (c) 2019, Jeffrey Hugo. All rights reserved. */

/dts-v1/;

#include "msm8998-clamshell.dtsi"

/ {
	model = "Asus NovaGo TP370QL";
	compatible = "asus,novago-tp370ql", "qcom,msm8998";
	chassis-type = "convertible";
};

&blsp1_i2c6 {
	status = "okay";

	touchpad@15 {
		compatible = "hid-over-i2c";
		reg = <0x15>;
		pinctrl-names = "default";
		pinctrl-0 = <&touchpad>;

		interrupt-parent = <&tlmm>;
		interrupts = <123 IRQ_TYPE_LEVEL_LOW>;

		hid-descr-addr = <0x0001>;
	};

	keyboard@3a {
		compatible = "hid-over-i2c";
		reg = <0x3a>;
		interrupt-parent = <&tlmm>;
		interrupts = <37 IRQ_TYPE_LEVEL_LOW>;

		hid-descr-addr = <0x0001>;
	};
};

&sdhc2 {
	cd-gpios = <&tlmm 95 GPIO_ACTIVE_HIGH>;
};

Annotation

• Immediate include surface: `msm8998-clamshell.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.