public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/i915: Only check pipe state for fast modeset when it's possible.
Date: Wed, 23 Sep 2015 13:38:38 +0200	[thread overview]
Message-ID: <56028F3E.4080902@linux.intel.com> (raw)
In-Reply-To: <55F9B98A.2020501@virtuousgeek.org>

Op 16-09-15 om 20:48 schreef Jesse Barnes:
> On 09/14/2015 02:30 AM, Maarten Lankhorst wrote:
>> +		if (!crtc_state->connectors_changed &&
>> +		    !crtc_state->active_changed &&
>> +		    crtc_state->active &&
>> +		    intel_pipe_config_compare(state->dev,
>> +					      to_intel_crtc_state(crtc->state),
>> +					      pipe_config, true)) {
>>  			crtc_state->mode_changed = false;
>> -			to_intel_crtc_state(crtc_state)->update_pipe = true;
>> -		}
> Doesn't needs_modeset() cover the connectors and active changed cases?  Could we just hoist that up earlier in this function instead?
>
Not sure what you're saying, since needs_modeset is always true here.

~Maarten
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-09-23 11:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-14  9:30 [PATCH 1/2] drm/i915: Fix fastboot scalers for skylake Maarten Lankhorst
2015-09-14  9:30 ` [PATCH 2/2] drm/i915: Only check pipe state for fast modeset when it's possible Maarten Lankhorst
2015-09-14 13:55   ` Daniel Vetter
2015-09-14 17:10   ` Daniel Stone
2015-09-23 13:35     ` Maarten Lankhorst
2015-09-16 18:48   ` Jesse Barnes
2015-09-23 11:38     ` Maarten Lankhorst [this message]
2015-09-16 18:45 ` [PATCH 1/2] drm/i915: Fix fastboot scalers for skylake Jesse Barnes
2015-09-23  8:55   ` Daniel Vetter

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=56028F3E.4080902@linux.intel.com \
    --to=maarten.lankhorst@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jbarnes@virtuousgeek.org \
    /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