[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7df81e96-14b0-4fde-955d-2960e240b4c7@tuxedocomputers.com>
Date: Fri, 4 Jul 2025 21:22:51 +0200
From: Werner Sembach <wse@...edocomputers.com>
To: Jani Nikula <jani.nikula@...ux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@...el.com>,
Joonas Lahtinen <joonas.lahtinen@...ux.intel.com>,
Tvrtko Ursulin <tursulin@...ulin.net>, David Airlie <airlied@...il.com>,
Simona Vetter <simona@...ll.ch>
Cc: intel-gfx@...ts.freedesktop.org, intel-xe@...ts.freedesktop.org,
dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
t.guttzeit@...edocomputers.com
Subject: Re: [RFC PATCH 0/1] drm/i915/display: Avoid unsupported 300Hz output
mode on a TUXEDO device
Forgot to add Tim to the cover letter cc (I have not yet found a nice way to
auto generate cover letter to's and cc's unlike for the actual patches)
Am 04.07.25 um 21:03 schrieb Werner Sembach:
> RFC because I'm not sure if this is the right approach.
>
> 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(+)
>
Powered by blists - more mailing lists