All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ville Syrjala <ville.syrjala@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t 0/7] kms: Fix i915 fixed_mode vrefresh fallout
Date: Wed, 13 Oct 2021 15:59:42 +0300	[thread overview]
Message-ID: <20211013125949.19373-1-ville.syrjala@linux.intel.com> (raw)

From: Ville Syrjälä <ville.syrjala@linux.intel.com>

A few igts use a 60Hz hardcoded override mode currently. If the 
panel's fixed_mode dosn't happen to match that i915 will now reject
the mode. So let's adjust the override modes to match the refresh
rate the panel needs. We just pick the refresh rate of the first
reported mode, which sould be the panel's preferred mode. So this
will work just fine even if the panel/driver report and accept
multiple refresh rates.

Ville Syrjälä (7):
  lib: Introduce igt_memdup()
  tests/i915/kms_frontbuffer_tracking: Get rid of the funny mode_copy
  lib/kms: Have igt_std_1024_mode_get() return a copy of the mode
  lib/kms: Have igt_std_1024_mode_get() return a mode with specific
    refresh
  lib/kms: Introduce igt_output_preferred_vrefresh()
  tests/i915/kms_frontbuffer_tracking: Use preferred modes's vrefresh
  tests/kms_concurrent: Use preferred modes's vrefresh

 lib/igt_aux.c                         |  11 +++
 lib/igt_aux.h                         |   2 +
 lib/igt_kms.c                         |  28 +++++--
 lib/igt_kms.h                         |   3 +-
 tests/i915/kms_frontbuffer_tracking.c | 113 +++++++++++++-------------
 tests/kms_concurrent.c                |  25 +++---
 6 files changed, 103 insertions(+), 79 deletions(-)

-- 
2.32.0

             reply	other threads:[~2021-10-13 12:59 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-13 12:59 Ville Syrjala [this message]
2021-10-13 12:59 ` [igt-dev] [PATCH i-g-t 1/7] lib: Introduce igt_memdup() Ville Syrjala
2021-10-18  4:19   ` Modem, Bhanuprakash
2021-10-18  7:19     ` Ville Syrjälä
2021-10-18 10:10       ` Modem, Bhanuprakash
2021-10-13 12:59 ` [igt-dev] [PATCH i-g-t 2/7] tests/i915/kms_frontbuffer_tracking: Get rid of the funny mode_copy Ville Syrjala
2021-10-18  4:34   ` Modem, Bhanuprakash
2021-10-13 12:59 ` [igt-dev] [PATCH i-g-t 3/7] lib/kms: Have igt_std_1024_mode_get() return a copy of the mode Ville Syrjala
2021-10-18  4:56   ` Modem, Bhanuprakash
2021-10-13 12:59 ` [igt-dev] [PATCH i-g-t 4/7] lib/kms: Have igt_std_1024_mode_get() return a mode with specific refresh Ville Syrjala
2021-10-18  4:59   ` Modem, Bhanuprakash
2021-10-13 12:59 ` [igt-dev] [PATCH i-g-t 5/7] lib/kms: Introduce igt_output_preferred_vrefresh() Ville Syrjala
2021-10-18  5:00   ` Modem, Bhanuprakash
2021-10-13 12:59 ` [igt-dev] [PATCH i-g-t 6/7] tests/i915/kms_frontbuffer_tracking: Use preferred modes's vrefresh Ville Syrjala
2021-10-18  5:02   ` Modem, Bhanuprakash
2021-10-13 12:59 ` [igt-dev] [PATCH i-g-t 7/7] tests/kms_concurrent: " Ville Syrjala
2021-10-18  5:03   ` Modem, Bhanuprakash
2021-10-13 15:16 ` [igt-dev] ✗ Fi.CI.BAT: failure for kms: Fix i915 fixed_mode vrefresh fallout Patchwork
2021-10-14  8:35 ` [igt-dev] ✓ Fi.CI.BAT: success for kms: Fix i915 fixed_mode vrefresh fallout (rev2) Patchwork
2021-10-14  9:34 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork

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=20211013125949.19373-1-ville.syrjala@linux.intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=igt-dev@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 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.