From: Ray Wu <ray.wu@amd.com>
To: <igt-dev@lists.freedesktop.org>
Cc: <jani.nikula@linux.intel.com>, <kamil.konieczny@linux.intel.com>,
<alex.hung@amd.com>, <sunpeng.li@amd.com>,
<chiahsuan.chung@amd.com>, Ray Wu <ray.wu@amd.com>
Subject: [PATCH i-g-t v3 0/5] tests/amdgpu/amd_replay: Fix state checks
Date: Mon, 16 Nov 2026 16:12:29 +0800 [thread overview]
Message-ID: <20261116070248.4103604-1-ray.wu@amd.com> (raw)
Most checks in amd_replay can never fail. Fix them one per patch.
Tested on an eDP panel with FreeSync Replay: all four subtests pass.
v3:
- Drop the DPCD 0x378 error status check
v2:
- Split into separate patches, one fix per patch (Jani)
Ray Wu (5):
tests/amdgpu/amd_replay: Read DPCD at the target offset
tests/amdgpu/amd_replay: Fix test_mode checks
tests/amdgpu/amd_replay: Fix inverted Replay state range checks
tests/amdgpu/amd_replay: Require REPLAY_STATE_3 after settle
tests/amdgpu/amd_replay: Fail on page flip errors
tests/amdgpu/amd_replay.c | 39 ++++++++++++---------------------------
1 file changed, 12 insertions(+), 27 deletions(-)
--
2.43.0
WARNING: multiple messages have this Message-ID (diff)
From: Ray Wu <ray.wu@amd.com>
To: <igt-dev@lists.freedesktop.org>
Cc: <jani.nikula@linux.intel.com>, <kamil.konieczny@linux.intel.com>,
<alex.hung@amd.com>, <sunpeng.li@amd.com>,
<chiahsuan.chung@amd.com>, Ray Wu <ray.wu@amd.com>
Subject: [PATCH i-g-t v3 0/5] tests/amdgpu/amd_replay: Fix state checks
Date: Mon, 16 Nov 2026 15:02:43 +0800 [thread overview]
Message-ID: <20261116070248.4103604-1-ray.wu@amd.com> (raw)
Message-ID: <20261116070243.mH7jPNvvQoo8EHqVtZq1CO2xqaR7W2cpMINOxKd3IoI@z> (raw)
Most checks in amd_replay can never fail. Fix them one per patch.
Tested on an eDP panel with FreeSync Replay: all four subtests pass.
v3:
- Drop the DPCD 0x378 error status check
v2:
- Split into separate patches, one fix per patch (Jani)
Ray Wu (5):
tests/amdgpu/amd_replay: Read DPCD at the target offset
tests/amdgpu/amd_replay: Fix test_mode checks
tests/amdgpu/amd_replay: Fix inverted Replay state range checks
tests/amdgpu/amd_replay: Require REPLAY_STATE_3 after settle
tests/amdgpu/amd_replay: Fail on page flip errors
tests/amdgpu/amd_replay.c | 39 ++++++++++++---------------------------
1 file changed, 12 insertions(+), 27 deletions(-)
--
2.43.0
next reply other threads:[~2026-11-16 8:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 8:12 Ray Wu [this message]
2026-11-16 7:02 ` [PATCH i-g-t v3 0/5] tests/amdgpu/amd_replay: Fix state checks Ray Wu
2026-11-16 7:02 ` [PATCH i-g-t v3 1/5] tests/amdgpu/amd_replay: Read DPCD at the target offset Ray Wu
2026-11-16 8:12 ` Ray Wu
2026-11-16 7:02 ` [PATCH i-g-t v3 2/5] tests/amdgpu/amd_replay: Fix test_mode checks Ray Wu
2026-11-16 7:02 ` [PATCH i-g-t v3 3/5] tests/amdgpu/amd_replay: Fix inverted Replay state range checks Ray Wu
2026-11-16 7:02 ` [PATCH i-g-t v3 5/5] tests/amdgpu/amd_replay: Fail on page flip errors Ray Wu
2026-11-16 8:12 ` [PATCH i-g-t v3 4/5] tests/amdgpu/amd_replay: Require REPLAY_STATE_3 after settle Ray Wu
2026-11-16 7:02 ` Ray Wu
2026-11-16 8:16 ` Ray Wu
2026-11-16 21:34 ` ✓ Xe.CI.BAT: success for tests/amdgpu/amd_replay: Fix state checks Patchwork
2026-11-17 8:42 ` ✗ Xe.CI.FULL: 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=20261116070248.4103604-1-ray.wu@amd.com \
--to=ray.wu@amd.com \
--cc=alex.hung@amd.com \
--cc=chiahsuan.chung@amd.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=kamil.konieczny@linux.intel.com \
--cc=sunpeng.li@amd.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