stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: Ander Conselvan De Oliveira <conselvan2@gmail.com>,
	intel-gfx@lists.freedesktop.org
Cc: "Tomas M." <tmezzadra@gmail.com>, stable@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Do a better job at disabling primary plane in the noatomic case.
Date: Thu, 12 Nov 2015 14:58:46 +0100	[thread overview]
Message-ID: <56449B16.2050001@linux.intel.com> (raw)
In-Reply-To: <1447335466.2774.13.camel@gmail.com>

Op 12-11-15 om 14:37 schreef Ander Conselvan De Oliveira:
> On Wed, 2015-11-11 at 15:36 +0100, Maarten Lankhorst wrote:
>> When disable_noatomic is called plane_mask is not reliable yet,
>> and plane_state->visible = true even after disabling the primary plane.
> So the stale value of plane_state->visible causes a subsequent modeset to enable
> the primary again?
Probably not because it would get recalculated in calc_changes, but it should really be set to false afterwards.

in intel_plane_atomic_calc_changes:
if (!was_crtc_enabled && WARN_ON(was_visible))
was_visible = false;

and in intel_sanitize_crtc when intel_check_plane_mapping fails, it gets set to true to disable it.

This is really a special case and it's for disable_noatomic only. As the name says it can't rely on the atomic state.

>> Fix this by unsetting plane->visible if it was visible, and calling
>> disable_planes with the primary plane as mask.
>>
>> The other planes are already disabled in intel_sanitize_crtc, so
>> they don't have to be handled here.
>>
>> Cc: stable@vger.kernel.org #v4.3, v4.2?
>> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=92655
>> Tested-by: Tomas Mezzadra <tmezzadra@gmail.com>
>> Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
>> ---
>>  drivers/gpu/drm/i915/intel_display.c | 4 +++-
>>  1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/i915/intel_display.c
>> b/drivers/gpu/drm/i915/intel_display.c
>> index b5f7493213b7..bc3282ab5ed2 100644
>> --- a/drivers/gpu/drm/i915/intel_display.c
>> +++ b/drivers/gpu/drm/i915/intel_display.c
>> @@ -6267,9 +6267,11 @@ static void intel_crtc_disable_noatomic(struct drm_crtc
>> *crtc)
>>  		WARN_ON(intel_crtc->unpin_work);
>>  
>>  		intel_pre_disable_primary(crtc);
>> +
>> +		intel_crtc_disable_planes(crtc, 1 << drm_plane_index(crtc
>> ->primary));
>> +		to_intel_plane_state(crtc->primary->state)->visible = false;
>>  	}
>>  
>> -	intel_crtc_disable_planes(crtc, crtc->state->plane_mask);
> Can't we just make plane_mask reliable? We know whether the primary plane is
> enabled and all others were disabled prior to that. Or did I miss something.
>
In the case of hardware readout you can't. The plane_mask gets set only if we can preserve the initial framebuffer
else the primary plane gets disabled.

~Maarten

  reply	other threads:[~2015-11-12 13:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1447252573-26167-1-git-send-email-maarten.lankhorst@linux.intel.com>
2015-11-12 13:37 ` [Intel-gfx] [PATCH] drm/i915: Do a better job at disabling primary plane in the noatomic case Ander Conselvan De Oliveira
2015-11-12 13:58   ` Maarten Lankhorst [this message]
2015-11-13 13:28     ` Ander Conselvan De Oliveira
2015-11-23  9:25       ` [PATCH v2] " Maarten Lankhorst
2015-12-01  9:07         ` [Intel-gfx] " Jani Nikula
     [not found]           ` <CAFCWdWcGDcU-jpDCS_VL-oJptp9K6pv9JK+a-UFTEefd=wtMUQ@mail.gmail.com>
2015-12-09 14:22             ` Jani Nikula
2015-12-10  8:33         ` Daniel Vetter
2015-12-10 12:47           ` Jani Nikula

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=56449B16.2050001@linux.intel.com \
    --to=maarten.lankhorst@linux.intel.com \
    --cc=conselvan2@gmail.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=stable@vger.kernel.org \
    --cc=tmezzadra@gmail.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;
as well as URLs for NNTP newsgroup(s).