drivers/media/i2c/cvs/core.c

File Facts

System

Linux kernel

Corpus path

drivers/media/i2c/cvs/core.c

Extension

.c

Size

26519 bytes

Lines

1044

Domain

Driver Families

Bucket

drivers/media

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.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/acpi.h
• linux/cleanup.h
• linux/delay.h
• linux/device.h
• linux/gpio/consumer.h
• linux/i2c.h
• linux/init.h
• linux/interrupt.h
• linux/jiffies.h
• linux/mod_devicetable.h
• linux/module.h
• linux/pci.h
• linux/platform_device.h
• linux/pm_runtime.h
• linux/slab.h
• linux/time64.h
• linux/workqueue.h
• media/ipu-bridge.h
• media/ipu6-pci-table.h
• icvs.h

Detected Declarations

• function cvs_set_quirks
• function cvs_read_i2c
• function cvs_write_i2c
• function cvs_checksum
• function cvs_schedule_and_wait
• function devices
• function cvs_config_mipi
• function cvs_get_device_state
• function cvs_get_device_caps
• function cvs_hw_init
• function cvs_irq_handler
• function cvs_reset
• function cvs_recv
• function waits
• function cvs_set_link_owner
• function features
• function cvs_core_probe
• function cvs_probe
• function cvs_core_remove
• function cvs_remove
• function cvs_suspend
• function cvs_resume
• function IPU
• function cvs_runtime_suspend
• function cvs_platform_probe
• function cvs_platform_remove
• function cvs_init
• function cvs_exit
• module init cvs_init

Annotated Snippet

module_init(cvs_init);
module_exit(cvs_exit);

MODULE_IMPORT_NS("INTEL_IPU_BRIDGE");
MODULE_AUTHOR("Miguel Vadillo <miguel.vadillo@intel.com>");
MODULE_DESCRIPTION("Intel Vision Sensing Controller driver");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/acpi.h`, `linux/cleanup.h`, `linux/delay.h`, `linux/device.h`, `linux/gpio/consumer.h`, `linux/i2c.h`, `linux/init.h`, `linux/interrupt.h`.
• Detected declarations: `function cvs_set_quirks`, `function cvs_read_i2c`, `function cvs_write_i2c`, `function cvs_checksum`, `function cvs_schedule_and_wait`, `function devices`, `function cvs_config_mipi`, `function cvs_get_device_state`, `function cvs_get_device_caps`, `function cvs_hw_init`.
• Atlas domain: Driver Families / drivers/media.
• Implementation status: integration 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.