arch/arm/boot/dts/renesas/r8a7742-iwg21d-q7-dbcm-ov5640-single.dtsi
Source file repositories/reference/linux-study-clean/arch/arm/boot/dts/renesas/r8a7742-iwg21d-q7-dbcm-ov5640-single.dtsi
File Facts
- System
- Linux kernel
- Corpus path
arch/arm/boot/dts/renesas/r8a7742-iwg21d-q7-dbcm-ov5640-single.dtsi- Extension
.dtsi- Size
- 778 bytes
- Lines
- 38
- 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
dt-bindings/media/video-interfaces.h
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0
/*
* This include file ties a VIN interface with a single ov5640 sensor on
* the iWave-RZ/G1H Qseven board development platform connected with the
* camera daughter board.
*
* Copyright (C) 2020 Renesas Electronics Corp.
*/
#include <dt-bindings/media/video-interfaces.h>
#define CAM_ENABLED 1
&CAM_PARENT_I2C {
status = "okay";
ov5640@3c {
compatible = "ovti,ov5640";
reg = <0x3c>;
clocks = <&MCLK_CAM>;
clock-names = "xclk";
AVDD-supply = <®_2p8v>;
DOVDD-supply = <®_2p8v>;
DVDD-supply = <®_1p8v>;
status = "okay";
port {
CAM_EP: endpoint {
bus-width = <8>;
data-shift = <2>;
bus-type = <MEDIA_BUS_TYPE_BT656>;
pclk-sample = <1>;
remote-endpoint = <&VIN_EP>;
};
};
};
};
Annotation
- Immediate include surface: `dt-bindings/media/video-interfaces.h`.
- 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.