Home
last modified time | relevance | path

Searched +full:frame +full:- +full:buffer (Results 1 – 25 of 1049) sorted by relevance

12345678910>>...42

/linux-5.10/drivers/video/
Dhdmi.c17 * FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. IN NO EVENT SHALL
43 return 256 - csum; in hdmi_infoframe_checksum()
46 static void hdmi_infoframe_set_checksum(void *buffer, size_t size) in hdmi_infoframe_set_checksum() argument
48 u8 *ptr = buffer; in hdmi_infoframe_set_checksum()
50 ptr[3] = hdmi_infoframe_checksum(buffer, size); in hdmi_infoframe_set_checksum()
54 * hdmi_avi_infoframe_init() - initialize an HDMI AVI infoframe
55 * @frame: HDMI AVI infoframe
57 void hdmi_avi_infoframe_init(struct hdmi_avi_infoframe *frame) in hdmi_avi_infoframe_init() argument
59 memset(frame, 0, sizeof(*frame)); in hdmi_avi_infoframe_init()
61 frame->type = HDMI_INFOFRAME_TYPE_AVI; in hdmi_avi_infoframe_init()
[all …]
/linux-5.10/Documentation/fb/
Dframebuffer.rst2 The Frame Buffer Device
9 ---------------
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
13 software to access the graphics hardware through a well-defined interface, so
14 the software doesn't need to know anything about the low-level (hardware
22 --------------------------
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
[all …]
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
11 - one generic video mode database with a fair amount of standard videomodes
13 - the possibility to supply your own mode database for graphics hardware that
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
23 <xres>x<yres>[M][R][-<bpp>][@<refresh>][i][m][eDd]
24 <name>[-<bpp>][@<refresh>]
37 Sample usage: 1024x768M@60m - CVT timing with margins
[all …]
Dinternals.rst2 Frame Buffer device internals
5 This is a first start for some documentation about frame buffer device
10 - Geert Uytterhoeven <geert@linux-m68k.org>, 21 July 1998
11 - James Simmons <jsimmons@user.sf.net>, Nov 26 2002
13 --------------------------------------------------------------------------------
15 Structures used by the frame buffer device API
18 The following structures play a role in the game of frame buffer devices. They
23 - struct fb_fix_screeninfo
25 Device independent unchangeable information about a frame buffer device and
29 - struct fb_var_screeninfo
[all …]
Dapi.rst2 The Frame Buffer Device API
9 ---------------
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
13 buffer core are not described.
15 Due to a lack of documentation in the original frame buffer API, drivers
22 ---------------
36 - FB_CAP_FOURCC
44 --------------------
46 Pixels are stored in memory in hardware-dependent formats. Applications need
[all …]
/linux-5.10/Documentation/userspace-api/media/v4l/
Dpixfmt-compressed.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
8 .. _compressed-formats:
12 .. flat-table:: Compressed Image Formats
13 :header-rows: 1
14 :stub-columns: 0
17 * - Identifier
18 - Code
19 - Details
20 * .. _V4L2-PIX-FMT-JPEG:
22 - ``V4L2_PIX_FMT_JPEG``
[all …]
Ddev-stateless-decoder.rst1 .. SPDX-License-Identifier: GPL-2.0
6 Memory-to-memory Stateless Video Decoder Interface
10 between processed frames. This means that each frame is decoded independently
18 This section describes how user-space ("the client") is expected to communicate
24 Stateless decoders make use of the :ref:`media-request-api`. A stateless
30 frame may be the result of several decode requests (for instance, H.264 streams
31 with multiple slices per frame). Decoders that support such formats must also
45 codec-specific capability controls (such as H.264 profiles) to the set
55 formats may depend on the value of some codec-dependent controls.
110 frame buffer resolution for the decoded frames.
[all …]
Ddev-encoder.rst1 .. SPDX-License-Identifier: GPL-2.0 OR GFDL-1.1-no-invariants-or-later
6 Memory-to-Memory Stateful Video Encoder Interface
12 further post-processing by the client.
34 5. Single-planar API (see :ref:`planar-apis`) and applicable structures may be
35 used interchangeably with multi-planar API, unless specified otherwise,
41 7. Given an ``OUTPUT`` buffer A, then A' represents a buffer on the ``CAPTURE``
42 queue containing data that resulted from processing buffer A.
47 Refer to :ref:`decoder-glossary`.
52 .. kernel-render:: DOT
65 qi -> Initialization [ label = "open()" ];
[all …]
Dbuffer.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
10 A buffer contains data exchanged by application and driver using one of
11 the Streaming I/O methods. In the multi-planar API, the data is held in
12 planes, while the buffer structure acts as a container for the planes.
14 copied. These pointers, together with meta-information like timestamps
18 :ref:`VIDIOC_DQBUF <VIDIOC_QBUF>` ioctl. In the multi-planar API,
19 some plane-specific members of struct :c:type:`v4l2_buffer`,
25 part of the frame and with which clock the timestamp is taken. Please
27 ``V4L2_BUF_FLAG_TSTAMP_SRC_MASK`` in :ref:`buffer-flags`. These flags
33 mem-to-mem devices is an exception to the rule: the timestamp source
[all …]
Dfunc-read.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
4 .. _func-read:
13 v4l2-read - Read from a V4L2 device
18 .. code-block:: c
31 Buffer to be filled
40 descriptor ``fd`` into the buffer starting at ``buf``. The layout of the
41 data in the buffer is discussed in the respective device interface
45 :c:func:`read()` call will provide at most one frame (two fields)
61 :c:func:`read()` never returns a "snapshot" of a buffer being filled.
62 Using a single buffer the driver will stop capturing when the
[all …]
/linux-5.10/include/linux/
Dhdmi.h17 * FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. IN NO EVENT SHALL
125 /* The following EC values are only defined in CEA-861-F. */
138 /* non-uniform picture scaling */
211 void hdmi_avi_infoframe_init(struct hdmi_avi_infoframe *frame);
212 ssize_t hdmi_avi_infoframe_pack(struct hdmi_avi_infoframe *frame, void *buffer,
214 ssize_t hdmi_avi_infoframe_pack_only(const struct hdmi_avi_infoframe *frame,
215 void *buffer, size_t size);
216 int hdmi_avi_infoframe_check(struct hdmi_avi_infoframe *frame);
217 int hdmi_drm_infoframe_init(struct hdmi_drm_infoframe *frame);
218 ssize_t hdmi_drm_infoframe_pack(struct hdmi_drm_infoframe *frame, void *buffer,
[all …]
Dzstd.h2 * Copyright (c) 2016-present, Yann Collet, Facebook, Inc.
5 * This source code is licensed under the BSD-style license found in the
12 * Free Software Foundation. This program is dual-licensed; you may select
24 /*-*****************************************************************************
28 * targeting real-time compression scenarios at zlib-level and better
29 * compression ratios. The zstd compression library provides in-memory
34 * - a single step, reusing a context (described as Explicit memory management)
35 * - unbounded multiple steps (described as Streaming compression)
38 * - a single step (described as Simple dictionary API)
39 * - a single step, reusing a dictionary (described as Fast dictionary API)
[all …]
/linux-5.10/drivers/video/fbdev/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
13 tristate "Support for frame buffer devices"
17 The frame buffer device provides an abstraction for the graphics
18 hardware. It represents the frame buffer of some video hardware and
20 a well-defined interface, so the software doesn't need to know
21 anything about the low-level (hardware register) stuff.
23 Frame buffer devices work identically across the different
26 server exists which uses the frame buffer device exclusively.
27 On several non-X86 architectures, the frame buffer device is the
33 You need an utility program called fbset to make full use of frame
[all …]
/linux-5.10/drivers/staging/media/atomisp/pci/
Dia_css_frame_public.h1 /* SPDX-License-Identifier: GPL-2.0 */
20 * This file contains structs to describe various frame-formats supported by the ISP.
42 /* Frame plane structure. This describes one plane in an image
43 * frame buffer.
52 unsigned int offset; /** offset in bytes to start of frame data.
72 /* Container for semi-planar YUV frames.
87 /* Container for 6-plane frames. These frames are used internally
93 struct ia_css_frame_plane gr; /** Red-green plane */
94 struct ia_css_frame_plane gb; /** Blue-green plane */
99 /* Crop info struct - stores the lines to be cropped in isp */
[all …]
/linux-5.10/drivers/media/platform/mtk-vcodec/
Dvdec_drv_if.h1 /* SPDX-License-Identifier: GPL-2.0 */
17 * struct vdec_fb_status - decoder frame buffer status
19 * @FB_ST_DISPLAY : frmae buffer is ready to be displayed
20 * @FB_ST_FREE : frame buffer is not used by decoder any more
29 * the caller does not own the returned buffer. The buffer will not be
31 * GET_PARAM_DISP_FRAME_BUFFER : get next displayable frame buffer,
33 * GET_PARAM_FREE_FRAME_BUFFER : get non-referenced framebuffer, vdec_fb**
47 * struct vdec_fb_node - decoder frame buffer node
49 * @fb : point to frame buffer (vdec_fb), fb could point to frame buffer and
50 * working buffer this is for maintain buffers in different state
[all …]
Dvenc_drv_if.h1 /* SPDX-License-Identifier: GPL-2.0 */
16 * enum venc_yuv_fmt - The type of input yuv format
31 * enum venc_start_opt - encode frame option used in venc_if_encode()
33 * @VENC_START_OPT_ENCODE_FRAME: encode normal frame
41 * enum venc_set_param_type - The type of set parameter used in
45 * @VENC_SET_PARAM_FORCE_INTRA: force an intra frame
47 * @VENC_SET_PARAM_ADJUST_FRAMERATE: set frame rate
49 * @VENC_SET_PARAM_INTRA_PERIOD: set I frame interval
50 * @VENC_SET_PARAM_SKIP_FRAME: set H264 skip one frame
67 * struct venc_enc_prm - encoder settings for VENC_SET_PARAM_ENC used in
[all …]
/linux-5.10/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
32 -------------------
34 .. kernel-doc:: drivers/video/fbdev/core/fbmem.c
37 Frame Buffer Colormap
38 ---------------------
40 .. kernel-doc:: drivers/video/fbdev/core/fbcmap.c
[all …]
/linux-5.10/drivers/scsi/isci/
Dunsolicited_frame_control.h7 * Copyright(c) 2008 - 2011 Intel Corporation. All rights reserved.
20 * Foundation, Inc., 51 Franklin St - Fifth Floor, Boston, MA 02110-1301 USA.
26 * Copyright(c) 2008 - 2011 Intel Corporation. All rights reserved.
64 * struct scu_unsolicited_frame_header -
66 * This structure delineates the format of an unsolicited frame header. The
83 * This field indicates if the frame is an address frame (IAF or OAF)
84 * or if it is a information unit frame.
89 * This field simply indicates the connection rate at which the frame
106 * enum unsolicited_frame_state -
108 * This enumeration represents the current unsolicited frame state. The
[all …]
/linux-5.10/include/uapi/drm/
Dlima_drm.h1 /* SPDX-License-Identifier: (GPL-2.0 WITH Linux-syscall-note) OR MIT */
2 /* Copyright 2017-2018 Qiang Yu <yuq825@gmail.com> */
36 * heap buffer dynamically increase backup memory size when GP task fail
37 * due to lack of heap memory. size field of heap buffer is an up bound of
43 * create a buffer for used by GPU
46 __u32 size; /* in, buffer size */
47 __u32 flags; /* in, buffer flags */
48 __u32 handle; /* out, GEM buffer handle */
53 * get information of a buffer
56 __u32 handle; /* in, GEM buffer handle */
[all …]
/linux-5.10/drivers/tty/
Dn_hdlc.c1 // SPDX-License-Identifier: GPL-1.0+
16 * tty device drivers that support bit-synchronous HDLC communications.
18 * All HDLC data is frame oriented which means:
20 * 1. tty write calls represent one complete transmit frame of data
21 * The device driver should accept the complete frame or none of
22 * the frame (busy) in the write method. Each write call should have
23 * a byte count in the range of 2-65535 bytes (2 is min HDLC frame
26 * CCITT CRC32, 4 crc bytes are required, so the maximum size frame
28 * CRC16, the maximum application frame size would be 65533.
32 * one received frame. The device driver should bypass
[all …]
/linux-5.10/drivers/staging/media/tegra-video/
Dvi.h1 /* SPDX-License-Identifier: GPL-2.0-only */
16 #include <media/media-entity.h>
17 #include <media/v4l2-async.h>
18 #include <media/v4l2-ctrls.h>
19 #include <media/v4l2-device.h>
20 #include <media/v4l2-dev.h>
21 #include <media/v4l2-subdev.h>
22 #include <media/videobuf2-v4l2.h>
42 * struct tegra_vi_ops - Tegra VI operations
45 * kthreads for capturing frames to buffer and returns them back.
[all …]
/linux-5.10/drivers/thunderbolt/
Dctl.c1 // SPDX-License-Identifier: GPL-2.0
3 * Thunderbolt driver - control channel and configuration commands
23 * struct tb_cfg - thunderbolt control channel
42 dev_WARN(&(ctl)->nhi->pdev->dev, format, ## arg)
45 dev_err(&(ctl)->nhi->pdev->dev, format, ## arg)
48 dev_warn(&(ctl)->nhi->pdev->dev, format, ## arg)
51 dev_info(&(ctl)->nhi->pdev->dev, format, ## arg)
54 dev_dbg(&(ctl)->nhi->pdev->dev, format, ## arg)
61 * tb_cfg_request_alloc() - Allocates a new config request
74 kref_init(&req->kref); in tb_cfg_request_alloc()
[all …]
/linux-5.10/drivers/gpu/drm/radeon/
Dr600_hdmi.c87 dev_err(rdev->dev, "Unknown bits per sample 0x%x, using 16\n", in r600_audio_status()
118 struct drm_device *dev = rdev->ddev; in r600_audio_update_hdmi()
123 if (rdev->audio.pin[0].channels != audio_status.channels || in r600_audio_update_hdmi()
124 rdev->audio.pin[0].rate != audio_status.rate || in r600_audio_update_hdmi()
125 rdev->audio.pin[0].bits_per_sample != audio_status.bits_per_sample || in r600_audio_update_hdmi()
126 rdev->audio.pin[0].status_bits != audio_status.status_bits || in r600_audio_update_hdmi()
127 rdev->audio.pin[0].category_code != audio_status.category_code) { in r600_audio_update_hdmi()
128 rdev->audio.pin[0] = audio_status; in r600_audio_update_hdmi()
132 list_for_each_entry(encoder, &dev->mode_config.encoder_list, head) { in r600_audio_update_hdmi()
173 /* only one pin on 6xx-NI */ in r600_audio_get_pin()
[all …]
/linux-5.10/drivers/media/platform/mtk-vcodec/vdec/
Dvdec_vp9_if.c1 // SPDX-License-Identifier: GPL-2.0
5 * Kai-Sean Yang <kai-sean.yang@mediatek.com>
29 * struct vp9_dram_buf - contains buffer info for vpu
32 * @sz : buffer size
43 * struct vp9_fb_info - contains frame buffer info
44 * @fb : frmae buffer
53 * struct vp9_ref_cnt_buf - contains reference buffer information
54 * @buf : referenced frame buffer
55 * @ref_cnt : referenced frame buffer's reference count.
64 * struct vp9_fb_info - contains current frame's reference buffer information
[all …]
/linux-5.10/drivers/media/platform/sti/hva/
Dhva-h264.c1 // SPDX-License-Identifier: GPL-2.0
9 #include "hva-hw.h"
32 /* source buffer copy in YUV 420 MB-tiled format with size=16*256*3/2 */
41 /* factor for bitrate and cpb buffer size max values if profile >= high */
44 /* factor for bitrate and cpb buffer size max values if profile < high */
152 * @frame_width: width in pixels of the buffer containing the input frame
153 * @frame_height: height in pixels of the buffer containing the input frame
169 * @ir_param_option: defines the number of macroblocks per frame to be
200 * @brc_type: selects the bit-rate control algorithm
205 * @non_VCL_NALU_Size: size of non-VCL NALUs (SPS, PPS, filler),
[all …]

12345678910>>...42