From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Takashi Iwai <tiwai@suse.de>
Subject: Re: [PATCH 0/2] drm/i915: Fix the invisible cursor syndrome
Date: Mon, 14 Dec 2015 22:23:27 +0200 [thread overview]
Message-ID: <20151214202327.GX4437@intel.com> (raw)
In-Reply-To: <1450091808-32607-1-git-send-email-ville.syrjala@linux.intel.com>
On Mon, Dec 14, 2015 at 01:16:46PM +0200, ville.syrjala@linux.intel.com wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> These two should provide the minimal fix for the invisible cursor
> problem that's been plaguing me and some other people. It's caused
> by the cursor bo getting bound at ggtt offset 0, which the code then
> considers to mean "not enabled". These patches get rid of that assumption,
> with the caveat that we may do some needless cursor register writes.
> I have a more generic fix for that (and a ton of other cursor improvements)
> at [1], but I figured that I'll just post the critical fixes now and allow
> the others to stew a bit more in the branch until maybe early next year.
>
> I assume the problem is also related to the lack of fbdev pinning that
> Chris has fixed [2]. With fbdev permanalty pinned at offset 0, there's
> no opportunity for the cursor bo to travel there. Without fbdev I suppose
> something else rings, status page, etc. could get permanently placed
> at offset 0, so not sure if this can be hit in that case (didn't try it).
>
> I'm a bit wary about adding cc stable to these since I suspect that
> backporting them too far will cause regressions, on account of the
> atomic/plane stuff probably not being up to the task in older kernels.
> So maybe better get these in w/o cc stable and consider a backport again
> later if it looks necessary.
>
> [1] git://github.com/vsyrjala/linux.git cursor_improvements
> [2] http://lists.freedesktop.org/archives/intel-gfx/2015-December/082114.html
>
> Ville Syrjälä (2):
> drm/i915: Kill intel_crtc->cursor_bo
> drm/i915: Drop the broken cursor base==0 special casing
Both patches pushed to dinq with cc: fixes. Thanks for the reviews.
>
> drivers/gpu/drm/i915/intel_display.c | 34 ++++++++++++----------------------
> drivers/gpu/drm/i915/intel_drv.h | 1 -
> 2 files changed, 12 insertions(+), 23 deletions(-)
>
> Cc: Takashi Iwai <tiwai@suse.de>
> Cc: Jani Nikula <jani.nikula@linux.intel.com>
> --
> 2.4.10
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2015-12-14 20:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 11:16 [PATCH 0/2] drm/i915: Fix the invisible cursor syndrome ville.syrjala
2015-12-14 11:16 ` [PATCH 1/2] drm/i915: Kill intel_crtc->cursor_bo ville.syrjala
2015-12-14 11:32 ` Chris Wilson
2015-12-14 15:30 ` Ville Syrjälä
2015-12-14 15:35 ` [PATCH v2 " ville.syrjala
2015-12-14 15:37 ` Chris Wilson
2015-12-14 11:16 ` [PATCH 2/2] drm/i915: Drop the broken cursor base==0 special casing ville.syrjala
2015-12-14 11:33 ` Chris Wilson
2015-12-14 20:23 ` Ville Syrjälä [this message]
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=20151214202327.GX4437@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tiwai@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).