Home
last modified time | relevance | path

Searched full:frame (Results 1 – 25 of 289) sorted by relevance

12345678910>>...12

/Documentation/media/uapi/v4l/
Dvidioc-enum-frameintervals.rst19 VIDIOC_ENUM_FRAMEINTERVALS - Enumerate frame intervals
37 that contains a pixel format and size and receives a frame interval.
43 This ioctl allows applications to enumerate all frame intervals that the
44 device supports for the given pixel format and frame size.
46 The supported pixel formats and frame sizes can be obtained by using the
51 depend on the type of frame intervals the device supports. Here are the
75 the ``type`` field to determine the type of frame interval enumeration
77 does it make sense to increase the index value to receive more frame
82 The order in which the frame intervals are returned has no
84 default frame intervals.
[all …]
Dvidioc-enum-framesizes.rst19 VIDIOC_ENUM_FRAMESIZES - Enumerate frame sizes
37 that contains an index and pixel format and receives a frame width
44 This ioctl allows applications to enumerate all frame sizes (i. e. width
52 depend on the type of frame sizes the device supports. Here are the
76 the ``type`` field to determine the type of frame size enumeration the
78 it make sense to increase the index value to receive more frame sizes.
82 The order in which the frame sizes are returned has no special
89 other ioctl calls while it runs the frame size enumeration.
111 - Width of the frame [pixel].
114 - Height of the frame [pixel].
[all …]
Dvidioc-subdev-enum-frame-interval.rst19 VIDIOC_SUBDEV_ENUM_FRAME_INTERVAL - Enumerate frame intervals
42 This ioctl lets applications enumerate available frame intervals on a
43 given sub-device pad. Frame intervals only makes sense for sub-devices
44 that can control the frame period on their own. This includes, for
47 For the common use case of image sensors, the frame intervals available
48 on the sub-device output pad depend on the frame format and size on the
50 when enumerating frame intervals.
52 To enumerate frame intervals applications initialize the ``index``,
57 EINVAL error code if one of the input fields is invalid. All frame
61 Available frame intervals may depend on the current 'try' formats at
[all …]
Dvidioc-subdev-enum-frame-size.rst19 VIDIOC_SUBDEV_ENUM_FRAME_SIZE - Enumerate media bus frame sizes
42 This ioctl allows applications to enumerate all frame sizes supported by
48 To enumerate frame sizes applications initialize the ``pad``, ``which``
52 structure. Drivers fill the minimum and maximum frame sizes or return an
55 Sub-devices that only support discrete frame sizes (such as most
56 sensors) will return one or more frame sizes with identical minimum and
61 might not be able to produce every frame size between the minimum and
64 sub-device for an exact supported frame size.
66 Available frame sizes may depend on the current 'try' formats at other
94 - Minimum frame width, in pixels.
[all …]
Dvidioc-subdev-g-frame-interval.rst19 VIDIOC_SUBDEV_G_FRAME_INTERVAL - VIDIOC_SUBDEV_S_FRAME_INTERVAL - Get or set the frame interval on …
45 These ioctls are used to get and set the frame interval at specific
46 subdev pads in the image pipeline. The frame interval only makes sense
47 for sub-devices that can control the frame period on their own. This
49 don't support frame intervals must not implement these ioctls.
51 To retrieve the current frame interval applications set the ``pad``
58 To change the current frame interval applications set both the ``pad``
65 contains the current frame interval as would be returned by a
73 Changing the frame interval shall never change the format. Changing the
74 format, on the other hand, may change the frame interval.
[all …]
Dpixfmt-compressed.rst71 In addition, metadata associated with the frame to decode are
81 corresponding frame to the matching capture buffer.
118 Metadata associated with the frame to decode is required to be passed
125 of macroblocks to decode a full corresponding frame to the matching
151 - VP8 compressed video frame. The encoder generates one
152 compressed frame per buffer, and the decoder requires one
153 compressed frame per buffer.
154 * .. _V4L2-PIX-FMT-VP8-FRAME:
158 - VP8 parsed frame, as extracted from the container.
161 Metadata associated with the frame to decode is required to be passed
[all …]
Dpixfmt-meta-d4xx.rst22 Intel D4xx (D435 and other) cameras include per-frame metadata in their UVC
34 per frame, therefore their headers cannot be larger than 255 bytes.
62 capture the frame
64 - Exposure time (in microseconds) used to capture the frame
70 - Exposure priority value: 0 - constant frame rate
95 * - __u32 Frame counter
98 - Time in microseconds from the beginning of a frame till its middle
100 - Time, used to read out a frame in microseconds
102 - Frame exposure time in microseconds
103 * - __u32 Frame interval
[all …]
Dext-ctrls-codec.rst596 For every captured frame, skip this many subsequent frames (default
630 currently displayed frame. This is the same PTS as is used in
633 .. _v4l2-mpeg-video-dec-frame:
636 This read-only control returns the frame counter of the frame that
642 otherwise the decoder expects a single frame in per buffer.
942 Determines how the encoder should handle division of frame into
954 - Single slice per frame.
1056 macroblocks refreshed every frame. Each frame a successive set of
1058 the top of the frame. Applicable to H264, H263 and MPEG4 encoder.
1061 Frame level rate control enable. If this control is disabled then
[all …]
Dfield-order.rst22 original frame. This curious technique was invented because at refresh
24 fields reduces the flicker without the necessity of doubling the frame
27 It is important to understand a video camera does not expose one frame
32 which field of a frame is older, the *temporal order*.
38 the first line of an interlaced frame, the first line of the bottom
39 field is the second line of that frame.
42 whether a frame commences with the top or bottom field is pointless. Any
44 frame. Only when the source was progressive to begin with, e. g. when
45 transferring film to video, two fields may come from the same frame,
95 - Images are in progressive (frame-based) format, not interlaced
[all …]
Dfunc-read.rst54 :ref:`read() <func-read>` call will provide at most one frame (two fields)
74 reading, or the capture rate must fall below the nominal frame rate of
81 previously, not read frame, and returns the frame being received at the
85 :ref:`read() <func-read>` call. The frame being received at :ref:`read() <func-read>`
86 time is discarded, returning the following frame instead. Again this
88 nominal frame rate. An example of this model is the video read mode of
110 of data required for one frame. This may happen for example because
113 the next read will start at the beginning of a new frame. Possible error
/Documentation/driver-api/
Dframe-buffer.rst1 Frame Buffer Library
4 The frame buffer drivers depend heavily on four data structures. These
20 otherwise. A good example of this is the start of the frame buffer
21 memory. This "locks" the address of the frame buffer memory, so that it
31 Frame Buffer Memory
37 Frame Buffer Colormap
43 Frame Buffer Video Mode Database
52 Frame Buffer Macintosh Video Mode Database
58 Frame Buffer Fonts
/Documentation/devicetree/bindings/timer/
Darm,arch_timer_mmio.yaml15 frames with a physical and optional virtual timer per frame.
27 description: The control frame base address
61 '^frame@[0-9a-z]*$':
63 description: A timer node has up to 8 frame sub-nodes, each with the following properties.
65 frame-number:
86 - frame-number
106 frame@f0001000 {
107 frame-number = <0>;
114 frame@f0003000 {
115 frame-number = <1>;
/Documentation/ABI/testing/
Dconfigfs-usb-gadget-uvc185 bDefaultFrameIndex - optimum frame index for this stream
190 Description: Specific MJPEG frame descriptors
196 dwFrameInterval - indicates how frame interval can be
199 dwDefaultFrameInterval - the frame interval the device would
203 frame or still image
205 frame interval in bps
207 frame interval in bps
208 wHeight - height of decoded bitmap frame in px
209 wWidth - width of decoded bitmam frame in px
210 bmCapabilities - still image support, fixed frame-rate
[all …]
/Documentation/fb/
Dframebuffer.rst2 The Frame Buffer Device
11 The frame buffer device provides an abstraction for the graphics hardware. It
12 represents the frame buffer of some video hardware and allows application
24 From the user's point of view, the frame buffer device looks just like any
26 specifies the frame buffer number.
31 0 = /dev/fb0 First frame buffer
32 1 = /dev/fb1 Second frame buffer
34 31 = /dev/fb31 32nd frame buffer
44 The frame buffer devices are also `normal` memory devices, this means, you can
49 There also can be more than one frame buffer at a time, e.g. if you have a
[all …]
Dinternals.rst2 Frame Buffer device internals
5 This is a first start for some documentation about frame buffer device
15 Structures used by the frame buffer device API
18 The following structures play a role in the game of frame buffer devices. They
25 Device independent unchangeable information about a frame buffer device and
31 Device independent changeable information about a frame buffer device and a
46 Generic information, API and low level information about a specific frame
55 Visuals used by the frame buffer device API
Dmodedb.rst6 Currently all frame buffer device drivers have their own video mode databases,
9 - one routine to probe for video modes, which can be used by all frame buffer
14 needs non-standard modes, like amifb and Mac frame buffer drivers (which
17 When a frame buffer device receives a video= option it doesn't know, it should
18 consider that to be a video mode option. If no frame buffer device is specified
158 amifb - Amiga chipset frame buffer
159 aty128fb - ATI Rage128 / Pro frame buffer
160 atyfb - ATI Mach64 frame buffer
161 pm2fb - Permedia 2/2V frame buffer
162 pm3fb - Permedia 3 frame buffer
[all …]
Dapi.rst2 The Frame Buffer Device API
11 This document describes the frame buffer API used by applications to interact
12 with frame buffer devices. In-kernel APIs between device drivers and the frame
15 Due to a lack of documentation in the original frame buffer API, drivers
48 frame buffer memory in the format expected by the hardware.
50 Formats are described by frame buffer types and visuals. Some visuals require
153 about the frame buffer device and the current format. Those information can't
159 unsigned long smem_start; /* Start of frame buffer mem */
161 __u32 smem_len; /* Length of frame buffer mem */
179 about a frame buffer device, its current format and video mode, as well as
[all …]
/Documentation/devicetree/bindings/watchdog/
Dsbsa-gwdt.txt11 - reg: Each entry specifies the base physical address of a register frame
12 and the length of that frame; currently, two frames must be defined,
14 1: Watchdog control frame;
15 2: Refresh frame.
/Documentation/networking/device_drivers/freescale/
Ddpaa.txt14 - DPAA Ethernet Frame Processing
32 - Frame Manager (FMan)
70 FMan = DPAA Frame Manager
77 FQ = QMan Frame Queue
81 Tx FQs = transmission frame queues
129 DPAA Ethernet Frame Processing
137 confirmation frame queues. The driver is then responsible for freeing the
183 hardware frame queues using a hash on IP v4/v6 source and destination
184 and L4 source and destination ports, in present in the received frame.
186 received on the default Rx frame queue. The default DPAA Rx frame
[all …]
/Documentation/devicetree/bindings/hsi/
Dclient-devices.txt9 - hsi-rx-mode: Receiver Bit transmission mode ("stream" or "frame")
10 - hsi-tx-mode: Transmitter Bit transmission mode ("stream" or "frame")
16 - hsi-arb-mode: Arbitration mode for TX frame ("round-robin", "priority")
37 hsi-mode = "frame";
/Documentation/devicetree/bindings/sound/
Dmikroe,mikroe-proto.txt11 - frame-master: Indicates dai-link frame master; for details see simple-card.txt (1).
13 (1) : There must be the same master for both bit and frame clocks.
Dcs35l35.txt108 for adjusting the Depth, Location and Frame of the Monitoring Signals
115 for depth, location, and frame.
119 Sections 7.44 - 7.53 lists values for the depth, location, and frame
122 - cirrus,imon : 4 8 bit values to set the depth, location, frame and ADC
125 - cirrus,vmon : 3 8 bit values to set the depth, location, and frame
128 - cirrus,vpmon : 3 8 bit values to set the depth, location, and frame
131 - cirrus,vbstmon : 3 8 bit values to set the depth, location, and frame
134 - cirrus,vpbrstat : 3 8 bit values to set the depth, location, and frame
137 - cirrus,zerofill : 3 8 bit values to set the depth, location, and frame\
171 /* Depth, Location, Frame */
/Documentation/devicetree/bindings/iio/
Dmount-matrix.txt16 The purpose of the mounting matrix is to translate the sensor frame of
17 reference into the device frame of reference using a translation matrix as
23 relative to some specific device frame of reference.
36 A sensor can be mounted in any angle along the axes relative to the frame of
38 or tilted at any angle relative to the frame of reference.
40 Another frame of reference is how the device with its sensor relates to the
49 - Accelerometers have their world frame of reference toward the center of
53 this point. Up and down in the world relative to the device frame of
93 - Magnetometers (compasses) have their world frame of reference relative to the
95 respect to the local earth geomagnetic reference frame where (y) is in the
[all …]
/Documentation/networking/
Dmac80211-auth-assoc-deauth.txt35 mac80211->driver: TX auth frame
36 driver->mac80211: RX auth frame
39 mac80211->driver: TX auth frame
40 driver->mac80211: RX auth frame
44 mac80211->userspace: RX auth frame
/Documentation/sound/soc/
Ddai.rst16 frame (FRAME) (usually 48kHz) is always driven by the controller. Each AC97
17 frame is 21uS long and is divided into 13 time slots.
61 MSB is transmitted on falling edge of first BCLK after FRAME/SYNC.
64 MSB is transmitted on rising edge of FRAME/SYNC.

12345678910>>...12