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 2/2] drm/i915/display: allow eDP VRR when EDID has adaptive sync range
Date: Wed, 15 Apr 2026 19:08:30 +0000 [thread overview]
Message-ID: <69dfe22f.050a0220.301b30.5755@mx.google.com> (raw)
In-Reply-To: <20260415130626.10523-3-j@metarealtyinc.ca>
Hi Ville,
> AFAICS the Windows driver does respect that VBT bit. So we should too.
That's fair -- I don't have visibility into the Windows driver
internals so I can't say definitively whether it checks VBT or not.
What I can confirm is the end-user result: on this Dell XPS 2026
(Panther Lake), VRR 20-120Hz works on Windows but not on Linux with
the same firmware. The VBT does not contain a VRR flag for this panel
at all -- intel_vbt_decode shows no VRR-related fields in the child
device block.
So either Windows has a fallback path when VBT doesn't declare VRR,
or Dell's Intel DCH driver ships with a driver-side override. Either
way, the panel clearly supports VRR (the EDID's DisplayID extension
explicitly declares Adaptive Sync 20-120Hz), and it works in practice
on this hardware.
Framework laptop users have reported the same class of issue with
their BOE panels.
If respecting VBT is important (and I understand the reasoning --
OEM validation), would something like a quirk table or a module
parameter be an acceptable alternative? I'd rather have any path to
making this work than no path.
Thanks for the review.
Jake
next prev 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 [this message]
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
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=69dfe22f.050a0220.301b30.5755@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