Searched full:overlay (Results 1 – 25 of 66) sorted by relevance
123
| /Documentation/devicetree/ |
| D | overlay-notes.rst | 4 Devicetree Overlay Notes
8 device tree overlay functionality residing in drivers/of/overlay.c and is a
14 A Devicetree's overlay purpose is to modify the kernel's live tree, and
41 The overlay bar.dts,
44 ---- bar.dts - overlay target location by label ----------------------------
81 As a result of the overlay, a new device node (bar) has been created
86 will not be available to resolve the overlay node(s) to the proper location
88 location by label syntax is preferred because the overlay can be applied to
93 ---- bar.dts - overlay target location by explicit path --------------------
106 Overlay in-kernel API
[all …]
|
| D | kernel-api.rst | 47 Overlay and Dynamic DT functions
56 .. kernel-doc:: drivers/of/overlay.c
|
| D | index.rst | 23 overlay-notes
|
| /Documentation/filesystems/ |
| D | overlayfs.rst | 6 Overlay Filesystem
10 overlay-filesystem functionality in Linux (sometimes referred to as
11 union-filesystems). An overlay-filesystem tries to present a
16 Overlay objects
19 The overlay filesystem approach is 'hybrid', because the objects that
25 While directories will report an st_dev from the overlay-filesystem,
32 In the special case of all overlay layers on the same underlying
33 filesystem, all objects will report an st_dev from the overlay
35 make the overlay mount more compliant with filesystem scanners and
36 overlay objects will be distinguishable from the corresponding
[all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | dev-osd.rst | 6 Video Output Overlay Interface
11 Some video output devices can overlay a framebuffer image onto the
12 outgoing video signal. Applications can set up such an overlay using
14 :ref:`Video Overlay <overlay>` interface.
29 Devices supporting the *Video Output Overlay* interface set the
38 Contrary to the *Video Overlay* interface the framebuffer is normally
103 for the video output overlay, or -1 if no device was found. */
106 Overlay Window and Scaling
109 The overlay is controlled by source and target rectangles. The source
115 :ref:`Video Overlay <overlay>` interface.
[all …]
|
| D | vidioc-overlay.rst | 13 VIDIOC_OVERLAY - Start or stop video overlay
34 This ioctl is part of the :ref:`video overlay <overlay>` I/O method.
35 Applications call :ref:`VIDIOC_OVERLAY` to start or stop the overlay. It
37 application to stop overlay, to one to start.
51 The overlay parameters have not been set up. See :ref:`overlay`
|
| D | dev-overlay.rst | 6 Video Overlay Interface
9 **Also known as Framebuffer Overlay or Previewing.**
11 Video overlay devices have the ability to genlock (TV-)video into the
19 Video overlay devices are accessed through the same character special
25 capturing. The overlay function is only available after calling
28 The driver may support simultaneous overlay and capturing using the
31 directed away from overlay to capture, or one field may be used for
32 overlay and the other for capture if the capture parameters permit this.
35 overlay. This must be supported by all drivers capable of simultaneous
36 capturing and overlay. Optionally these drivers may also permit
[all …]
|
| D | vidioc-g-fbuf.rst | 13 VIDIOC_G_FBUF - VIDIOC_S_FBUF - Get or set frame buffer overlay parameters
40 :ref:`Video Overlay <overlay>` or :ref:`Video Output Overlay <osd>`
41 (OSD). The type of overlay is implied by the device type (capture or
44 device must not support both kinds of overlay.
47 destructive overlay copies captured video images into the video memory
48 of a graphics card. A non-destructive overlay blends video images into a
52 Destructive overlay support has been removed: with modern GPUs and CPUs
60 To set the parameters for a *Video Output Overlay*, applications must
65 this structure, the driver prepares for the overlay and returns the
69 To set the parameters for a *Video Capture Overlay*
[all …]
|
| D | io.rst | 22 Video overlay can be considered another I/O method, although the
24 initiating video overlay with the :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`
25 ioctl. For more information see :ref:`overlay`.
27 Generally exactly one I/O method, including overlay, is associated with
30 and drivers permitting simultaneous video capturing and overlay using
|
| D | diff-v4l.rst | 21 for V4L2 video capture, overlay, radio and raw vbi capture devices did
44 * - Video capture and overlay
72 capturing, video overlay and VBI capturing. See :ref:`open` for an
102 - The :ref:`video overlay <overlay>` interface is supported.
106 - Whether chromakey overlay is supported. For more information on
107 overlay see :ref:`overlay`.
113 :ref:`overlay`.
117 - Whether overlay overwrites frame buffer memory, see
118 :ref:`overlay`.
411 Frame Buffer Overlay
[all …]
|
| D | format.rst | 49 example video overlay is about to start or already in progress,
61 overlay using the same file descriptor for compatibility with V4L and
74 enumerate all image formats supported by video capture, overlay or
|
| D | vidioc-querycap.rst | 172 - The device supports the :ref:`Video Overlay <overlay>`
173 interface. A video overlay device typically stores captured images
197 - The device supports the :ref:`Video Output Overlay <osd>` (OSD)
198 interface. Unlike the *Video Overlay* interface, this is a
289 type of overlay is implied by the driver capabilities.
|
| D | devices.rst | 14 dev-overlay
|
| D | pixfmt.rst | 15 focus on video capturing and output, for overlay frame buffer formats
|
| /Documentation/ABI/testing/ |
| D | sysfs-devices-platform-sh_mobile_lcdc_fb | 6 to overlay planes.
8 Stores the alpha blending value for the overlay. Values range
17 to overlay planes.
19 Selects the composition mode for the overlay. Possible values
30 to overlay planes.
32 Stores the x,y overlay position on the display in pixels. The
40 to overlay planes.
42 Stores the raster operation (ROP3) for the overlay. Values
|
| /Documentation/arch/arm/omap/ |
| D | dss.rst | 46 The DSS driver models OMAP's overlays, overlay managers and displays in a
48 modelling the hardware overlays, omapdss supports virtual overlays and overlay
132 - Overlay defines where the pixels are read from and where they go on the
133 screen. The overlay may be smaller than framebuffer, thus displaying only
134 part of the framebuffer. The position of the overlay may be changed if
135 the overlay is smaller than the display.
136 - Overlay manager combines the overlays in to one image and feeds them to
141 on all of the overlays. Note that in this case the overlay input sizes must be
143 framebuffer can be connected to any overlay.
145 An overlay can be connected to one overlay manager. Also DISPC overlays can be
[all …]
|
| /Documentation/gpu/amdgpu/display/ |
| D | mpo-overview.rst | 2 Multiplane Overlay (MPO)
9 Multiplane Overlay (MPO) allows for multiple framebuffers to be composited via
24 Multiplane Overlay is only available using the DRM atomic model. The atomic
36 * ``DRM_PLANE_TYPE_OVERLAY``: Overlay planes represent all non-primary,
45 * 1 Overlay plane (shared among CRTCs).
55 A typical MPO configuration from userspace - 1 primary + 1 overlay on a single
58 At least 1 pipe must be used per plane (primary and overlay), so for this
73 * Overlay planes must be in ARGB8888 or XRGB8888 format
81 * Only overlay planes have alpha blending support
115 * 1 RGBA DRM Overlay Plane (e.g. ARGB8888 desktop). The compositor should
[all …]
|
| /Documentation/fb/ |
| D | pxafb.rst | 84 Overlay Support for PXA27x and later LCD controllers
93 However, there are some differences between these overlay framebuffers
96 1. overlay can start at a 32-bit word aligned position within the base
101 2. overlay framebuffer is allocated dynamically according to specified
118 a. overlay does not support panning in x-direction, thus
121 b. line length of overlay(s) must be on a 32-bit word boundary,
130 d. the rectangle of the overlay should be within the base plane,
133 Applications should follow the sequence below to operate an overlay
|
| /Documentation/devicetree/bindings/fpga/ |
| D | fpga-region.yaml | 115 When a DT overlay that targets an FPGA Region is applied, the FPGA Region will
121 4. The Device Tree overlay is accepted into the live tree.
124 When the overlay is removed, the child nodes will be removed and the FPGA Region
140 The intended use is that a Device Tree overlay (DTO) can be used to reprogram an
147 FPGA. After reprogramming is successful, the overlay is accepted into the live
178 a FPGA Region. The target of the Device Tree Overlay is the FPGA Region. Some
188 need to be controlled during full reconfiguration. Before the overlay is
192 fpga-bridges property in the FPGA region or in the device tree overlay.
257 If this property is in an overlay targeting an FPGA region, it is
302 * Full Reconfiguration without Bridges with DT overlay
[all …]
|
| /Documentation/devicetree/bindings/display/ti/ |
| D | ti,j721e-dss.yaml | 34 - description: OVR1 overlay manager for vp1
35 - description: OVR2 overlay manager for vp2
36 - description: OVR3 overlay manager for vp3
37 - description: OVR4 overlay manager for vp4
|
| /Documentation/virt/hyperv/ |
| D | overview.rst | 97 and the Linux guest are "overlay" pages. With overlay pages, Linux
103 that it originally allocated. The "overlay" behavior is visible
106 overlay page is inserted. Similarly, the contents change if Linux
107 revokes the sharing, in which case Hyper-V removes the overlay page,
113 a shared page or remove an overlay page after the new kernel is
|
| /Documentation/devicetree/bindings/display/mediatek/ |
| D | mediatek,ovl-2l.yaml | 7 title: Mediatek display overlay 2 layer
14 Mediatek display overlay 2 layer, namely OVL-2L, provides 2 more layer
|
| D | mediatek,ovl.yaml | 7 title: Mediatek display overlay
14 Mediatek display overlay, namely OVL, can do alpha blending from
|
| /Documentation/translations/zh_CN/devicetree/ |
| D | kernel-api.rst | 58 drivers/of/overlay.c
|
| D | index.rst | 36 overlay-notes
|
123