drivers/staging/media/atomisp/pci/atomisp_v4l2.c

File Facts

System

Linux kernel

Corpus path

drivers/staging/media/atomisp/pci/atomisp_v4l2.c

Extension

.c

Size

44420 bytes

Lines

1514

Domain

Driver Families

Bucket

drivers/staging

Inferred role

Driver Families: operation-table or driver-model contract

Status

pattern 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.
• Defines an operation table; this is where Linux turns generic core objects into subsystem-specific behavior.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• 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/module.h
• linux/pci.h
• linux/pm_domain.h
• linux/pm_runtime.h
• linux/pm_qos.h
• linux/timer.h
• linux/delay.h
• linux/dmi.h
• linux/interrupt.h
• linux/bits.h
• linux/string_choices.h
• media/v4l2-fwnode.h
• asm/iosf_mbi.h
• ../../include/linux/atomisp_gmin_platform.h
• atomisp_cmd.h
• atomisp_common.h
• atomisp_fops.h
• atomisp_ioctl.h
• atomisp_internal.h
• atomisp-regs.h
• atomisp_dfs_tables.h
• hmm/hmm.h
• atomisp_trace_event.h
• sh_css_firmware.h
• device_access.h

Detected Declarations

• function atomisp_video_init
• function atomisp_video_unregister
• function atomisp_save_iunit_reg
• function atomisp_restore_iunit_reg
• function atomisp_mrfld_pre_power_down
• function punit_ddr_dvfs_enable
• function atomisp_mrfld_power
• function atomisp_power_off
• function atomisp_power_on
• function atomisp_suspend
• function atomisp_resume
• function atomisp_csi_lane_config
• function atomisp_subdev_probe
• function atomisp_unregister_entities
• function atomisp_register_entities
• function atomisp_init_sensor
• function atomisp_register_device_nodes
• function atomisp_initialize_modules
• function atomisp_uninitialize_modules
• function atomisp_load_firmware
• function atomisp_pm_init
• function atomisp_pm_uninit
• function atomisp_pci_probe
• function atomisp_pci_remove

Annotated Snippet

static struct pci_driver atomisp_pci_driver = {
	.name = "atomisp-isp2",
	.id_table = atomisp_pci_tbl,
	.probe = atomisp_pci_probe,
	.remove = atomisp_pci_remove,
};

module_pci_driver(atomisp_pci_driver);

MODULE_AUTHOR("Wen Wang <wen.w.wang@intel.com>");
MODULE_AUTHOR("Xiaolin Zhang <xiaolin.zhang@intel.com>");
MODULE_LICENSE("GPL");
MODULE_DESCRIPTION("Intel ATOM Platform ISP Driver");
MODULE_IMPORT_NS("INTEL_IPU_BRIDGE");
MODULE_IMPORT_NS("INTEL_INT3472_DISCRETE");

Annotation

• Immediate include surface: `linux/module.h`, `linux/pci.h`, `linux/pm_domain.h`, `linux/pm_runtime.h`, `linux/pm_qos.h`, `linux/timer.h`, `linux/delay.h`, `linux/dmi.h`.
• Detected declarations: `function atomisp_video_init`, `function atomisp_video_unregister`, `function atomisp_save_iunit_reg`, `function atomisp_restore_iunit_reg`, `function atomisp_mrfld_pre_power_down`, `function punit_ddr_dvfs_enable`, `function atomisp_mrfld_power`, `function atomisp_power_off`, `function atomisp_power_on`, `function atomisp_suspend`.
• Atlas domain: Driver Families / drivers/staging.
• Implementation status: pattern implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
• 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.