Searched +full:display +full:- +full:related (Results 1 – 25 of 70) sorted by relevance
123
| /Documentation/gpu/amdgpu/display/ |
| D | dc-glossary.rst | 5 On this page, we try to keep track of acronyms related to the display 7 'Documentation/gpu/amdgpu/amdgpu-glossary.rst'; if you cannot find it anywhere, 19 Application-Specific Integrated Circuit 37 * DISPCLK: Display Clock 39 * DCFCLK: Display Controller Fabric Clock 49 Cathode Ray Tube Controller - commonly called "Controller" - Generates 56 Display Abstraction layer 59 Display Core 62 Display Controller 68 Display Controller Engine [all …]
|
| D | dc-debug.rst | 2 Display Core Debug tools 8 Display core provides a feature named visual confirmation, which is a set of 19 --------------------- 21 If you want to enable or debug multiple planes in a specific user-space 31 * The color indicates the format - For example, red is AR24 and green is NV12 49 ---------------- 58 bottom of the display covering the entire display width and another bar 67 using Display Test Next (DTN) log, which can be captured via debugfs by using:: 72 change in real-time by using something like:: 74 sudo watch -d cat /sys/kernel/debug/dri/0/amdgpu_dm_dtn_log [all …]
|
| /Documentation/devicetree/bindings/gpio/ |
| D | xylon,logicvc-gpio.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 4 --- 5 $id: http://devicetree.org/schemas/gpio/xylon,logicvc-gpio.yaml# 6 $schema: http://devicetree.org/meta-schemas/core.yaml# 11 - Paul Kocialkowski <paul.kocialkowski@bootlin.com> 14 The LogiCVC GPIO describes the GPIO block included in the LogiCVC display 15 controller. These are meant to be used for controlling display-related 18 The controller exposes GPIOs from the display and power control registers, 20 - GPIO[4:0] (display control) mapped to index 0-4 21 - EN_BLIGHT (power control) mapped to index 5 [all …]
|
| /Documentation/gpu/ |
| D | i915.rst | 6 models) integrated GFX chipsets with both Intel display and rendering 13 This section covers core driver infrastructure used by both the display 17 ------------------------ 19 .. kernel-doc:: drivers/gpu/drm/i915/intel_runtime_pm.c 22 .. kernel-doc:: drivers/gpu/drm/i915/intel_runtime_pm.c 25 .. kernel-doc:: drivers/gpu/drm/i915/intel_uncore.c 29 ------------------ 31 .. kernel-doc:: drivers/gpu/drm/i915/i915_irq.c 34 .. kernel-doc:: drivers/gpu/drm/i915/i915_irq.c 37 .. kernel-doc:: drivers/gpu/drm/i915/i915_irq.c [all …]
|
| D | vc4.rst | 5 .. kernel-doc:: drivers/gpu/drm/vc4/vc4_drv.c 8 Display Hardware Handling 11 This section covers everything related to the display hardware including 13 display, output probing and related topics. 16 ---------------------- 18 .. kernel-doc:: drivers/gpu/drm/vc4/vc4_crtc.c 22 --- 24 .. kernel-doc:: drivers/gpu/drm/vc4/vc4_hvs.c 28 ---------- 30 .. kernel-doc:: drivers/gpu/drm/vc4/vc4_plane.c [all …]
|
| D | komeda-kms.rst | 1 .. SPDX-License-Identifier: GPL-2.0 4 drm/komeda Arm display driver 7 The drm/komeda driver supports the Arm display processor D71 and later products, 11 Overview of D71 like display IPs 14 From D71, Arm display IP begins to adopt a flexible and modularized 15 architecture. A display pipeline is made up of multiple individual and 23 ----- 30 ------ 34 for layer scaling, or connected to compositor and scale the whole display 39 ------------------- [all …]
|
| D | drm-kms-helpers.rst | 23 also the simple display pipe helpers. 27 for handling panel-related information and logic. Plus then a big set of 32 * The last group of helpers concerns itself with the frontend side of a display 39 .. kernel-doc:: include/drm/drm_modeset_helper_vtables.h 42 .. kernel-doc:: include/drm/drm_modeset_helper_vtables.h 51 -------- 53 .. kernel-doc:: drivers/gpu/drm/drm_atomic_helper.c 57 --------------------------------------- 59 .. kernel-doc:: drivers/gpu/drm/drm_atomic_helper.c 63 -------------------------- [all …]
|
| D | drm-uapi.rst | 9 addition, drivers export device-specific interfaces for use by userspace 10 drivers & device-aware applications through ioctls and sysfs files. 16 Cover generic ioctls and sysfs layout here. We only need high-level 22 .. kernel-doc:: drivers/gpu/drm/drm_ioctl.c 31 .. kernel-doc:: drivers/gpu/drm/drm_auth.c 34 .. kernel-doc:: drivers/gpu/drm/drm_auth.c 37 .. kernel-doc:: include/drm/drm_auth.h 43 DRM Display Resource Leasing 46 .. kernel-doc:: drivers/gpu/drm/drm_lease.c 49 Open-Source Userspace Requirements [all …]
|
| D | todo.rst | 11 ---------- 18 subsystem, or some specific GPU/display graphics knowledge. For debugging issue 29 Subsystem-wide refactorings 33 --------------------------------------------- 45 -------------------------------------------------- 53 non-converted driver. The "Atomic mode setting design overview" series [2]_ 60 .. [1] https://blog.ffwll.ch/2014/11/atomic-modeset-support-for-kms-drivers.html 69 --------------------------------------------------------- 75 avoid confusion - the other helpers in that file are all deprecated legacy 83 ---------------------------------- [all …]
|
| /Documentation/admin-guide/auxdisplay/ |
| D | ks0108.rst | 7 :Date: 2006-10-27 19 --------------------- 25 --------------------- 30 :Webpage: - 31 :Device Webpage: - 32 :Type: LCD Controller (Liquid Crystal Display Controller) 43 --------- 47 If you aren't building LCD related hardware, you should check 50 For example, check Documentation/admin-guide/auxdisplay/cfag12864b.rst
|
| /Documentation/devicetree/bindings/display/bridge/ |
| D | fsl,imx93-mipi-dsi.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/display/bridge/fsl,imx93-mipi-dsi.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Liu Ying <victor.liu@nxp.com> 15 and extensions to them are controlled by i.MX93 media blk-ctrl. 18 - $ref: snps,dw-mipi-dsi.yaml# 22 const: fsl,imx93-mipi-dsi 26 - description: apb clock 27 - description: pixel clock [all …]
|
| /Documentation/netlink/specs/ |
| D | ovs_flow.yaml | 1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 5 protocol: genetlink-legacy 6 uapi-header: linux/openvswitch.h 12 - 13 name: ovs-header 18 - 19 name: dp-ifindex 24 - 25 name: ovs-flow-stats 28 - [all …]
|
| /Documentation/hwmon/ |
| D | acpi_power_meter.rst | 17 ----------- 21 features--a power meter that returns average power use over a configurable 24 of Documentation/hwmon/sysfs-interface.rst. 27 ---------------- 29 The `power[1-*]_is_battery` knob indicates if the power supply is a battery. 30 Both `power[1-*]_average_{min,max}` must be set before the trip points will work. 33 `power[1-*]_average` sysfs file. 35 The `power[1-*]_{model_number, serial_number, oem_info}` fields display 40 the case, the `power[1-*]_cap` and related sysfs files will appear. When the 43 appropriate `power[1-*]_alarm` file to indicate that capping has begun, and the [all …]
|
| /Documentation/admin-guide/media/ |
| D | mgb4.rst | 1 .. SPDX-License-Identifier: GPL-2.0 7 --------------- 10 stream related parameters (some of them must be set properly before the v4l2 13 There are two types of parameters - global / PCI card related, found under 23 | 0 - No module present 24 | 1 - FPDL3 25 | 2 - GMSL 33 | 1 - FPDL3 34 | 2 - GMSL 42 PRODUCT-REVISION-SERIES-SERIAL [all …]
|
| /Documentation/gpu/amdgpu/ |
| D | driver-core.rst | 32 This was a dedicated IP on older pre-vega chips, but has since 56 DCN (Display Controller Next) 57 This is the display controller. It handles the display hardware. 58 It is described in more details in :ref:`Display Core <amdgpu-display-core>`. 61 This is a multi-purpose DMA engine. The kernel driver uses it for 69 largest block on the GPU. The 3D pipeline has tons of sub-blocks. In 75 This is the multi-media engine. It handles video and image encode and 76 decode. It's exposed to userspace for user mode drivers (VA-API, 80 ------------------------------------- 97 power management related functionality within the GFX/Compute engine. [all …]
|
| /Documentation/networking/ |
| D | vxlan.rst | 1 .. SPDX-License-Identifier: GPL-2.0 20 use of statically-configured forwarding entries. 34 the IANA-assigned value of 4789. The Linux implementation of VXLAN 35 pre-dates the IANA's selection of a standard destination port number 36 and uses the Linux-selected value by default to maintain backwards 45 # ip -d link show vxlan0 47 It is possible to create, destroy and display the vxlan 62 The following NIC features may indicate support for UDP tunnel-related 66 - `tx-udp_tnl-segmentation` 67 - `tx-udp_tnl-csum-segmentation` [all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-fm-rx.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later 3 .. _fm-rx-controls: 13 .. _fm-rx-control-id: 27 Gets RDS Programme Type field. This encodes up to 31 pre-defined 32 static display on a receiver. It is the primary aid to listeners in 45 wishes to transmit longer PS names, programme-related information or 70 enum v4l2_deemphasis - 71 Configures the de-emphasis value for reception. A de-emphasis filter 75 values for de-emphasis. Here they are: 79 .. flat-table:: [all …]
|
| D | ext-ctrls-fm-tx.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later 3 .. _fm-tx-controls: 15 .. _fm-tx-control-id: 27 step are driver-specific. 34 to 31 pre-defined programme types. 38 intended for static display on a receiver. It is the primary aid to 52 programme-related information or any other text. In these cases, 103 receiver-generated distortion and prevent overmodulation. 107 useconds. Step and range are driver-specific. 111 are driver-specific. [all …]
|
| /Documentation/virt/hyperv/ |
| D | overview.rst | 1 .. SPDX-License-Identifier: GPL-2.0 6 enlightened guest on Microsoft's Hyper-V hypervisor. Hyper-V 7 consists primarily of a bare-metal hypervisor plus a virtual machine 10 partitions. In this documentation, references to Hyper-V usually 15 Hyper-V runs on x86/x64 and arm64 architectures, and Linux guests 16 are supported on both. The functionality and behavior of Hyper-V is 19 Linux Guest Communication with Hyper-V 20 -------------------------------------- 21 Linux guests communicate with Hyper-V in four different ways: 24 some guest actions trap to Hyper-V. Hyper-V emulates the action and [all …]
|
| /Documentation/trace/ |
| D | osnoise-tracer.rst | 5 In the context of high-performance computing (HPC), the Operating System 9 system. Moreover, hardware-related jobs can also cause noise, for example, 32 source of interferences, increasing a per-cpu interference counter. The 38 hardware-related noise. In this way, osnoise can account for any 44 ----- 59 # _-----=> irqs-off 60 # / _----=> need-resched 61 # | / _---=> hardirq/softirq 62 # || / _--=> preempt-depth MAX 64 … |||| RUNTIME NOISE % OF CPU NOISE +-----------------------------+ [all …]
|
| /Documentation/admin-guide/laptops/ |
| D | thinkpad-acpi.rst | 9 - Borislav Deianov <borislav@users.sf.net> 10 - Henrique de Moraes Holschuh <hmh@hmh.eng.br> 12 http://ibm-acpi.sf.net/ 19 This driver used to be named ibm-acpi until kernel 2.6.21 and release 20 0.13-20070314. It used to be in the drivers/acpi tree, but it was 21 moved to the drivers/misc tree and renamed to thinkpad-acpi for kernel 25 The driver is named "thinkpad-acpi". In some places, like module 29 "tpacpi" is used as a shorthand where "thinkpad-acpi" would be too 33 ------ 38 - Fn key combinations [all …]
|
| /Documentation/wmi/devices/ |
| D | dell-wmi-ddv.rst | 1 .. SPDX-License-Identifier: GPL-2.0-or-later 4 Dell DDV WMI interface driver (dell-wmi-ddv) 10 Many Dell notebooks made after ~2020 support a WMI-based interface for 15 so it was called `DDV`. Currently the ``dell-wmi-ddv`` driver supports 21 trial-and-error, please keep that in mind. 27 including batteries. It has a form similar to `CC-PPPPPP-MMMMM-YMD-SSSS-FFF` 39 to decode and display this information. 52 …), Locale("MS\\0x409"), Description("WMI Function"), guid("{8A42EA14-4F2A-FD45-6422-0087F7A7E608}"… 67 …[WmiMethodId(11), Implemented, read, write, Description("Return Battery Relative State-Of-Charge."… 79 Each WMI method takes an ACPI buffer containing a 32-bit index as input argument, [all …]
|
| /Documentation/devicetree/bindings/pci/ |
| D | fsl,imx6q-pcie-common.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/pci/fsl,imx6q-pcie-common.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Lucas Stach <l.stach@pengutronix.de> 11 - Richard Zhu <hongxing.zhu@nxp.com> 22 clock-names: 26 num-lanes: 29 fsl,imx7d-pcie-phy: 31 description: A phandle to an fsl,imx7d-pcie-phy node. Additional [all …]
|
| /Documentation/driver-api/nvdimm/ |
| D | security.rst | 6 --------------- 16 ------------------ 21 The "show" attribute of that attribute will display the security state for 28 update <old_keyid> <new_keyid> - enable or update passphrase. 29 disable <keyid> - disable enabled security and remove key. 30 freeze - freeze changing of security states. 31 erase <keyid> - delete existing user encryption key. 32 overwrite <keyid> - wipe the entire nvdimm. 33 master_update <keyid> <new_keyid> - enable or update master passphrase. 34 master_erase <keyid> - delete existing user encryption key. [all …]
|
| /Documentation/locking/ |
| D | pi-futex.rst | 2 Lightweight PI-futexes 7 - in the user-space fastpath a PI-enabled futex involves no kernel work 9 calls - just pure fast atomic ops in userspace. 11 - even in the slowpath, the system call and scheduling pattern is very 14 - the in-kernel PI implementation is streamlined around the mutex 17 read-write lock support), only the owner may unlock a lock, no 20 Priority Inheritance - why? 21 --------------------------- 23 The short reply: user-space PI helps achieving/improving determinism for 24 user-space applications. In the best-case, it can help achieve [all …]
|
123