arch/arm/boot/dts/mediatek/mt6589-fairphone-fp1.dts

File Facts

System

Linux kernel

Corpus path

arch/arm/boot/dts/mediatek/mt6589-fairphone-fp1.dts

Extension

.dts

Size

477 bytes

Lines

31

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

• mt6589.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
/*
 * Copyright (c) 2021, Luca Weiss <luca@z3ntu.xyz>
 */

/dts-v1/;
#include "mt6589.dtsi"

/ {
	model = "Fairphone 1";
	compatible = "fairphone,fp1", "mediatek,mt6589";

	chosen {
		stdout-path = &uart3;
	};

	memory@80000000 {
		device_type = "memory";
		reg = <0x80000000 0x40000000>;
	};
};

&cpus {
	/* SMP is not stable on this board, makes the kernel panic */
	/delete-property/ enable-method;
};

&uart3 {
	status = "okay";
};

Annotation

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