fimc_sensor_notify(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… 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 be S5P_FIMC_TX_END_NOTIFY.
  • arg β€” pointer to an u32 type 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 πŸ’–


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