arch/arm/boot/dts/qcom/qcom-msm8974pro-samsung-klte.dts

File Facts

System

Linux kernel

Corpus path

arch/arm/boot/dts/qcom/qcom-msm8974pro-samsung-klte.dts

Extension

.dts

Size

394 bytes

Lines

17

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-msm8974pro-samsung-klte-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
#include "qcom-msm8974pro-samsung-klte-common.dtsi"

/ {
	model = "Samsung Galaxy S5";
	compatible = "samsung,klte", "qcom,msm8974pro", "qcom,msm8974";
};

&i2c_led_gpio {
	scl-gpios = <&tlmm 121 (GPIO_ACTIVE_HIGH | GPIO_OPEN_DRAIN)>;
	sda-gpios = <&tlmm 120 (GPIO_ACTIVE_HIGH | GPIO_OPEN_DRAIN)>;
};

&i2c_led_gpioex_pins {
	pins = "gpio120", "gpio121";
};

Annotation

• Immediate include surface: `qcom-msm8974pro-samsung-klte-common.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.