drivers/media/platform/rockchip/rkcif/rkcif-capture-mipi.h

File Facts

System

Linux kernel

Corpus path

drivers/media/platform/rockchip/rkcif/rkcif-capture-mipi.h

Extension

.h

Size

664 bytes

Lines

25

Domain

Driver Families

Bucket

drivers/media

Inferred role

Driver Families: implementation source

Status

source implementation candidate

Why This File Exists

Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

• Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• rkcif-common.h

Detected Declarations

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

Annotated Snippet

#ifndef _RKCIF_CAPTURE_MIPI_H
#define _RKCIF_CAPTURE_MIPI_H

#include "rkcif-common.h"

extern const struct rkcif_mipi_match_data rkcif_rk3568_vicap_mipi_match_data;
extern const struct rkcif_mipi_match_data rkcif_rk3588_vicap_mipi_match_data;

int rkcif_mipi_register(struct rkcif_device *rkcif);

void rkcif_mipi_unregister(struct rkcif_device *rkcif);

irqreturn_t rkcif_mipi_isr(int irq, void *ctx);

#endif

Annotation

• Immediate include surface: `rkcif-common.h`.
• Atlas domain: Driver Families / drivers/media.
• Implementation status: source implementation candidate.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.