/** * DOC: frontbuffer tracking * * Many features require us to track changes to the currently active * frontbuffer, especially rendering targeted at the frontbuffer. * * To be able to do so we track frontbuffers using a bitmask for all possible * frontbuffer slots through intel_frontbuffer_track(). The functions in this * file are then called when the contents of the frontbuffer are invalidated, * when frontbuffer rendering has stopped again to flush out all the changes * and when the frontbuffer is exchanged with a flip. Subsystems interested in * frontbuffer changes (e.g. PSR, FBC, DRRS) should directly put their callbacks * into the relevant places and filter for the frontbuffer slots that they are * interested int. * * On a high level there are two types of powersaving features. The first one * work like a special cache (FBC and PSR) and are interested when they should * stop caching and when to restart caching. This is done by placing callbacks * into the invalidate and the flush functions: At invalidate the caching must * be stopped and at flush time it can be restarted. And maybe they need to know * when the frontbuffer changes (e.g. when the hw doesn't initiate an invalidate * and flush on its own) which can be achieved with placing callbacks into the * flip functions. * * The other type of display power saving feature only cares about busyness * (e.g. DRRS). In that case all three (invalidate, flush and flip) indicate * busyness. There is no direct way to detect idleness. Instead an idle timer * work delayed work should be started from the flush and flip functions and * cancelled as soon as busyness is detected.
*/
/** * frontbuffer_flush - flush frontbuffer * @display: display device * @frontbuffer_bits: frontbuffer plane tracking bits * @origin: which operation caused the flush * * This function gets called every time rendering on the given planes has * completed and frontbuffer caching can be started again. Flushes will get * delayed if they're blocked by some outstanding asynchronous rendering. * * Can be called without any locks held.
*/ staticvoid frontbuffer_flush(struct intel_display *display, unsignedint frontbuffer_bits, enum fb_op_origin origin)
{ /* Delay flushing when rings are still busy.*/
spin_lock(&display->fb_tracking.lock);
frontbuffer_bits &= ~display->fb_tracking.busy_bits;
spin_unlock(&display->fb_tracking.lock);
/** * intel_frontbuffer_flip_prepare - prepare asynchronous frontbuffer flip * @display: display device * @frontbuffer_bits: frontbuffer plane tracking bits * * This function gets called after scheduling a flip on @obj. The actual * frontbuffer flushing will be delayed until completion is signalled with * intel_frontbuffer_flip_complete. If an invalidate happens in between this * flush will be cancelled. * * Can be called without any locks held.
*/ void intel_frontbuffer_flip_prepare(struct intel_display *display, unsigned frontbuffer_bits)
{
spin_lock(&display->fb_tracking.lock);
display->fb_tracking.flip_bits |= frontbuffer_bits; /* Remove stale busy bits due to the old buffer. */
display->fb_tracking.busy_bits &= ~frontbuffer_bits;
spin_unlock(&display->fb_tracking.lock);
}
/** * intel_frontbuffer_flip_complete - complete asynchronous frontbuffer flip * @display: display device * @frontbuffer_bits: frontbuffer plane tracking bits * * This function gets called after the flip has been latched and will complete * on the next vblank. It will execute the flush if it hasn't been cancelled yet. * * Can be called without any locks held.
*/ void intel_frontbuffer_flip_complete(struct intel_display *display, unsigned frontbuffer_bits)
{
spin_lock(&display->fb_tracking.lock); /* Mask any cancelled flips. */
frontbuffer_bits &= display->fb_tracking.flip_bits;
display->fb_tracking.flip_bits &= ~frontbuffer_bits;
spin_unlock(&display->fb_tracking.lock);
if (frontbuffer_bits)
frontbuffer_flush(display, frontbuffer_bits, ORIGIN_FLIP);
}
/** * intel_frontbuffer_flip - synchronous frontbuffer flip * @display: display device * @frontbuffer_bits: frontbuffer plane tracking bits * * This function gets called after scheduling a flip on @obj. This is for * synchronous plane updates which will happen on the next vblank and which will * not get delayed by pending gpu rendering. * * Can be called without any locks held.
*/ void intel_frontbuffer_flip(struct intel_display *display, unsigned frontbuffer_bits)
{
spin_lock(&display->fb_tracking.lock); /* Remove stale busy bits due to the old buffer. */
display->fb_tracking.busy_bits &= ~frontbuffer_bits;
spin_unlock(&display->fb_tracking.lock);
/** * intel_frontbuffer_queue_flush - queue flushing frontbuffer object * @front: GEM object to flush * * This function is targeted for our dirty callback for queueing flush when * dma fence is signals
*/ void intel_frontbuffer_queue_flush(struct intel_frontbuffer *front)
{ if (!front) return;
kref_get(&front->ref); if (!schedule_work(&front->flush_work))
intel_frontbuffer_put(front);
}
/** * intel_frontbuffer_track - update frontbuffer tracking * @old: current buffer for the frontbuffer slots * @new: new buffer for the frontbuffer slots * @frontbuffer_bits: bitmask of frontbuffer slots * * This updates the frontbuffer tracking bits @frontbuffer_bits by clearing them * from @old and setting them in @new. Both @old and @new can be NULL.
*/ void intel_frontbuffer_track(struct intel_frontbuffer *old, struct intel_frontbuffer *new, unsignedint frontbuffer_bits)
{ /* * Control of individual bits within the mask are guarded by * the owning plane->mutex, i.e. we can never see concurrent * manipulation of individual bits. But since the bitfield as a whole * is updated using RMW, we need to use atomics in order to update * the bits.
*/
BUILD_BUG_ON(INTEL_FRONTBUFFER_BITS_PER_PIPE * I915_MAX_PIPES >
BITS_PER_TYPE(atomic_t));
BUILD_BUG_ON(INTEL_FRONTBUFFER_BITS_PER_PIPE * I915_MAX_PIPES > 32);
BUILD_BUG_ON(I915_MAX_PLANES > INTEL_FRONTBUFFER_BITS_PER_PIPE);
if (old) { struct intel_display *display = to_intel_display(old->obj->dev);
Die Informationen auf dieser Webseite wurden
nach bestem Wissen sorgfältig zusammengestellt. Es wird jedoch weder Vollständigkeit, noch Richtigkeit,
noch Qualität der bereit gestellten Informationen zugesichert.
Bemerkung:
Die farbliche Syntaxdarstellung und die Messung sind noch experimentell.