| /linux/drivers/gpu/drm/vmwgfx/ |
| H A D | vmwgfx_overlay.c | 46 * Overlay control
50 * Each stream is a single overlay. In Xv these are called ports.
239 * The caller must hold the overlay lock.
248 struct vmw_overlay *overlay = dev_priv->overlay_priv; in vmw_overlay_stop() local
249 struct vmw_stream *stream = &overlay->stream[stream_id]; in vmw_overlay_stop()
285 * The caller must hold the overlay lock.
296 struct vmw_overlay *overlay = dev_priv->overlay_priv; in vmw_overlay_update_stream() local
297 struct vmw_stream *stream = &overlay->stream[arg->stream_id]; in vmw_overlay_update_stream()
355 * Takes the overlay lock.
359 struct vmw_overlay *overlay = dev_priv->overlay_priv; in vmw_overlay_resume_all() local
[all …]
|
| /linux/Documentation/filesystems/ |
| H A 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 …]
|
| /linux/include/video/ |
| H A D | mmp_disp.h | 66 /* parameters used by path/overlay */
67 /* overlay related para: win/addr */
137 void (*set_fetch)(struct mmp_overlay *overlay, int fetch_id);
138 void (*set_onoff)(struct mmp_overlay *overlay, int status);
139 void (*set_win)(struct mmp_overlay *overlay, struct mmp_win *win);
140 int (*set_addr)(struct mmp_overlay *overlay, struct mmp_addr *addr);
143 /* overlay describes a z-order indexed slot in each path. */
149 /* overlay info: private data */
263 static inline void mmp_overlay_set_fetch(struct mmp_overlay *overlay, in mmp_overlay_set_fetch() argument
266 if (overlay) in mmp_overlay_set_fetch()
[all …]
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | dev-osd.rst | 7 Video Output Overlay Interface
12 Some video output devices can overlay a framebuffer image onto the
13 outgoing video signal. Applications can set up such an overlay using
15 :ref:`Video Overlay <overlay>` interface.
30 Devices supporting the *Video Output Overlay* interface set the
39 Contrary to the *Video Overlay* interface the framebuffer is normally
104 for the video output overlay, or -1 if no device was found. */
107 Overlay Window and Scaling
110 The overlay is controlled by source and target rectangles. The source
116 :ref:`Video Overlay <overlay>` interface.
[all …]
|
| H A D | dev-overlay.rst | 7 Video Overlay Interface
10 **Also known as Framebuffer Overlay or Previewing.**
12 Video overlay devices have the ability to genlock (TV-)video into the
20 Video overlay devices are accessed through the same character special
26 capturing. The overlay function is only available after calling
29 The driver may support simultaneous overlay and capturing using the
32 directed away from overlay to capture, or one field may be used for
33 overlay and the other for capture if the capture parameters permit this.
36 overlay. This must be supported by all drivers capable of simultaneous
37 capturing and overlay. Optionally these drivers may also permit
[all …]
|
| H A 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 …]
|
| H A 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`
|
| H A 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
|
| H A 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 …]
|
| /linux/drivers/of/ |
| H A D | unittest.c | 1904 * the respective unittest overlay contains a label that has the in update_node_properties()
1909 * overlay dts files with an odd prefix that is unlikely to be in update_node_properties()
2249 "Adding overlay 'overlay_gpio_01' failed\n"); in of_unittest_overlay_gpio()
2252 "Adding overlay 'overlay_gpio_02a' failed\n"); in of_unittest_overlay_gpio()
2255 "Adding overlay 'overlay_gpio_02b' failed\n"); in of_unittest_overlay_gpio()
2278 * apply overlay will result in in of_unittest_overlay_gpio()
2288 "Adding overlay 'overlay_gpio_03' failed\n"); in of_unittest_overlay_gpio()
2302 * apply the overlay will result in in of_unittest_overlay_gpio()
2312 "Adding overlay 'overlay_gpio_04a' failed\n"); in of_unittest_overlay_gpio()
2322 * apply the overlay will result in in of_unittest_overlay_gpio()
[all …]
|
| /linux/drivers/video/fbdev/mmp/hw/ |
| H A D | mmp_ctrl.c | 48 static u32 fmt_to_reg(struct mmp_overlay *overlay, int pix_fmt) in fmt_to_reg() argument
52 vid = overlay_is_vid(overlay); in fmt_to_reg()
119 static void dmafetch_set_fmt(struct mmp_overlay *overlay) in dmafetch_set_fmt() argument
122 struct mmp_path *path = overlay->path; in dmafetch_set_fmt()
124 tmp &= ~dma_mask(overlay_is_vid(overlay)); in dmafetch_set_fmt()
125 tmp |= fmt_to_reg(overlay, overlay->win.pix_fmt); in dmafetch_set_fmt()
129 static void overlay_set_win(struct mmp_overlay *overlay, struct mmp_win *win) in overlay_set_win() argument
131 struct lcd_regs *regs = path_regs(overlay->path); in overlay_set_win()
134 memcpy(&overlay->win, win, sizeof(struct mmp_win)); in overlay_set_win()
136 mutex_lock(&overlay->access_ok); in overlay_set_win()
[all …]
|
| /linux/fs/overlayfs/ |
| H A D | Kconfig | 3 tristate "Overlay filesystem support"
7 An overlay filesystem combines two filesystems - an 'upper' filesystem
19 If this config option is enabled then overlay filesystems will use
26 an overlay which has redirects on a kernel that doesn't support this
50 If this config option is enabled then overlay filesystems will use
60 That is, mounting an overlay which has an inodes index on a kernel
71 If this config option is enabled then overlay filesystems will use
72 the index directory to decode overlay NFS file handles by default.
78 directory. This full index is used to detect overlay filesystems
85 That is, mounting an overlay which has a full index on a kernel
[all …]
|
| H A D | Makefile | 3 # Makefile for the overlay filesystem.
6 obj-$(CONFIG_OVERLAY_FS) += overlay.o
8 overlay-objs := super.o namei.o util.o inode.o file.o dir.o readdir.o \
|
| /linux/Documentation/ABI/testing/ |
| H A 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
|
| /linux/Documentation/arch/arm/omap/ |
| H A 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 …]
|
| /linux/include/kunit/ |
| H A D | of.h | 42 * @overlay_begin: start address of overlay to apply
43 * @overlay_end: end address of overlay to apply
48 * Similar to of_overlay_fdt_apply(), except the overlay is managed by the test
75 * @overlay_name: name of overlay to apply
77 * This macro is used to apply a device tree overlay built with the
79 * kernel image or KUnit test module. The overlay is automatically removed when
82 * Unit tests that need device tree nodes should compile an overlay file with
84 * load the overlay during their test. The @overlay_name matches the filename
85 * of the overlay without the dtbo filename extension. If CONFIG_OF_OVERLAY is
|
| /linux/Documentation/gpu/amdgpu/display/ |
| H A 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 …]
|
| /linux/drivers/video/fbdev/kyro/ |
| H A D | STG4000OverlayDevice.c | 34 /* Overlay surface */
57 /*clipped on-screen pixel position of overlay */
69 /* on-screen pixel position of overlay */
83 /* Set Overlay address to default */ in ResetOverlayRegisters()
89 /* Set Overlay U address */ in ResetOverlayRegisters()
94 /* Set Overlay V address */ in ResetOverlayRegisters()
99 /* Set Overlay Size */ in ResetOverlayRegisters()
105 /* Set Overlay Vt Decimation */ in ResetOverlayRegisters()
109 /* Set Overlay format to default value */ in ResetOverlayRegisters()
175 /* Set Overlay address and Format mode */ in CreateOverlaySurface()
[all …]
|
| /linux/Documentation/fb/ |
| H A 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
|
| /linux/drivers/gpu/drm/omapdrm/ |
| H A D | omap_overlay.h | 18 /* Used to associate a HW overlay/plane to a plane */
31 u32 caps, u32 fourcc, struct omap_hw_overlay **overlay,
33 void omap_overlay_release(struct drm_atomic_state *s, struct omap_hw_overlay *overlay);
34 void omap_overlay_update_state(struct omap_drm_private *priv, struct omap_hw_overlay *overlay);
|
| /linux/drivers/of/unittest-data/ |
| H A D | overlay_bad_add_dup_prop.dtso | 11 * This will result in an error and the overlay apply
18 * will occur if the overlay is removed. Since the overlay apply
21 * enabled. Adding the overlay node 'electric' avoids the
|
| /linux/Documentation/devicetree/bindings/fpga/ |
| H A D | fpga-region.yaml | 112 When a DT overlay that targets an FPGA Region is applied, the FPGA Region will
118 4. The Device Tree overlay is accepted into the live tree.
121 When the overlay is removed, the child nodes will be removed and the FPGA Region
136 The intended use is that a Device Tree overlay (DTO) can be used to reprogram an
143 FPGA. After reprogramming is successful, the overlay is accepted into the live
173 a FPGA Region. The target of the Device Tree Overlay is the FPGA Region. Some
183 need to be controlled during full reconfiguration. Before the overlay is
187 fpga-bridges property in the FPGA region or in the device tree overlay.
252 If this property is in an overlay targeting an FPGA region, it is
297 * Full Reconfiguration without Bridges with DT overlay
[all …]
|
| /linux/drivers/video/fbdev/omap2/omapfb/dss/ |
| H A D | overlay-sysfs.c | 10 #define DSS_SUBSYS_NAME "OVERLAY"
88 DSSERR("Failed to attach overlay\n"); in overlay_manager_store()
399 struct omap_overlay *overlay; in overlay_attr_show() local
402 overlay = container_of(kobj, struct omap_overlay, kobj); in overlay_attr_show()
408 return overlay_attr->show(overlay, buf); in overlay_attr_show()
414 struct omap_overlay *overlay; in overlay_attr_store() local
417 overlay = container_of(kobj, struct omap_overlay, kobj); in overlay_attr_store()
423 return overlay_attr->store(overlay, buf, size); in overlay_attr_store()
440 &pdev->dev.kobj, "overlay%d", ovl->id); in dss_overlay_kobj_init()
|
| /linux/drivers/gpu/drm/exynos/ |
| H A D | exynos_drm_drv.h | 60 * specific overlay info.
78 * Exynos drm common overlay structure.
81 * @index: hardware index of the overlay layer
84 * to hardware specific overlay info.
104 * @type: type of the plane (primary, cursor or overlay).
129 * @update_plane: apply hardware specific overlay data to registers.
130 * @disable_plane: disable hardware specific overlay.
|
| /linux/arch/arm64/boot/dts/broadcom/ |
| H A D | bcm2712-rpi-5-b.dts | 3 * bcm2712-rpi-5-b-ovl-rp1.dts is the overlay-ready DT which will make
4 * the RP1 driver to load the RP1 dtb overlay at runtime, while
6 * already contains RP1 node, so no overlay is loaded nor needed).
12 * are not yet defined in the DT since they are loaded at runtime via overlay.
|