arch/arm/boot/dts/synaptics/berlin2-sony-nsz-gs7.dts

File Facts

System

Linux kernel

Corpus path

arch/arm/boot/dts/synaptics/berlin2-sony-nsz-gs7.dts

Extension

.dts

Size

743 bytes

Lines

44

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

• berlin2.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 MIT)
/*
 * Device Tree file for Sony NSZ-GS7
 *
 * Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
 */

/dts-v1/;

#include "berlin2.dtsi"

/ {
	model = "Sony NSZ-GS7";
	compatible = "sony,nsz-gs7", "marvell,berlin2", "marvell,berlin";

	chosen {
		bootargs = "earlyprintk";
		stdout-path = "serial0:115200n8";
	};

	memory@0 {
		device_type = "memory";
		reg = <0x00000000 0x40000000>; /* 1 GB */
	};
};

&ahci { status = "okay"; };

&eth1 { status = "okay"; };

/* Unpopulated SATA plug on solder side */
&sata0 { status = "okay"; };

&sata_phy { status = "okay"; };

/* Samsung M8G2FA 8GB eMMC */
&sdhci2 {
	non-removable;
	bus-width = <8>;
	status = "okay";
};

&uart0 { status = "okay"; };

Annotation

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