Home
last modified time | relevance | path

Searched refs:overlay (Results 1 – 25 of 142) sorted by relevance

123456

/linux/drivers/gpu/drm/vmwgfx/
H A Dvmwgfx_overlay.c248 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()
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()
359 struct vmw_overlay *overlay = dev_priv->overlay_priv; in vmw_overlay_resume_all() local
362 if (!overlay) in vmw_overlay_resume_all()
365 mutex_lock(&overlay->mutex); in vmw_overlay_resume_all()
368 struct vmw_stream *stream = &overlay->stream[i]; in vmw_overlay_resume_all()
379 mutex_unlock(&overlay->mutex); in vmw_overlay_resume_all()
393 struct vmw_overlay *overlay = dev_priv->overlay_priv; in vmw_overlay_pause_all() local
[all …]
/linux/include/video/
H A Dmmp_disp.h137 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);
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()
267 overlay->ops->set_fetch(overlay, fetch_id); in mmp_overlay_set_fetch()
269 static inline void mmp_overlay_set_onoff(struct mmp_overlay *overlay, in mmp_overlay_set_onoff() argument
272 if (overlay) in mmp_overlay_set_onoff()
273 overlay->ops->set_onoff(overlay, status); in mmp_overlay_set_onoff()
[all …]
/linux/drivers/video/fbdev/mmp/hw/
H A Dmmp_ctrl.c48 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/Documentation/ABI/testing/
H A Dsysfs-devices-platform-sh_mobile_lcdc_fb6 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/userspace-api/media/v4l/
H A Dvidioc-overlay.rst13 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 Ddev-overlay.rst12 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
38 capturing and overlay with a single file descriptor for compatibility
43 While the X server controls video overlay, the application can take
[all …]
H A Dvidioc-g-fbuf.rst13 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
65 this structure, the driver prepares for the overlay and returns the
72 the overlay and returns the framebuffer parameters as :ref:`VIDIOC_G_FBUF <VIDIOC_G_FBUF>`
259 the overlay is destructive. This flag is typically set by any
[all …]
H A Ddev-osd.rst12 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.
104 for the video output overlay, or -1 if no device was found. */
110 The overlay is controlled by source and target rectangles. The source
116 :ref:`Video Overlay <overlay>` interface.
120 clipping/blending method to be used for the overlay. To get the current
136 :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>` this also works after the overlay has been enabled.
139 of the target rectangle. The scaling factor of the overlay is implied by
150 There is no V4L2 ioctl to enable or disable the overlay, however the
H A Dio.rst22 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
/linux/Documentation/filesystems/
H A Doverlayfs.rst10 overlay-filesystem functionality in Linux (sometimes referred to as
11 union-filesystems). An overlay-filesystem tries to present a
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
39 On 64bit systems, even if all overlay layers are not on the same
45 the underlying inode number does overflow into the high xino bits, overlay
[all …]
/linux/fs/overlayfs/
H A DKconfig7 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
99 If this config option is enabled then overlay filesystems will use
[all …]
H A DMakefile6 obj-$(CONFIG_OVERLAY_FS) += overlay.o
8 overlay-objs := super.o namei.o util.o inode.o file.o dir.o readdir.o \
/linux/drivers/gpu/drm/omapdrm/
H A Domap_overlay.h31 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 Doverlay_bad_add_dup_prop.dtso11 * 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
H A DMakefile4 obj-$(CONFIG_OF_OVERLAY) += overlay.dtbo.o \
97 apply_static_overlay_2 := overlay.dtbo
/linux/Documentation/arch/arm/omap/
H A Ddss.rst46 The DSS driver models OMAP's overlays, overlay managers and displays in a
48 modelling the hardware overlays, omapdss supports virtual overlays and overlay
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.
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
146 connected only to DISPC overlay managers, and virtual overlays can be only
149 An overlay manager can be connected to one display. There are certain
[all …]
/linux/drivers/of/
H A DMakefile13 obj-$(CONFIG_OF_OVERLAY) += overlay.o
24 obj-$(CONFIG_OF_OVERLAY_KUNIT_TEST) += overlay-test.o
25 overlay-test-y := overlay_test.o kunit_overlay_test.dtbo.o
/linux/Documentation/fb/
H A Dpxafb.rst93 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/arch/arm64/boot/dts/broadcom/
H A Dbcm2712-rpi-5-b.dts3 * 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.
/linux/drivers/video/fbdev/omap2/omapfb/dss/
H A Doverlay-sysfs.c399 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()
H A DMakefile8 omapdss-y += manager.o manager-sysfs.o overlay.o overlay-sysfs.o apply.o \
/linux/arch/arm64/boot/dts/rockchip/
H A Drk3588-rock-5b-pcie-srns.dtso3 * DT-overlay to run the PCIe3_4L Dual Mode controller in Root Complex
6 * This device tree overlay is only needed (on the RC side) when running
H A Drk3588-rock-5b-pcie-ep.dtso3 * DT-overlay to run the PCIe3_4L Dual Mode controller in Endpoint mode
8 * tree overlay: rk3588-rock-5b-pcie-srns.dtso.
/linux/Documentation/translations/zh_CN/devicetree/
H A Doverlay-notes.rst4 :Original: Documentation/devicetree/overlay-notes.rst
16 本文档描述了drivers/of/overlay.c中的内核内设备树覆盖功能的实现，是
/linux/drivers/video/fbdev/mmp/fb/
H A Dmmpfb.c342 mmp_overlay_set_addr(fbi->overlay, &addr); in mmpfb_pan_display()
395 mmp_overlay_set_win(fbi->overlay, &win); in mmpfb_set_win()
421 mmp_overlay_set_addr(fbi->overlay, &addr); in mmpfb_set_par()
441 mmp_overlay_set_addr(fbi->overlay, &addr); in mmpfb_power()
443 mmp_overlay_set_onoff(fbi->overlay, power); in mmpfb_power()
575 fbi->overlay = mmp_path_get_overlay(fbi->path, mi->overlay_id); in mmpfb_probe()
576 if (!fbi->overlay) { in mmpfb_probe()
581 mmp_overlay_set_fetch(fbi->overlay, mi->dmafetch_id); in mmpfb_probe()

123456