arch/arm64/boot/dts/renesas/r8a779f4.dtsi

File Facts

System

Linux kernel

Corpus path

arch/arm64/boot/dts/renesas/r8a779f4.dtsi

Extension

.dtsi

Size

482 bytes

Lines

30

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

• r8a779f0.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 Source for the R-Car S4-8 (R8A779F4) SoC
 *
 * Copyright (C) 2023 Renesas Electronics Corp.
 */

#include "r8a779f0.dtsi"

/ {
	compatible = "renesas,r8a779f4", "renesas,r8a779f0";
};

&fuse {
	nvmem-layout {
		compatible = "fixed-layout";
		#address-cells = <1>;
		#size-cells = <1>;

		ufs_tune: calib@144 {
			reg = <0x144 0x08>;
		};
	};
};

&ufs {
	nvmem-cells = <&ufs_tune>;
	nvmem-cell-names = "calibration";
};

Annotation

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