arch/arm64/boot/dts/renesas/rzg2-advantech-idk-1110wr-panel.dtsi

File Facts

System

Linux kernel

Corpus path

arch/arm64/boot/dts/renesas/rzg2-advantech-idk-1110wr-panel.dtsi

Extension

.dtsi

Size

734 bytes

Lines

42

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

• No C-style include directives detected by the generator.

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

// SPDX-License-Identifier: GPL-2.0
/*
 * Device Tree Source for the Advantech idk-1110wr LVDS panel connected
 * to RZ/G2 boards
 *
 * Copyright (C) 2019 Renesas Electronics Corp.
 */

/ {
	panel-lvds {
		compatible = "advantech,idk-1110wr", "panel-lvds";

		width-mm = <223>;
		height-mm = <125>;

		data-mapping = "jeida-24";

		panel-timing {
			/* 1024x600 @60Hz */
			clock-frequency = <51200000>;
			hactive = <1024>;
			vactive = <600>;
			hsync-len = <240>;
			hfront-porch = <40>;
			hback-porch = <40>;
			vfront-porch = <15>;
			vback-porch = <10>;
			vsync-len = <10>;
		};

		port {
			panel_in: endpoint {
				remote-endpoint = <&lvds_connector>;
			};
		};
	};
};

&lvds_connector {
	remote-endpoint = <&panel_in>;
};

Annotation

• 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.