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(+)
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(+)
--
2.43.0
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 >
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 >>
Hi all, > Tim can you follow up with this? Reducing the communication chain to avoid dropping information. Yes, here is the Ticket: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/14616 Best regards, Tim Guttzeit Am 09.07.25 um 13:49 schrieb Werner Sembach: > 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 >>>
Hi all, added intel-gfx@lists.freedesktop.org and intel-xe@lists.freedesktop.org, as requested in the ticket. Best regards, Tim Guttzeit Am 09.07.25 um 15:32 schrieb Tim Guttzeit: > Hi all, > > > Tim can you follow up with this? Reducing the communication chain to > avoid dropping information. > > Yes, here is the Ticket: > https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/14616 > > Best regards, > Tim Guttzeit > > Am 09.07.25 um 13:49 schrieb Werner Sembach: >> 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 >>>> > -- Tim Guttzeit Development -- TUXEDO Computers GmbH Alter Postweg 101 D-86159 Augsburg -- www.tuxedocomputers.com Fon: +49 (0) 821 / 8998 2992 -- Amtsgericht Augsburg: HRB 27755 CEO: Herbert Feiler VAT-ID: DE815420876
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(+) >
© 2016 - 2025 Red Hat, Inc.