drivers/staging/media/imx/imx-media-of.c

File Facts

System

Linux kernel

Corpus path

drivers/staging/media/imx/imx-media-of.c

Extension

.c

Size

1587 bytes

Lines

71

Domain

Driver Families

Bucket

drivers/staging

Inferred role

Driver Families: exported/initcall integration point

Status

integration 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.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/of_platform.h
• media/v4l2-ctrls.h
• media/v4l2-device.h
• media/v4l2-fwnode.h
• media/v4l2-subdev.h
• media/videobuf2-dma-contig.h
• linux/of_graph.h
• video/imx-ipu-v3.h
• imx-media.h

Detected Declarations

• function Copyright
• function imx_media_add_of_subdevs
• export imx_media_add_of_subdevs

Annotated Snippet

if (ret) {
			/* unavailable or already added is not an error */
			if (ret == -ENODEV || ret == -EEXIST)
				continue;

			/* other error, can't continue */
			return ret;
		}
	}

	return 0;
}
EXPORT_SYMBOL_GPL(imx_media_add_of_subdevs);

Annotation

• Immediate include surface: `linux/of_platform.h`, `media/v4l2-ctrls.h`, `media/v4l2-device.h`, `media/v4l2-fwnode.h`, `media/v4l2-subdev.h`, `media/videobuf2-dma-contig.h`, `linux/of_graph.h`, `video/imx-ipu-v3.h`.
• Detected declarations: `function Copyright`, `function imx_media_add_of_subdevs`, `export imx_media_add_of_subdevs`.
• Atlas domain: Driver Families / drivers/staging.
• Implementation status: integration implementation candidate.

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.