Searched +full:display +full:- +full:depth (Results 1 – 25 of 50) sorted by relevance
12
| /Documentation/devicetree/bindings/display/ |
| D | xylon,logicvc-display.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 4 --- 5 $id: http://devicetree.org/schemas/display/xylon,logicvc-display.yaml# 6 $schema: http://devicetree.org/meta-schemas/core.yaml# 8 title: Xylon LogiCVC display controller 11 - Paul Kocialkowski <paul.kocialkowski@bootlin.com> 14 The Xylon LogiCVC is a display controller that supports multiple layers. 16 with Xilinx Zynq-7000 SoCs and Xilinx FPGAs. 20 synthesis time. As a result, many of the device-tree bindings are meant to 24 Layers are declared in the "layers" sub-node and have dedicated configuration. [all …]
|
| D | wm,wm8505-fb.txt | 2 ----------------------------------------------------- 5 - compatible : "wm,wm8505-fb" 6 - reg : Should contain 1 register ranges(address and length) 7 - bits-per-pixel : bit depth of framebuffer (16 or 32) 10 - display-timings: see display-timing.txt for information 15 compatible = "wm,wm8505-fb"; 17 bits-per-pixel = <16>; 19 display-timings { 20 native-mode = <&timing0>; 22 clock-frequency = <0>; /* unused but required */ [all …]
|
| D | via,vt8500-fb.txt | 2 ----------------------------------------------------- 5 - compatible : "via,vt8500-fb" 6 - reg : Should contain 1 register ranges(address and length) 7 - interrupts : framebuffer controller interrupt 8 - bits-per-pixel : bit depth of framebuffer (16 or 32) 11 - display-timings: see display-timing.txt for information 16 compatible = "via,vt8500-fb"; 19 bits-per-pixel = <16>; 21 display-timings { 22 native-mode = <&timing0>; [all …]
|
| D | allwinner,sun4i-a10-display-engine.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 4 $id: http://devicetree.org/schemas/display/allwinner,sun4i-a10-display-engine.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Allwinner A10 Display Engine Pipeline 10 - Chen-Yu Tsai <wens@csie.org> 11 - Maxime Ripard <mripard@kernel.org> 14 The display engine pipeline (and its entry point, since it can be 18 The Allwinner A10 Display pipeline is composed of several components 22 display pipeline, when there are multiple components of the same [all …]
|
| D | atmel,lcdc-display.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/display/atmel,lcdc-display.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Microchip's LCDC Display 10 - Nicolas Ferre <nicolas.ferre@microchip.com> 11 - Dharma Balasubiramani <dharma.b@microchip.com> 15 from an external display buffer to a TFT LCD panel. The LCDC has one display 17 interface and a look-up table to allow palletized display configurations. The 26 - required: [ 'atmel,dmacon' ] [all …]
|
| /Documentation/fb/ |
| D | efifb.rst | 13 - iMac 17"/20" 14 - Macbook 15 - Macbook Pro 15"/17" 16 - MacMini 17 - ARM/ARM64/X86 systems with UEFI firmware 36 For GOP displays, efifb can autodetect the display's resolution and framebuffer 43 to workaround side-effects and slowdowns on other CPU cores 50 The EFI stub will set the mode of the display to mode number n if 53 <xres>x<yres>[-(rgb|bgr|<bpp>)] 54 The EFI stub will search for a display mode that matches the specified [all …]
|
| D | viafb.rst | 6 -------- 15 --------------- 29 color depth: 8 bpp, 16 bpp, 32 bpp supports. 34 ---------------------- 47 - 640x480 (default) 48 - 720x480 49 - 800x600 50 - 1024x768 53 - 8, 16, 32 (default:32) 56 - 60, 75, 85, 100, 120 (default:60) [all …]
|
| D | sisfb.rst | 8 - SiS 300 series: SiS 300/305, 540, 630(S), 730(S) 9 - SiS 315 series: SiS 315/H/PRO, 55x, (M)65x, 740, (M)661(F/M)X, (M)741(GX) 10 - SiS 330 series: SiS 330 ("Xabre"), (M)760 16 sisfb is eg. useful if you want a high-resolution text console. Besides that, 59 Additionally: If you give more than one argument to the in-kernel sisfb, the 74 The desired display mode can be specified using the keyword "mode" with 77 - XxYxDepth or 78 - XxY-Depth or 79 - XxY-Depth@Rate or 80 - XxY [all …]
|
| 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] 27 The resolution of the display in pixels 29 BPP == The bit depth. Valid values are 1, 2, 4, 8 and 16. 47 Display margins and sync times 55 Active (TFT) or Passive (STN) display 59 Single or dual panel passive display 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 [all …]
|
| D | matroxfb.rst | 16 * Most important: boot logo :-) 34 box) and matroxfb (for graphics mode). You should not compile-in vesafb 35 unless you have primary display on non-Matrox VBE2.0 device (see 43 ------------- 58 ------------------------- 73 ---------- 86 Non-listed number can be achieved by more complicated command-line, for 87 example 1600x1200x32bpp can be specified by `video=matroxfb:vesa:0x11C,depth:32`. 93 XF{68,86}_FBDev should work just fine, but it is non-accelerated. On non-intel 97 Running another (accelerated) X-Server like XF86_SVGA works too. But (at least) [all …]
|
| D | framebuffer.rst | 9 --------------- 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 -------------------------- 39 /dev/fb0current -> fb0 40 /dev/fb1current -> fb1 50 graphics card in addition to the built-in hardware. The corresponding frame 69 -------------------------------- 82 - You can request unchangeable information about the hardware, like name, 86 - You can request and change variable information about the hardware, like [all …]
|
| /Documentation/devicetree/bindings/display/samsung/ |
| D | samsung,exynos5-dp.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 4 $id: http://devicetree.org/schemas/display/samsung/samsung,exynos5-dp.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Samsung Exynos5250/Exynos5420 SoC Display Port 10 - Inki Dae <inki.dae@samsung.com> 11 - Seung-Woo Kim <sw0312.kim@samsung.com> 12 - Kyungmin Park <kyungmin.park@samsung.com> 13 - Krzysztof Kozlowski <krzk@kernel.org> 17 const: samsung,exynos5-dp [all …]
|
| /Documentation/devicetree/bindings/spi/ |
| D | spi-controller.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 4 $id: http://devicetree.org/schemas/spi/spi-controller.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Mark Brown <broonie@kernel.org> 20 pattern: "^spi(@.*|-([0-9]|[1-9][0-9]+))?$" 22 "#address-cells": 25 "#size-cells": 28 cs-gpios: 32 increased automatically with max(cs-gpios, hardware chip selects). [all …]
|
| /Documentation/gpu/amdgpu/display/ |
| D | dcn-overview.rst | 2 Display Core Next (DCN) 5 To equip our readers with the basic knowledge of how AMD Display Core Next 10 .. kernel-figure:: dc_pipeline_overview.svg 15 * **Display Controller Hub (DCHUB)**: This is the gateway between the Scalable 19 * **Display Pipe and Plane (DPP)**: This block provides pre-blend pixel 24 multiple planes, using global or per-pixel alpha. 27 the display. 32 * **Display Output (DIO)**: Codify the output to the display connected to our 35 * **Display Writeback (DWB)**: It provides the ability to write the output of 36 the display pipe back to memory as video frames. [all …]
|
| D | display-manager.rst | 2 AMDgpu Display Manager 6 :depth: 3 8 .. kernel-doc:: drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c 11 .. kernel-doc:: drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.h 17 .. kernel-doc:: drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c 20 .. kernel-doc:: drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c 26 .. kernel-doc:: drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_irq.c 29 .. kernel-doc:: drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_irq.c 32 .. kernel-doc:: drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c 38 .. kernel-doc:: drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c [all …]
|
| /Documentation/scsi/ |
| D | aic79xx.rst | 1 .. SPDX-License-Identifier: GPL-2.0 28 AIC-7901A Single Channel 64-bit PCI-X 133MHz to 30 AIC-7901B Single Channel 64-bit PCI-X 133MHz to 32 AIC-7902A4 Dual Channel 64-bit PCI-X 133MHz to 34 AIC-7902B Dual Channel 64-bit PCI-X 133MHz to 41 Adaptec SCSI Card 39320 Dual Channel 64-bit PCI-X 133MHz to 7902A4/7902B 43 68-pin, two internal 68-pin) 44 Adaptec SCSI Card 39320A Dual Channel 64-bit PCI-X 133MHz to 7902B 46 68-pin, two internal 68-pin) 47 Adaptec SCSI Card 39320D Dual Channel 64-bit PCI-X 133MHz to 7902A4 [all …]
|
| D | ChangeLog.sym53c8xx_2 | 2 * version sym-2.1.0-20001230 3 - Initial release of SYM-2. 6 * version sym-2.1.1-20010108 7 - Change a couple of defines containing ncr or NCR by their 11 * version sym-2.1.2-20010114 12 - Fix a couple of printfs: 13 * Add the target number to the display of transfer parameters. 14 * Make the display of TCQ and queue depth clearer. 17 * version sym-2.1.3-20010117 18 - Wrong residual values were returned in some situations. [all …]
|
| /Documentation/devicetree/bindings/display/bridge/ |
| D | adi,adv7511.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/display/bridge/adi,adv7511.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Laurent Pinchart <laurent.pinchart@ideasonboard.com> 21 - adi,adv7511 22 - adi,adv7511w 23 - adi,adv7513 37 reg-names: 40 needing a non-default address. [all …]
|
| D | ite,it6505.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/display/bridge/ite,it6505.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Allen Chen <allen.chen@ite.com.tw> 13 - $ref: /schemas/sound/dai-common.yaml# 16 The IT6505 is a high-performance DisplayPort 1.1a transmitter, 18 The IT6505 supports color depth of up to 36 bits (12 bits/color) 19 and ensures robust transmission of high-quality uncompressed video 30 transmission of high-definition content. Users of the IT6505 need not [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 29 screen and (z) being depth, the axis perpendicular to the screen. 33 and (z) depth to be negative under the screen and positive in front of it, 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. 59 If you tilt the device, the g vector virtually coming out of the display 60 is projected onto the (x,y) plane of the display panel. [all …]
|
| /Documentation/userspace-api/media/dvb/ |
| D | legacy_dvb_osd.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later OR GPL-2.0 14 The DVB OSD device controls the OnScreen-Display of the AV7110 based 15 DVB-cards with hardware MPEG2 decoder. It can be accessed through 20 The OSD is not a frame-buffer like on many other cards. 22 The color-depth is limited depending on the memory size installed. 31 ----------- 36 .. code-block:: c 39 /* All functions return -2 on "not open" */ 67 .. note:: All functions return -2 on "not open" 69 .. flat-table:: [all …]
|
| /Documentation/arch/m68k/ |
| D | kernel-options.rst | 9 Author: Roman.Hodek@informatik.uni-erlangen.de (Roman Hodek) 11 Update: jds@kom.auc.dk (Jes Sorensen) and faq@linux-m68k.org (Chris Lawrence) 58 ---------- 76 /dev/ram: -> 0x0100 (initial ramdisk) 77 /dev/hda: -> 0x0300 (first IDE disk) 78 /dev/hdb: -> 0x0340 (second IDE disk) 79 /dev/sda: -> 0x0800 (first SCSI disk) 80 /dev/sdb: -> 0x0810 (second SCSI disk) 81 /dev/sdc: -> 0x0820 (third SCSI disk) 82 /dev/sdd: -> 0x0830 (forth SCSI disk) [all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | colorspaces.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later 12 you can accurately display that color. A colorspace defines what it 74 Different display devices will have different primaries and some 75 primaries are more suitable for some display technologies than others. 77 different display technologies or uses. To define a colorspace you need 93 eye, nor display technology is linear. Doubling the values of all 97 the non-linear component value, which is a closer match to the 98 non-linear performance of both the eye and displays. Linear component 99 values are denoted RGB, non-linear are denoted as R'G'B'. In general 102 provide linear RGB colors or to use the built-in openGL support to apply [all …]
|
| /Documentation/arch/arm/omap/ |
| D | dss.rst | 2 OMAP2/3 Display Subsystem 7 TV-out and multiple display support, but there are lots of small improvements 10 The DSS2 driver (omapdss module) is in arch/arm/plat-omap/dss/, and the FB, 15 -------- 19 - MIPI DPI (parallel) output 20 - MIPI DSI output in command mode 21 - MIPI DBI (RFBI) output 22 - SDI output 23 - TV output 24 - All pieces can be compiled as a module or inside kernel [all …]
|
| /Documentation/trace/ |
| D | ftrace.rst | 2 ftrace - Function Tracer 13 - Written for: 2.6.28-rc2 14 - Updated for: 3.10 15 - Updated for: 4.13 - Copyright 2017 VMware Inc. Steven Rostedt 16 - Converted to rst format - Changbin Du <changbin.du@intel.com> 19 ------------ 24 performance issues that take place outside of user-space. 41 ---------------------- 43 See Documentation/trace/ftrace-design.rst for details for arch porters and such. 47 --------------- [all …]
|
12