From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Werner Sembach <wse@tuxedocomputers.com>
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Tvrtko Ursulin <tursulin@ursulin.net>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
<intel-gfx@lists.freedesktop.org>,
<intel-xe@lists.freedesktop.org>,
<dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH 0/1] drm/i915/display: Avoid unsupported 300Hz output mode on a TUXEDO device
Date: Tue, 8 Jul 2025 17:05:51 -0400 [thread overview]
Message-ID: <aG2IL07UtZ4YICMn@intel.com> (raw)
In-Reply-To: <20250704192007.526044-1-wse@tuxedocomputers.com>
On Fri, Jul 04, 2025 at 09:03:45PM +0200, Werner Sembach wrote:
> RFC because I'm not sure if this is the right approach.
Could you please file a gitlab issue for us so we can get someone from our
display team to take a look and see if there's anything else that could be done
before we take the quirk route?
https://drm.pages.freedesktop.org/intel-docs/how-to-file-i915-bugs.html
Thanks for the investigation and the quirk,
Rodrigo.
>
> The flicker manifests ever few seconds 1-3 black frames in quick
> succession.
>
> On windows 300Hz can not be selected for the iGPU, but the panel advertises
> it.
>
> A cleaner solution would probably to go over the pixel clock, but for this
> device there is only one 300Hz mode in the panels edid and that is at the
> nativ resolution. Chroma subsampling was not tested as linux afaik offers
> no way to easily enforce it for intel gpus.
>
> Tim Guttzeit (1):
> drm/i915/display: Avoid unsupported output mode with 300Hz on TUXEDO
> device
>
> drivers/gpu/drm/i915/display/intel_dp.c | 5 ++++
> drivers/gpu/drm/i915/display/intel_quirks.c | 30 +++++++++++++++++++++
> drivers/gpu/drm/i915/display/intel_quirks.h | 1 +
> 3 files changed, 36 insertions(+)
>
> --
> 2.43.0
>
next prev parent reply other threads:[~2025-07-08 21:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-04 19:03 [RFC PATCH 0/1] drm/i915/display: Avoid unsupported 300Hz output mode on a TUXEDO device Werner Sembach
2025-07-04 19:03 ` [RFC PATCH 1/1] " Werner Sembach
2025-07-17 7:30 ` Murthy, Arun R
2025-07-17 8:29 ` Tim Guttzeit
2025-07-04 19:22 ` [RFC PATCH 0/1] " Werner Sembach
2025-07-07 13:02 ` ✗ LGCI.VerificationFailed: failure for " Patchwork
2025-07-08 21:05 ` Rodrigo Vivi [this message]
2025-07-09 11:49 ` [RFC PATCH 0/1] " Werner Sembach
2025-07-09 13:32 ` Tim Guttzeit
2025-07-15 15:45 ` Tim Guttzeit
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=aG2IL07UtZ4YICMn@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=simona@ffwll.ch \
--cc=tursulin@ursulin.net \
--cc=wse@tuxedocomputers.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