Re: [RFC PATCH 0/1] drm/i915/display: Avoid unsupported 300Hz output mode on a TUXEDO device

[Werner Sembach <wse@tuxedocomputers.com>]

Hi all,

Am 08.07.25 um 23:05 schrieb Rodrigo Vivi:
> 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

Tim can you follow up with this? Reducing the communication chain to avoid 
dropping information.

Best regards,

Werner Sembach

>
> 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
>>