Skip to contentSkip to conversation

drm/i915/display: Avoid unsupported 300Hz output mode on a TUXEDO device

RFC PATCH In review Werner Sembach 5 participants 11 messages Jul 4, 2025 – Jul 17, 2025

Subsystems (3)
lore
Share & tools
lore
#0 lore raw

cover drm/i915/display: Avoid unsupported 300Hz output mode on a TUXEDO device

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(+)
Signature · 1 line
2.43.0
#1 lore raw

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

From: Tim Guttzeit <[email protected]>

Removes all display modes with more than 240 Hz for the integrated display on a TUXEDO Stellaris 16 Gen7, because using the iGPU with higer refresh rates causes screen flicker.

---
 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(+)
drivers/gpu/drm/i915/display/intel_dp.c +5 -0
index 640c43bf62d4c..5ce00cfe36ee1 100644
@@ -1436,6 +1436,11 @@ intel_dp_mode_valid(struct drm_connector *_connector,
 	if (mode->clock < 10000)
 		return MODE_CLOCK_LOW;
 
+	if (intel_has_quirk(display, QUIRK_EDP_MAX_240HZ_HOOK) &&
+	    intel_dp_is_edp(intel_dp) &&
+	    drm_mode_vrefresh(mode) > 240)
+		return MODE_BAD;
+
 	fixed_mode = intel_panel_fixed_mode(connector, mode);
 	if (intel_dp_is_edp(intel_dp) && fixed_mode) {
 		status = intel_panel_mode_valid(connector, mode);
drivers/gpu/drm/i915/display/intel_quirks.c +30 -0
index a32fae510ed27..438ce2cb37a01 100644
@@ -72,6 +72,12 @@ static void quirk_no_pps_backlight_power_hook(struct intel_display *display)
 	drm_info(display->drm, "Applying no pps backlight power quirk\n");
 }
 
+static void quirk_edp_max_240hz_hook(struct intel_display *display)
+{
+	intel_set_quirk(display, QUIRK_EDP_MAX_240HZ_HOOK);
+	drm_info(display->drm, "Applying max 240Hz quirk\n");
+}
+
 static void quirk_fw_sync_len(struct intel_dp *intel_dp)
 {
 	struct intel_display *display = to_intel_display(intel_dp);
@@ -120,6 +126,12 @@ static int intel_dmi_no_pps_backlight(const struct dmi_system_id *id)
 	return 1;
 }
 
+static int intel_dmi_edp_max_240hz(const struct dmi_system_id *id)
+{
+	DRM_INFO("Restrict output refreshrate to maximum 240Hz %s\n", id->ident);
+	return 1;
+}
+
 static const struct intel_dmi_quirk intel_dmi_quirks[] = {
 	{
 		.dmi_id_list = &(const struct dmi_system_id[]) {
@@ -166,6 +178,24 @@ static const struct intel_dmi_quirk intel_dmi_quirks[] = {
 		},
 		.hook = quirk_no_pps_backlight_power_hook,
 	},
+	{
+		.dmi_id_list = &(const struct dmi_system_id[]) {
+			{
+				.callback = intel_dmi_edp_max_240hz,
+				.ident = "TUXEDO Stellaris 16 Intel Gen7",
+				.matches = {DMI_EXACT_MATCH(DMI_BOARD_NAME, "X6AR5xxY"),
+				},
+			},
+			{
+				.callback = intel_dmi_edp_max_240hz,
+				.ident = "TUXEDO Stellaris 16 Intel Gen7",
+				.matches = {DMI_EXACT_MATCH(DMI_BOARD_NAME, "X6AR5xxY_mLED"),
+				},
+			},
+			{ }
+		},
+		.hook = quirk_edp_max_240hz_hook,
+	},
 };
 
 static struct intel_quirk intel_quirks[] = {
drivers/gpu/drm/i915/display/intel_quirks.h +1 -0
index cafdebda75354..8fe3f3467106a 100644
@@ -20,6 +20,7 @@ enum intel_quirk_id {
 	QUIRK_LVDS_SSC_DISABLE,
 	QUIRK_NO_PPS_BACKLIGHT_POWER_HOOK,
 	QUIRK_FW_SYNC_LEN,
+	QUIRK_EDP_MAX_240HZ_HOOK,
 };
 
 void intel_init_quirks(struct intel_display *display);
Signature · 1 line
2.43.0
#2 lore raw
Quoted 37 lines

-----Original Message-----
From: Intel-gfx <[email protected]> On Behalf Of Werner Sembach
Sent: Saturday, July 5, 2025 12:34 AM
To: Jani Nikula <[email protected]>; Vivi, Rodrigo <[email protected]>; Joonas Lahtinen <[email protected]>; Tvrtko Ursulin <[email protected]>; David Airlie <[email protected]>; Simona Vetter <[email protected]>
Cc: Tim Guttzeit <[email protected]>; Werner Sembach <[email protected]>; [email protected]; intel- [email protected]; [email protected]; linux- [email protected]
Subject: [RFC PATCH 1/1] drm/i915/display: Avoid unsupported 300Hz output mode on a TUXEDO device

From: Tim Guttzeit <[email protected]>

Removes all display modes with more than 240 Hz for the integrated display on a TUXEDO Stellaris 16 Gen7, because using the iGPU with higer refresh rates causes screen flicker.

---
 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(+)
drivers/gpu/drm/i915/display/intel_dp.c +0 -0
index 640c43bf62d4c..5ce00cfe36ee1 100644

drivers/gpu/drm/i915/display/intel_dp.c intel_dp_mode_valid(struct drm_connector · line 1444

Quoted 9 lines
drivers/gpu/drm/i915/display/intel_dp.c +5 -0
@@ -1436,6 +1436,11 @@ intel_dp_mode_valid(struct drm_connector
 *_connector,
 	if (mode->clock < 10000)
 		return MODE_CLOCK_LOW;
 
+	if (intel_has_quirk(display, QUIRK_EDP_MAX_240HZ_HOOK) &&
+	    intel_dp_is_edp(intel_dp) &&
+	    drm_mode_vrefresh(mode) > 240)
+		return MODE_BAD;
+

Adding a quirk for this is not the right approach. If this is not supported by the display, should have been pruned by the driver.

Thanks and Regards,
Arun R Murthy
-------------> fixed_mode = intel_panel_fixed_mode(connector, mode);

Quoted 73 lines
drivers/gpu/drm/i915/display/intel_dp.c +0 -0
 	if (intel_dp_is_edp(intel_dp) && fixed_mode) {
 		status = intel_panel_mode_valid(connector, mode); diff --git

a/drivers/gpu/drm/i915/display/intel_quirks.c
b/drivers/gpu/drm/i915/display/intel_quirks.c
index a32fae510ed27..438ce2cb37a01 100644

drivers/gpu/drm/i915/display/intel_quirks.c +7 -0
@@ -72,6 +72,12 @@ static void quirk_no_pps_backlight_power_hook(struct
 intel_display *display)
 	drm_info(display->drm, "Applying no pps backlight power quirk\n");  }
 
+static void quirk_edp_max_240hz_hook(struct intel_display *display) {
+	intel_set_quirk(display, QUIRK_EDP_MAX_240HZ_HOOK);
+	drm_info(display->drm, "Applying max 240Hz quirk\n"); }
+
 static void quirk_fw_sync_len(struct intel_dp *intel_dp)  {
 	struct intel_display *display = to_intel_display(intel_dp); @@ -120,6
+126,12 @@ static int intel_dmi_no_pps_backlight(const struct dmi_system_id
 *id)
 	return 1;
 }
 
+static int intel_dmi_edp_max_240hz(const struct dmi_system_id *id) {
+	DRM_INFO("Restrict output refreshrate to maximum 240Hz %s\n", id-
Quoted 1 line

ident);

drivers/gpu/drm/i915/display/intel_quirks.c +10 -0
+	return 1;
+}
+
 static const struct intel_dmi_quirk intel_dmi_quirks[] = {
 	{
 		.dmi_id_list = &(const struct dmi_system_id[]) { @@ -166,6
+178,24 @@ static const struct intel_dmi_quirk intel_dmi_quirks[] = {
 		},
 		.hook = quirk_no_pps_backlight_power_hook,
 	},
+	{
+		.dmi_id_list = &(const struct dmi_system_id[]) {
+			{
+				.callback = intel_dmi_edp_max_240hz,
+				.ident = "TUXEDO Stellaris 16 Intel Gen7",
+				.matches =

{DMI_EXACT_MATCH(DMI_BOARD_NAME, "X6AR5xxY"),

drivers/gpu/drm/i915/display/intel_quirks.c +6 -0
+				},
+			},
+			{
+				.callback = intel_dmi_edp_max_240hz,
+				.ident = "TUXEDO Stellaris 16 Intel Gen7",
+				.matches =

{DMI_EXACT_MATCH(DMI_BOARD_NAME, "X6AR5xxY_mLED"),

drivers/gpu/drm/i915/display/intel_quirks.c +6 -0
+				},
+			},
+			{ }
+		},
+		.hook = quirk_edp_max_240hz_hook,
+	},
 };
 
 static struct intel_quirk intel_quirks[] = { diff --git

a/drivers/gpu/drm/i915/display/intel_quirks.h
b/drivers/gpu/drm/i915/display/intel_quirks.h
index cafdebda75354..8fe3f3467106a 100644

drivers/gpu/drm/i915/display/intel_quirks.h +1 -1
@@ -20,6 +20,7 @@ enum intel_quirk_id {
 	QUIRK_LVDS_SSC_DISABLE,
 	QUIRK_NO_PPS_BACKLIGHT_POWER_HOOK,
 	QUIRK_FW_SYNC_LEN,
+	QUIRK_EDP_MAX_240HZ_HOOK,
 };
 
 void intel_init_quirks(struct intel_display *display);
--

2.43.0

#3 lore raw

Am 17.07.25 um 09:30 schrieb Murthy, Arun R:

Quoted 41 lines
Quoted 41 lines

-----Original Message-----
From: Intel-gfx <[email protected]> On Behalf Of Werner Sembach
Sent: Saturday, July 5, 2025 12:34 AM
To: Jani Nikula <[email protected]>; Vivi, Rodrigo <[email protected]>; Joonas Lahtinen <[email protected]>; Tvrtko Ursulin <[email protected]>; David Airlie <[email protected]>; Simona Vetter <[email protected]>
Cc: Tim Guttzeit <[email protected]>; Werner Sembach <[email protected]>; [email protected]; intel- [email protected]; [email protected]; linux- [email protected]
Subject: [RFC PATCH 1/1] drm/i915/display: Avoid unsupported 300Hz output mode on a TUXEDO device

From: Tim Guttzeit <[email protected]>

Removes all display modes with more than 240 Hz for the integrated display on a TUXEDO Stellaris 16 Gen7, because using the iGPU with higer refresh rates causes screen flicker.

---
 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(+)
drivers/gpu/drm/i915/display/intel_dp.c +0 -0
index 640c43bf62d4c..5ce00cfe36ee1 100644
@@ -1436,6 +1436,11 @@ intel_dp_mode_valid(struct drm_connector
 *_connector,
      if (mode->clock < 10000)
          return MODE_CLOCK_LOW;
 
Quoted 7 lines

drivers/gpu/drm/i915/display/intel_dp.c intel_dp_mode_valid(struct drm_connector *_connector, · line 1443

Quoted 5 lines
drivers/gpu/drm/i915/display/intel_dp.c +5 -0
+    if (intel_has_quirk(display, QUIRK_EDP_MAX_240HZ_HOOK) &&
+        intel_dp_is_edp(intel_dp) &&
+        drm_mode_vrefresh(mode) > 240)
+        return MODE_BAD;
+

Adding a quirk for this is not the right approach. If this is not supported by the display, should have been pruned by the driver.

Thank you for your reply. The panel (NE160QDM-NZL) supports 300 Hz and advertises it. Also when running the system on its NVIDIA dGPU, it runs perfectly fine without the flickering and on 300 Hz. On the iGPU, which is apparently unable to support 300 Hz, it is not pruned, thus leading to the flickering.

Best regards,
Tim Guttzeit

Quoted 79 lines

------------->      fixed_mode = intel_panel_fixed_mode(connector, mode);

Quoted 75 lines
drivers/gpu/drm/i915/display/intel_dp.c +0 -0
      if (intel_dp_is_edp(intel_dp) && fixed_mode) {

         status = intel_panel_mode_valid(connector, mode); diff --git a/drivers/gpu/drm/i915/display/intel_quirks.c b/drivers/gpu/drm/i915/display/intel_quirks.c
index a32fae510ed27..438ce2cb37a01 100644

drivers/gpu/drm/i915/display/intel_quirks.c +4 -0
@@ -72,6 +72,12 @@ static void quirk_no_pps_backlight_power_hook(struct
 intel_display *display)
      drm_info(display->drm, "Applying no pps backlight power quirk\n");  }
 
+static void quirk_edp_max_240hz_hook(struct intel_display *display) {
+    intel_set_quirk(display, QUIRK_EDP_MAX_240HZ_HOOK);
+    drm_info(display->drm, "Applying max 240Hz quirk\n"); }
+
  static void quirk_fw_sync_len(struct intel_dp *intel_dp)  {

     struct intel_display *display = to_intel_display(intel_dp); @@ -120,6
+126,12 @@ static int intel_dmi_no_pps_backlight(const struct dmi_system_id
*id)
     return 1;
 }

+static int intel_dmi_edp_max_240hz(const struct dmi_system_id *id) { +    DRM_INFO("Restrict output refreshrate to maximum 240Hz %s\n", id-

Quoted 1 line

ident);

+    return 1;

drivers/gpu/drm/i915/display/intel_quirks.c +2 -0
+}
+

 static const struct intel_dmi_quirk intel_dmi_quirks[] = { {
         .dmi_id_list = &(const struct dmi_system_id[]) { @@ -166,6 +178,24 @@ static const struct intel_dmi_quirk intel_dmi_quirks[] = { },
         .hook = quirk_no_pps_backlight_power_hook,
     },
+    {
+        .dmi_id_list = &(const struct dmi_system_id[]) { +            {
+                .callback = intel_dmi_edp_max_240hz,
+                .ident = "TUXEDO Stellaris 16 Intel Gen7", +                .matches = {DMI_EXACT_MATCH(DMI_BOARD_NAME, "X6AR5xxY"),
+                },
+            },
+            {
+                .callback = intel_dmi_edp_max_240hz,
+                .ident = "TUXEDO Stellaris 16 Intel Gen7", +                .matches = {DMI_EXACT_MATCH(DMI_BOARD_NAME, "X6AR5xxY_mLED"),
+                },
+            },
+            { }
+        },
+        .hook = quirk_edp_max_240hz_hook,
+    },
 };

 static struct intel_quirk intel_quirks[] = { diff --git a/drivers/gpu/drm/i915/display/intel_quirks.h b/drivers/gpu/drm/i915/display/intel_quirks.h index cafdebda75354..8fe3f3467106a 100644

drivers/gpu/drm/i915/display/intel_quirks.h +1 -0
@@ -20,6 +20,7 @@ enum intel_quirk_id {
      QUIRK_LVDS_SSC_DISABLE,
      QUIRK_NO_PPS_BACKLIGHT_POWER_HOOK,
      QUIRK_FW_SYNC_LEN,
+    QUIRK_EDP_MAX_240HZ_HOOK,
  };
 
  void intel_init_quirks(struct intel_display *display);
Signature · 1 line
2.43.0
#4 lore raw
In reply to Werner Sembach

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:

Quoted 22 lines

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(+)
#5 lore raw

✗ LGCI.VerificationFailed: failure for drm/i915/display: Avoid unsupported 300Hz output mode on a TUXEDO device

In reply to Werner Sembach
== Series Details ==

== Series Details ==

Series: drm/i915/display: Avoid unsupported 300Hz output mode on a TUXEDO device
URL : https://patchwork.freedesktop.org/series/151265/
State : failure

== Summary ==

Address '[email protected]' is not on the allowlist, which prevents CI from being triggered for this patch. If you want Intel GFX CI to accept this address, please contact the script maintainers at [email protected]. Exception occurred during validation, bailing out!

#6 lore raw

✗ LGCI.VerificationFailed: failure for drm/i915/display: Avoid unsupported 300Hz output mode on a TUXEDO device

In reply to Werner Sembach
== Series Details ==

== Series Details ==

Series: drm/i915/display: Avoid unsupported 300Hz output mode on a TUXEDO device
URL : https://patchwork.freedesktop.org/series/151268/
State : failure

== Summary ==

Address '[email protected]' is not on the allowlist, which prevents CI from being triggered for this patch. If you want Intel GFX CI to accept this address, please contact the script maintainers at [email protected]. Exception occurred during validation, bailing out!

maintainer
#7 lore raw
In reply to Werner Sembach
Quoted 1 line · Werner Sembach

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.

Quoted 24 lines

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(+)
Signature · 1 line
2.43.0
#8 lore raw

Hi all,

Am 08.07.25 um 23:05 schrieb Rodrigo Vivi:

Quoted 7 lines · Werner Sembach
Quoted 1 line

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

Quoted 27 lines

Thanks for the investigation and the quirk,
Rodrigo.

Quoted 23 lines

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(+)
Signature · 1 line
2.43.0
#9 lore raw

Hi all,

Quoted 1 line

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:

Quoted 45 lines

Hi all,

Am 08.07.25 um 23:05 schrieb Rodrigo Vivi:

Quoted 7 lines · Werner Sembach
Quoted 1 line

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

Quoted 28 lines

Thanks for the investigation and the quirk,
Rodrigo.

Quoted 24 lines

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(+)
Signature · 1 line
2.43.0
#10 lore raw

Hi all,

added [email protected] and [email protected], as requested in the ticket.

Best regards,
Tim Guttzeit

Am 09.07.25 um 15:32 schrieb Tim Guttzeit:

Quoted 57 lines

Hi all,

Quoted 1 line

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:

Quoted 45 lines

Hi all,

Am 08.07.25 um 23:05 schrieb Rodrigo Vivi:

Quoted 7 lines · Werner Sembach
Quoted 1 line

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

Quoted 28 lines

Thanks for the investigation and the quirk,
Rodrigo.

Quoted 24 lines

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(+)
Signature · 1 line
2.43.0
Signature · 13 lines
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