fimc_sensor_notify(9)
π
fimc_sensor_notify(9) π
okay so bestie, this page comes from the Kernel API Manual, and it's giving v4l2_device notification from a sensor subdev energy. lowkey niche, highkey iconic. β¨
πΈ NAME πΈ
fimc_sensor_notify β v4l2_device notification from a sensor subdev π
β¨ SYNOPSIS β¨
void fimc_sensor_notify (struct v4l2_subdev *sd , unsigned int
notification , void *arg );
π ARGUMENTS π
sdβ pointer to a subdev generating the notification.notificationβ the notification type; it must beS5P_FIMC_TX_END_NOTIFY.argβ pointer to anu32type integer that stores the frame payload value.
π¦ DESCRIPTION π¦
okay so this is the End Of Frame notification sent by a sensor subdev in its still capture mode. π¦
The way it works: if there is only a single VSYNC generated by the sensor at the beginning of a frame transmission, FIMC does not issue the LastIrq (end of frame) interrupt. and this notification is used to complete the frame capture and returning a buffer to user-space. no cap, that's the whole vibe.
Subdev drivers should call this notification from their last 'End of frame capture' interrupt. π
π SEE ALSO π
- Kernel file
./drivers/media/platform/samsung/exynos4-is/fimc-capture.c fimc_capture_config_update(9)fimc_pipeline_try_format(9)fimc_get_sensor_frame_desc(9)fimc_pipeline_validate(9)
mwah π β this cutie is sourced from ./drivers/media/platform/samsu..., dated October 2026, and its page name is fimc_sensor_notify(9). byeee π«Ά
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms