All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liviu Dudau <liviu.dudau@arm.com>
To: Petri Latvala <petri.latvala@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [PATCH 2/4] lib/igt_kms: Fix override_mode handling
Date: Mon,  5 Jun 2017 14:28:38 +0100	[thread overview]
Message-ID: <20170605132840.9125-3-liviu.dudau@arm.com> (raw)
In-Reply-To: <20170605132840.9125-1-liviu.dudau@arm.com>

From: Brian Starkey <brian.starkey@arm.com>

igt_display_commit isn't refreshing all outputs anymore, which means
that an override mode may never get picked up.

Instead of forcing a reprobe to handle copying the override_mode into
default_mode, just change igt_output_get_mode() to return the
override_mode if it's been set, and remove the old code which would
directly overwrite default_mode.

This should be more robust, as igt_output_get_mode() will always return
the correct mode, without needing the output to be reprobed.

This change means that output->config.default_mode always contains the
"non-overridden" default mode.

Signed-off-by: Brian Starkey <brian.starkey@arm.com>
---
 lib/igt_kms.c | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)

diff --git a/lib/igt_kms.c b/lib/igt_kms.c
index 5e2ef97b..6d60a14f 100644
--- a/lib/igt_kms.c
+++ b/lib/igt_kms.c
@@ -2821,7 +2821,10 @@ const char *igt_output_name(igt_output_t *output)
 
 drmModeModeInfo *igt_output_get_mode(igt_output_t *output)
 {
-	return &output->config.default_mode;
+	if (output->use_override_mode)
+		return &output->override_mode;
+	else
+		return &output->config.default_mode;
 }
 
 /**
@@ -2839,10 +2842,6 @@ void igt_output_override_mode(igt_output_t *output, drmModeModeInfo *mode)
 
 	if (mode)
 		output->override_mode = *mode;
-	else /* restore default_mode, may have been overwritten in igt_output_refresh */
-		kmstest_get_connector_default_mode(output->display->drm_fd,
-						   output->config.connector,
-						   &output->config.default_mode);
 
 	output->use_override_mode = !!mode;
 
-- 
2.13.0

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

  parent reply	other threads:[~2017-06-05 13:48 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-05 13:28 [PATCH 0/4] Cleanups and fixes Liviu Dudau
2017-06-05 13:28 ` [PATCH 1/4] lib/igt_kms: Fix erroneous assert Liviu Dudau
2017-06-06 10:32   ` Arkadiusz Hiler
2017-06-05 13:28 ` Liviu Dudau [this message]
2017-06-06 10:30   ` [PATCH 2/4] lib/igt_kms: Fix override_mode handling Arkadiusz Hiler
2017-06-06 10:54     ` Liviu Dudau
2017-06-16 14:00     ` [PATCH v2] " Liviu Dudau
2017-06-20 13:28       ` Arkadiusz Hiler
2017-06-20 15:22         ` Liviu Dudau
2017-06-05 13:28 ` [PATCH 3/4] lib/igt_debugfs: Remove igt_debugfs_t Liviu Dudau
2017-06-06 10:37   ` Arkadiusz Hiler
2017-06-05 13:28 ` [PATCH 4/4] lib/igt_debugfs: Only use valid values in igt_crc_to_str() Liviu Dudau
2017-06-06 11:06   ` Arkadiusz Hiler
2017-06-09 12:34 ` [PATCH 0/4] Cleanups and fixes Arkadiusz Hiler
2017-06-09 12:37   ` Arkadiusz Hiler
2017-06-09 12:47     ` Liviu Dudau
2017-06-12 10:33     ` Liviu Dudau
2017-06-16 11:08       ` Arkadiusz Hiler
2017-06-16 11:34         ` Liviu Dudau

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=20170605132840.9125-3-liviu.dudau@arm.com \
    --to=liviu.dudau@arm.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=petri.latvala@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.