public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Mohammed Bilal <mohammed.bilal@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: kunal1.joshi@intel.com, Mohammed Bilal <mohammed.bilal@intel.com>
Subject: [PATCH v1 0/2] tests/kms_hdmi_inject: Add low refresh rate subtests
Date: Wed,  1 Apr 2026 12:56:13 +0530	[thread overview]
Message-ID: <20260401072615.3456135-1-mohammed.bilal@intel.com> (raw)

This series adds two subtests to validate low refresh rate (11Hz, 10Hz,
5Hz, 4Hz) mode handling on HDMI connectors. The tests verify driver
behavior around the hardware minimum pixel clock threshold (34.38 MHz).

Patch 1 adds a positive test that validates low refresh rates are
achievable when pixel clock is maintained at the hardware minimum by
adjusting vtotal.

Patch 2 adds a negative test that validates the driver correctly rejects
modes when the standard pixel clock calculation drops below the hardware
minimum.

Together these tests ensure the driver properly enforces hardware
constraints while still supporting valid low refresh rate configurations.

Mohammed Bilal (2):
  tests/kms_hdmi_inject: Add inject-low-refresh-fixed-clock subtest
  tests/kms_hdmi_inject: Add inject-low-refresh-default-clock subtest

 tests/kms_hdmi_inject.c | 295 ++++++++++++++++++++++++++++++++++++++++
 1 file changed, 295 insertions(+)

-- 
2.48.1


             reply	other threads:[~2026-04-01  7:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-01  7:26 Mohammed Bilal [this message]
2026-04-01  7:26 ` [PATCH v1 1/2] tests/kms_hdmi_inject: Add inject-low-refresh-fixed-clock subtest Mohammed Bilal
2026-04-01  7:26 ` [PATCH v1 2/2] tests/kms_hdmi_inject: Add inject-low-refresh-default-clock subtest Mohammed Bilal
2026-04-01  8:48 ` ✓ Xe.CI.BAT: success for tests/kms_hdmi_inject: Add low refresh rate subtests Patchwork
2026-04-01  9:01 ` ✓ i915.CI.BAT: " Patchwork
2026-04-01 13:54 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-04-01 23:53 ` ✗ i915.CI.Full: " 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=20260401072615.3456135-1-mohammed.bilal@intel.com \
    --to=mohammed.bilal@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=kunal1.joshi@intel.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