Lines Matching +full:flip +full:- +full:vertical

3  * Copyright © 2007-2008 Dave Airlie
4 * Copyright © 2007-2008 Intel Corporation
67 * struct drm_crtc_state - mutable CRTC state
138 * Drivers are supposed to set this as-needed from their own atomic
235 * built-in panel), this mode here should match the physical mode on the
280 * Target vertical blank period when a page flip
298 * hardware capabiltiy - lacking support is not treated as failure.
327 * - The event is for a CRTC which is being disabled through this
335 * - For a CRTC which is enabled at the end of the commit (even when it
341 * - Events for disabled CRTCs are not allowed, and drivers can ignore
355 * the ones returned from page flip events. With the current vblank
357 * reference while the page flip is pending, acquired through
369 * If the device can't notify of flip completion in a race-free way
370 * at all, then the event should be armed just after the page flip is
391 * struct drm_crtc_funcs - control CRTCs for a given device
511 * &struct drm_mode_set - see there for details.
526 * Legacy entry point to schedule a flip to the given framebuffer.
530 * vertical blanking, avoiding tearing (except when requested otherwise
532 * requests a page flip the DRM core verifies that the new frame buffer
538 * to complete before executing the flip. It should also wait for any
540 * shared dma-buf.
542 * An application can request to be notified when the page flip has
546 * the provided event upon completion of the flip. Note that if
549 * flip events. With the current vblank helper infrastructure this can
550 * be achieved by holding a vblank reference while the page flip is
562 * flip operation has completed and the old framebuffer is no longer
570 * page flip operation is already pending the callback should return
571 * -EBUSY. Pageflips on a disabled CRTC (either by setting a NULL mode
573 * "ACTIVE" state) should result in an -EINVAL error code. Note that
586 * absolute target vertical blank period (as reported by
587 * drm_crtc_vblank_count()) when the flip should take effect.
591 * any non-0 error code. It's the driver's responsibility to call
593 * the flip completes.
608 * driver-private properties. For atomic drivers it is not used because
632 * state structure to extend it with driver-private state should use
665 * Decode a driver-private property value and store the decoded value
666 * into the passed-in state structure. Since the atomic core decodes all
671 * Such driver-private properties should really only be implemented for
680 * driver-private atomic properties.
697 * 0 if the property has been found, -EINVAL if the property isn't
711 * Reads out the decoded driver-private property. This is used to
718 * driver-private atomic properties.
722 * 0 on success, -EINVAL if the property isn't implemented by the
809 * callback does the verification on each crc-source before passing it
912 * need to apply some workarounds for gpu-specific vblank irq quirks
927 * struct drm_crtc - central CRTC control structure
1034 * &drm_crtc_state.adjusted_mode. And for high-precision timestamps
1079 /** @helper_private: mid-layer private data */
1117 * any locking or list-walking. @commit_list should only be used to
1181 * struct drm_mode_set - new values for a CRTC config change
1234 * drmm_crtc_alloc_with_planes - Allocate and initialize a new CRTC object with
1259 * drm_crtc_index - find the index of a registered CRTC
1267 return crtc->index; in drm_crtc_index()
1271 * drm_crtc_mask - find the mask of a registered CRTC
1286 * drm_crtc_find - look up a CRTC object from its ID
1305 * drm_for_each_crtc - iterate over all CRTCs
1312 list_for_each_entry(crtc, &(dev)->mode_config.crtc_list, head)
1315 * drm_for_each_crtc_reverse - iterate over all CRTCs in reverse order
1322 list_for_each_entry_reverse(crtc, &(dev)->mode_config.crtc_list, head)