arch/arm64/boot/dts/qcom/ipq6018-mp5496.dtsi

File Facts

System

Linux kernel

Corpus path

arch/arm64/boot/dts/qcom/ipq6018-mp5496.dtsi

Extension

.dtsi

Size

752 bytes

Lines

45

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

• ipq6018.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+ OR BSD-3-Clause)
/*
 * ipq6018-mp5496.dtsi describes common properties (e.g. regulators) that
 * apply to most devices that make use of the IPQ6018 SoC and MP5496 PMIC.
 */

#include "ipq6018.dtsi"

&cpu0 {
	cpu-supply = <&mp5496_s2>;
};

&cpu1 {
	cpu-supply = <&mp5496_s2>;
};

&cpu2 {
	cpu-supply = <&mp5496_s2>;
};

&cpu3 {
	cpu-supply = <&mp5496_s2>;
};

&rpm_requests {
	regulators {
		compatible = "qcom,rpm-mp5496-regulators";

		mp5496_s2: s2 {
			regulator-min-microvolt = <725000>;
			regulator-max-microvolt = <1062500>;
			regulator-always-on;
		};

		mp5496_l2: l2 {
			regulator-min-microvolt = <1800000>;
			regulator-max-microvolt = <3300000>;
		};
	};
};

&sdhc {
	vqmmc-supply = <&mp5496_l2>;
};

Annotation

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