From: Daniel Vetter <daniel@ffwll.ch>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 4/5] drm/i915: Invalidate frontbuffer bits on FBDEV sync
Date: Mon, 22 Jun 2015 15:58:53 +0200 [thread overview]
Message-ID: <20150622135853.GF25769@phenom.ffwll.local> (raw)
In-Reply-To: <1434653006-5693-4-git-send-email-rodrigo.vivi@intel.com>
On Thu, Jun 18, 2015 at 11:43:25AM -0700, Rodrigo Vivi wrote:
> @@ -259,6 +269,15 @@ void intel_frontbuffer_flip_complete(struct drm_device *dev,
> struct drm_i915_private *dev_priv = dev->dev_private;
>
> mutex_lock(&dev_priv->fb_tracking.lock);
> +
> + /*
> + * Let's assume that if this asynchronous flip happened
> + * FBDEV might not be in use anymore.
> + * If this is not the case fb_sync will happen on next
> + * frontbuffer touch and invalidate bits again
> + */
> + dev_priv->fb_tracking.fbdev_running = false;
This pretty much destroys frontbuffer tracking for everyone if they boot
up with fbdev.
Since this seems to be epic fun indeed I think what we need to do is:
- Fill out the ->dirty callback.
- Extend the drm fbdev helpers to call ->dirty at all suitable places if
needed.
For an example of how to do this all see udl/udl_fb.c. Imo a good patch
would be to replace all the udl special casing with the new fbdev helpers,
just as a demonstration patch. i915 isn't the only driver where every
frontbuffer change must involve some manual driver action, there's no
reason we need to roll our own solution.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-06-22 13:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 18:43 [PATCH 1/5] drm/i915: Enable runtime pm Rodrigo Vivi
2015-06-18 18:43 ` [PATCH 2/5] drm/i915: PSR: Remove Low Power HW tracking mask Rodrigo Vivi
2015-06-19 20:32 ` Daniel Vetter
2015-06-19 22:05 ` Rodrigo Vivi
2015-06-22 22:31 ` Runyan, Arthur J
2015-06-22 23:07 ` Rodrigo Vivi
2015-06-23 18:40 ` Runyan, Arthur J
2015-06-23 18:52 ` Rodrigo Vivi
2015-06-18 18:43 ` [PATCH 3/5] drm/i915: Remove unused ring argument from frontbuffer invalidate and busy functions Rodrigo Vivi
2015-06-22 14:00 ` Daniel Vetter
2015-06-18 18:43 ` [PATCH 4/5] drm/i915: Invalidate frontbuffer bits on FBDEV sync Rodrigo Vivi
2015-06-22 13:58 ` Daniel Vetter [this message]
2015-06-22 16:53 ` Rodrigo Vivi
2015-06-18 18:43 ` [PATCH 5/5] drm/i915: Enable PSR by default Rodrigo Vivi
2015-06-18 18:54 ` Paulo Zanoni
2015-06-24 21:48 ` Paulo Zanoni
2015-06-24 22:12 ` Vivi, Rodrigo
2015-06-18 18:53 ` [PATCH 1/5] drm/i915: Enable runtime pm Rodrigo Vivi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150622135853.GF25769@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox