Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Liviu Dudau <liviu.dudau@arm.com>
To: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/4] lib/igt_kms: Fix override_mode handling
Date: Tue, 6 Jun 2017 11:54:13 +0100	[thread overview]
Message-ID: <20170606105413.GD10049@e110455-lin.cambridge.arm.com> (raw)
In-Reply-To: <20170606103028.GA3475@ahiler-desk1.ger.corp.intel.com>

On Tue, Jun 06, 2017 at 01:30:28PM +0300, Arkadiusz Hiler wrote:
> On Mon, Jun 05, 2017 at 02:28:38PM +0100, Liviu Dudau wrote:
> > 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 */
> 
> The warning caught my eye.
> 
> From what I understand, the idea for this change is that:
>  * we should not ever go for output->cofnig.default_mode if the default
>    mode is not what we really want.
>  * we should use the igt_output_get_mode() to get the current mode (i.e.
>    either the default or the overriden)
> 
> And yet igt_output_refresh() has this:
> 
> 	if (output->use_override_mode)
> 		output->config.default_mode = output->override_mode;
> 
> 
> Am I missing something or is this an oversight?

Hi Arek,

An oversight, will fix in the next version.

Thanks for reviewing this!
Liviu

> 
> -- 
> Cheers,
> Arek
> 
> > -		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

-- 
====================
| I would like to |
| fix the world,  |
| but they're not |
| giving me the   |
 \ source code!  /
  ---------------
    ¯\_(ツ)_/¯
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-06-06 10:54 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 ` [PATCH 2/4] lib/igt_kms: Fix override_mode handling Liviu Dudau
2017-06-06 10:30   ` Arkadiusz Hiler
2017-06-06 10:54     ` Liviu Dudau [this message]
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=20170606105413.GD10049@e110455-lin.cambridge.arm.com \
    --to=liviu.dudau@arm.com \
    --cc=arkadiusz.hiler@intel.com \
    --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