From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: Daniel Stone <daniel@fooishbar.org>
Cc: intel-gfx <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 15:35:28 +0200 [thread overview]
Message-ID: <5602AAA0.1030404@linux.intel.com> (raw)
In-Reply-To: <CAPj87rO+jV7hQJZ95igK-45mZnCu02=HznY0dpnzsArXSQN9Aw@mail.gmail.com>
Op 14-09-15 om 19:10 schreef Daniel Stone:
> Hi,
>
> On 14 September 2015 at 10:30, Maarten Lankhorst
> <maarten.lankhorst@linux.intel.com> wrote:
>> @@ -13013,14 +13013,15 @@ static int intel_atomic_check(struct drm_device *dev,
>> if (ret)
>> return ret;
>>
>> - if (intel_pipe_config_compare(state->dev,
>> - to_intel_crtc_state(crtc->state),
>> - pipe_config, true)) {
>> + if (!crtc_state->connectors_changed &&
>> + !crtc_state->active_changed && look
>> + 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;
>> - }
>> -
>> - if (needs_modeset(crtc_state)) {
>> + pipe_config->update_pipe = true;
>> + } else {
>> any_ms = true;
> The change from only setting any_ms if needs_modeset() is true, to
> always if we can't do a fastset, seems correct but maybe a bit subtle.
It's exactly the same thing, just made a bit more explicit.
before: any_ms = needs_modeset() with mode_changed = !update_pipe.
After: any_ms = !update_pipe.
> Was that intended? At the moment it does look like it'll widen the net
> a little bit, but I _suspect_ that's a good thing. Pending igt:
> Acked-by: Daniel Stone <daniels@collabora.com>
>
> Cheers,
> Daniel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-09-23 13:35 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 [this message]
2015-09-16 18:48 ` Jesse Barnes
2015-09-23 11:38 ` Maarten Lankhorst
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=5602AAA0.1030404@linux.intel.com \
--to=maarten.lankhorst@linux.intel.com \
--cc=daniel@fooishbar.org \
--cc=intel-gfx@lists.freedesktop.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