arch/arm/boot/dts/qcom/qcom-ipq8064-ap148.dts

File Facts

System

Linux kernel

Corpus path

arch/arm/boot/dts/qcom/qcom-ipq8064-ap148.dts

Extension

.dts

Size

519 bytes

Lines

28

Domain

Architecture Layer

Bucket

arch/arm

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

• qcom-ipq8064-v1.0.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
#include "qcom-ipq8064-v1.0.dtsi"

/ {
	model = "Qualcomm Technologies, Inc. IPQ8064/AP-148";
	compatible = "qcom,ipq8064-ap148", "qcom,ipq8064";

	soc {
		pinmux@800000 {
			buttons_pins: buttons-state {
				pins = "gpio54", "gpio65";
				function = "gpio";
				drive-strength = <2>;
				bias-pull-up;
			};
		};

		gsbi@16300000 {
			i2c@16380000 {
				status = "okay";
				clock-frequency = <200000>;
				pinctrl-0 = <&i2c4_pins>;
				pinctrl-names = "default";
			};
		};
	};
};

Annotation

• Immediate include surface: `qcom-ipq8064-v1.0.dtsi`.
• Atlas domain: Architecture Layer / arch/arm.
• 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.