7.63. ioctl VIDIOC_SUBSCRIBE_EVENT, VIDIOC_UNSUBSCRIBE_EVENT¶
VIDIOC_SUBSCRIBE_EVENT - VIDIOC_UNSUBSCRIBE_EVENT - Subscribe or unsubscribe event
ioctl(int fd, VIDIOC_SUBSCRIBE_EVENT, struct v4l2_event_subscription *argp)¶
ioctl(int fd, VIDIOC_UNSUBSCRIBE_EVENT, struct v4l2_event_subscription *argp)¶
- File descriptor returned by open().
- Pointer to struct
Subscribe or unsubscribe V4L2 event. Subscribed events are dequeued by using the ioctl VIDIOC_DQEVENT ioctl.
Type of the event, see Event Types.
||ID of the event source. If there is no ID associated with the event source, then set this to 0. Whether or not an event needs an ID depends on the event type.|
||Event flags, see Event Flags.|
||Reserved for future extensions. Drivers and applications must set the array to zero.|
||0x0001||When this event is subscribed an initial event will be sent
containing the current status. This only makes sense for events
that are triggered by a status change such as
If set, then events directly caused by an ioctl will also be sent to the filehandle that called that ioctl. For example, changing a control using VIDIOC_S_CTRL will cause a V4L2_EVENT_CTRL to be sent back to that same filehandle. Normally such events are suppressed to prevent feedback loops where an application changes a control to a one value and then another, and then receives an event telling it that that control has changed to the first value.
Since it can’t tell whether that event was caused by another application or by the VIDIOC_S_CTRL call it is hard to decide whether to set the control to the value in the event, or ignore it.
Think carefully when you set this flag so you won’t get into situations like that.
7.63.5. Return Value¶
On success 0 is returned, on error -1 and the
errno variable is set
appropriately. The generic error codes are described at the
Generic Error Codes chapter.