Lines Matching full:events

3 V4L2 events
6 The V4L2 events provide a generic way to pass events to user space.
7 The driver must use :c:type:`v4l2_fh` to be able to support V4L2 events.
9 Events are subscribed per-filehandle. An event specification consists of a
14 The :c:type:`v4l2_fh` struct has a list of subscribed events on its
23 of :c:func:`v4l2_event_subscribe`. This ringbuffer is used to store any events
28 generating lots of events of one type in a short time, then that will
29 not overwrite events of another type.
31 But if you get more events of one type than the size of the
47 - struct :c:type:`v4l2_fh` has two lists: one of the ``subscribed`` events,
48   and one of the ``available`` events.
51   (pending) events of that particular type.
82 In order to queue events to video device, drivers should call:
102 but the driver must check first if the driver is able to produce events
140 The special type ``V4L2_EVENT_ALL`` may be used to unsubscribe all events. The
152 This function returns the number of pending events. Useful when implementing
155 How events work
158 Events are delivered to user space through the poll system call. The driver
162 There are standard and private events. New standard events must use the
163 smallest available event type. The drivers must allocate their events from
169 An example on how the V4L2 events may be used can be found in the OMAP