drm/i915: keep backlight_enable on until turn eDP display off
Subsystems (3)
PATCH 1/1 drm/i915: keep backlight_enable on until turn eDP display off
This workaround is specific for a particular panel on Google chromebook project. When user space daemon enter idle state. It request adjust brightness to 0, turn backlight_enable signal off and keep eDP main link active.
On general LCD, this behavior might not be a problem. But on this panel, its tcon would expect source to execute full eDP power off sequence after drop backlight_enable signal. Without eDP power off sequence. Even source try to turn backlight_enable signal on and restore proper brightness level. This panel is not able to light on again.
This WA ignored the request from user space daemon to disable backlight_enable signal and keep it on always. When user space request kernel to turn eDP display off, kernel driver still can control backlight_enable signal properly. It would not impact standard eDP power off sequence.
--- drivers/gpu/drm/i915/display/intel_panel.c | 4 ++- drivers/gpu/drm/i915/display/intel_quirks.c | 34 +++++++++++++++++++++ drivers/gpu/drm/i915/i915_drv.h | 1 + 3 files changed, 38 insertions(+), 1 deletion(-)
drivers/gpu/drm/i915/display/intel_panel.c +3 -1
@@ -1311,6 +1311,7 @@ static void intel_panel_set_backlight(const struct drm_connector_state *conn_stastatic int intel_backlight_device_update_status (struct backlight_device *bd) {struct intel_connector *connector =bl_get_data (bd); +struct drm_i915_private *dev_priv =to_i915 (connector->base.dev);struct intel_panel *panel = &connector->panel;struct drm_device *dev = connector->base.dev;
@@ -1330,7 +1331,8 @@ static int intel_backlight_device_update_status(struct backlight_device *bd)if (panel->backlight.power) {bool enable = bd->props.power ==FB_BLANK_UNBLANK && bd->props.brightness !=0 ; - panel->backlight.power (connector, enable); +if (enable || !(dev_priv->quirks &QUIRK_KEEP_BACKLIGHT_ENABLE_ON )) + panel->backlight.power (connector, enable); } }else { bd->props.power =FB_BLANK_POWERDOWN ;
drivers/gpu/drm/i915/display/intel_quirks.c +34 -0
@@ -53,6 +53,12 @@ static void quirk_increase_ddi_disabled_time(struct drm_i915_private *i915)drm_info (&i915->drm,"Applying Increase DDI Disabled quirk\n" ); } +static void quirk_keep_backlight_enable_on (struct drm_i915_private *i915) +{ + i915->quirks |=QUIRK_KEEP_BACKLIGHT_ENABLE_ON ; +drm_info (&i915->drm,"applying keep backlight enable on quirk\n" ); +} +struct intel_quirk {int device;int subsystem_vendor;
@@ -72,6 +78,12 @@ static int intel_dmi_reverse_brightness(const struct dmi_system_id *id)return 1 ; } +static int backlight_wa_callback (const struct dmi_system_id *id) +{ +DRM_INFO ("This is WA to ignore backlight off to prevent OLED panel issue on %s device\n" , id->ident); +return 1 ; +} +static const struct intel_dmi_quirk intel_dmi_quirks[] = { { .dmi_id_list = &(const struct dmi_system_id []) {
@@ -96,6 +108,28 @@ static const struct intel_dmi_quirk intel_dmi_quirks[] = { }, .hook = quirk_invert_brightness, }, + { + .dmi_id_list = &(const struct dmi_system_id[]) { + { + .callback = backlight_wa_callback, + .ident ="Google Lillipup" , + .matches = {DMI_MATCH (DMI_BOARD_VENDOR ,"Google" ), +DMI_MATCH (DMI_BOARD_NAME ,"Lindar" ), +DMI_MATCH (DMI_PRODUCT_SKU ,"sku524294" ), + }, + }, + { + .callback = backlight_wa_callback, + .ident ="Google Lillipup" , + .matches = {DMI_MATCH (DMI_BOARD_VENDOR ,"Google" ), +DMI_MATCH (DMI_BOARD_NAME ,"Lindar" ), +DMI_MATCH (DMI_PRODUCT_SKU ,"sku524295" ), + }, + }, + { } + }, + .hook = quirk_keep_backlight_enable_on, + }, }; static struct intel_quirk intel_quirks[] = {
drivers/gpu/drm/i915/i915_drv.h +1 -0
@@ -467,6 +467,7 @@ struct i915_drrs {#define QUIRK_PIN_SWIZZLED_PAGES (1<<5)#define QUIRK_INCREASE_T12_DELAY (1<<6)#define QUIRK_INCREASE_DDI_DISABLED_TIME (1<<7) +#define QUIRK_KEEP_BACKLIGHT_ENABLE_ON (1<<8)struct intel_fbdev ;struct intel_fbc_work ;
Signature · 6 lines
2.17.1 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Jani Nikula
maintainerQuoted 43 lines · Lee Shawn C
This workaround is specific for a particular panel on Google chromebook project. When user space daemon enter idle state. It request adjust brightness to 0, turn
backlight_enablesignal off and keep eDP main link active.On general LCD, this behavior might not be a problem. But on this panel, its tcon would expect source to execute full eDP power off sequence after drop
backlight_enablesignal. Without eDP power off sequence. Even source try to turnbacklight_enablesignal on and restore proper brightness level. This panel is not able to light on again.This WA ignored the request from user space daemon to disable
backlight_enablesignal and keep it on always. When user space request kernel to turn eDP display off, kernel driver still can controlbacklight_enablesignal properly. It would not impact standard eDP power off sequence.Cc Ville Syrjala <[email protected]>Cc Imre Deak <[email protected]>Cc Jani Nikula <[email protected]>Cc Cooper Chiou <[email protected]>Signed-off-by Lee Shawn C <[email protected]>--- drivers/gpu/drm/i915/display/intel_panel.c | 4 ++- drivers/gpu/drm/i915/display/intel_quirks.c | 34 +++++++++++++++++++++ drivers/gpu/drm/i915/i915_drv.h | 1 + 3 files changed, 38 insertions(+), 1 deletion(-)drivers/gpu/drm/i915/display/intel_panel.c +1
-0@@ -1311,6 +1311,7 @@ static void intel_panel_set_backlight(const struct drm_connector_state *conn_stastatic int intel_backlight_device_update_status (struct backlight_device *bd) {struct intel_connector *connector =bl_get_data (bd); +struct drm_i915_private *dev_priv =to_i915 (connector->base.dev);struct intel_panel *panel = &connector->panel;struct drm_device *dev = connector->base.dev;
drivers/gpu/drm/i915/display/intel_panel.c static int intel_backlight_device_update_status(struct backlight_device *bd) · line 1335
Quoted 6 lines
drivers/gpu/drm/i915/display/intel_panel.c +2
-1@@ -1330,7 +1331,8 @@ static int intel_backlight_device_update_status(struct backlight_device *bd)if (panel->backlight.power) {bool enable = bd->props.power ==FB_BLANK_UNBLANK && bd->props.brightness !=0 ; - panel->backlight.power (connector, enable); +if (enable || !(dev_priv->quirks &QUIRK_KEEP_BACKLIGHT_ENABLE_ON )) + panel->backlight.power (connector, enable);
We'll want to avoid the hook altogether in this case, instead of complicating the logic even more. Something like:
drivers/gpu/drm/i915/display/intel_dp.c +2 -1
@@ -5286,7 +5286,8 @@ static bool intel_edp_init_connector(struct intel_dp *intel_dp, }intel_panel_init (&intel_connector->panel, fixed_mode, downclock_mode); - intel_connector->panel.backlight.power = intel_pps_backlight_power; +if (!(dev_priv->quirks &QUIRK_NO_PPS_BACKLIGHT_POWER_HOOK )) + intel_connector->panel.backlight.power = intel_pps_backlight_power;intel_panel_setup_backlight (connector, pipe);if (fixed_mode) {
---
Please adjust the quirk name and debug logs accordingly.
Truth be told I'd rather nuke the hook completely. But it was a request from Chrome to have this lightweight sub-state to black out the display, without mode set, using the panel power sequencer in cases where we can't set the backlight PWM to 0.
Hmm. Is the brightness controlled using PWM or DPCD? We probably shouldn't do this at all when the brightness control is done using DPCD.
BR,
Jani.
Quoted 74 lines
drivers/gpu/drm/i915/display/intel_panel.c +0
-0} }else { bd->props.power =FB_BLANK_POWERDOWN ;drivers/gpu/drm/i915/display/intel_quirks.c +34
-0@@ -53,6 +53,12 @@ static void quirk_increase_ddi_disabled_time(struct drm_i915_private *i915)drm_info (&i915->drm,"Applying Increase DDI Disabled quirk\n" ); } +static void quirk_keep_backlight_enable_on (struct drm_i915_private *i915) +{ + i915->quirks |=QUIRK_KEEP_BACKLIGHT_ENABLE_ON ; +drm_info (&i915->drm,"applying keep backlight enable on quirk\n" ); +} +struct intel_quirk {int device;int subsystem_vendor;@@ -72,6 +78,12 @@ static int intel_dmi_reverse_brightness(const struct dmi_system_id *id)return 1 ; } +static int backlight_wa_callback (const struct dmi_system_id *id) +{ +DRM_INFO ("This is WA to ignore backlight off to prevent OLED panel issue on %s device\n" , id->ident); +return 1 ; +} +static const struct intel_dmi_quirk intel_dmi_quirks[] = { { .dmi_id_list = &(const struct dmi_system_id []) {@@ -96,6 +108,28 @@ static const struct intel_dmi_quirk intel_dmi_quirks[] = { }, .hook = quirk_invert_brightness, }, + { + .dmi_id_list = &(const struct dmi_system_id[]) { + { + .callback = backlight_wa_callback, + .ident ="Google Lillipup" , + .matches = {DMI_MATCH (DMI_BOARD_VENDOR ,"Google" ), +DMI_MATCH (DMI_BOARD_NAME ,"Lindar" ), +DMI_MATCH (DMI_PRODUCT_SKU ,"sku524294" ), + }, + }, + { + .callback = backlight_wa_callback, + .ident ="Google Lillipup" , + .matches = {DMI_MATCH (DMI_BOARD_VENDOR ,"Google" ), +DMI_MATCH (DMI_BOARD_NAME ,"Lindar" ), +DMI_MATCH (DMI_PRODUCT_SKU ,"sku524295" ), + }, + }, + { } + }, + .hook = quirk_keep_backlight_enable_on, + }, }; static struct intel_quirk intel_quirks[] = {drivers/gpu/drm/i915/i915_drv.h +1
-0@@ -467,6 +467,7 @@ struct i915_drrs {#define QUIRK_PIN_SWIZZLED_PAGES (1<<5)#define QUIRK_INCREASE_T12_DELAY (1<<6)#define QUIRK_INCREASE_DDI_DISABLED_TIME (1<<7) +#define QUIRK_KEEP_BACKLIGHT_ENABLE_ON (1<<8)struct intel_fbdev ;struct intel_fbc_work ;
Signature · 5 lines
Jani Nikula, Intel Open Source Graphics Center _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoted 69 lines · Jani Nikula
Quoted 44 lines · Lee Shawn C
This workaround is specific for a particular panel on Google chromebook project. When user space daemon enter idle state. It request adjust brightness to 0, turn
backlight_enablesignal off and keep eDP main link active.On general LCD, this behavior might not be a problem. But on this panel, its tcon would expect source to execute full eDP power off sequence after drop
backlight_enablesignal. Without eDP power off sequence. Even source try to turnbacklight_enablesignal on and restore proper brightness level. This panel is not able to light on again.This WA ignored the request from user space daemon to disable
backlight_enablesignal and keep it on always. When user space request kernel to turn eDP display off, kernel driver still can controlbacklight_enablesignal properly. It would not impact standard eDP power off sequence.Cc Ville Syrjala <[email protected]>Cc Imre Deak <[email protected]>Cc Jani Nikula <[email protected]>Cc Cooper Chiou <[email protected]>Signed-off-by Lee Shawn C <[email protected]>--- drivers/gpu/drm/i915/display/intel_panel.c | 4 ++- drivers/gpu/drm/i915/display/intel_quirks.c | 34 +++++++++++++++++++++ drivers/gpu/drm/i915/i915_drv.h | 1 + 3 files changed, 38 insertions(+), 1 deletion(-)drivers/gpu/drm/i915/display/intel_panel.c +0
-0@@ -1311,6 +1311,7 @@ static void intel_panel_set_backlight(conststruct
drm_connector_state*conn_stastatic intintel_backlight_device_update_status(struct backlight_device *bd){drivers/gpu/drm/i915/display/intel_panel.c +1
-0struct intel_connector *connector =bl_get_data (bd); +struct drm_i915_private *dev_priv =to_i915 (connector->base.dev);struct intel_panel *panel = &connector->panel;struct drm_device *dev = connector->base.dev;drivers/gpu/drm/i915/display/intel_panel.c static int intel_backlight_device_update_status(struct backlight_device *bd) · line 1335
Quoted 6 lines
drivers/gpu/drm/i915/display/intel_panel.c +2
-1@@ -1330,7 +1331,8 @@ static int intel_backlight_device_update_status(struct backlight_device *bd)if (panel->backlight.power) {bool enable = bd->props.power ==FB_BLANK_UNBLANK && bd->props.brightness !=0 ; - panel->backlight.power (connector, enable); +if (enable || !(dev_priv->quirks &QUIRK_KEEP_BACKLIGHT_ENABLE_ON )) + panel->backlight.power (connector, enable);We'll want to avoid the hook altogether in this case, instead of complicating the logic even more. Something like:
drivers/gpu/drm/i915/display/intel_dp.c +2
-2@@ -5286,7 +5286,8 @@ static bool intel_edp_init_connector(struct intel_dp *intel_dp, }intel_panel_init (&intel_connector->panel, fixed_mode, downclock_mode); - intel_connector->panel.backlight.power = intel_pps_backlight_power; +if (!(dev_priv->quirks &QUIRK_NO_PPS_BACKLIGHT_POWER_HOOK )) + intel_connector->panel.backlight.power = intel_pps_backlight_power;intel_panel_setup_backlight (connector, pipe);if (fixed_mode) { ---
Quoted 2 lines
Please adjust the quirk name and debug logs accordingly.
Thanks! I will modify the quirk name and debug messages later.
Quoted 3 lines
Truth be told I'd rather nuke the hook completely. But it was a request from Chrome to have this lightweight sub-state to black out the display, without mode set, using the panel power sequencer in cases where we can't set the backlight PWM to 0.
Hmm. Is the brightness controlled using PWM or DPCD? We probably shouldn't do this at all when the brightness control is done using DPCD.
This panel refer to soc's backlight_enable signal to enable backlight. But adjust brightness via DPCD aux interface. If source turn backlight_enable signal off, panel tcon await source execute full eDP power off sequence to disable local display. And panel's backlight is not able to turn on again.
Best regards,
Shawn
Quoted 74 lines
BR,
Jani.Quoted 69 lines
drivers/gpu/drm/i915/display/intel_panel.c +0
-0} }else { bd->props.power = FB_BLANK_POWERDOWN; diff --git
a/drivers/gpu/drm/i915/display/intel_quirks.cb/drivers/gpu/drm/i915/display/intel_quirks.c
index98dd787b00e3..ed57b083edbb100644drivers/gpu/drm/i915/display/intel_quirks.c +10
-0@@ -53,6 +53,12 @@ static void quirk_increase_ddi_disabled_time(struct drm_i915_private *i915)drm_info (&i915->drm,"Applying Increase DDI Disabled quirk\n" ); } +static void quirk_keep_backlight_enable_on (struct drm_i915_private +*i915) { + i915->quirks |=QUIRK_KEEP_BACKLIGHT_ENABLE_ON ; +drm_info (&i915->drm,"applying keep backlight enable on quirk\n" ); } +struct intel_quirk {int device;int subsystem_vendor;@@ -72,6 +78,12 @@ static int intel_dmi_reverse_brightness(const struct dmi_system_id *id)return 1 ; } +static int backlight_wa_callback (const struct dmi_system_id *id) { +DRM_INFO ("This is WA to ignore backlight off to prevent OLED panel issue on %s device\n" , id->ident); +return 1 ; +} +static const struct intel_dmi_quirk intel_dmi_quirks[] = { { .dmi_id_list = &(const struct dmi_system_id[]) { @@ -96,6 +108,28@@ static const struct
intel_dmi_quirkintel_dmi_quirks[] = {drivers/gpu/drm/i915/display/intel_quirks.c +22
-0}, .hook = quirk_invert_brightness, }, + { + .dmi_id_list = &(const struct dmi_system_id[]) { + { + .callback = backlight_wa_callback, + .ident = "Google Lillipup", + .matches = {DMI_MATCH(DMI_BOARD_VENDOR, "Google"), + DMI_MATCH(DMI_BOARD_NAME, "Lindar"), + DMI_MATCH(DMI_PRODUCT_SKU, "sku524294"), + }, + }, + { + .callback = backlight_wa_callback, + .ident = "Google Lillipup", + .matches = {DMI_MATCH(DMI_BOARD_VENDOR, "Google"), + DMI_MATCH(DMI_BOARD_NAME, "Lindar"), + DMI_MATCH(DMI_PRODUCT_SKU, "sku524295"), + }, + }, + { } + }, + .hook = quirk_keep_backlight_enable_on, + }, }; static struct intel_quirk intel_quirks[] = { diff --git
a/drivers/gpu/drm/i915/i915_drv.hb/drivers/gpu/drm/i915/i915_drv.hindex01e11fe38642..8103919bf3b4100644drivers/gpu/drm/i915/i915_drv.h +0
-0@@ -467,6 +467,7 @@ struct i915_drrs { #define
QUIRK_PIN_SWIZZLED_PAGES(1<<5) #defineQUIRK_INCREASE_T12_DELAY(1<<6) #defineQUIRK_INCREASE_DDI_DISABLED_TIME(1<<7) +#defineQUIRK_KEEP_BACKLIGHT_ENABLE_ON(1<<8)
Quoted 6 lines
Quoted 2 lines
struct
intel_fbdev;
structintel_fbc_work;--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/i915: keep backlight_enable on until turn eDP display off (rev2)
In reply to Lee Shawn C== Series Details ==
== Series Details ==
Series: drm/i915: keep backlight_enable on until turn eDP display off (rev2)
URL : https://patchwork.freedesktop.org/series/91780/
State : failure
== Summary ==
CALL scripts/checksyscalls.sh
CALL scripts/atomic/check-atomics.sh
DESCEND objtool
CHK include/generated/compile.h
CC [M] drivers/gpu/drm/i915/display/intel_dp.odrivers/gpu/drm/i915/display/intel_dp.c: In function ‘intel_edp_init_connector’:drivers/gpu/drm/i915/display/intel_dp.c:5241:27: error: ‘QUIRK_NO_PPS_BACKLIGHT_POWER_HOOK’ undeclared (first use in this function); did you mean ‘QUIRK_BACKLIGHT_PRESENT’?
if (!(dev_priv->quirks & QUIRK_NO_PPS_BACKLIGHT_POWER_HOOK))
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
QUIRK_BACKLIGHT_PRESENTdrivers/gpu/drm/i915/display/intel_dp.c:5241:27: note: each undeclared identifier is reported only once for each function it appears in scripts/Makefile.build:272: recipe for target 'drivers/gpu/drm/i915/display/intel_dp.o' failed
make[4]: *** [drivers/gpu/drm/i915/display/intel_dp.o] Error 1scripts/Makefile.build:515: recipe for target 'drivers/gpu/drm/i915' failed
make[3]: *** [drivers/gpu/drm/i915] Error 2scripts/Makefile.build:515: recipe for target 'drivers/gpu/drm' failed
make[2]: *** [drivers/gpu/drm] Error 2scripts/Makefile.build:515: recipe for target 'drivers/gpu' failed
make[1]: *** [drivers/gpu] Error 2
Makefile:1847: recipe for target 'drivers' failed
make: *** [drivers] Error 2
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v3 1/1 drm/i915: keep backlight_enable on until turn eDP display off
In reply to Lee Shawn CThis workaround is specific for a particular panel on Google chromebook project. When user space daemon enter idle state. It request adjust brightness to 0, turn backlight_enable signal off and keep eDP main link active.
On general LCD, this behavior might not be a problem. But on this panel, its tcon would expect source to execute full eDP power off sequence after drop backlight_enable signal. Without eDP power off sequence. Even source try to turn backlight_enable signal on and restore proper brightness level. This panel is not able to light on again.
This WA ignored the request from user space daemon to disable backlight_enable signal and keep it on always. When user space request kernel to turn eDP display off, kernel driver still can control backlight_enable signal properly. It would not impact standard eDP power off sequence.
v2: modify the quirk name and debug messages.
unregister backlight.power callback for specific device.
--- drivers/gpu/drm/i915/display/intel_dp.c | 3 +- drivers/gpu/drm/i915/display/intel_quirks.c | 34 +++++++++++++++++++++ drivers/gpu/drm/i915/i915_drv.h | 1 + 3 files changed, 37 insertions(+), 1 deletion(-)
drivers/gpu/drm/i915/display/intel_dp.c +2 -1
@@ -5238,7 +5238,8 @@ static bool intel_edp_init_connector(struct intel_dp *intel_dp, }intel_panel_init (&intel_connector->panel, fixed_mode, downclock_mode); - intel_connector->panel.backlight.power = intel_pps_backlight_power; +if (!(dev_priv->quirks &QUIRK_NO_PPS_BACKLIGHT_POWER_HOOK )) + intel_connector->panel.backlight.power = intel_pps_backlight_power;intel_panel_setup_backlight (connector, pipe);if (fixed_mode) {
drivers/gpu/drm/i915/display/intel_quirks.c +34 -0
@@ -53,6 +53,12 @@ static void quirk_increase_ddi_disabled_time(struct drm_i915_private *i915)drm_info (&i915->drm,"Applying Increase DDI Disabled quirk\n" ); } +static void quirk_no_pps_backlight_power_hook (struct drm_i915_private *i915) +{ + i915->quirks |=QUIRK_NO_PPS_BACKLIGHT_POWER_HOOK ; +drm_info (&i915->drm,"Applying no pps backlight power quirk\n" ); +} +struct intel_quirk {int device;int subsystem_vendor;
@@ -72,6 +78,12 @@ static int intel_dmi_reverse_brightness(const struct dmi_system_id *id)return 1 ; } +static int intel_dmi_no_pps_backlight (const struct dmi_system_id *id) +{ +DRM_INFO ("This workaround prevented panel backlight issue on %s device\n" , id->ident); +return 1 ; +} +static const struct intel_dmi_quirk intel_dmi_quirks[] = { { .dmi_id_list = &(const struct dmi_system_id []) {
@@ -96,6 +108,28 @@ static const struct intel_dmi_quirk intel_dmi_quirks[] = { }, .hook = quirk_invert_brightness, }, + { + .dmi_id_list = &(const struct dmi_system_id[]) { + { + .callback = intel_dmi_no_pps_backlight, + .ident ="Google Lillipup" , + .matches = {DMI_MATCH (DMI_BOARD_VENDOR ,"Google" ), +DMI_MATCH (DMI_BOARD_NAME ,"Lindar" ), +DMI_MATCH (DMI_PRODUCT_SKU ,"sku524294" ), + }, + }, + { + .callback = intel_dmi_no_pps_backlight, + .ident ="Google Lillipup" , + .matches = {DMI_MATCH (DMI_BOARD_VENDOR ,"Google" ), +DMI_MATCH (DMI_BOARD_NAME ,"Lindar" ), +DMI_MATCH (DMI_PRODUCT_SKU ,"sku524295" ), + }, + }, + { } + }, + .hook = quirk_no_pps_backlight_power_hook, + }, }; static struct intel_quirk intel_quirks[] = {
drivers/gpu/drm/i915/i915_drv.h +1 -0
@@ -467,6 +467,7 @@ struct i915_drrs {#define QUIRK_PIN_SWIZZLED_PAGES (1<<5)#define QUIRK_INCREASE_T12_DELAY (1<<6)#define QUIRK_INCREASE_DDI_DISABLED_TIME (1<<7) +#define QUIRK_NO_PPS_BACKLIGHT_POWER_HOOK (1<<8)struct intel_fbdev ;struct intel_fbc_work ;
Signature · 6 lines
2.17.1 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Jani Nikula
maintainerQuoted 65 lines · Lee Shawn C
This workaround is specific for a particular panel on Google chromebook project. When user space daemon enter idle state. It request adjust brightness to 0, turn
backlight_enablesignal off and keep eDP main link active.On general LCD, this behavior might not be a problem. But on this panel, its tcon would expect source to execute full eDP power off sequence after drop
backlight_enablesignal. Without eDP power off sequence. Even source try to turnbacklight_enablesignal on and restore proper brightness level. This panel is not able to light on again.This WA ignored the request from user space daemon to disable
backlight_enablesignal and keep it on always. When user space request kernel to turn eDP display off, kernel driver still can controlbacklight_enablesignal properly. It would not impact standard eDP power off sequence.v2: modify the quirk name and debug messages.
unregister backlight.power callback for specific device.Cc Ville Syrjala <[email protected]>Cc Imre Deak <[email protected]>Cc Jani Nikula <[email protected]>Cc Cooper Chiou <[email protected]>Signed-off-by Lee Shawn C <[email protected]>--- drivers/gpu/drm/i915/display/intel_dp.c | 3 +- drivers/gpu/drm/i915/display/intel_quirks.c | 34 +++++++++++++++++++++ drivers/gpu/drm/i915/i915_drv.h | 1 + 3 files changed, 37 insertions(+), 1 deletion(-)drivers/gpu/drm/i915/display/intel_dp.c +2
-1@@ -5238,7 +5238,8 @@ static bool intel_edp_init_connector(struct intel_dp *intel_dp, }intel_panel_init (&intel_connector->panel, fixed_mode, downclock_mode); - intel_connector->panel.backlight.power = intel_pps_backlight_power; +if (!(dev_priv->quirks &QUIRK_NO_PPS_BACKLIGHT_POWER_HOOK )) + intel_connector->panel.backlight.power = intel_pps_backlight_power;intel_panel_setup_backlight (connector, pipe);if (fixed_mode) {drivers/gpu/drm/i915/display/intel_quirks.c +6
-0@@ -53,6 +53,12 @@ static void quirk_increase_ddi_disabled_time(struct drm_i915_private *i915)drm_info (&i915->drm,"Applying Increase DDI Disabled quirk\n" ); } +static void quirk_no_pps_backlight_power_hook (struct drm_i915_private *i915) +{ + i915->quirks |=QUIRK_NO_PPS_BACKLIGHT_POWER_HOOK ; +drm_info (&i915->drm,"Applying no pps backlight power quirk\n" ); +} +struct intel_quirk {int device;int subsystem_vendor;
drivers/gpu/drm/i915/display/intel_quirks.c static int intel_dmi_reverse_brightness(const struct dmi_system_id *id) · line 83
Quoted 6 lines
drivers/gpu/drm/i915/display/intel_quirks.c +3
-0@@ -72,6 +78,12 @@ static int intel_dmi_reverse_brightness(const struct dmi_system_id *id)return 1 ; } +static int intel_dmi_no_pps_backlight (const struct dmi_system_id *id) +{ +DRM_INFO ("This workaround prevented panel backlight issue on %s device\n" , id->ident);
Not sure I like the verbose "This workaround ..." style messages.
Contrast with what the messages for reverse polarity would be via dmi:
"Backlight polarity reversed on %s\n"
->
"applying inverted panel brightness quirk\n"
Quoted 17 lines
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 []) {@@ -96,6 +108,28 @@ static const struct intel_dmi_quirk intel_dmi_quirks[] = { }, .hook = quirk_invert_brightness, }, + { + .dmi_id_list = &(const struct dmi_system_id[]) { + { + .callback = intel_dmi_no_pps_backlight, + .ident = "Google Lillipup", + .matches = {DMI_MATCH(DMI_BOARD_VENDOR, "Google"), + DMI_MATCH(DMI_BOARD_NAME, "Lindar"),
drivers/gpu/drm/i915/display/intel_quirks.c static const struct intel_dmi_quirk intel_dmi_quirks[] = { · line 127
Quoted 10 lines
drivers/gpu/drm/i915/display/intel_quirks.c +10
-0+ DMI_MATCH(DMI_PRODUCT_SKU, "sku524294"), + }, + }, + { + .callback = intel_dmi_no_pps_backlight, + .ident = "Google Lillipup", + .matches = {DMI_MATCH(DMI_BOARD_VENDOR, "Google"), +DMI_MATCH (DMI_BOARD_NAME ,"Lindar" ), + DMI_MATCH(DMI_PRODUCT_SKU, "sku524295"), + },
I think you should use DMI_EXACT_MATCH instead of DMI_MATCH. The former users strcmp while the latter uses strstr for comparison.
The .ident string should probably be different for the two cases; otherwise the DRM_INFO() logging above does not differentiate between the two.
Sorry for not catching all of these at v1 review. Anyway, this is just small details, the approach is fine.
BR,
Jani.
Quoted 20 lines
drivers/gpu/drm/i915/display/intel_quirks.c +5
-0+ }, + { } + }, + .hook = quirk_no_pps_backlight_power_hook, + }, }; static struct intel_quirk intel_quirks[] = {drivers/gpu/drm/i915/i915_drv.h +1
-0@@ -467,6 +467,7 @@ struct i915_drrs {#define QUIRK_PIN_SWIZZLED_PAGES (1<<5)#define QUIRK_INCREASE_T12_DELAY (1<<6)#define QUIRK_INCREASE_DDI_DISABLED_TIME (1<<7) +#define QUIRK_NO_PPS_BACKLIGHT_POWER_HOOK (1<<8)struct intel_fbdev ;struct intel_fbc_work ;
Signature · 5 lines
Jani Nikula, Intel Open Source Graphics Center _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoted 76 lines · Jani Nikula
Quoted 65 lines · Lee Shawn C
This workaround is specific for a particular panel on Google chromebook project. When user space daemon enter idle state. It request adjust brightness to 0, turn
backlight_enablesignal off and keep eDP main link active.On general LCD, this behavior might not be a problem. But on this panel, its tcon would expect source to execute full eDP power off sequence after drop
backlight_enablesignal. Without eDP power off sequence. Even source try to turnbacklight_enablesignal on and restore proper brightness level. This panel is not able to light on again.This WA ignored the request from user space daemon to disable
backlight_enablesignal and keep it on always. When user space request kernel to turn eDP display off, kernel driver still can controlbacklight_enablesignal properly. It would not impact standard eDP power off sequence.v2: modify the quirk name and debug messages.
unregister backlight.power callback for specific device.Cc Ville Syrjala <[email protected]>Cc Imre Deak <[email protected]>Cc Jani Nikula <[email protected]>Cc Cooper Chiou <[email protected]>Signed-off-by Lee Shawn C <[email protected]>--- drivers/gpu/drm/i915/display/intel_dp.c | 3 +- drivers/gpu/drm/i915/display/intel_quirks.c | 34 +++++++++++++++++++++ drivers/gpu/drm/i915/i915_drv.h | 1 + 3 files changed, 37 insertions(+), 1 deletion(-)drivers/gpu/drm/i915/display/intel_dp.c +2
-1@@ -5238,7 +5238,8 @@ static bool intel_edp_init_connector(struct intel_dp *intel_dp, }intel_panel_init (&intel_connector->panel, fixed_mode, downclock_mode); - intel_connector->panel.backlight.power = intel_pps_backlight_power; +if (!(dev_priv->quirks &QUIRK_NO_PPS_BACKLIGHT_POWER_HOOK )) + intel_connector->panel.backlight.power = intel_pps_backlight_power;intel_panel_setup_backlight (connector, pipe);if (fixed_mode) {drivers/gpu/drm/i915/display/intel_quirks.c +5
-0@@ -53,6 +53,12 @@ static void quirk_increase_ddi_disabled_time(struct drm_i915_private *i915)drm_info (&i915->drm,"Applying Increase DDI Disabled quirk\n" ); } +static void quirk_no_pps_backlight_power_hook (struct drm_i915_private +*i915) { + i915->quirks |=QUIRK_NO_PPS_BACKLIGHT_POWER_HOOK ; +drm_info (&i915->drm,"Applying no pps backlight power quirk\n" ); } +struct intel_quirk {int device;int subsystem_vendor;drivers/gpu/drm/i915/display/intel_quirks.c static int intel_dmi_reverse_brightness(const struct dmi_system_id *id) · line 84
Quoted 7 lines
drivers/gpu/drm/i915/display/intel_quirks.c +4
-0@@ -72,6 +78,12 @@ static int intel_dmi_reverse_brightness(const struct dmi_system_id *id)return 1 ; } +static int intel_dmi_no_pps_backlight (const struct dmi_system_id *id) +{ +DRM_INFO ("This workaround prevented panel backlight issue on %s +device\n", id->ident);Not sure I like the verbose "This workaround ..." style messages.
Quoted 6 lines
Contrast with what the messages for reverse polarity would be via dmi:
"Backlight polarity reversed on %s\n"
->
"applying inverted panel brightness quirk\n"
The hook function will print messages to indicate driver had this quirk and it should be enough. I will remove this debug output DRM_INFO("This ....").
Quoted 30 lines
Quoted 17 lines
drivers/gpu/drm/i915/display/intel_quirks.c +3
-0+return 1 ; +} +static const struct intel_dmi_quirk intel_dmi_quirks[] = { { .dmi_id_list = &(const struct dmi_system_id[]) { @@ -96,6 +108,28@@ static const struct
intel_dmi_quirkintel_dmi_quirks[] = {drivers/gpu/drm/i915/display/intel_quirks.c +7
-0}, .hook = quirk_invert_brightness, }, + { + .dmi_id_list = &(const struct dmi_system_id[]) { + { + .callback = intel_dmi_no_pps_backlight, + .ident = "Google Lillipup", + .matches = {DMI_MATCH(DMI_BOARD_VENDOR, "Google"), + DMI_MATCH(DMI_BOARD_NAME, "Lindar"),drivers/gpu/drm/i915/display/intel_quirks.c static const struct intel_dmi_quirk intel_dmi_quirks[] = { · line 127
Quoted 10 lines
drivers/gpu/drm/i915/display/intel_quirks.c +10
-0+ DMI_MATCH(DMI_PRODUCT_SKU, "sku524294"), + }, + }, + { + .callback = intel_dmi_no_pps_backlight, + .ident = "Google Lillipup", + .matches = {DMI_MATCH(DMI_BOARD_VENDOR, "Google"), +DMI_MATCH (DMI_BOARD_NAME ,"Lindar" ), + DMI_MATCH(DMI_PRODUCT_SKU, "sku524295"), + },I think you should use
DMI_EXACT_MATCHinstead ofDMI_MATCH. The former users strcmp while the latter uses strstr for comparison.
Quoted 2 lines
The .ident string should probably be different for the two cases; otherwise the
DRM_INFO()logging above does not differentiate between the two.
OK! Let me confirm with ODM team. We can have differnt .ident string (+ sku1, sku2, etc...).
Best regards,
Shawn
Quoted 23 lines
Sorry for not catching all of these at v1 review. Anyway, this is just small details, the approach is fine.
BR,
Jani.Quoted 17 lines
drivers/gpu/drm/i915/display/intel_quirks.c +5
-0+ }, + { } + }, + .hook = quirk_no_pps_backlight_power_hook, + }, }; static struct intel_quirk intel_quirks[] = { diff --git
a/drivers/gpu/drm/i915/i915_drv.hb/drivers/gpu/drm/i915/i915_drv.hindex01e11fe38642..5a065be0792a100644drivers/gpu/drm/i915/i915_drv.h +0
-0@@ -467,6 +467,7 @@ struct i915_drrs { #define
QUIRK_PIN_SWIZZLED_PAGES(1<<5) #defineQUIRK_INCREASE_T12_DELAY(1<<6) #defineQUIRK_INCREASE_DDI_DISABLED_TIME(1<<7) +#defineQUIRK_NO_PPS_BACKLIGHT_POWER_HOOK(1<<8)
Quoted 5 lines
Quoted 2 lines
struct
intel_fbdev;
structintel_fbc_work;--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: keep backlight_enable on until turn eDP display off (rev3)
In reply to Lee Shawn C== Series Details ==
== Series Details ==
Series: drm/i915: keep backlight_enable on until turn eDP display off (rev3)
URL : https://patchwork.freedesktop.org/series/91780/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
9d04638ef39d drm/i915: keep backlight_enable on until turn eDP display off
-:115: CHECK:SPACING: spaces preferred around that '<<' (ctx:VxV)
#115: FILE: drivers/gpu/drm/i915/i915_drv.h:470:
+#define QUIRK_NO_PPS_BACKLIGHT_POWER_HOOK (1<<8)
^total: 0 errors, 0 warnings, 1 checks, 68 lines checked
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: keep backlight_enable on until turn eDP display off (rev3)
In reply to Lee Shawn C== Series Details ==
== Series Details ==
Series: drm/i915: keep backlight_enable on until turn eDP display off (rev3)
URL : https://patchwork.freedesktop.org/series/91780/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10262 -> Patchwork_20430
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/index.html
Changes
-------
No changes found
Participating hosts (43 -> 39)
------------------------------
Missing (4): fi-ilk-m540 fi-bsw-cyan fi-bdw-samus fi-hsw-4200u
Build changes
-------------
* Linux: CI_DRM_10262 -> Patchwork_20430
CI-20190529: 20190529
CI_DRM_10262: 56fd29b5c9b4b66818fc768e87dadea323babc1f @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6117: 3ba0a02404f243d6d8f232c6215163cc4b0fd699 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_20430: 9d04638ef39d4663002c6ba97298903b8eb66466 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
9d04638ef39d drm/i915: keep backlight_enable on until turn eDP display off
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: keep backlight_enable on until turn eDP display off (rev3)
In reply to Lee Shawn C== Series Details ==
== Series Details ==
Series: drm/i915: keep backlight_enable on until turn eDP display off (rev3)
URL : https://patchwork.freedesktop.org/series/91780/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10262_full -> Patchwork_20430_full
====================================================
Summary
-------
**SUCCESS**
No regressions found.
Known issues
------------
Here are the changes found in Patchwork_20430_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@feature_discovery@psr2:
- shard-iclb: [PASS][1] -> [SKIP][2] ([i915#658])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10262/shard-iclb2/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-iclb7/igt@[email protected]
* igt@gem_create@create-clear:
- shard-glk: [PASS][3] -> [FAIL][4] ([i915#1888] / [i915#3160])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10262/shard-glk5/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-glk8/igt@[email protected]
* igt@gem_ctx_persistence@engines-mixed:
- shard-snb: NOTRUN -> [SKIP][5] ([fdo#109271] / [i915#1099]) +2 similar issues
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-snb6/igt@[email protected]
* igt@gem_eio@unwedge-stress:
- shard-snb: NOTRUN -> [FAIL][6] ([i915#3354])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-snb2/igt@[email protected]
* igt@gem_exec_fair@basic-deadline:
- shard-apl: NOTRUN -> [FAIL][7] ([i915#2846])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-apl6/igt@[email protected]
* igt@gem_exec_fair@basic-none-solo@rcs0:
- shard-kbl: [PASS][8] -> [FAIL][9] ([i915#2842])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10262/shard-kbl3/igt@gem_exec_fair@[email protected]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-kbl1/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-pace-share@rcs0:
- shard-tglb: [PASS][10] -> [FAIL][11] ([i915#2842])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10262/shard-tglb5/igt@gem_exec_fair@[email protected]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-tglb2/igt@gem_exec_fair@[email protected]
- shard-glk: [PASS][12] -> [FAIL][13] ([i915#2842])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10262/shard-glk8/igt@gem_exec_fair@[email protected]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-glk8/igt@gem_exec_fair@[email protected]
* igt@gem_exec_params@no-blt:
- shard-iclb: NOTRUN -> [SKIP][14] ([fdo#109283])
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-iclb3/igt@[email protected]
* igt@gem_exec_reloc@basic-wide-active@vcs1:
- shard-iclb: NOTRUN -> [FAIL][15] ([i915#3633])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-iclb4/igt@gem_exec_reloc@[email protected]
* igt@gem_huc_copy@huc-copy:
- shard-apl: NOTRUN -> [SKIP][16] ([fdo#109271] / [i915#2190])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-apl6/igt@[email protected]
* igt@gem_mmap_gtt@big-copy-xy:
- shard-glk: [PASS][17] -> [FAIL][18] ([i915#307])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10262/shard-glk3/igt@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-glk1/igt@[email protected]
* igt@gem_mmap_gtt@cpuset-basic-small-copy-odd:
- shard-glk: [PASS][19] -> [FAIL][20] ([i915#307] / [i915#3468]) +1 similar issue
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10262/shard-glk6/igt@[email protected]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-glk6/igt@[email protected]
* igt@gem_mmap_gtt@cpuset-big-copy:
- shard-iclb: [PASS][21] -> [FAIL][22] ([i915#307])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10262/shard-iclb1/igt@[email protected]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-iclb8/igt@[email protected]
* igt@gem_mmap_offset@clear:
- shard-skl: [PASS][23] -> [FAIL][24] ([i915#3160])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10262/shard-skl3/igt@[email protected]
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-skl5/igt@[email protected]
* igt@gem_pread@exhaustion:
- shard-apl: NOTRUN -> [WARN][25] ([i915#2658])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-apl8/igt@[email protected]
* igt@gem_render_copy@y-tiled-ccs-to-y-tiled-mc-ccs:
- shard-iclb: NOTRUN -> [SKIP][26] ([i915#768]) +1 similar issue
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-iclb3/igt@[email protected]
* igt@gen9_exec_parse@allowed-single:
- shard-skl: [PASS][27] -> [DMESG-WARN][28] ([i915#1436] / [i915#716])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10262/shard-skl3/igt@[email protected]
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-skl8/igt@[email protected]
* igt@i915_pm_lpsp@kms-lpsp@kms-lpsp-dp:
- shard-apl: NOTRUN -> [SKIP][29] ([fdo#109271] / [i915#1937])
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-apl6/igt@i915_pm_lpsp@[email protected]
* igt@i915_pm_rc6_residency@rc6-fence:
- shard-iclb: NOTRUN -> [WARN][30] ([i915#1804] / [i915#2684])
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-iclb7/igt@[email protected]
* igt@kms_async_flips@alternate-sync-async-flip:
- shard-skl: [PASS][31] -> [FAIL][32] ([i915#2521])
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10262/shard-skl3/igt@[email protected]
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-skl5/igt@[email protected]
* igt@kms_big_fb@linear-32bpp-rotate-180:
- shard-glk: [PASS][33] -> [DMESG-WARN][34] ([i915#118] / [i915#95])
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10262/shard-glk3/igt@[email protected]
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-glk3/igt@[email protected]
* igt@kms_chamelium@dp-crc-fast:
- shard-iclb: NOTRUN -> [SKIP][35] ([fdo#109284] / [fdo#111827]) +1 similar issue
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-iclb7/igt@[email protected]
- shard-glk: NOTRUN -> [SKIP][36] ([fdo#109271] / [fdo#111827]) +2 similar issues
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-glk5/igt@[email protected]
* igt@kms_chamelium@dp-mode-timings:
- shard-apl: NOTRUN -> [SKIP][37] ([fdo#109271] / [fdo#111827]) +27 similar issues
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-apl3/igt@[email protected]
* igt@kms_chamelium@hdmi-hpd-with-enabled-mode:
- shard-snb: NOTRUN -> [SKIP][38] ([fdo#109271] / [fdo#111827]) +20 similar issues
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-snb2/igt@[email protected]
* igt@kms_chamelium@vga-frame-dump:
- shard-skl: NOTRUN -> [SKIP][39] ([fdo#109271] / [fdo#111827]) +2 similar issues
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-skl2/igt@[email protected]
* igt@kms_color_chamelium@pipe-a-ctm-blue-to-red:
- shard-kbl: NOTRUN -> [SKIP][40] ([fdo#109271] / [fdo#111827]) +3 similar issues
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-kbl1/igt@[email protected]
* igt@kms_content_protection@atomic-dpms:
- shard-apl: NOTRUN -> [TIMEOUT][41] ([i915#1319])
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-apl8/igt@[email protected]
- shard-iclb: NOTRUN -> [SKIP][42] ([fdo#109300] / [fdo#111066])
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-iclb7/igt@[email protected]
* igt@kms_cursor_crc@pipe-b-cursor-512x170-sliding:
- shard-iclb: NOTRUN -> [SKIP][43] ([fdo#109278] / [fdo#109279])
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-iclb7/igt@[email protected]
* igt@kms_cursor_legacy@cursorb-vs-flipb-atomic-transitions-varying-size:
- shard-iclb: NOTRUN -> [SKIP][44] ([fdo#109274] / [fdo#109278]) +1 similar issue
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-iclb7/igt@kms_cursor_legacy@cursorb-vs-flipb-atomic-transitions-varying-size.html
* igt@kms_cursor_legacy@flip-vs-cursor-busy-crc-atomic:
- shard-apl: NOTRUN -> [DMESG-WARN][45] ([IGT#6])
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-apl6/igt@[email protected]
* igt@kms_cursor_legacy@pipe-d-torture-move:
- shard-skl: NOTRUN -> [SKIP][46] ([fdo#109271]) +29 similar issues
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-skl2/igt@[email protected]
* igt@kms_dp_tiled_display@basic-test-pattern:
- shard-iclb: NOTRUN -> [SKIP][47] ([i915#426])
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-iclb3/igt@[email protected]
* igt@kms_flip@2x-flip-vs-rmfb-interruptible:
- shard-iclb: NOTRUN -> [SKIP][48] ([fdo#109274])
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-iclb3/igt@[email protected]
* igt@kms_flip@plain-flip-fb-recreate-interruptible@b-edp1:
- shard-skl: [PASS][49] -> [FAIL][50] ([i915#2122]) +2 similar issues
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10262/shard-skl4/igt@kms_flip@[email protected]
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-skl10/igt@kms_flip@[email protected]
* igt@kms_flip@single-buffer-flip-vs-dpms-off-vs-modeset@a-edp1:
- shard-skl: [PASS][51] -> [DMESG-WARN][52] ([i915#1982]) +1 similar issue
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10262/shard-skl9/igt@kms_flip@[email protected]
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-skl9/igt@kms_flip@[email protected]
* igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytilercccs:
- shard-apl: NOTRUN -> [SKIP][53] ([fdo#109271] / [i915#2672])
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-apl8/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbc-2p-primscrn-spr-indfb-draw-blt:
- shard-kbl: NOTRUN -> [SKIP][54] ([fdo#109271]) +17 similar issues
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-kbl1/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbcpsr-2p-shrfb-fliptrack-mmap-gtt:
- shard-iclb: NOTRUN -> [SKIP][55] ([fdo#109280]) +8 similar issues
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-iclb7/igt@[email protected]
- shard-glk: NOTRUN -> [SKIP][56] ([fdo#109271]) +21 similar issues
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-glk5/igt@[email protected]
* igt@kms_hdr@bpc-switch-suspend:
- shard-kbl: [PASS][57] -> [DMESG-WARN][58] ([i915#180]) +5 similar issues
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10262/shard-kbl1/igt@[email protected]
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-kbl2/igt@[email protected]
* igt@kms_invalid_dotclock:
- shard-iclb: NOTRUN -> [SKIP][59] ([fdo#109310])
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-iclb7/igt@kms_invalid_dotclock.html
* igt@kms_pipe_crc_basic@read-crc-pipe-d:
- shard-apl: NOTRUN -> [SKIP][60] ([fdo#109271] / [i915#533]) +2 similar issues
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-apl6/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-a-alpha-opaque-fb:
- shard-apl: NOTRUN -> [FAIL][61] ([fdo#108145] / [i915#265]) +3 similar issues
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-apl8/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-c-alpha-transparent-fb:
- shard-apl: NOTRUN -> [FAIL][62] ([i915#265])
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-apl6/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-c-coverage-7efc:
- shard-skl: [PASS][63] -> [FAIL][64] ([fdo#108145] / [i915#265]) +1 similar issue
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10262/shard-skl3/igt@[email protected]
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-skl5/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-d-coverage-vs-premult-vs-constant:
- shard-iclb: NOTRUN -> [SKIP][65] ([fdo#109278]) +6 similar issues
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-iclb7/igt@kms_plane_alpha_blend@pipe-d-coverage-vs-premult-vs-constant.html
* igt@kms_plane_scaling@scaler-with-clipping-clamping@pipe-c-scaler-with-clipping-clamping:
- shard-apl: NOTRUN -> [SKIP][66] ([fdo#109271] / [i915#2733])
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-apl6/igt@kms_plane_scaling@scaler-with-clipping-clamping@pipe-c-scaler-with-clipping-clamping.html
* igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-3:
- shard-iclb: NOTRUN -> [SKIP][67] ([i915#658])
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-iclb3/igt@[email protected]
* igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-5:
- shard-apl: NOTRUN -> [SKIP][68] ([fdo#109271] / [i915#658]) +4 similar issues
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-apl8/igt@[email protected]
* igt@kms_psr@psr2_cursor_plane_move:
- shard-iclb: NOTRUN -> [SKIP][69] ([fdo#109441])
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-iclb3/igt@kms_psr@psr2_cursor_plane_move.html
* igt@kms_psr@psr2_cursor_plane_onoff:
- shard-iclb: [PASS][70] -> [SKIP][71] ([fdo#109441]) +1 similar issue
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10262/shard-iclb2/igt@kms_psr@psr2_cursor_plane_onoff.html
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-iclb7/igt@kms_psr@psr2_cursor_plane_onoff.html
* igt@kms_setmode@basic:
- shard-snb: NOTRUN -> [FAIL][72] ([i915#31])
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-snb2/igt@[email protected]
* igt@kms_vblank@pipe-d-query-forked-hang:
- shard-snb: NOTRUN -> [SKIP][73] ([fdo#109271]) +325 similar issues
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-snb6/igt@[email protected]
* igt@kms_writeback@writeback-check-output:
- shard-apl: NOTRUN -> [SKIP][74] ([fdo#109271] / [i915#2437]) +1 similar issue
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-apl6/igt@[email protected]
* igt@nouveau_crc@pipe-d-ctx-flip-skip-current-frame:
- shard-iclb: NOTRUN -> [SKIP][75] ([fdo#109278] / [i915#2530])
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-iclb3/igt@[email protected]
* igt@perf@short-reads:
- shard-skl: [PASS][76] -> [FAIL][77] ([i915#51])
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10262/shard-skl4/igt@[email protected]
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-skl10/igt@[email protected]
* igt@prime_nv_api@i915_nv_reimport_twice_check_flink_name:
- shard-apl: NOTRUN -> [SKIP][78] ([fdo#109271]) +297 similar issues
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-apl6/igt@prime_nv_api@i915_nv_reimport_twice_check_flink_name.html
- shard-iclb: NOTRUN -> [SKIP][79] ([fdo#109291])
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-iclb3/igt@prime_nv_api@i915_nv_reimport_twice_check_flink_name.html
* igt@sysfs_clients@fair-7:
- shard-apl: NOTRUN -> [SKIP][80] ([fdo#109271] / [i915#2994]) +1 similar issue
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-apl6/igt@[email protected]
#### Possible fixes ####
* igt@gem_create@create-clear:
- shard-skl: [FAIL][81] ([i915#3160]) -> [PASS][82]
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10262/shard-skl4/igt@[email protected]
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-skl10/igt@[email protected]
* igt@gem_ctx_isolation@preservation-s3@rcs0:
- shard-kbl: [INCOMPLETE][83] ([i915#794]) -> [PASS][84]
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10262/shard-kbl4/igt@gem_ctx_isolation@[email protected]
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-kbl1/igt@gem_ctx_isolation@[email protected]
* igt@gem_exec_capture@pi@rcs0:
- shard-skl: [INCOMPLETE][85] ([i915#2369]) -> [PASS][86]
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10262/shard-skl7/igt@gem_exec_capture@[email protected]
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-skl4/igt@gem_exec_capture@[email protected]
* igt@gem_exec_fair@basic-none@vcs0:
- shard-kbl: [FAIL][87] ([i915#2842]) -> [PASS][88]
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10262/shard-kbl3/igt@gem_exec_fair@[email protected]
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-kbl3/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-pace@rcs0:
- shard-glk: [FAIL][89] ([i915#2842]) -> [PASS][90]
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10262/shard-glk3/igt@gem_exec_fair@[email protected]
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-glk3/igt@gem_exec_fair@[email protected]
* igt@gem_mmap_gtt@cpuset-basic-small-copy:
- shard-iclb: [FAIL][91] ([i915#307]) -> [PASS][92]
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10262/shard-iclb6/igt@[email protected]
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-iclb3/igt@[email protected]
* igt@gen9_exec_parse@allowed-all:
- shard-skl: [DMESG-WARN][93] ([i915#1436] / [i915#716]) -> [PASS][94]
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10262/shard-skl2/igt@[email protected]
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-skl2/igt@[email protected]
- shard-glk: [DMESG-WARN][95] ([i915#1436] / [i915#716]) -> [PASS][96]
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10262/shard-glk4/igt@[email protected]
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-glk5/igt@[email protected]
* igt@i915_pm_dc@dc6-psr:
- shard-iclb: [FAIL][97] ([i915#454]) -> [PASS][98]
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10262/shard-iclb4/igt@[email protected]
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-iclb8/igt@[email protected]
- shard-skl: [FAIL][99] ([i915#454]) -> [PASS][100]
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10262/shard-skl6/igt@[email protected]
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-skl5/igt@[email protected]
* igt@kms_big_fb@x-tiled-64bpp-rotate-0:
- shard-iclb: [DMESG-WARN][101] ([i915#3621]) -> [PASS][102]
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10262/shard-iclb1/igt@[email protected]
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-iclb3/igt@[email protected]
* igt@kms_cursor_crc@pipe-b-cursor-suspend:
- shard-kbl: [DMESG-WARN][103] ([i915#180]) -> [PASS][104]
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10262/shard-kbl2/igt@[email protected]
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-kbl3/igt@[email protected]
* igt@kms_flip@flip-vs-expired-vblank-interruptible@c-edp1:
- shard-skl: [FAIL][105] ([i915#79]) -> [PASS][106] +1 similar issue
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10262/shard-skl7/igt@kms_flip@[email protected]
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-skl4/igt@kms_flip@[email protected]
* igt@kms_plane_alpha_blend@pipe-a-constant-alpha-min:
- shard-skl: [FAIL][107] ([fdo#108145] / [i915#265]) -> [PASS][108]
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10262/shard-skl1/igt@[email protected]
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-skl1/igt@[email protected]
* igt@kms_psr2_su@frontbuffer:
- shard-iclb: [SKIP][109] ([fdo#109642] / [fdo#111068] / [i915#658]) -> [PASS][110]
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10262/shard-iclb5/igt@[email protected]
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-iclb2/igt@[email protected]
* igt@kms_psr@psr2_primary_blt:
- shard-iclb: [SKIP][111] ([fdo#109441]) -> [PASS][112]
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10262/shard-iclb8/igt@kms_psr@psr2_primary_blt.html
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-iclb2/igt@kms_psr@psr2_primary_blt.html
* igt@sysfs_timeslice_duration@timeout@vecs0:
- shard-skl: [FAIL][113] -> [PASS][114]
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10262/shard-skl7/igt@sysfs_timeslice_duration@[email protected]
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-skl9/igt@sysfs_timeslice_duration@[email protected]
#### Warnings ####
* igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-1:
- shard-iclb: [SKIP][115] ([i915#658]) -> [SKIP][116] ([i915#2920]) +1 similar issue
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10262/shard-iclb5/igt@[email protected]
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-iclb2/igt@[email protected]
* igt@runner@aborted:
- shard-iclb: ([FAIL][117], [FAIL][118], [FAIL][119], [FAIL][120]) ([i915#1814] / [i915#3002]) -> ([FAIL][121], [FAIL][122]) ([i915#3002])
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10262/shard-iclb2/igt@[email protected]
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10262/shard-iclb1/igt@[email protected]
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10262/shard-iclb8/igt@[email protected]
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10262/shard-iclb7/igt@[email protected]
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-iclb1/igt@[email protected]
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-iclb4/igt@[email protected]
- shard-apl: ([FAIL][123], [FAIL][124], [FAIL][125]) ([i915#180] / [i915#3002] / [i915#3363]) -> ([FAIL][126], [FAIL][127]) ([i915#3002] / [i915#3363])
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10262/shard-apl6/igt@[email protected]
[124]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10262/shard-apl3/igt@[email protected]
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10262/shard-apl7/igt@[email protected]
[126]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-apl7/igt@[email protected]
[127]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/shard-apl7/igt@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[IGT#6]: https://gitlab.freedesktop.org/drm/igt-gpu-tools/issues/6
[fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109274]: https://bugs.freedesktop.org/show_bug.cgi?id=109274
[fdo#109278]: https://bugs.freedesktop.org/show_bug.cgi?id=109278
[fdo#109279]: https://bugs.freedesktop.org/show_bug.cgi?id=109279
[fdo#109280]: https://bugs.freedesktop.org/show_bug.cgi?id=109280
[fdo#109283]: https://bugs.freedesktop.org/show_bug.cgi?id=109283
[fdo#109284]: https://bugs.freedesktop.org/show_bug.cgi?id=109284
[fdo#109291]: https://bugs.freedesktop.org/show_bug.cgi?id=109291
[fdo#109300]: https://bugs.freedesktop.org/show_bug.cgi?id=109300
[fdo#109310]: https://bugs.freedesktop.org/show_bug.cgi?id=109310
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#109642]: https://bugs.freedesktop.org/show_bug.cgi?id=109642
[fdo#111066]: https://bugs.freedesktop.org/show_bug.cgi?id=111066
[fdo#111068]: https://bugs.freedesktop.org/show_bug.cgi?id=111068
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1099]: https://gitlab.freedesktop.org/drm/intel/issues/1099
[i915#118]: https://gitlab.freedesktop.org/drm/intel/issues/118
[i915#1319]: https://gitlab.freedesktop.org/drm/intel/issues/1319
[i915#1436]: https://gitlab.freedesktop.org/drm/intel/issues/1436
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#1804]: https://gitlab.freedesktop.org/drm/intel/issues/1804
[i915#1814]: https://gitlab.freedesktop.org/drm/intel/issues/1814
[i915#1888]: https://gitlab.freedesktop.org/drm/intel/issues/1888
[i915#1937]: https://gitlab.freedesktop.org/drm/intel/issues/1937
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2122]: https://gitlab.freedesktop.org/drm/intel/issues/2122
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#2369]: https://gitlab.freedesktop.org/drm/intel/issues/2369
[i915#2437]: https://gitlab.freedesktop.org/drm/intel/issues/2437
[i915#2521]: https://gitlab.freedesktop.org/drm/intel/issues/2521
[i915#2530]: https://gitlab.freedesktop.org/drm/intel/issues/2530
[i915#265]: https://gitlab.freedesktop.org/drm/intel/issues/265
[i915#2658]: https://gitlab.freedesktop.org/drm/intel/issues/2658
[i915#2672]: https://gitlab.freedesktop.org/drm/intel/issues/2672
[i915#2684]: https://gitlab.freedesktop.org/drm/intel/issues/2684
[i915#2733]: https://gitlab.freedesktop.org/drm/intel/issues/2733
[i915#2842]: https://gitlab.freedesktop.org/drm/intel/issues/2842
[i915#2846]: https://gitlab.freedesktop.org/drm/intel/issues/2846
[i915#2920]: https://gitlab.freedesktop.org/drm/intel/issues/2920
[i915#2994]: https://gitlab.freedesktop.org/drm/intel/issues/2994
[i915#3002]: https://gitlab.freedesktop.org/drm/intel/issues/3002
[i915#307]: https://gitlab.freedesktop.org/drm/intel/issues/307
[i915#31]: https://gitlab.freedesktop.org/drm/intel/issues/31
[i915#3160]: https://gitlab.freedesktop.org/drm/intel/issues/3160
[i915#3354]: https://gitlab.freedesktop.org/drm/intel/issues/3354
[i915#3363]: https://gitlab.freedesktop.org/drm/intel/issues/3363
[i915#3468]: https://gitlab.freedesktop.org/drm/intel/issues/3468
[i915#3621]: https://gitlab.freedesktop.org/drm/intel/issues/3621
[i915#3633]: https://gitlab.freedesktop.org/drm/intel/issues/3633
[i915#426]: https://gitlab.freedesktop.org/drm/intel/issues/426
[i915#454]: https://gitlab.freedesktop.org/drm/intel/issues/454
[i915#51]: https://gitlab.freedesktop.org/drm/intel/issues/51
[i915#533]: https://gitlab.freedesktop.org/drm/intel/issues/533
[i915#658]: https://gitlab.freedesktop.org/drm/intel/issues/658
[i915#716]: https://gitlab.freedesktop.org/drm/intel/issues/716
[i915#768]: https://gitlab.freedesktop.org/drm/intel/issues/768
[i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79
[i915#794]: https://gitlab.freedesktop.org/drm/intel/issues/794
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95
Participating hosts (10 -> 10)
------------------------------
No changes in participating hosts
Build changes
-------------
* Linux: CI_DRM_10262 -> Patchwork_20430
CI-20190529: 20190529
CI_DRM_10262: 56fd29b5c9b4b66818fc768e87dadea323babc1f @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6117: 3ba0a0240
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20430/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v4 1/1 drm/i915: keep backlight_enable on until turn eDP display off
In reply to Lee Shawn CThis workaround is specific for a particular panel on Google chromebook project. When user space daemon enter idle state. It request adjust brightness to 0, turn backlight_enable signal off and keep eDP main link active.
On general LCD, this behavior might not be a problem. But on this panel, its tcon would expect source to execute full eDP power off sequence after drop backlight_enable signal. Without eDP power off sequence. Even source try to turn backlight_enable signal on and restore proper brightness level. This panel is not able to light on again.
This WA ignored the request from user space daemon to disable backlight_enable signal and keep it on always. When user space request kernel to turn eDP display off, kernel driver still can control backlight_enable signal properly. It would not impact standard eDP power off sequence.
v2: 1. modify the quirk name and debug messages.
2. unregister backlight.power callback for specific device.
v3: 1. modify debug output messages.
2. use DMI_EXACT_MATCH instead of DMI_MATCH.
--- drivers/gpu/drm/i915/display/intel_dp.c | 3 +- drivers/gpu/drm/i915/display/intel_quirks.c | 34 +++++++++++++++++++++ drivers/gpu/drm/i915/i915_drv.h | 1 + 3 files changed, 37 insertions(+), 1 deletion(-)
drivers/gpu/drm/i915/display/intel_dp.c +2 -1
@@ -5238,7 +5238,8 @@ static bool intel_edp_init_connector(struct intel_dp *intel_dp, }intel_panel_init (&intel_connector->panel, fixed_mode, downclock_mode); - intel_connector->panel.backlight.power = intel_pps_backlight_power; +if (!(dev_priv->quirks &QUIRK_NO_PPS_BACKLIGHT_POWER_HOOK )) + intel_connector->panel.backlight.power = intel_pps_backlight_power;intel_panel_setup_backlight (connector, pipe);if (fixed_mode) {
drivers/gpu/drm/i915/display/intel_quirks.c +34 -0
@@ -53,6 +53,12 @@ static void quirk_increase_ddi_disabled_time(struct drm_i915_private *i915)drm_info (&i915->drm,"Applying Increase DDI Disabled quirk\n" ); } +static void quirk_no_pps_backlight_power_hook (struct drm_i915_private *i915) +{ + i915->quirks |=QUIRK_NO_PPS_BACKLIGHT_POWER_HOOK ; +drm_info (&i915->drm,"Applying no pps backlight power quirk\n" ); +} +struct intel_quirk {int device;int subsystem_vendor;
@@ -72,6 +78,12 @@ static int intel_dmi_reverse_brightness(const struct dmi_system_id *id)return 1 ; } +static int intel_dmi_no_pps_backlight (const struct dmi_system_id *id) +{ +DRM_INFO ("No pps backlight support on %s\n" , id->ident); +return 1 ; +} +static const struct intel_dmi_quirk intel_dmi_quirks[] = { { .dmi_id_list = &(const struct dmi_system_id []) {
@@ -96,6 +108,28 @@ static const struct intel_dmi_quirk intel_dmi_quirks[] = { }, .hook = quirk_invert_brightness, }, + { + .dmi_id_list = &(const struct dmi_system_id[]) { + { + .callback = intel_dmi_no_pps_backlight, + .ident ="Google Lillipup sku524294" , + .matches = {DMI_EXACT_MATCH (DMI_BOARD_VENDOR ,"Google" ), +DMI_EXACT_MATCH (DMI_BOARD_NAME ,"Lindar" ), +DMI_EXACT_MATCH (DMI_PRODUCT_SKU ,"sku524294" ), + }, + }, + { + .callback = intel_dmi_no_pps_backlight, + .ident ="Google Lillipup sku524295" , + .matches = {DMI_EXACT_MATCH (DMI_BOARD_VENDOR ,"Google" ), +DMI_EXACT_MATCH (DMI_BOARD_NAME ,"Lindar" ), +DMI_EXACT_MATCH (DMI_PRODUCT_SKU ,"sku524295" ), + }, + }, + { } + }, + .hook = quirk_no_pps_backlight_power_hook, + }, }; static struct intel_quirk intel_quirks[] = {
drivers/gpu/drm/i915/i915_drv.h +1 -0
@@ -467,6 +467,7 @@ struct i915_drrs {#define QUIRK_PIN_SWIZZLED_PAGES (1<<5)#define QUIRK_INCREASE_T12_DELAY (1<<6)#define QUIRK_INCREASE_DDI_DISABLED_TIME (1<<7) +#define QUIRK_NO_PPS_BACKLIGHT_POWER_HOOK (1<<8)struct intel_fbdev ;struct intel_fbc_work ;
Signature · 6 lines
2.17.1 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Jani Nikula
maintainerQuoted 23 lines · Lee Shawn C
This workaround is specific for a particular panel on Google chromebook project. When user space daemon enter idle state. It request adjust brightness to 0, turn
backlight_enablesignal off and keep eDP main link active.On general LCD, this behavior might not be a problem. But on this panel, its tcon would expect source to execute full eDP power off sequence after drop
backlight_enablesignal. Without eDP power off sequence. Even source try to turnbacklight_enablesignal on and restore proper brightness level. This panel is not able to light on again.This WA ignored the request from user space daemon to disable
backlight_enablesignal and keep it on always. When user space request kernel to turn eDP display off, kernel driver still can controlbacklight_enablesignal properly. It would not impact standard eDP power off sequence.v2: 1. modify the quirk name and debug messages.
2. unregister backlight.power callback for specific device.
v3: 1. modify debug output messages.
2. useDMI_EXACT_MATCHinstead ofDMI_MATCH.
Quoted 5 lines
Cc Ville Syrjala <[email protected]>Cc Imre Deak <[email protected]>Cc Jani Nikula <[email protected]>Cc Cooper Chiou <[email protected]>Signed-off-by Lee Shawn C <[email protected]>
Thanks, pushed to drm-intel-next.
Quoted 91 lines
--- drivers/gpu/drm/i915/display/intel_dp.c | 3 +- drivers/gpu/drm/i915/display/intel_quirks.c | 34 +++++++++++++++++++++ drivers/gpu/drm/i915/i915_drv.h | 1 + 3 files changed, 37 insertions(+), 1 deletion(-)drivers/gpu/drm/i915/display/intel_dp.c +2
-1@@ -5238,7 +5238,8 @@ static bool intel_edp_init_connector(struct intel_dp *intel_dp, }intel_panel_init (&intel_connector->panel, fixed_mode, downclock_mode); - intel_connector->panel.backlight.power = intel_pps_backlight_power; +if (!(dev_priv->quirks &QUIRK_NO_PPS_BACKLIGHT_POWER_HOOK )) + intel_connector->panel.backlight.power = intel_pps_backlight_power;intel_panel_setup_backlight (connector, pipe);if (fixed_mode) {drivers/gpu/drm/i915/display/intel_quirks.c +34
-0@@ -53,6 +53,12 @@ static void quirk_increase_ddi_disabled_time(struct drm_i915_private *i915)drm_info (&i915->drm,"Applying Increase DDI Disabled quirk\n" ); } +static void quirk_no_pps_backlight_power_hook (struct drm_i915_private *i915) +{ + i915->quirks |=QUIRK_NO_PPS_BACKLIGHT_POWER_HOOK ; +drm_info (&i915->drm,"Applying no pps backlight power quirk\n" ); +} +struct intel_quirk {int device;int subsystem_vendor;@@ -72,6 +78,12 @@ static int intel_dmi_reverse_brightness(const struct dmi_system_id *id)return 1 ; } +static int intel_dmi_no_pps_backlight (const struct dmi_system_id *id) +{ +DRM_INFO ("No pps backlight support on %s\n" , id->ident); +return 1 ; +} +static const struct intel_dmi_quirk intel_dmi_quirks[] = { { .dmi_id_list = &(const struct dmi_system_id []) {@@ -96,6 +108,28 @@ static const struct intel_dmi_quirk intel_dmi_quirks[] = { }, .hook = quirk_invert_brightness, }, + { + .dmi_id_list = &(const struct dmi_system_id[]) { + { + .callback = intel_dmi_no_pps_backlight, + .ident ="Google Lillipup sku524294" , + .matches = {DMI_EXACT_MATCH (DMI_BOARD_VENDOR ,"Google" ), +DMI_EXACT_MATCH (DMI_BOARD_NAME ,"Lindar" ), +DMI_EXACT_MATCH (DMI_PRODUCT_SKU ,"sku524294" ), + }, + }, + { + .callback = intel_dmi_no_pps_backlight, + .ident ="Google Lillipup sku524295" , + .matches = {DMI_EXACT_MATCH (DMI_BOARD_VENDOR ,"Google" ), +DMI_EXACT_MATCH (DMI_BOARD_NAME ,"Lindar" ), +DMI_EXACT_MATCH (DMI_PRODUCT_SKU ,"sku524295" ), + }, + }, + { } + }, + .hook = quirk_no_pps_backlight_power_hook, + }, }; static struct intel_quirk intel_quirks[] = {drivers/gpu/drm/i915/i915_drv.h +1
-0@@ -467,6 +467,7 @@ struct i915_drrs {#define QUIRK_PIN_SWIZZLED_PAGES (1<<5)#define QUIRK_INCREASE_T12_DELAY (1<<6)#define QUIRK_INCREASE_DDI_DISABLED_TIME (1<<7) +#define QUIRK_NO_PPS_BACKLIGHT_POWER_HOOK (1<<8)struct intel_fbdev ;struct intel_fbc_work ;
Signature · 5 lines
Jani Nikula, Intel Open Source Graphics Center _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: keep backlight_enable on until turn eDP display off (rev4)
In reply to Lee Shawn C== Series Details ==
== Series Details ==
Series: drm/i915: keep backlight_enable on until turn eDP display off (rev4)
URL : https://patchwork.freedesktop.org/series/91780/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
8f8d8fc4ecbc drm/i915: keep backlight_enable on until turn eDP display off
-:116: CHECK:SPACING: spaces preferred around that '<<' (ctx:VxV)
#116: FILE: drivers/gpu/drm/i915/i915_drv.h:470:
+#define QUIRK_NO_PPS_BACKLIGHT_POWER_HOOK (1<<8)
^total: 0 errors, 0 warnings, 1 checks, 68 lines checked
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: keep backlight_enable on until turn eDP display off (rev4)
In reply to Lee Shawn C== Series Details ==
== Series Details ==
Series: drm/i915: keep backlight_enable on until turn eDP display off (rev4)
URL : https://patchwork.freedesktop.org/series/91780/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10271 -> Patchwork_20448
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/index.html
Known issues
------------
Here are the changes found in Patchwork_20448 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@amdgpu/amd_basic@cs-gfx:
- fi-kbl-soraka: NOTRUN -> [SKIP][1] ([fdo#109271]) +10 similar issues
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/fi-kbl-soraka/igt@amdgpu/[email protected]
* igt@i915_selftest@live@gt_heartbeat:
- fi-bdw-5557u: [PASS][2] -> [DMESG-FAIL][3] ([i915#541])
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/fi-bdw-5557u/igt@i915_selftest@live@gt_heartbeat.html
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/fi-bdw-5557u/igt@i915_selftest@live@gt_heartbeat.html
* igt@kms_chamelium@dp-crc-fast:
- fi-bsw-nick: NOTRUN -> [SKIP][4] ([fdo#109271] / [fdo#111827]) +8 similar issues
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/fi-bsw-nick/igt@[email protected]
* igt@prime_vgem@basic-fence-flip:
- fi-bsw-nick: NOTRUN -> [SKIP][5] ([fdo#109271]) +63 similar issues
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/fi-bsw-nick/igt@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1888]: https://gitlab.freedesktop.org/drm/intel/issues/1888
[i915#541]: https://gitlab.freedesktop.org/drm/intel/issues/541
Participating hosts (41 -> 38)
------------------------------
Missing (3): fi-ilk-m540 fi-bsw-cyan fi-bdw-samus
Build changes
-------------
* Linux: CI_DRM_10271 -> Patchwork_20448
CI-20190529: 20190529
CI_DRM_10271: 7a4a01d6716339c418394dbeb9a20d55bbb9a9ba @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6117: 3ba0a02404f243d6d8f232c6215163cc4b0fd699 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_20448: 8f8d8fc4ecbcb12609676c49faed23fc68eb78f2 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
8f8d8fc4ecbc drm/i915: keep backlight_enable on until turn eDP display off
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: keep backlight_enable on until turn eDP display off (rev4)
In reply to Lee Shawn C== Series Details ==
== Series Details ==
Series: drm/i915: keep backlight_enable on until turn eDP display off (rev4)
URL : https://patchwork.freedesktop.org/series/91780/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10271_full -> Patchwork_20448_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_20448_full absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in Patchwork_20448_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_20448_full:
### IGT changes ###
#### Possible regressions ####
* igt@sysfs_timeslice_duration@timeout@vecs0:
- shard-skl: [PASS][1] -> [FAIL][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-skl5/igt@sysfs_timeslice_duration@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-skl6/igt@sysfs_timeslice_duration@[email protected]
#### Warnings ####
* igt@kms_psr2_sf@cursor-plane-update-sf:
- shard-tglb: [SKIP][3] ([i915#2920]) -> [SKIP][4] +19 similar issues
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-tglb2/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-tglb3/igt@[email protected]
* igt@kms_psr2_sf@plane-move-sf-dmg-area-0:
- shard-iclb: [SKIP][5] ([i915#2920]) -> [SKIP][6] +1 similar issue
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-iclb2/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-iclb2/igt@[email protected]
* igt@kms_psr2_sf@plane-move-sf-dmg-area-1:
- shard-iclb: [SKIP][7] ([i915#658]) -> [SKIP][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-iclb1/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-iclb2/igt@[email protected]
Known issues
------------
Here are the changes found in Patchwork_20448_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_create@create-massive:
- shard-kbl: NOTRUN -> [DMESG-WARN][9] ([i915#3002])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-kbl2/igt@[email protected]
* igt@gem_ctx_persistence@engines-cleanup:
- shard-snb: NOTRUN -> [SKIP][10] ([fdo#109271] / [i915#1099]) +2 similar issues
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-snb2/igt@[email protected]
* igt@gem_exec_capture@pi@rcs0:
- shard-skl: [PASS][11] -> [INCOMPLETE][12] ([i915#2369])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-skl3/igt@gem_exec_capture@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-skl6/igt@gem_exec_capture@[email protected]
* igt@gem_exec_fair@basic-none-solo@rcs0:
- shard-kbl: NOTRUN -> [FAIL][13] ([i915#2842])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-kbl2/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-pace-share@rcs0:
- shard-tglb: [PASS][14] -> [FAIL][15] ([i915#2842]) +1 similar issue
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-tglb3/igt@gem_exec_fair@[email protected]
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-tglb5/igt@gem_exec_fair@[email protected]
- shard-glk: [PASS][16] -> [FAIL][17] ([i915#2842])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-glk9/igt@gem_exec_fair@[email protected]
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-glk7/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-pace@vecs0:
- shard-kbl: [PASS][18] -> [FAIL][19] ([i915#2842])
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-kbl4/igt@gem_exec_fair@[email protected]
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-kbl3/igt@gem_exec_fair@[email protected]
* igt@gem_exec_reloc@basic-wide-active@rcs0:
- shard-snb: NOTRUN -> [FAIL][20] ([i915#3633]) +2 similar issues
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-snb2/igt@gem_exec_reloc@[email protected]
* igt@gem_exec_whisper@basic-queues-forked-all:
- shard-glk: [PASS][21] -> [DMESG-WARN][22] ([i915#118] / [i915#95]) +2 similar issues
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-glk5/igt@[email protected]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-glk5/igt@[email protected]
* igt@gem_mmap_gtt@big-copy-xy:
- shard-glk: [PASS][23] -> [FAIL][24] ([i915#307])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-glk1/igt@[email protected]
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-glk1/igt@[email protected]
* igt@gem_mmap_gtt@cpuset-big-copy:
- shard-iclb: [PASS][25] -> [FAIL][26] ([i915#307])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-iclb1/igt@[email protected]
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-iclb5/igt@[email protected]
* igt@gem_mmap_gtt@cpuset-medium-copy-xy:
- shard-iclb: NOTRUN -> [FAIL][27] ([i915#307])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-iclb7/igt@[email protected]
* igt@gem_pread@exhaustion:
- shard-kbl: NOTRUN -> [WARN][28] ([i915#2658])
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-kbl6/igt@[email protected]
* igt@gem_pwrite@basic-exhaustion:
- shard-snb: NOTRUN -> [WARN][29] ([i915#2658])
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-snb2/igt@[email protected]
* igt@gem_userptr_blits@dmabuf-sync:
- shard-apl: NOTRUN -> [SKIP][30] ([fdo#109271] / [i915#3323])
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-apl3/igt@[email protected]
* igt@gem_userptr_blits@input-checking:
- shard-snb: NOTRUN -> [DMESG-WARN][31] ([i915#3002])
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-snb2/igt@[email protected]
* igt@gem_userptr_blits@vma-merge:
- shard-kbl: NOTRUN -> [FAIL][32] ([i915#3318])
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-kbl2/igt@[email protected]
* igt@gem_workarounds@suspend-resume:
- shard-skl: [PASS][33] -> [INCOMPLETE][34] ([i915#198])
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-skl4/igt@[email protected]
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-skl8/igt@[email protected]
* igt@gen9_exec_parse@allowed-all:
- shard-glk: [PASS][35] -> [DMESG-WARN][36] ([i915#1436] / [i915#716])
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-glk2/igt@[email protected]
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-glk6/igt@[email protected]
* igt@i915_module_load@reload-with-fault-injection:
- shard-skl: [PASS][37] -> [DMESG-WARN][38] ([i915#1982]) +1 similar issue
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-skl10/igt@[email protected]
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-skl3/igt@[email protected]
* igt@i915_pm_rc6_residency@rc6-fence:
- shard-iclb: NOTRUN -> [WARN][39] ([i915#1804] / [i915#2684])
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-iclb7/igt@[email protected]
* igt@kms_async_flips@alternate-sync-async-flip:
- shard-skl: [PASS][40] -> [FAIL][41] ([i915#2521])
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-skl10/igt@[email protected]
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-skl4/igt@[email protected]
* igt@kms_chamelium@dp-crc-fast:
- shard-iclb: NOTRUN -> [SKIP][42] ([fdo#109284] / [fdo#111827]) +1 similar issue
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-iclb7/igt@[email protected]
* igt@kms_color_chamelium@pipe-a-ctm-blue-to-red:
- shard-snb: NOTRUN -> [SKIP][43] ([fdo#109271] / [fdo#111827]) +16 similar issues
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-snb7/igt@[email protected]
* igt@kms_color_chamelium@pipe-a-ctm-green-to-red:
- shard-apl: NOTRUN -> [SKIP][44] ([fdo#109271] / [fdo#111827]) +7 similar issues
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-apl3/igt@[email protected]
* igt@kms_color_chamelium@pipe-b-ctm-0-25:
- shard-kbl: NOTRUN -> [SKIP][45] ([fdo#109271] / [fdo#111827]) +13 similar issues
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-kbl6/igt@[email protected]
* igt@kms_color_chamelium@pipe-c-degamma:
- shard-skl: NOTRUN -> [SKIP][46] ([fdo#109271] / [fdo#111827]) +1 similar issue
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-skl2/igt@[email protected]
* igt@kms_content_protection@atomic-dpms:
- shard-apl: NOTRUN -> [TIMEOUT][47] ([i915#1319])
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-apl2/igt@[email protected]
- shard-iclb: NOTRUN -> [SKIP][48] ([fdo#109300] / [fdo#111066])
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-iclb7/igt@[email protected]
* igt@kms_cursor_crc@pipe-a-cursor-suspend:
- shard-kbl: NOTRUN -> [DMESG-WARN][49] ([i915#180])
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-kbl3/igt@[email protected]
- shard-skl: [PASS][50] -> [INCOMPLETE][51] ([i915#146] / [i915#2828] / [i915#300])
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-skl5/igt@[email protected]
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-skl6/igt@[email protected]
* igt@kms_cursor_crc@pipe-b-cursor-512x170-sliding:
- shard-iclb: NOTRUN -> [SKIP][52] ([fdo#109278] / [fdo#109279])
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-iclb7/igt@[email protected]
* igt@kms_cursor_crc@pipe-c-cursor-suspend:
- shard-skl: [PASS][53] -> [INCOMPLETE][54] ([i915#300])
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-skl10/igt@[email protected]
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-skl4/igt@[email protected]
* igt@kms_cursor_edge_walk@pipe-d-128x128-right-edge:
- shard-snb: NOTRUN -> [SKIP][55] ([fdo#109271]) +283 similar issues
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-snb7/igt@[email protected]
* igt@kms_cursor_legacy@cursorb-vs-flipb-atomic-transitions-varying-size:
- shard-iclb: NOTRUN -> [SKIP][56] ([fdo#109274] / [fdo#109278]) +1 similar issue
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-iclb7/igt@kms_cursor_legacy@cursorb-vs-flipb-atomic-transitions-varying-size.html
* igt@kms_cursor_legacy@flip-vs-cursor-busy-crc-atomic:
- shard-apl: [PASS][57] -> [DMESG-WARN][58] ([IGT#6])
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-apl7/igt@[email protected]
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-apl2/igt@[email protected]
* igt@kms_cursor_legacy@pipe-d-torture-bo:
- shard-kbl: NOTRUN -> [SKIP][59] ([fdo#109271] / [i915#533]) +2 similar issues
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-kbl1/igt@[email protected]
* igt@kms_flip@flip-vs-expired-vblank@c-edp1:
- shard-skl: [PASS][60] -> [FAIL][61] ([i915#79])
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-skl5/igt@kms_flip@[email protected]
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-skl6/igt@kms_flip@[email protected]
* igt@kms_flip@plain-flip-ts-check@b-edp1:
- shard-skl: [PASS][62] -> [FAIL][63] ([i915#2122])
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-skl5/igt@kms_flip@[email protected]
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-skl6/igt@kms_flip@[email protected]
* igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytilercccs:
- shard-kbl: NOTRUN -> [SKIP][64] ([fdo#109271] / [i915#2672])
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-kbl2/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbcpsr-2p-shrfb-fliptrack-mmap-gtt:
- shard-iclb: NOTRUN -> [SKIP][65] ([fdo#109280]) +5 similar issues
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-iclb7/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbcpsr-farfromfence-mmap-gtt:
- shard-skl: NOTRUN -> [SKIP][66] ([fdo#109271]) +27 similar issues
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-skl6/igt@[email protected]
* igt@kms_frontbuffer_tracking@psr-2p-scndscrn-pri-shrfb-draw-mmap-cpu:
- shard-kbl: NOTRUN -> [SKIP][67] ([fdo#109271]) +108 similar issues
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-kbl6/igt@kms_frontbuffer_tracking@psr-2p-scndscrn-pri-shrfb-draw-mmap-cpu.html
* igt@kms_hdr@bpc-switch-dpms:
- shard-skl: [PASS][68] -> [FAIL][69] ([i915#1188]) +1 similar issue
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-skl7/igt@[email protected]
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-skl2/igt@[email protected]
* igt@kms_hdr@bpc-switch-suspend:
- shard-kbl: [PASS][70] -> [DMESG-WARN][71] ([i915#180]) +4 similar issues
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-kbl7/igt@[email protected]
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-kbl4/igt@[email protected]
* igt@kms_invalid_dotclock:
- shard-iclb: NOTRUN -> [SKIP][72] ([fdo#109310])
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-iclb7/igt@kms_invalid_dotclock.html
* igt@kms_plane_alpha_blend@pipe-b-alpha-opaque-fb:
- shard-kbl: NOTRUN -> [FAIL][73] ([fdo#108145] / [i915#265]) +1 similar issue
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-kbl1/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-b-coverage-7efc:
- shard-skl: [PASS][74] -> [FAIL][75] ([fdo#108145] / [i915#265])
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-skl7/igt@[email protected]
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-skl4/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-c-alpha-7efc:
- shard-apl: NOTRUN -> [FAIL][76] ([fdo#108145] / [i915#265])
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-apl3/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-c-constant-alpha-max:
- shard-skl: NOTRUN -> [FAIL][77] ([fdo#108145] / [i915#265])
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-skl7/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-d-coverage-vs-premult-vs-constant:
- shard-iclb: NOTRUN -> [SKIP][78] ([fdo#109278]) +3 similar issues
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-iclb7/igt@kms_plane_alpha_blend@pipe-d-coverage-vs-premult-vs-constant.html
* igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-3:
- shard-kbl: NOTRUN -> [SKIP][79] ([fdo#109271] / [i915#658]) +5 similar issues
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-kbl2/igt@[email protected]
* igt@perf@polling-parameterized:
- shard-skl: [PASS][80] -> [FAIL][81] ([i915#1542])
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-skl2/igt@[email protected]
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-skl1/igt@[email protected]
* igt@perf_pmu@event-wait@rcs0:
- shard-apl: NOTRUN -> [SKIP][82] ([fdo#109271]) +49 similar issues
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-apl3/igt@perf_pmu@[email protected]
* igt@sysfs_clients@sema-10:
- shard-kbl: NOTRUN -> [SKIP][83] ([fdo#109271] / [i915#2994])
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-kbl2/igt@[email protected]
#### Possible fixes ####
* igt@gem_eio@unwedge-stress:
- shard-iclb: [TIMEOUT][84] ([i915#2369] / [i915#2481] / [i915#3070]) -> [PASS][85]
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-iclb2/igt@[email protected]
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-iclb5/igt@[email protected]
* igt@gem_exec_fair@basic-none@vcs0:
- shard-kbl: [FAIL][86] ([i915#2842]) -> [PASS][87] +1 similar issue
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-kbl3/igt@gem_exec_fair@[email protected]
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-kbl3/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-pace@rcs0:
- shard-kbl: [SKIP][88] ([fdo#109271]) -> [PASS][89]
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-kbl4/igt@gem_exec_fair@[email protected]
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-kbl3/igt@gem_exec_fair@[email protected]
* igt@gem_mmap_gtt@big-copy-odd:
- shard-glk: [FAIL][90] ([i915#307]) -> [PASS][91]
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-glk1/igt@[email protected]
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-glk2/igt@[email protected]
* igt@gem_softpin@noreloc-s3:
- shard-apl: [DMESG-WARN][92] ([i915#180]) -> [PASS][93] +1 similar issue
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-apl7/igt@[email protected]
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-apl2/igt@[email protected]
* igt@kms_atomic_transition@plane-toggle-modeset-transition:
- shard-snb: [SKIP][94] ([fdo#109271]) -> [PASS][95] +1 similar issue
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-snb2/igt@[email protected]
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-snb6/igt@[email protected]
* igt@kms_big_fb@linear-32bpp-rotate-180:
- shard-glk: [DMESG-WARN][96] ([i915#118] / [i915#95]) -> [PASS][97] +1 similar issue
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-glk4/igt@[email protected]
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-glk4/igt@[email protected]
* igt@kms_color@pipe-b-ctm-blue-to-red:
- shard-skl: [DMESG-WARN][98] ([i915#1982]) -> [PASS][99]
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-skl7/igt@[email protected]
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-skl4/igt@[email protected]
* igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size:
- shard-skl: [FAIL][100] ([i915#2346] / [i915#533]) -> [PASS][101]
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-skl7/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-skl3/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html
* igt@kms_flip@flip-vs-suspend-interruptible@a-dp1:
- shard-kbl: [DMESG-WARN][102] ([i915#180]) -> [PASS][103] +12 similar issues
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-kbl3/igt@kms_flip@[email protected]
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-kbl2/igt@kms_flip@[email protected]
* igt@kms_flip@flip-vs-suspend@c-edp1:
- shard-skl: [INCOMPLETE][104] ([i915#198] / [i915#1982]) -> [PASS][105]
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-skl7/igt@kms_flip@[email protected]
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-skl2/igt@kms_flip@[email protected]
* igt@kms_flip@plain-flip-ts-check-interruptible@c-edp1:
- shard-skl: [FAIL][106] ([i915#2122]) -> [PASS][107] +1 similar issue
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-skl2/igt@kms_flip@[email protected]
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-skl1/igt@kms_flip@[email protected]
* igt@kms_hdr@bpc-switch:
- shard-skl: [FAIL][108] ([i915#1188]) -> [PASS][109]
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-skl3/igt@[email protected]
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-skl6/igt@[email protected]
* igt@kms_pipe_crc_basic@suspend-read-crc-pipe-b:
- shard-skl: [INCOMPLETE][110] ([i915#198]) -> [PASS][111]
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-skl1/igt@[email protected]
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-skl7/igt@[email protected]
* igt@kms_psr@psr2_cursor_mmap_gtt:
- shard-iclb: [SKIP][112] ([fdo#109441]) -> [PASS][113]
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-iclb1/igt@kms_psr@psr2_cursor_mmap_gtt.html
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-iclb2/igt@kms_psr@psr2_cursor_mmap_gtt.html
#### Warnings ####
* igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-1:
- shard-iclb: [SKIP][114] ([i915#2920]) -> [SKIP][115] ([i915#658]) +1 similar issue
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-iclb2/igt@[email protected]
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-iclb5/igt@[email protected]
* igt@runner@aborted:
- shard-kbl: ([FAIL][116], [FAIL][117], [FAIL][118], [FAIL][119], [FAIL][120], [FAIL][121], [FAIL][122], [FAIL][123], [FAIL][124], [FAIL][125], [FAIL][126], [FAIL][127], [FAIL][128], [FAIL][129]) ([fdo#109271] / [i915#1436] / [i915#180] / [i915#1814] / [i915#2505] / [i915#3002] / [i915#3363] / [i915#602]) -> ([FAIL][130], [FAIL][131], [FAIL][132], [FAIL][133], [FAIL][134], [FAIL][135], [FAIL][136], [FAIL][137], [FAIL][138], [FAIL][139], [FAIL][140]) ([fdo#109271] / [i915#1436] / [i915#180] / [i915#1814] / [i915#2505] / [i915#3002] / [i915#3363])
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-kbl4/igt@[email protected]
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-kbl6/igt@[email protected]
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-kbl4/igt@[email protected]
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-kbl7/igt@[email protected]
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-kbl4/igt@[email protected]
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-kbl7/igt@[email protected]
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-kbl7/igt@[email protected]
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-kbl7/igt@[email protected]
[124]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-kbl4/igt@[email protected]
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-kbl3/igt@[email protected]
[126]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-kbl1/igt@[email protected]
[127]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-kbl1/igt@[email protected]
[128]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-kbl1/igt@[email protected]
[129]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-kbl1/igt@[email protected]
[130]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-kbl4/igt@[email protected]
[131]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-kbl6/igt@[email protected]
[132]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-kbl7/igt@[email protected]
[133]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-kbl4/igt@[email protected]
[134]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-kbl3/igt@[email protected]
[135]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-kbl7/igt@[email protected]
[136]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-kbl6/igt@[email protected]
[137]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-kbl4/igt@[email protected]
[138]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-kbl7/igt@[email protected]
[139]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-kbl1/igt@[email protected]
[140]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-kbl2/igt@[email protected]
- shard-iclb: ([FAIL][141], [FAIL][142], [FAIL][143]) ([i915#1814] / [i915#3002]) -> ([FAIL][144], [FAIL][145]) ([i915#3002])
[141]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-iclb3/igt@[email protected]
[142]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-iclb1/igt@[email protected]
[143]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-iclb8/igt@[email protected]
[144]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-iclb4/igt@[email protected]
[145]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-iclb2/igt@[email protected]
- shard-apl: ([FAIL][146], [FAIL][147], [FAIL][148]) ([i915#180] / [i915#3002] / [i915#3363]) -> [FAIL][149] ([i915#3002] / [i915#3363])
[146]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-apl7/igt@[email protected]
[147]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-apl8/igt@[email protected]
[148]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10271/shard-apl7/igt@[email protected]
[149]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/shard-apl7/igt@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[IGT#6]: https://gitlab.freedesktop.org/drm/igt-gpu-tools/issues/6
[fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109274]: https://bugs.freedesktop.org/show_bug.cgi?id=109274
[fdo#109278]: https://bugs.freedesktop.org/show_bug.cgi?id=109278
[fdo#109279]: https://bugs.freedesktop.org/show_bug.cgi?id=109279
[fdo#109280]: https://bugs.freedesktop.org/show_bug.cgi?id=109280
[fdo#109284]: https://bugs.freedesktop.org/show_bug.cgi?id=109284
[fdo#109300]: https://bugs.freedesktop.org/show_bug.cgi?id=109300
[fdo#109310]: https://bugs.freedesktop.org/show_bug.cgi?id=109310
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#111066]: https://bugs.freedesktop.org/show_bug.cgi?id=111066
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1099]: https://gitlab.freedesktop.org/drm/intel/issues/1099
[i915#118]: https://gitlab.freedesktop.org/drm/intel/issues/118
[i915#1188]: https://gitlab.freedesktop.org/drm/intel/issues/1188
[i915#1319]: https://gitlab.freedesktop.org/drm/intel/issues/1319
[i915#1436]: https://gitlab.freedesktop.org/drm/intel/issues/1436
[i915#146]: https://gitlab.freedesktop.org/drm/intel/issues/146
[i915#1542]: https://gitlab.freedesktop.org/drm/intel/issues/1542
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/18
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20448/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx