1 <refentry id="vidioc-dqevent">
3 <refentrytitle>ioctl VIDIOC_DQEVENT</refentrytitle>
8 <refname>VIDIOC_DQEVENT</refname>
9 <refpurpose>Dequeue event</refpurpose>
15 <funcdef>int <function>ioctl</function></funcdef>
16 <paramdef>int <parameter>fd</parameter></paramdef>
17 <paramdef>int <parameter>request</parameter></paramdef>
18 <paramdef>struct v4l2_event
19 *<parameter>argp</parameter></paramdef>
25 <title>Arguments</title>
29 <term><parameter>fd</parameter></term>
35 <term><parameter>request</parameter></term>
37 <para>VIDIOC_DQEVENT</para>
41 <term><parameter>argp</parameter></term>
50 <title>Description</title>
52 <para>Dequeue an event from a video device. No input is required
53 for this ioctl. All the fields of the &v4l2-event; structure are
54 filled by the driver. The file handle will also receive exceptions
55 which the application may get by e.g. using the select system
58 <table frame="none" pgwide="1" id="v4l2-event">
59 <title>struct <structname>v4l2_event</structname></title>
65 <entry><structfield>type</structfield></entry>
67 <entry>Type of the event, see <xref linkend="event-type" />.</entry>
71 <entry><structfield>u</structfield></entry>
77 <entry>&v4l2-event-vsync;</entry>
78 <entry><structfield>vsync</structfield></entry>
79 <entry>Event data for event <constant>V4L2_EVENT_VSYNC</constant>.
84 <entry>&v4l2-event-ctrl;</entry>
85 <entry><structfield>ctrl</structfield></entry>
86 <entry>Event data for event <constant>V4L2_EVENT_CTRL</constant>.
91 <entry>&v4l2-event-frame-sync;</entry>
92 <entry><structfield>frame_sync</structfield></entry>
93 <entry>Event data for event
94 <constant>V4L2_EVENT_FRAME_SYNC</constant>.</entry>
98 <entry>&v4l2-event-motion-det;</entry>
99 <entry><structfield>motion_det</structfield></entry>
100 <entry>Event data for event V4L2_EVENT_MOTION_DET.</entry>
104 <entry>&v4l2-event-src-change;</entry>
105 <entry><structfield>src_change</structfield></entry>
106 <entry>Event data for event V4L2_EVENT_SOURCE_CHANGE.</entry>
111 <entry><structfield>data</structfield>[64]</entry>
112 <entry>Event data. Defined by the event type. The union
113 should be used to define easily accessible type for
118 <entry><structfield>pending</structfield></entry>
120 <entry>Number of pending events excluding this one.</entry>
124 <entry><structfield>sequence</structfield></entry>
126 <entry>Event sequence number. The sequence number is
127 incremented for every subscribed event that takes place.
128 If sequence numbers are not contiguous it means that
129 events have been lost.
133 <entry>struct timespec</entry>
134 <entry><structfield>timestamp</structfield></entry>
136 <entry>Event timestamp.</entry>
140 <entry><structfield>id</structfield></entry>
142 <entry>The ID associated with the event source. If the event does not
143 have an associated ID (this depends on the event type), then this
148 <entry><structfield>reserved</structfield>[8]</entry>
150 <entry>Reserved for future extensions. Drivers must set
151 the array to zero.</entry>
157 <table frame="none" pgwide="1" id="event-type">
158 <title>Event Types</title>
163 <entry><constant>V4L2_EVENT_ALL</constant></entry>
165 <entry>All events. V4L2_EVENT_ALL is valid only for
166 VIDIOC_UNSUBSCRIBE_EVENT for unsubscribing all events at once.
170 <entry><constant>V4L2_EVENT_VSYNC</constant></entry>
172 <entry>This event is triggered on the vertical sync.
173 This event has a &v4l2-event-vsync; associated with it.
177 <entry><constant>V4L2_EVENT_EOS</constant></entry>
179 <entry>This event is triggered when the end of a stream is reached.
180 This is typically used with MPEG decoders to report to the application
181 when the last of the MPEG stream has been decoded.
185 <entry><constant>V4L2_EVENT_CTRL</constant></entry>
187 <entry><para>This event requires that the <structfield>id</structfield>
188 matches the control ID from which you want to receive events.
189 This event is triggered if the control's value changes, if a
190 button control is pressed or if the control's flags change.
191 This event has a &v4l2-event-ctrl; associated with it. This struct
192 contains much of the same information as &v4l2-queryctrl; and
193 &v4l2-control;.</para>
195 <para>If the event is generated due to a call to &VIDIOC-S-CTRL; or
196 &VIDIOC-S-EXT-CTRLS;, then the event will <emphasis>not</emphasis> be sent to
197 the file handle that called the ioctl function. This prevents
198 nasty feedback loops. If you <emphasis>do</emphasis> want to get the
199 event, then set the <constant>V4L2_EVENT_SUB_FL_ALLOW_FEEDBACK</constant>
203 <para>This event type will ensure that no information is lost when
204 more events are raised than there is room internally. In that
205 case the &v4l2-event-ctrl; of the second-oldest event is kept,
206 but the <structfield>changes</structfield> field of the
207 second-oldest event is ORed with the <structfield>changes</structfield>
208 field of the oldest event.</para>
212 <entry><constant>V4L2_EVENT_FRAME_SYNC</constant></entry>
215 <para>Triggered immediately when the reception of a
216 frame has begun. This event has a
217 &v4l2-event-frame-sync; associated with it.</para>
219 <para>If the hardware needs to be stopped in the case of a
220 buffer underrun it might not be able to generate this event.
221 In such cases the <structfield>frame_sequence</structfield>
222 field in &v4l2-event-frame-sync; will not be incremented. This
223 causes two consecutive frame sequence numbers to have n times
224 frame interval in between them.</para>
228 <entry><constant>V4L2_EVENT_SOURCE_CHANGE</constant></entry>
231 <para>This event is triggered when a source parameter change is
232 detected during runtime by the video device. It can be a
233 runtime resolution change triggered by a video decoder or the
234 format change happening on an input connector.
235 This event requires that the <structfield>id</structfield>
236 matches the input index (when used with a video device node)
237 or the pad index (when used with a subdevice node) from which
238 you want to receive events.</para>
240 <para>This event has a &v4l2-event-src-change; associated
241 with it. The <structfield>changes</structfield> bitfield denotes
242 what has changed for the subscribed pad. If multiple events
243 occurred before application could dequeue them, then the changes
244 will have the ORed value of all the events generated.</para>
248 <entry><constant>V4L2_EVENT_MOTION_DET</constant></entry>
251 <para>Triggered whenever the motion detection state for one or more of the regions
252 changes. This event has a &v4l2-event-motion-det; associated with it.</para>
256 <entry><constant>V4L2_EVENT_PRIVATE_START</constant></entry>
257 <entry>0x08000000</entry>
258 <entry>Base event number for driver-private events.</entry>
264 <table frame="none" pgwide="1" id="v4l2-event-vsync">
265 <title>struct <structname>v4l2_event_vsync</structname></title>
271 <entry><structfield>field</structfield></entry>
272 <entry>The upcoming field. See &v4l2-field;.</entry>
278 <table frame="none" pgwide="1" id="v4l2-event-ctrl">
279 <title>struct <structname>v4l2_event_ctrl</structname></title>
285 <entry><structfield>changes</structfield></entry>
287 <entry>A bitmask that tells what has changed. See <xref linkend="ctrl-changes-flags" />.</entry>
291 <entry><structfield>type</structfield></entry>
293 <entry>The type of the control. See &v4l2-ctrl-type;.</entry>
296 <entry>union (anonymous)</entry>
304 <entry><structfield>value</structfield></entry>
305 <entry>The 32-bit value of the control for 32-bit control types.
306 This is 0 for string controls since the value of a string
307 cannot be passed using &VIDIOC-DQEVENT;.</entry>
312 <entry><structfield>value64</structfield></entry>
313 <entry>The 64-bit value of the control for 64-bit control types.</entry>
317 <entry><structfield>flags</structfield></entry>
319 <entry>The control flags. See <xref linkend="control-flags" />.</entry>
323 <entry><structfield>minimum</structfield></entry>
325 <entry>The minimum value of the control. See &v4l2-queryctrl;.</entry>
329 <entry><structfield>maximum</structfield></entry>
331 <entry>The maximum value of the control. See &v4l2-queryctrl;.</entry>
335 <entry><structfield>step</structfield></entry>
337 <entry>The step value of the control. See &v4l2-queryctrl;.</entry>
341 <entry><structfield>default_value</structfield></entry>
343 <entry>The default value value of the control. See &v4l2-queryctrl;.</entry>
349 <table frame="none" pgwide="1" id="v4l2-event-frame-sync">
350 <title>struct <structname>v4l2_event_frame_sync</structname></title>
356 <entry><structfield>frame_sequence</structfield></entry>
358 The sequence number of the frame being received.
365 <table frame="none" pgwide="1" id="v4l2-event-src-change">
366 <title>struct <structname>v4l2_event_src_change</structname></title>
372 <entry><structfield>changes</structfield></entry>
374 A bitmask that tells what has changed. See <xref linkend="src-changes-flags" />.
381 <table frame="none" pgwide="1" id="v4l2-event-motion-det">
382 <title>struct <structname>v4l2_event_motion_det</structname></title>
388 <entry><structfield>flags</structfield></entry>
390 Currently only one flag is available: if <constant>V4L2_EVENT_MD_FL_HAVE_FRAME_SEQ</constant>
391 is set, then the <structfield>frame_sequence</structfield> field is valid,
392 otherwise that field should be ignored.
397 <entry><structfield>frame_sequence</structfield></entry>
399 The sequence number of the frame being received. Only valid if the
400 <constant>V4L2_EVENT_MD_FL_HAVE_FRAME_SEQ</constant> flag was set.
405 <entry><structfield>region_mask</structfield></entry>
407 The bitmask of the regions that reported motion. There is at least one
408 region. If this field is 0, then no motion was detected at all.
409 If there is no <constant>V4L2_CID_DETECT_MD_REGION_GRID</constant> control
410 (see <xref linkend="detect-controls" />) to assign a different region
411 to each cell in the motion detection grid, then that all cells
412 are automatically assigned to the default region 0.
419 <table pgwide="1" frame="none" id="ctrl-changes-flags">
420 <title>Control Changes</title>
425 <entry><constant>V4L2_EVENT_CTRL_CH_VALUE</constant></entry>
426 <entry>0x0001</entry>
427 <entry>This control event was triggered because the value of the control
428 changed. Special cases: Volatile controls do no generate this event;
429 If a control has the <constant>V4L2_CTRL_FLAG_EXECUTE_ON_WRITE</constant>
430 flag set, then this event is sent as well, regardless its value.</entry>
433 <entry><constant>V4L2_EVENT_CTRL_CH_FLAGS</constant></entry>
434 <entry>0x0002</entry>
435 <entry>This control event was triggered because the control flags
439 <entry><constant>V4L2_EVENT_CTRL_CH_RANGE</constant></entry>
440 <entry>0x0004</entry>
441 <entry>This control event was triggered because the minimum,
442 maximum, step or the default value of the control changed.</entry>
448 <table pgwide="1" frame="none" id="src-changes-flags">
449 <title>Source Changes</title>
454 <entry><constant>V4L2_EVENT_SRC_CH_RESOLUTION</constant></entry>
455 <entry>0x0001</entry>
456 <entry>This event gets triggered when a resolution change is
457 detected at an input. This can come from an input connector or
458 from a video decoder.