From: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
To: Liviu Dudau <liviu.dudau@arm.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2] lib/igt_kms: Fix override_mode handling
Date: Tue, 20 Jun 2017 16:28:14 +0300 [thread overview]
Message-ID: <20170620132814.GA6401@ahiler-desk1.ger.corp.intel.com> (raw)
In-Reply-To: <20170616140006.27985-1-liviu.dudau@arm.com>
On Fri, Jun 16, 2017 at 03:00:06PM +0100, Liviu Dudau wrote:
> From: Brian Starkey <brian.starkey@arm.com>
>
> Changelog:
> - v2: removed the forced overwrite of output->config.default_mode
> - v1: original submission by Brian
>
> 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>
> Signed-off-by: Liviu Dudau <liviu.dudau@arm.com>
Reviewed-by: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
... and pushed, thanks!
Also please remember of setting subject prefix to "PATCH i-g-t" as it
makes the changes easily trackable via filters and patchwork :-)
Excerpt from CONTRIBUTING:
-----------------------------------------------------------------------------
Please use --subject-prefix="PATCH i-g-t" so that i-g-t patches are easily
identified in the massive amount mails on intel-gfx. To ensure this is always
done, autogen.sh will run:
git config format.subjectprefix "PATCH i-g-t"
on its first invocation.
-----------------------------------------------------------------------------
The autogen.sh thing is new addition.
--
Cheers,
Arek
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-06-20 13:28 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
2017-06-16 14:00 ` [PATCH v2] " Liviu Dudau
2017-06-20 13:28 ` Arkadiusz Hiler [this message]
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=20170620132814.GA6401@ahiler-desk1.ger.corp.intel.com \
--to=arkadiusz.hiler@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=liviu.dudau@arm.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