drivers/media/platform/samsung/exynos4-is/fimc-is.c

File Facts

System

Linux kernel

Corpus path

drivers/media/platform/samsung/exynos4-is/fimc-is.c

Extension

.c

Size

23721 bytes

Lines

1000

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.
• 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/device.h
• linux/debugfs.h
• linux/delay.h
• linux/errno.h
• linux/firmware.h
• linux/interrupt.h
• linux/kernel.h
• linux/module.h
• linux/i2c.h
• linux/of_irq.h
• linux/of_address.h
• linux/of_graph.h
• linux/of_platform.h
• linux/platform_device.h
• linux/pm_runtime.h
• linux/slab.h
• linux/types.h
• linux/videodev2.h
• media/videobuf2-dma-contig.h
• media-dev.h
• fimc-is.h
• fimc-is-command.h
• fimc-is-errno.h
• fimc-is-i2c.h
• fimc-is-param.h
• fimc-is-regs.h

Detected Declarations

• function fimc_is_put_clocks
• function fimc_is_get_clocks
• function fimc_is_setup_clocks
• function fimc_is_enable_clocks
• function fimc_is_disable_clocks
• function fimc_is_parse_sensor_config
• function fimc_is_register_subdevs
• function for_each_compatible_node_scoped
• function fimc_is_unregister_subdevs
• function fimc_is_load_setfile
• function fimc_is_cpu_set_power
• function fimc_is_wait_event
• function fimc_is_start_firmware
• function fimc_is_alloc_cpu_memory
• function fimc_is_free_cpu_memory
• function fimc_is_load_firmware
• function fimc_is_request_firmware
• function fimc_is_general_irq_handler
• function fimc_is_irq_handler
• function fimc_is_hw_open_sensor
• function fimc_is_hw_initialize
• function fimc_is_show
• function fimc_is_debugfs_remove
• function fimc_is_debugfs_create
• function fimc_is_probe
• function fimc_is_runtime_resume
• function fimc_is_runtime_suspend
• function fimc_is_resume
• function fimc_is_suspend
• function fimc_is_remove
• function fimc_is_module_init
• function fimc_is_module_exit
• module init fimc_is_module_init

Annotated Snippet

module_init(fimc_is_module_init);
module_exit(fimc_is_module_exit);

MODULE_AUTHOR("Younghwan Joo <yhwan.joo@samsung.com>");
MODULE_AUTHOR("Sylwester Nawrocki <s.nawrocki@samsung.com>");
MODULE_DESCRIPTION("Samsung EXYNOS4x12 FIMC-IS (Imaging Subsystem) driver");
MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `linux/device.h`, `linux/debugfs.h`, `linux/delay.h`, `linux/errno.h`, `linux/firmware.h`, `linux/interrupt.h`, `linux/kernel.h`, `linux/module.h`.
• Detected declarations: `function fimc_is_put_clocks`, `function fimc_is_get_clocks`, `function fimc_is_setup_clocks`, `function fimc_is_enable_clocks`, `function fimc_is_disable_clocks`, `function fimc_is_parse_sensor_config`, `function fimc_is_register_subdevs`, `function for_each_compatible_node_scoped`, `function fimc_is_unregister_subdevs`, `function fimc_is_load_setfile`.
• Atlas domain: Driver Families / drivers/media.
• Implementation status: integration 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.