Home
last modified time | relevance | path

Searched refs:overlays (Results 1 – 25 of 95) sorted by relevance

1234

/OK3568_Linux_fs/u-boot/doc/
H A DREADME.fdt-overlays7 Overlays require slightly different syntax compared to traditional overlays.
9 regarding the internal format of overlays:
15 In a nutshell overlays provides a means to manipulate a symbol a previous dtb
16 or overlay has defined. It requires both the base and all the overlays
62 There are two ways to apply overlays in U-boot.
63 1. Include and define overlays within a FIT image and have overlays
66 2. Manually load and apply overlays
68 The remainder of this document will discuss using overlays via the manual
69 approach. For information on using overlays as part of a FIT image please see:
91 4. Grow it enough so it can 'fit' all the applied overlays
[all …]
/OK3568_Linux_fs/kernel/drivers/video/fbdev/omap2/omapfb/dss/
H A Doverlay.c28 static struct omap_overlay *overlays; variable
41 return &overlays[num]; in omap_dss_get_overlay()
51 overlays = kcalloc(num_overlays, sizeof(struct omap_overlay), in dss_init_overlays()
54 BUG_ON(overlays == NULL); in dss_init_overlays()
57 struct omap_overlay *ovl = &overlays[i]; in dss_init_overlays()
93 struct omap_overlay *ovl = &overlays[i]; in dss_uninit_overlays()
97 kfree(overlays); in dss_uninit_overlays()
98 overlays = NULL; in dss_uninit_overlays()
H A Dmanager.c66 INIT_LIST_HEAD(&mgr->overlays); in dss_init_overlay_managers()
145 list_for_each_entry(ovl1, &mgr->overlays, list) { in dss_mgr_check_zorder()
151 list_for_each_entry(ovl2, &mgr->overlays, list) { in dss_mgr_check_zorder()
236 list_for_each_entry(ovl, &mgr->overlays, list) { in dss_mgr_check()
H A Dapply.c218 list_for_each_entry(ovl, &mgr->overlays, list) { in dss_check_settings_low()
298 list_for_each_entry(ovl, &mgr->overlays, list) { in need_isr()
345 list_for_each_entry(ovl, &mgr->overlays, list) { in need_go()
377 list_for_each_entry(ovl, &mgr->overlays, list) { in extra_info_update_ongoing()
690 list_for_each_entry(ovl, &mgr->overlays, list) { in dss_mgr_write_regs()
790 list_for_each_entry(ovl, &mgr->overlays, list) { in mgr_clear_shadow_dirty()
983 list_for_each_entry(ovl, &mgr->overlays, list) in omap_dss_mgr_apply()
1048 list_for_each_entry(ovl, &mgr->overlays, list) in dss_mgr_setup_fifos()
1369 list_add_tail(&ovl->list, &mgr->overlays); in dss_ovl_set_manager()
/OK3568_Linux_fs/kernel/drivers/video/fbdev/mmp/
H A Dcore.c20 return &path->overlays[overlay_id]; in path_get_overlay()
28 if (path->overlays[i].status) in path_check_status()
159 path = kzalloc(struct_size(path, overlays, info->overlay_num), in mmp_register_path()
197 path->overlays[i].path = path; in mmp_register_path()
198 path->overlays[i].id = i; in mmp_register_path()
199 mutex_init(&path->overlays[i].access_ok); in mmp_register_path()
200 path->overlays[i].ops = info->overlay_ops; in mmp_register_path()
230 mutex_destroy(&path->overlays[i].access_ok); in mmp_unregister_path()
/OK3568_Linux_fs/kernel/drivers/video/fbdev/omap2/omapfb/
H A Domapfb-sysfs.c143 struct omap_overlay *ovl = ofbi->overlays[t]; in show_overlays()
147 if (ovl == fbdev->overlays[ovlnum]) in show_overlays()
171 if (ofbi->overlays[t] == ovl) in get_overlay_fb()
219 if (ovls[i] == fbdev->overlays[ovlnum]) { in store_overlays()
226 ovls[num_ovls++] = fbdev->overlays[ovlnum]; in store_overlays()
245 ovl = ofbi->overlays[i]; in store_overlays()
259 DBG("detaching %d\n", ofbi->overlays[i]->id); in store_overlays()
272 ofbi->overlays[t-1] = ofbi->overlays[t]; in store_overlays()
287 if (ovl == ofbi->overlays[t]) { in store_overlays()
296 ofbi->overlays[ofbi->num_overlays++] = ovl; in store_overlays()
[all …]
H A Domapfb-ioctl.c68 ovl = ofbi->overlays[0]; in omapfb_setup_plane()
186 ovl = ofbi->overlays[0]; in omapfb_query_plane()
241 ovl = ofbi2->overlays[j]; in omapfb_setup_mem()
427 if (ofbi->overlays[i]->manager) { in omapfb_set_color_key()
428 mgr = ofbi->overlays[i]->manager; in omapfb_set_color_key()
457 if (ofbi->overlays[i]->manager) { in omapfb_get_color_key()
458 mgr = ofbi->overlays[i]->manager; in omapfb_get_color_key()
522 ovl = fbdev->overlays[ovl_idx]; in omapfb_get_ovl_colormode()
563 struct omap_overlay *ovl = ofbi->overlays[i]; in omapfb_wait_for_go()
H A Domapfb.h62 struct omap_overlay *overlays[OMAPFB_MAX_OVL_PER_FB]; member
93 struct omap_overlay *overlays[10]; member
144 ovl = ofbi->overlays[0]; in fb2display()
/OK3568_Linux_fs/u-boot/doc/uImage.FIT/
H A Doverlay-fdt-boot.txt11 This document focuses on specifically using overlays as part of a FIT image.
12 General information regarding overlays including its syntax and building it
13 can be found in doc/README.fdt-overlays
15 Configuration without overlays
22 Without using overlays the configuration would be as follows for every case.
110 Configuration using overlays
113 Device tree overlays can be applied to a base DT and result in the same blob
196 u-boot will retrieve the base blob and apply the overlays in sequence as
203 Configuration using overlays and feature selection
/OK3568_Linux_fs/kernel/Documentation/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
107 These framebuffers can be routed flexibly to any overlays, thus allowing very
136 - Overlay manager combines the overlays in to one image and feeds them to
140 A framebuffer can be connected to multiple overlays to show the same pixel data
141 on all of the overlays. Note that in this case the overlay input sizes must be
142 the same, but, in case of video overlays, the output size can be different. Any
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
147 connected to virtual overlays.
[all …]
/OK3568_Linux_fs/kernel/drivers/media/platform/omap/
H A Domap_vout.c246 ovl = ovid->overlays[0]; in video_mode_to_dss_mode()
368 ovl = ovid->overlays[i]; in omapvid_init()
429 ovl = ovid->overlays[i]; in omapvid_apply_changes()
490 ovl = ovid->overlays[0]; in omap_vout_isr()
616 ovl = ovid->overlays[0]; in vidioc_try_fmt_vid_out()
646 ovl = ovid->overlays[0]; in vidioc_s_fmt_vid_out()
708 ovl = ovid->overlays[0]; in vidioc_try_fmt_vid_overlay()
728 ovl = ovid->overlays[0]; in vidioc_s_fmt_vid_overlay()
774 ovl = ovid->overlays[0]; in vidioc_g_fmt_vid_overlay()
834 ovl = ovid->overlays[0]; in vidioc_s_selection()
[all …]
H A Domap_voutdef.h97 struct omap_overlay *overlays[MAX_OVLS]; member
112 struct omap_overlay *overlays[MAX_OVLS]; member
/OK3568_Linux_fs/buildroot/package/rpi-firmware/
H A Drpi-firmware.mk48 $(foreach ovldtb,$(wildcard $(@D)/boot/overlays/*.dtbo), \
49 $(INSTALL) -D -m 0644 $(ovldtb) $(BINARIES_DIR)/rpi-firmware/overlays/$(notdir $(ovldtb))
56 $(INSTALL) -d $(BINARIES_DIR)/rpi-firmware/overlays
H A DConfig.in85 bool "Install DTB overlays"
93 overlays, to support HATs (Hardware Attached on Top, add-on
/OK3568_Linux_fs/yocto/poky/meta/classes/
H A Doverlayfs.bbclass42 # started after the ${PN}-overlays.service to make sure that all overlays are
54 OVERLAYFS_ALL_OVERLAYS_TEMPLATE ??= "${COREBASE}/meta/files/overlayfs-all-overlays.service.in"
91 bb.debug(1, "Generate systemd unit with all overlays %s" % allOverlaysUnitName(d))
111 # when all overlays are mounted
/OK3568_Linux_fs/kernel/Documentation/userspace-api/media/v4l/
H A Dvidioc-g-fbuf.rst46 The V4L2 API distinguishes destructive and non-destructive overlays. A
55 EINVAL error code when overlays are not supported.
221 - The device is capable of non-destructive overlays. When the driver
222 clears this flag, only destructive overlays are supported. There
224 non-destructive overlays. Video Output Overlays are in practice
231 for destructive overlays.
242 destructive overlays.
246 Alpha blending makes no sense for destructive overlays.
251 sense for destructive overlays.
/OK3568_Linux_fs/kernel/drivers/of/
H A DKconfig10 be enabled manually for unittests, overlays or
16 bool "Enable dtc generation of symbols for overlays support"
107 bool "Device Tree overlays"
/OK3568_Linux_fs/kernel/drivers/staging/pi433/Documentation/devicetree/
H A Dpi433.txt49 Since Raspbian supports device tree overlays, you may use an overlay instead
58 arch/arm/boot/dts/overlays and you need to add the file to the list of files
/OK3568_Linux_fs/kernel/drivers/of/unittest-data/
H A Doverlay_6.dts6 /* overlays 6, 7 application and removal in sequence */
H A Doverlay_7.dts6 /* overlays 6, 7 application and removal in sequence */
H A Doverlay_8.dts6 /* overlays 8, 9, 10, 11 application and removal in bad sequence */
H A Doverlay_9.dts6 /* overlays 8, 9, 10, 11 application and removal in bad sequence */
H A Doverlay_10.dts6 /* overlays 8, 9, 10, 11 application and removal in bad sequence */
/OK3568_Linux_fs/kernel/Documentation/admin-guide/acpi/
H A Dindex.rst13 ssdt-overlays
/OK3568_Linux_fs/yocto/poky/meta/files/
H A Doverlayfs-all-overlays.service.in2 Description=Groups all overlays required by {PN} in one unit

1234