Searched +full:top +full:- +full:left (Results 1 – 25 of 162) sorted by relevance
1234567
| /Documentation/sound/designs/ |
| D | channel-mapping-api.rst | 2 ALSA PCM channel-mapping API 18 ``{ front left, front right, rear left, rear right }.`` 38 the kernel/user-space ABI perspective. It uses only the existing 57 --- 61 ``type data-bytes ch0 ch1 ch2...`` 71 type is where pair-wise channels are swappable. For example, when you 88 /* this follows the alsa-lib mixer channel value + 3 */ 89 SNDRV_CHMAP_FL, /* front left */ 91 SNDRV_CHMAP_RL, /* rear left */ 95 SNDRV_CHMAP_SL, /* side left */ [all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | selection-api-configuration.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later 20 :ref:`constraint flags <v4l2-selection-flags>`. 26 See figure :ref:`sel-targets-capture` for examples of the selection 30 The range of coordinates of the top left corner, width and height of 32 target. It is recommended for the driver developers to put the top/left 36 The top left corner, width and height of the source rectangle, that is 51 coordinates are expressed in pixels. The rectangle's top/left corner 63 :ref:`constraint flags <v4l2-selection-flags>`. 91 All coordinates are expressed in pixels. The top/left corner is always 95 The top left corner, width and height of the source rectangle, that is [all …]
|
| D | ext-ctrls-detect.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later 3 .. _detect-controls: 13 .. _detect-control-id: 28 .. flat-table:: 29 :header-rows: 0 30 :stub-columns: 0 32 * - ``V4L2_DETECT_MD_MODE_DISABLED`` 33 - Disable motion detection. 34 * - ``V4L2_DETECT_MD_MODE_GLOBAL`` 35 - Use a single motion detection threshold. [all …]
|
| D | vidioc-cropcap.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later 13 VIDIOC_CROPCAP - Information about the video cropping and scaling abilities 43 support cropping and/or scaling and/or have non-square pixels, and for 50 .. flat-table:: struct v4l2_cropcap 51 :header-rows: 0 52 :stub-columns: 0 55 * - __u32 56 - ``type`` 57 - Type of the data stream, set by the application. Only these types 61 * - struct :ref:`v4l2_rect <v4l2-rect-crop>` [all …]
|
| D | dev-overlay.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later 11 Video overlay devices have the ability to genlock (TV-)video into the 12 (VGA-)video signal of a graphics card, or to store captured images 62 :ref:`streaming parameter <streaming-par>` ioctls as needed. The 93 1. Chroma-keying displays the overlaid image only where pixels in the 162 ------------------ 165 Size and position of the window relative to the top, left corner of 181 When chroma-keying has been negotiated with 187 :ref:`V4L2_PIX_FMT_BGR24 <V4L2-PIX-FMT-BGR32>` the value should 192 When chroma-keying has *not* been negotiated and [all …]
|
| D | pixfmt-intro.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later 13 V4L2 drivers are not limited to these formats, however. Driver-specific 23 specification would not be complete without well-defined standard 27 are always arranged in memory from left to right, and from top to 30 immediately to its right, and so on until the end of the top row of 34 leftmost pixel of the second row from the top, and so on. The last row 40 :ref:`four character (FourCC) codes <v4l2-fourcc>` which are also 46 and are referred to as "multi-planar formats". For example, a 47 :ref:`YUV422 <V4L2-PIX-FMT-YUV422M>` frame is normally stored in one 50 in the 2-planar version or with each component in its own buffer in the [all …]
|
| D | v4l2-selection-targets.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later 3 .. _v4l2-selection-targets: 13 .. _v4l2-selection-targets-table: 23 .. flat-table:: Selection target definitions 24 :header-rows: 1 25 :stub-columns: 0 27 * - Target name 28 - id 29 - Definition 30 - Valid for V4L2 [all …]
|
| D | metafmt-d4xx.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later 3 .. _v4l2-meta-fmt-d4xx: 15 Intel D4xx (D435, D455 and others) cameras include per-frame metadata in their UVC 37 .. flat-table:: D4xx metadata 39 :header-rows: 1 40 :stub-columns: 0 42 * - **Field** 43 - **Description** 44 * - :cspan:`1` *Depth Control* 45 * - __u32 ID [all …]
|
| D | selection-api-examples.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later 14 .. code-block:: c 22 exit(-1); 26 exit(-1); 34 .. code-block:: c 44 exit(-1); 48 r.left = sel.r.width / 4; 49 r.top = sel.r.height / 4; 55 exit(-1); 63 .. code-block:: c [all …]
|
| D | crop.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later 6 Image Cropping, Insertion and Scaling -- the CROP API 12 <selection-api>`. The new API should be preferred in most cases, 15 equivalent in the SELECTION API. See :ref:`selection-vs-crop` for a 62 .. _crop-scale: 64 .. kernel-figure:: crop.svg 74 For capture devices the coordinates of the top left corner, width and 81 :ref:`vbi-hsync`). Vertically ITU-R line numbers of the first field 82 (see ITU R-525 line numbering for :ref:`525 lines <vbi-525>` and for 83 :ref:`625 lines <vbi-625>`), multiplied by two if the driver [all …]
|
| /Documentation/driver-api/media/drivers/ |
| D | sh_mobile_ceu_camera.rst | 1 .. SPDX-License-Identifier: GPL-2.0 9 ----------- 12 host scales: -"- host driver 17 --------------------------------- 19 .. code-block:: none 21 -1-- 23 -2-- -\ 24 | --\ 25 | --\ 26 +-5-- . -- -3-- -\ [all …]
|
| /Documentation/sphinx-static/ |
| D | custom.css | 1 /* SPDX-License-Identifier: GPL-2.0 */ 7 div.body h1 { font-size: 180%; } 8 div.body h2 { font-size: 150%; } 9 div.body h3 { font-size: 130%; } 10 div.body h4 { font-size: 110%; } 13 div.toctree-wrapper p.caption[role=heading] { font-size: 150%; } 18 div.sphinxsidebar { font-size: inherit; 19 max-height: 100%; 20 overflow-y: auto; } 30 margin-bottom: 20px; [all …]
|
| D | theme_overrides.css | 1 /* -*- coding: utf-8; mode: css -*- 11 font-family: serif; 12 font-size: 100%; 15 h1, h2, .rst-content .toctree-wrapper p.caption, h3, h4, h5, h6, legend { 16 font-family: sans-serif; 20 font-family: monospace; 21 font-size: 100%; 24 .wy-menu-vertical { 25 font-family: sans-serif; 29 font-style: normal; [all …]
|
| /Documentation/userspace-api/media/drivers/ |
| D | cx2341x-uapi.rst | 1 .. SPDX-License-Identifier: GPL-2.0 6 Non-compressed file format 7 -------------------------- 18 The Y plane is divided into blocks of 16x16 pixels from left to right 19 and from top to bottom. Each block is transmitted in turn, line-by-line. 21 So the first 16 bytes are the first line of the top-left block, the 22 second 16 bytes are the second line of the top-left block, etc. After 26 The UV plane is divided into blocks of 16x8 UV values going from left 27 to right, top to bottom. Each block is transmitted in turn, line-by-line. 29 So the first 16 bytes are the first line of the top-left block and [all …]
|
| /Documentation/leds/ |
| D | well-known-leds.txt | 1 -*- org -*- 17 Notice there's a list of functions in include/dt-bindings/leds/common.h . 24 player. For example, a game controller with 4 LEDs, may be programmed with "x---" 25 to indicate player 1, "-x--" to indicate player 2 etcetera where "x" means on. 31 Good: "input*:*:player-{1,2,3,4,5} 38 Legacy: "shift-key-light" (Motorola Droid 4, capslock) 47 Legacy: "button-backlight" (Motorola Droid 4) 62 Legacy: "status-led:{red,green,blue}" (Motorola Droid 4) 65 Phones usually have multi-color status LED. 69 Good: "platform:*:charging" (allwinner sun50i, leds-cht-wcove) [all …]
|
| /Documentation/input/ |
| D | gamepad.rst | 1 --------------------------- 3 --------------------------- 11 having user-space deal with different button-mappings for each gamepad, this 25 | <===DP===> |SE| |ST| (W) -|- (E) | | 35 D-Pad Left Right Action Pad 43 - Action-Pad 44 4 buttons in diamonds-shape (on the right side). The buttons are 47 - D-Pad (Direction-pad) 48 4 buttons (on the left side) that point up, down, left and right. 49 - Menu-Pad [all …]
|
| /Documentation/devicetree/bindings/iio/ |
| D | mount-matrix.txt | 2 * is the definition of +/- values practical or counterintuitive? 13 that produce three-dimensional data in relation to the world where it is 31 For a screen you probably want (x) coordinates to go from negative on the left 32 to positive on the right, (y) from negative on the bottom to positive on top 37 reference. This means that the sensor may be flipped upside-down, left-right, 47 Device-to-world examples for some three-dimensional sensor types: 49 - Accelerometers have their world frame of reference toward the center of 57 as the gravity vector is projected 1:1 onto the sensors (z)-axis. 67 +--------+ +--------+ 69 +--------+ +--------+ [all …]
|
| /Documentation/admin-guide/ |
| D | lcd-panel-cgram.rst | 8 number, and up to 8 couples of hex digits terminated by a semi-colon 9 (';'). Each couple of digits represents a line, with 1-bits for each 11 top of the character to the bottom. On a 5x7 matrix, only the 5 lower 19 printf "\e[LG3040E1F001F0E0400;" => 3 = [up-down] 20 printf "\e[LG40002060E1E0E0602;" => 4 = [left]
|
| /Documentation/input/devices/ |
| D | elantech.rst | 4 Copyright (C) 2007-2008 Arjan Opmeer <arjan@opmeer.net> 25 5.2.1 Parity checking and packet re-synchronization 81 On top of that, some register settings have effect only when the touchpad is 114 non-zero value will turn it ON. For hardware version 1 the default is ON. 145 4 bytes version: (after the arrow is the name given in the Dell-provided driver) 173 --------- 179 echo -n 0x16 > reg_10 193 B: 1 = swap left and right button 236 ----------------------------------------- 243 L, R, M = 1 when Left, Right, Middle mouse button pressed [all …]
|
| D | atarikbd.rst | 12 provides a convenient connection point for a mouse and switch-type joysticks. 13 The ikbd processor also maintains a time-of-day clock with one second 18 The ikbd communicates with the main processor over a high speed bi-directional 41 0xF8-0xFB relative mouse position records (lsbs determined by 43 0xFC time-of-day 67 --------------------------- 85 ; and x is the left button state 92 +127...-128 range, the motion is broken into multiple packets. 97 --------------------------- 104 --------------------- [all …]
|
| /Documentation/devicetree/bindings/input/ |
| D | google,cros-ec-keyb.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 5 $id: http://devicetree.org/schemas/input/google,cros-ec-keyb.yaml# 6 $schema: http://devicetree.org/meta-schemas/core.yaml# 11 - Simon Glass <sjg@chromium.org> 12 - Benson Leung <bleung@chromium.org> 24 - description: ChromeOS EC with only buttons/switches 25 const: google,cros-ec-keyb-switches 26 - description: ChromeOS EC with keyboard and possibly buttons/switches 27 const: google,cros-ec-keyb [all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | nxp,tfa989x.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Stephan Gerhold <stephan@gerhold.net> 13 - $ref: dai-common.yaml# 18 - nxp,tfa9890 19 - nxp,tfa9895 20 - nxp,tfa9897 25 '#sound-dai-cells': 28 rcv-gpios: [all …]
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | brcm,bcm7038-l1-intc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/interrupt-controller/brcm,bcm7038-l1-intc.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Broadcom BCM7038-style Level 1 interrupt controller 11 directly to one of the HW INT lines on each CPU. Every BCM7xxx set-top chip 16 - 64, 96, 128, or 160 incoming level IRQ lines 18 - Most onchip peripherals are wired directly to an L1 input 20 - A separate instance of the register set for each CPU, allowing individual 23 - Atomic mask/unmask operations [all …]
|
| /Documentation/fb/ |
| D | pxafb.rst | 10 modprobe pxafb options=vmem:2M,mode:640x480-8,passive 14 video=pxafb:vmem:2M,mode:640x480-8,passive 21 mode:XRESxYRES[-BPP] 35 left:LEFT == LCCR1_BLW + 1 87 PXA27x and later processors support overlay1 and overlay2 on-top of the 88 base framebuffer (although under-neath the base is also possible). They 89 support palette and no-palette RGB formats, as well as YUV formats (only 96 1. overlay can start at a 32-bit word aligned position within the base 98 is encoded into var->nonstd (no, var->xoffset and var->yoffset are 104 var->xres_virtual * var->yres_virtual * bpp [all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-firmware-acpi | 55 image: The image bitmap. Currently a 32-bit BMP. 61 xoffset: The number of pixels between the left of the screen 62 and the left edge of the image. 63 yoffset: The number of pixels between the top of the screen 64 and the top edge of the image. 93 cause -EINVAL to be returned.
|
1234567