drivers/media/platform/samsung/exynos4-is/fimc-is-sensor.h

File Facts

System

Linux kernel

Corpus path

drivers/media/platform/samsung/exynos4-is/fimc-is-sensor.h

Extension

.h

Size

1316 bytes

Lines

54

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/of.h
• linux/types.h

Detected Declarations

• struct sensor_drv_data
• struct fimc_is_sensor
• enum fimc_is_sensor_id

Annotated Snippet

struct sensor_drv_data {
	enum fimc_is_sensor_id id;
	/* sensor open timeout in ms */
	unsigned short open_timeout;
};

/**
 * struct fimc_is_sensor - fimc-is sensor data structure
 * @drvdata: a pointer to the sensor's parameters data structure
 * @i2c_bus: ISP I2C bus index (0...1)
 * @test_pattern: true to enable video test pattern
 */
struct fimc_is_sensor {
	const struct sensor_drv_data *drvdata;
	unsigned int i2c_bus;
	u8 test_pattern;
};

const struct sensor_drv_data *fimc_is_sensor_get_drvdata(
				struct device_node *node);

#endif /* FIMC_IS_SENSOR_H_ */

Annotation

• Immediate include surface: `linux/of.h`, `linux/types.h`.
• Detected declarations: `struct sensor_drv_data`, `struct fimc_is_sensor`, `enum fimc_is_sensor_id`.
• Atlas domain: Driver Families / drivers/media.
• Implementation status: source 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.