From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Per-crtc/connector DRRS debugfs (rev2)
Date: Mon, 3 Oct 2022 11:48:03 +0300 [thread overview]
Message-ID: <Yzqhwy1/41HmjKMp@intel.com> (raw)
In-Reply-To: <166466659715.32391.15847655821384807172@emeril.freedesktop.org>
On Sat, Oct 01, 2022 at 11:23:17PM -0000, Patchwork wrote:
> * igt@kms_frontbuffer_tracking@fbcdrrs-slowdraw (NEW):
> - shard-tglb: NOTRUN -> [FAIL][2] +12 similar issues
> [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109175v2/shard-tglb2/igt@kms_frontbuffer_tracking@fbcdrrs-slowdraw.html
shard-tglb passes most DRRS tests but fails a few. The reson looks to be
that we have a VRR panel rather than a DRRS panel:
using preferred EDID fixed mode: "1920x1080": 90 214000 1920 1936 1952 2104 1080 1083 1097 1128 0x48 0xa
using alternate EDID fixed mode: "1920x1080": 40 214000 1920 1936 1952 2104 1080 1083 1097 2532 0x40 0xa
The kernel still reports that the connector can do seamless DRRS
since it only checks that we have a multiple refresh rates available.
I guess I could try to tighten up that check a bit and make sure
we have a at least two modes suitable for DRRS in there...
--
Ville Syrjälä
Intel
prev parent reply other threads:[~2022-10-03 8:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-01 18:25 [Intel-gfx] [PATCH v2 0/4] drm/i915: Per-crtc/connector DRRS debugfs Ville Syrjala
2022-10-01 18:25 ` [Intel-gfx] [PATCH v2 1/4] drm/i915: Move DRRS debugfs next to the implementation Ville Syrjala
2022-10-01 18:25 ` [Intel-gfx] [PATCH v2 2/4] drm/i915: Make the DRRS debugfs contents more consistent Ville Syrjala
2022-10-01 18:25 ` [Intel-gfx] [PATCH v2 3/4] drm/i915: Make DRRS debugfs per-crtc/connector Ville Syrjala
2022-10-01 18:25 ` [Intel-gfx] [PATCH v2 4/4] drm/i915: Fix locking in DRRS debugfs Ville Syrjala
2022-10-01 19:02 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: Per-crtc/connector DRRS debugfs (rev2) Patchwork
2022-10-01 19:26 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-10-01 23:23 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-10-03 8:37 ` Ville Syrjälä
2022-10-03 8:44 ` Sarvela, Tomi P
2022-10-03 8:48 ` Ville Syrjälä [this message]
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=Yzqhwy1/41HmjKMp@intel.com \
--to=ville.syrjala@linux.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