public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jake S <j@metarealtyinc.ca>
To: intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org, ville.syrjala@linux.intel.com
Subject: Re: [PATCH 0/2] drm: Enable eDP VRR for panels with DisplayID Adaptive Sync
Date: Wed, 15 Apr 2026 19:08:28 +0000	[thread overview]
Message-ID: <69dfe22d.050a0220.60470.81b5@mx.google.com> (raw)
In-Reply-To: <20260415130626.10523-1-j@metarealtyinc.ca>

Hi Ville,

> Why did you post a different version?

Sorry for the confusion -- I wasn't building on Adriano Vero's
March 28 patch. I did the investigation independently and only found
his work afterwards. I referenced it in the cover letter but should
have been clearer.

The key difference: Adriano's patch handles tag 0x25 (Dynamic Video
Timing Range Limits). My panel (LG Display VNFT2 in a Dell XPS 2026)
only has tag 0x2B (Adaptive Sync Data Block), so his patch alone
wouldn't have helped here. My patch handles both 0x2B and 0x25.

Happy to coordinate with Adriano and fold the 0x2B handling into a
v2 of his series if that's preferred.

Thanks,
Jake

  parent reply	other threads:[~2026-04-16 13:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-15 13:06 [PATCH 0/2] drm: Enable eDP VRR for panels with DisplayID Adaptive Sync Jake S
2026-04-15 13:06 ` [PATCH 1/2] drm/edid: populate monitor_range from DisplayID Adaptive Sync block Jake S
2026-04-15 13:06 ` [PATCH 2/2] drm/i915/display: allow eDP VRR when EDID has adaptive sync range Jake S
2026-04-15 14:01   ` Ville Syrjälä
2026-04-15 19:08   ` Jake S
2026-04-15 19:16     ` Ville Syrjälä
2026-04-15 19:39   ` Jake S
2026-04-15 14:05 ` [PATCH 0/2] drm: Enable eDP VRR for panels with DisplayID Adaptive Sync Ville Syrjälä
2026-04-15 19:08 ` Jake S [this message]
2026-04-16 13:21 ` ✗ LGCI.VerificationFailed: failure for " 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=69dfe22d.050a0220.60470.81b5@mx.google.com \
    --to=j@metarealtyinc.ca \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=ville.syrjala@linux.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