Disable connector polling for a headless sku
Subsystems (3)
cover Disable connector polling for a headless sku
This patch set disables connector polling when entering runtime suspend for headless sku to prevent waking it up again when poll is performed.
Jouni Högander (2):
drm/i915/opregion: add function to check if headless sku drm/i915: do not start connector polling when headless sku
drivers/gpu/drm/i915/display/intel_hotplug.c | 3 ++- drivers/gpu/drm/i915/display/intel_opregion.c | 12 ++++++++++++ drivers/gpu/drm/i915/display/intel_opregion.h | 7 +++++++ 3 files changed, 21 insertions(+), 1 deletion(-)
Signature · 1 line
2.25.1
PATCH 1/2 drm/i915/opregion: add function to check if headless sku
Export headless sku bit (bit 13) from opregion->header->pcon as an interface to check if our device is headless configuration.
Bspec: 53441
--- drivers/gpu/drm/i915/display/intel_opregion.c | 12 ++++++++++++ drivers/gpu/drm/i915/display/intel_opregion.h | 7 +++++++ 2 files changed, 19 insertions(+)
drivers/gpu/drm/i915/display/intel_opregion.c +12 -0
@@ -53,6 +53,8 @@#define MBOX_ASLE_EXT BIT(4)/* Mailbox #5 */ #define MBOX_BACKLIGHT BIT(5)/* Mailbox #2 (valid from v3.x) */ +#define PCON_HEADLESS_SKU BIT(13) +struct opregion_header {u8 signature[16 ];u32 size;
@@ -1135,6 +1137,16 @@ struct edid *intel_opregion_get_edid(struct intel_connector *intel_connector)return new_edid; } +bool intel_opregion_headless_sku (struct drm_i915_private *i915) +{ +struct intel_opregion *opregion = &i915->opregion; + +if (!opregion->header) +return false; + +return opregion->header->pcon &PCON_HEADLESS_SKU ; +} +void intel_opregion_register (struct drm_i915_private *i915) {struct intel_opregion *opregion = &i915->opregion;
drivers/gpu/drm/i915/display/intel_opregion.h +7 -0
@@ -76,6 +76,8 @@ int intel_opregion_notify_adapter(struct drm_i915_private *dev_priv,int intel_opregion_get_panel_type (struct drm_i915_private *dev_priv);struct edid *intel_opregion_get_edid (struct intel_connector *connector); +bool intel_opregion_headless_sku (struct drm_i915_private *i915); +#else /* CONFIG_ACPI*/ static inline int intel_opregion_setup (struct drm_i915_private *dev_priv)
@@ -127,6 +129,11 @@ intel_opregion_get_edid(struct intel_connector *connector)return NULL ; } +bool intel_opregion_headless_sku (struct drm_i915_private *i915) +{ +return false; +} +#endif /* CONFIG_ACPI */ #endif
Signature · 1 line
2.25.1
Jani Nikula
maintainerRe: [Intel-gfx] [PATCH 1/2] drm/i915/opregion: add function to check if headless sku
Quoted 15 lines · Jouni Högander
Export headless sku bit (bit 13) from
opregion->header->pconas an interface to check if our device is headless configuration.Bspec: 53441
Signed-off-by Jouni Högander <[email protected]>--- drivers/gpu/drm/i915/display/intel_opregion.c | 12 ++++++++++++ drivers/gpu/drm/i915/display/intel_opregion.h | 7 +++++++ 2 files changed, 19 insertions(+)drivers/gpu/drm/i915/display/intel_opregion.c +0
-0
drivers/gpu/drm/i915/display/intel_opregion.c line 56
Quoted 4 lines
drivers/gpu/drm/i915/display/intel_opregion.c +1
-0@@ -53,6 +53,8 @@#define MBOX_ASLE_EXT BIT(4)/* Mailbox #5 */ #define MBOX_BACKLIGHT BIT(5)/* Mailbox #2 (valid from v3.x) */ +#define PCON_HEADLESS_SKU BIT(13)
Here we go again.
What does headless mean here? The spec does not say. Does it have display hardware? Apparently yes, since otherwise we wouldn't be here.
We have INTEL_DISPLAY_ENABLED() which should do the right thing when you do have display hardware and have done output setup etc. but want to force them disconnected, i.e. you take the hardware over properly, but put it to sleep for power savings.
Maybe we should bolt this opregion check in that macro?
Maybe we need to use INTEL_DISPLAY_ENABLED() also to prevent polling.
I certainly would not want to add another mode that's separate from HAS_DISPLAY() and INTEL_DISPLAY_ENABLED().
Quoted 6 lines
drivers/gpu/drm/i915/display/intel_opregion.c +1
-0+struct opregion_header {u8 signature[16 ];u32 size;@@ -1135,6 +1137,16 @@ struct edid *intel_opregion_get_edid(struct intel_connector *intel_connector)return new_edid;
drivers/gpu/drm/i915/display/intel_opregion.c struct edid *intel_opregion_get_edid(struct intel_connector *intel_connector) · line 1147
Quoted 10 lines
drivers/gpu/drm/i915/display/intel_opregion.c +8
-0} +bool intel_opregion_headless_sku (struct drm_i915_private *i915) +{ +struct intel_opregion *opregion = &i915->opregion; + +if (!opregion->header) +return false; + +return opregion->header->pcon &PCON_HEADLESS_SKU ;
We should probably start checking for opregion version for this stuff too.
BR,
Jani.
Quoted 30 lines
drivers/gpu/drm/i915/display/intel_opregion.c +2
-0+} +void intel_opregion_register (struct drm_i915_private *i915) {struct intel_opregion *opregion = &i915->opregion;drivers/gpu/drm/i915/display/intel_opregion.h +7
-0@@ -76,6 +76,8 @@ int intel_opregion_notify_adapter(struct drm_i915_private *dev_priv,int intel_opregion_get_panel_type (struct drm_i915_private *dev_priv);struct edid *intel_opregion_get_edid (struct intel_connector *connector); +bool intel_opregion_headless_sku (struct drm_i915_private *i915); +#else /* CONFIG_ACPI*/ static inline int intel_opregion_setup (struct drm_i915_private *dev_priv)@@ -127,6 +129,11 @@ intel_opregion_get_edid(struct intel_connector *connector)return NULL ; } +bool intel_opregion_headless_sku (struct drm_i915_private *i915) +{ +return false; +} +#endif /* CONFIG_ACPI */ #endif
Signature · 1 line
Jani Nikula, Intel Open Source Graphics Center
Re: [Intel-gfx] [PATCH 1/2] drm/i915/opregion: add function to check if headless sku
Quoted 21 lines · Jani Nikula
Quoted 20 lines · Jouni Högander
Export headless sku bit (bit 13) from
opregion->header->pconas an interface to check if our device is headless configuration.Bspec: 53441
Signed-off-by Jouni Högander <[email protected]>--- drivers/gpu/drm/i915/display/intel_opregion.c | 12 ++++++++++++ drivers/gpu/drm/i915/display/intel_opregion.h | 7 +++++++ 2 files changed, 19 insertions(+)drivers/gpu/drm/i915/display/intel_opregion.c +0
-0@@ -53,6 +53,8 @@#define MBOX_ASLE_EXT BIT(4)/* Mailbox #5 */ #define MBOX_BACKLIGHT BIT(5)/* Mailbox #2 (valid from v3.x) */
Quoted 7 lines
Quoted 1 line
+#define
PCON_HEADLESS_SKUBIT(13)Here we go again.
What does headless mean here? The spec does not say. Does it have display hardware? Apparently yes, since otherwise we wouldn't be here.
This is for hybrid setup with several display hw and the panel wont be connected into device driven by i915 driver.
Quoted 10 lines
We have
INTEL_DISPLAY_ENABLED()which should do the right thing when you
do have display hardware and have done output setup etc. but want to force them disconnected, i.e. you take the hardware over properly, but
put it to sleep for power savings.Maybe we should bolt this opregion check in that macro?
Maybe we need to use
INTEL_DISPLAY_ENABLED()also to prevent polling.
Thank you for pointing this out. HAS_DISPLAY I already notice and it's not suitable for what we want here. I think bolting this check into INTEL_DISPLAY_ENABLED as you suggested is enough. That will prevent waking up the hw into D0 state for polling.
Quoted 3 lines
I certainly would not want to add another mode that's separate from
HAS_DISPLAY()andINTEL_DISPLAY_ENABLED().
No need for this. I think we can go with INTEL_DISPLAY_ENABLED.
Quoted 10 lines
Quoted 10 lines
drivers/gpu/drm/i915/display/intel_opregion.c +1
-0+struct opregion_header {u8 signature[16 ];u32 size;@@ -1135,6 +1137,16 @@ struct edid *intel_opregion_get_edid(struct intel_connector *intel_connector)return new_edid; }
Quoted 12 lines
drivers/gpu/drm/i915/display/intel_opregion.c struct edid *intel_opregion_get_edid(struct intel_connector *intel_connector) · line 1147
Quoted 8 lines
drivers/gpu/drm/i915/display/intel_opregion.c +8
-0+bool intel_opregion_headless_sku (struct drm_i915_private *i915) +{ +struct intel_opregion *opregion = &i915->opregion; + +if (!opregion->header) +return false; + +return opregion->header->pcon &PCON_HEADLESS_SKU ;We should probably start checking for opregion version for this stuff too.
Yes, I will do this change.
Quoted 40 lines
BR,
Jani.Quoted 36 lines
drivers/gpu/drm/i915/display/intel_opregion.c +2
-0+} +void intel_opregion_register (struct drm_i915_private *i915) {drivers/gpu/drm/i915/display/intel_opregion.c +0
-0struct intel_opregion *opregion = &i915->opregion;drivers/gpu/drm/i915/display/intel_opregion.h +2
-0@@ -76,6 +76,8 @@ int intel_opregion_notify_adapter(structdrm_i915_private *dev_priv, int intel_opregion_get_panel_type(struct drm_i915_private *dev_priv);struct edid *intel_opregion_get_edid (struct intel_connector *connector); +bool intel_opregion_headless_sku (struct drm_i915_private *i915); +#else /* CONFIG_ACPI*/
static inline int intel_opregion_setup(struct
drm_i915_private*dev_priv)drivers/gpu/drm/i915/display/intel_opregion.h +5
-0@@ -127,6 +129,11 @@ intel_opregion_get_edid(struct intel_connector *connector) return NULL; } +bool intel_opregion_headless_sku (struct drm_i915_private *i915) +{ +return false; +} +#endif /* CONFIG_ACPI */ #endif
Re: [Intel-gfx] [PATCH 1/2] drm/i915/opregion: add function to check if headless sku
Quoted 40 lines · Jouni
Quoted 21 lines · Jani Nikula
Quoted 20 lines · Jouni Högander
Export headless sku bit (bit 13) from
opregion->header->pconas an interface to check if our device is headless configuration.Bspec: 53441
Signed-off-by Jouni Högander <[email protected]>--- drivers/gpu/drm/i915/display/intel_opregion.c | 12 ++++++++++++ drivers/gpu/drm/i915/display/intel_opregion.h | 7 +++++++ 2 files changed, 19 insertions(+)drivers/gpu/drm/i915/display/intel_opregion.c +0
-0@@ -53,6 +53,8 @@#define MBOX_ASLE_EXT BIT(4)/* Mailbox #5 */ #define MBOX_BACKLIGHT BIT(5)/* Mailbox #2 (valid from v3.x) */
Quoted 7 lines
Quoted 1 line
+#define
PCON_HEADLESS_SKUBIT(13)Here we go again.
What does headless mean here? The spec does not say. Does it have display hardware? Apparently yes, since otherwise we wouldn't be here.
This is for hybrid setup with several display hw and the panel wont be connected into device driven by i915 driver.
Quoted 7 lines
We have
INTEL_DISPLAY_ENABLED()which should do the right thing when you
do have display hardware and have done output setup etc. but want to force them disconnected, i.e. you take the hardware over properly, but
put it to sleep for power savings.
Quoted 8 lines
Quoted 3 lines
Maybe we should bolt this opregion check in that macro?
Maybe we need to use
INTEL_DISPLAY_ENABLED()also to prevent polling.Thank you for pointing this out.
HAS_DISPLAYI already notice and it's not suitable for what we want here. I think bolting this check intoINTEL_DISPLAY_ENABLEDas you suggested is enough. That will prevent waking up the hw into D0 state for polling.
A headless sku should not have any DDI ports enabled, much easier check for that.
Quoted 72 lines
Quoted 4 lines
I certainly would not want to add another mode that's separate from
HAS_DISPLAY()andINTEL_DISPLAY_ENABLED().No need for this. I think we can go with
INTEL_DISPLAY_ENABLED.Quoted 10 lines
Quoted 10 lines
drivers/gpu/drm/i915/display/intel_opregion.c +1
-0+struct opregion_header {u8 signature[16 ];u32 size;@@ -1135,6 +1137,16 @@ struct edid *intel_opregion_get_edid(struct intel_connector *intel_connector)return new_edid; }Quoted 12 lines
drivers/gpu/drm/i915/display/intel_opregion.c struct edid *intel_opregion_get_edid(struct intel_connector *intel_connector) · line 1147
Quoted 8 lines
drivers/gpu/drm/i915/display/intel_opregion.c +8
-0+bool intel_opregion_headless_sku (struct drm_i915_private *i915) +{ +struct intel_opregion *opregion = &i915->opregion; + +if (!opregion->header) +return false; + +return opregion->header->pcon &PCON_HEADLESS_SKU ;We should probably start checking for opregion version for this stuff too.
Yes, I will do this change.
Quoted 40 lines
BR,
Jani.Quoted 36 lines
drivers/gpu/drm/i915/display/intel_opregion.c +2
-0+} +void intel_opregion_register (struct drm_i915_private *i915) {drivers/gpu/drm/i915/display/intel_opregion.c +0
-0struct intel_opregion *opregion = &i915->opregion;drivers/gpu/drm/i915/display/intel_opregion.h +2
-0@@ -76,6 +76,8 @@ int intel_opregion_notify_adapter(structdrm_i915_private *dev_priv, int intel_opregion_get_panel_type(struct drm_i915_private *dev_priv);struct edid *intel_opregion_get_edid (struct intel_connector *connector); +bool intel_opregion_headless_sku (struct drm_i915_private *i915); +#else /* CONFIG_ACPI*/
static inline int intel_opregion_setup(struct
drm_i915_private*dev_priv)drivers/gpu/drm/i915/display/intel_opregion.h +5
-0@@ -127,6 +129,11 @@ intel_opregion_get_edid(struct intel_connector *connector) return NULL; } +bool intel_opregion_headless_sku (struct drm_i915_private *i915) +{ +return false; +} +#endif /* CONFIG_ACPI */ #endif
Re: [Intel-gfx] [PATCH 1/2] drm/i915/opregion: add function to check if headless sku
Quoted 53 lines · Jose
Quoted 52 lines · Jouni
Quoted 24 lines · Jani Nikula
Quoted 22 lines · Jouni Högander
Export headless sku bit (bit 13) from
opregion->header->pconas an
interface to check if our device is headless configuration.Bspec: 53441
Signed-off-by Jouni Högander <[email protected]>--- drivers/gpu/drm/i915/display/intel_opregion.c | 12 ++++++++++++ drivers/gpu/drm/i915/display/intel_opregion.h | 7 +++++++ 2 files changed, 19 insertions(+)drivers/gpu/drm/i915/display/intel_opregion.c +0
-0@@ -53,6 +53,8 @@ #define MBOX_ASLE_EXTBIT(4)/* Mailbox #5 */ #define MBOX_BACKLIGHTBIT(5)/* Mailbox #2(valid from v3.x) */
Quoted 7 lines
Quoted 1 line
+#define
PCON_HEADLESS_SKUBIT(13)Here we go again.
What does headless mean here? The spec does not say. Does it have display hardware? Apparently yes, since otherwise we wouldn't be here.
This is for hybrid setup with several display hw and the panel wont be
connected into device driven by i915 driver.Quoted 14 lines
We have
INTEL_DISPLAY_ENABLED()which should do the right thing when
you
do have display hardware and have done output setup etc. but want to
force them disconnected, i.e. you take the hardware over properly,
but
put it to sleep for power savings.Maybe we should bolt this opregion check in that macro?
Maybe we need to use
INTEL_DISPLAY_ENABLED()also to prevent polling.
Quoted 8 lines
Quoted 5 lines
Thank you for pointing this out.
HAS_DISPLAYI already notice and it's
not suitable for what we want here. I think bolting this check intoINTEL_DISPLAY_ENABLEDas you suggested is enough. That will prevent waking up the hw into D0 state for polling.A headless sku should not have any DDI ports enabled, much easier check for that.
Could you please clarify this a bit? What exactly you are thinking should be checked? Aren't DDI port also disabled when non-headless setup is in runtime suspend?
Quoted 75 lines
Quoted 75 lines
Quoted 4 lines
I certainly would not want to add another mode that's separate from
HAS_DISPLAY()andINTEL_DISPLAY_ENABLED().No need for this. I think we can go with
INTEL_DISPLAY_ENABLED.Quoted 10 lines
Quoted 10 lines
drivers/gpu/drm/i915/display/intel_opregion.c +1
-0+struct opregion_header {u8 signature[16 ];u32 size;@@ -1135,6 +1137,16 @@ struct edid *intel_opregion_get_edid(struct intel_connector *intel_connector)return new_edid; }Quoted 14 lines
drivers/gpu/drm/i915/display/intel_opregion.c struct edid *intel_opregion_get_edid(struct intel_connector *intel_connector) · line 1147
Quoted 9 lines
drivers/gpu/drm/i915/display/intel_opregion.c +8
-0+bool intel_opregion_headless_sku (struct drm_i915_private *i915) +{ +struct intel_opregion *opregion = &i915->opregion; + +if (!opregion->header) +return false; + +return opregion->header->pcon &PCON_HEADLESS_SKU ;We should probably start checking for opregion version for this stuff
too.Yes, I will do this change.
Quoted 42 lines
BR,
Jani.Quoted 39 lines
drivers/gpu/drm/i915/display/intel_opregion.c +2
-0+} +void
intel_opregion_register(struct drm_i915_private *i915){
structintel_opregion*opregion =&i915->opregion;drivers/gpu/drm/i915/display/intel_opregion.h +1
-0@@ -76,6 +76,8 @@ int intel_opregion_notify_adapter(structdrm_i915_private *dev_priv, int intel_opregion_get_panel_type(struct drm_i915_private *dev_priv);struct edid *intel_opregion_get_edid (struct intel_connector *connector); +bool intel_opregion_headless_sku(struct drm_i915_private*i915);
+
#else /* CONFIG_ACPI*/static inline int intel_opregion_setup(struct
drm_i915_private*dev_priv)drivers/gpu/drm/i915/display/intel_opregion.h +0
-0@@ -127,6 +129,11 @@ intel_opregion_get_edid(struct
intel_connector
*connector)
return NULL;
}+bool
intel_opregion_headless_sku(struct drm_i915_private *i915)drivers/gpu/drm/i915/display/intel_opregion.h +4
-0+{ +return false; +} +#endif /* CONFIG_ACPI */ #endif
Jani Nikula
maintainerRe: [Intel-gfx] [PATCH 1/2] drm/i915/opregion: add function to check if headless sku
Quoted 60 lines · Jouni
Quoted 59 lines · Jose
Quoted 57 lines · Jouni
Quoted 24 lines · Jani Nikula
Quoted 22 lines · Jouni Högander
Export headless sku bit (bit 13) from
opregion->header->pconas an
interface to check if our device is headless configuration.Bspec: 53441
Signed-off-by Jouni Högander <[email protected]>--- drivers/gpu/drm/i915/display/intel_opregion.c | 12 ++++++++++++ drivers/gpu/drm/i915/display/intel_opregion.h | 7 +++++++ 2 files changed, 19 insertions(+)drivers/gpu/drm/i915/display/intel_opregion.c +0
-0@@ -53,6 +53,8 @@ #define MBOX_ASLE_EXTBIT(4)/* Mailbox #5 */ #define MBOX_BACKLIGHTBIT(5)/* Mailbox #2(valid from v3.x) */
Quoted 7 lines
Quoted 1 line
+#define
PCON_HEADLESS_SKUBIT(13)Here we go again.
What does headless mean here? The spec does not say. Does it have display hardware? Apparently yes, since otherwise we wouldn't be here.
This is for hybrid setup with several display hw and the panel wont be
connected into device driven by i915 driver.Quoted 10 lines
We have
INTEL_DISPLAY_ENABLED()which should do the right thing when
you
do have display hardware and have done output setup etc. but want to
force them disconnected, i.e. you take the hardware over properly,
but
put it to sleep for power savings.Quoted 4 lines
Maybe we should bolt this opregion check in that macro?
Maybe we need to use
INTEL_DISPLAY_ENABLED()also to prevent polling.Thank you for pointing this out.
HAS_DISPLAYI already notice and it's
not suitable for what we want here. I think bolting this check intoINTEL_DISPLAY_ENABLEDas you suggested is enough. That will prevent waking up the hw into D0 state for polling.
Quoted 6 lines
Quoted 2 lines
A headless sku should not have any DDI ports enabled, much easier check for that.
Could you please clarify this a bit? What exactly you are thinking should be checked? Aren't DDI port also disabled when non-headless setup is in runtime suspend?
I also think "headless" and "DDI ports enabled" need clarification. They are overloaded terms.
Seems to me the use case here could be the same as INTEL_DISPLAY_ENABLED(), and that could benefit from polling disable.
BR,
Jani.
Quoted 77 lines
Quoted 76 lines
Quoted 76 lines
Quoted 5 lines
I certainly would not want to add another mode that's separate from
HAS_DISPLAY()andINTEL_DISPLAY_ENABLED().No need for this. I think we can go with
INTEL_DISPLAY_ENABLED.Quoted 10 lines
Quoted 10 lines
drivers/gpu/drm/i915/display/intel_opregion.c +1
-0+struct opregion_header {u8 signature[16 ];u32 size;@@ -1135,6 +1137,16 @@ struct edid *intel_opregion_get_edid(struct intel_connector *intel_connector)return new_edid; }Quoted 14 lines
drivers/gpu/drm/i915/display/intel_opregion.c struct edid *intel_opregion_get_edid(struct intel_connector *intel_connector) · line 1147
Quoted 9 lines
drivers/gpu/drm/i915/display/intel_opregion.c +8
-0+bool intel_opregion_headless_sku (struct drm_i915_private *i915) +{ +struct intel_opregion *opregion = &i915->opregion; + +if (!opregion->header) +return false; + +return opregion->header->pcon &PCON_HEADLESS_SKU ;We should probably start checking for opregion version for this stuff
too.Yes, I will do this change.
Quoted 42 lines
BR,
Jani.Quoted 39 lines
drivers/gpu/drm/i915/display/intel_opregion.c +2
-0+} +void
intel_opregion_register(struct drm_i915_private *i915){
structintel_opregion*opregion =&i915->opregion;drivers/gpu/drm/i915/display/intel_opregion.h +1
-0@@ -76,6 +76,8 @@ int intel_opregion_notify_adapter(structdrm_i915_private *dev_priv, int intel_opregion_get_panel_type(struct drm_i915_private *dev_priv);struct edid *intel_opregion_get_edid (struct intel_connector *connector); +bool intel_opregion_headless_sku(struct drm_i915_private*i915);
+
#else /* CONFIG_ACPI*/static inline int intel_opregion_setup(struct
drm_i915_private*dev_priv)drivers/gpu/drm/i915/display/intel_opregion.h +0
-0@@ -127,6 +129,11 @@ intel_opregion_get_edid(struct
intel_connector
*connector)
return NULL;
}+bool
intel_opregion_headless_sku(struct drm_i915_private *i915)drivers/gpu/drm/i915/display/intel_opregion.h +4
-0+{ +return false; +} +#endif /* CONFIG_ACPI */ #endif
Signature · 1 line
Jani Nikula, Intel Open Source Graphics Center
Re: [Intel-gfx] [PATCH 1/2] drm/i915/opregion: add function to check if headless sku
Quoted 64 lines · Jani Nikula
Quoted 63 lines · Jouni
Quoted 61 lines · Jose
Quoted 49 lines · Jouni
Quoted 24 lines · Jani Nikula
Quoted 22 lines · Jouni Högander
Export headless sku bit (bit 13) from
opregion->header->pconas an
interface to check if our device is headless configuration.Bspec: 53441
Signed-off-by Jouni Högander <[email protected]>--- drivers/gpu/drm/i915/display/intel_opregion.c | 12 ++++++++++++ drivers/gpu/drm/i915/display/intel_opregion.h | 7 +++++++ 2 files changed, 19 insertions(+)drivers/gpu/drm/i915/display/intel_opregion.c +0
-0@@ -53,6 +53,8 @@ #define MBOX_ASLE_EXTBIT(4)/* Mailbox #5 */ #define MBOX_BACKLIGHTBIT(5)/* Mailbox #2(valid from v3.x) */
Quoted 7 lines
Quoted 1 line
+#define
PCON_HEADLESS_SKUBIT(13)Here we go again.
What does headless mean here? The spec does not say. Does it have display hardware? Apparently yes, since otherwise we wouldn't be here.
This is for hybrid setup with several display hw and the panel wont be
connected into device driven by i915 driver.Quoted 12 lines
We have
INTEL_DISPLAY_ENABLED()which should do the right thing when
you
do have display hardware and have done output setup etc. but want to
force them disconnected, i.e. you take the hardware over properly,
but
put it to sleep for power savings.Maybe we should bolt this opregion check in that macro?
Quoted 8 lines
Quoted 2 lines
Maybe we need to use
INTEL_DISPLAY_ENABLED()also to prevent polling.Thank you for pointing this out.
HAS_DISPLAYI already notice and it's
not suitable for what we want here. I think bolting this check intoINTEL_DISPLAY_ENABLEDas you suggested is enough. That will prevent waking up the hw into D0 state for polling.A headless sku should not have any DDI ports enabled, much easier check for that.
Quoted 6 lines
Quoted 3 lines
Could you please clarify this a bit? What exactly you are thinking should be checked? Aren't DDI port also disabled when non-headless setup is in runtime suspend?
I also think "headless" and "DDI ports enabled" need clarification. They are overloaded terms.
In a properly setup headless sku, VBT should have all ports marked as disabled.
intel_ddi_init() {
...
if (!init_dp && !init_hdmi) {
drm_dbg_kms(&dev_priv->drm,
"VBT says port %c is not DVI/HDMI/DP compatible, respect it\n",
port_name(port));
return;
}All DDI should return earlier in the above.
So you can use the number of enabled connectors to know if it is a headless sku or not.
So you can skip the pooling in case there is no connectors.
Quoted 86 lines
Seems to me the use case here could be the same as
INTEL_DISPLAY_ENABLED(), and that could benefit from polling disable.BR,
Jani.Quoted 77 lines
Quoted 76 lines
Quoted 76 lines
Quoted 5 lines
I certainly would not want to add another mode that's separate from
HAS_DISPLAY()andINTEL_DISPLAY_ENABLED().No need for this. I think we can go with
INTEL_DISPLAY_ENABLED.Quoted 10 lines
Quoted 10 lines
drivers/gpu/drm/i915/display/intel_opregion.c +1
-0+struct opregion_header {u8 signature[16 ];u32 size;@@ -1135,6 +1137,16 @@ struct edid *intel_opregion_get_edid(struct intel_connector *intel_connector)return new_edid; }Quoted 14 lines
drivers/gpu/drm/i915/display/intel_opregion.c struct edid *intel_opregion_get_edid(struct intel_connector *intel_connector) · line 1147
Quoted 9 lines
drivers/gpu/drm/i915/display/intel_opregion.c +8
-0+bool intel_opregion_headless_sku (struct drm_i915_private *i915) +{ +struct intel_opregion *opregion = &i915->opregion; + +if (!opregion->header) +return false; + +return opregion->header->pcon &PCON_HEADLESS_SKU ;We should probably start checking for opregion version for this stuff
too.Yes, I will do this change.
Quoted 42 lines
BR,
Jani.Quoted 39 lines
drivers/gpu/drm/i915/display/intel_opregion.c +2
-0+} +void
intel_opregion_register(struct drm_i915_private *i915){
structintel_opregion*opregion =&i915->opregion;drivers/gpu/drm/i915/display/intel_opregion.h +1
-0@@ -76,6 +76,8 @@ int intel_opregion_notify_adapter(structdrm_i915_private *dev_priv, int intel_opregion_get_panel_type(struct drm_i915_private *dev_priv);struct edid *intel_opregion_get_edid (struct intel_connector *connector); +bool intel_opregion_headless_sku(struct drm_i915_private*i915);
+
#else /* CONFIG_ACPI*/static inline int intel_opregion_setup(struct
drm_i915_private*dev_priv)drivers/gpu/drm/i915/display/intel_opregion.h +0
-0@@ -127,6 +129,11 @@ intel_opregion_get_edid(struct
intel_connector
*connector)
return NULL;
}+bool
intel_opregion_headless_sku(struct drm_i915_private *i915)drivers/gpu/drm/i915/display/intel_opregion.h +4
-0+{ +return false; +} +#endif /* CONFIG_ACPI */ #endif
Jani Nikula
maintainerRe: [Intel-gfx] [PATCH 1/2] drm/i915/opregion: add function to check if headless sku
Quoted 65 lines · Jose
Quoted 64 lines · Jani Nikula
Quoted 63 lines · Jouni
Quoted 61 lines · Jose
Quoted 49 lines · Jouni
Quoted 24 lines · Jani Nikula
Quoted 22 lines · Jouni Högander
Export headless sku bit (bit 13) from
opregion->header->pconas an
interface to check if our device is headless configuration.Bspec: 53441
Signed-off-by Jouni Högander <[email protected]>--- drivers/gpu/drm/i915/display/intel_opregion.c | 12 ++++++++++++ drivers/gpu/drm/i915/display/intel_opregion.h | 7 +++++++ 2 files changed, 19 insertions(+)drivers/gpu/drm/i915/display/intel_opregion.c +0
-0@@ -53,6 +53,8 @@ #define MBOX_ASLE_EXTBIT(4)/* Mailbox #5 */ #define MBOX_BACKLIGHTBIT(5)/* Mailbox #2(valid from v3.x) */
Quoted 7 lines
Quoted 1 line
+#define
PCON_HEADLESS_SKUBIT(13)Here we go again.
What does headless mean here? The spec does not say. Does it have display hardware? Apparently yes, since otherwise we wouldn't be here.
This is for hybrid setup with several display hw and the panel wont be
connected into device driven by i915 driver.Quoted 12 lines
We have
INTEL_DISPLAY_ENABLED()which should do the right thing when
you
do have display hardware and have done output setup etc. but want to
force them disconnected, i.e. you take the hardware over properly,
but
put it to sleep for power savings.Maybe we should bolt this opregion check in that macro?
Quoted 8 lines
Quoted 2 lines
Maybe we need to use
INTEL_DISPLAY_ENABLED()also to prevent polling.Thank you for pointing this out.
HAS_DISPLAYI already notice and it's
not suitable for what we want here. I think bolting this check intoINTEL_DISPLAY_ENABLEDas you suggested is enough. That will prevent waking up the hw into D0 state for polling.A headless sku should not have any DDI ports enabled, much easier check for that.
Quoted 8 lines
Quoted 6 lines
Quoted 3 lines
Could you please clarify this a bit? What exactly you are thinking should be checked? Aren't DDI port also disabled when non-headless setup is in runtime suspend?
I also think "headless" and "DDI ports enabled" need clarification. They are overloaded terms.
In a properly setup headless sku, VBT should have all ports marked as disabled.
This is what I mean with overloaded terms. Now we're at "properly setup headless sku", and we're none the wiser. ;)
Is the hardware there?
If not, okay, but why aren't the pipes fused then? Why a different flag in opregion?
If yes, has the GOP taken over the hardware and put it into power save?
BR,
Jani.
Quoted 104 lines
intel_ddi_init() { ... if (!init_dp && !init_hdmi) { drm_dbg_kms(&dev_priv->drm, "VBT says port %c is not DVI/HDMI/DP compatible, respect it\n", port_name(port)); return; }All DDI should return earlier in the above.
So you can use the number of enabled connectors to know if it is a headless sku or not.So you can skip the pooling in case there is no connectors.
Quoted 86 lines
Seems to me the use case here could be the same as
INTEL_DISPLAY_ENABLED(), and that could benefit from polling disable.BR,
Jani.Quoted 77 lines
Quoted 76 lines
Quoted 76 lines
Quoted 5 lines
I certainly would not want to add another mode that's separate from
HAS_DISPLAY()andINTEL_DISPLAY_ENABLED().No need for this. I think we can go with
INTEL_DISPLAY_ENABLED.Quoted 10 lines
Quoted 10 lines
drivers/gpu/drm/i915/display/intel_opregion.c +1
-0+struct opregion_header {u8 signature[16 ];u32 size;@@ -1135,6 +1137,16 @@ struct edid *intel_opregion_get_edid(struct intel_connector *intel_connector)return new_edid; }Quoted 14 lines
drivers/gpu/drm/i915/display/intel_opregion.c struct edid · line 1150
Quoted 9 lines
drivers/gpu/drm/i915/display/intel_opregion.c +8
-0+bool intel_opregion_headless_sku (struct drm_i915_private *i915) +{ +struct intel_opregion *opregion = &i915->opregion; + +if (!opregion->header) +return false; + +return opregion->header->pcon &PCON_HEADLESS_SKU ;We should probably start checking for opregion version for this stuff
too.Yes, I will do this change.
Quoted 42 lines
BR,
Jani.Quoted 39 lines
drivers/gpu/drm/i915/display/intel_opregion.c +2
-0+} +void
intel_opregion_register(struct drm_i915_private *i915){
structintel_opregion*opregion =&i915->opregion;drivers/gpu/drm/i915/display/intel_opregion.h +1
-0@@ -76,6 +76,8 @@ int intel_opregion_notify_adapter(structdrm_i915_private *dev_priv, int intel_opregion_get_panel_type(struct drm_i915_private *dev_priv);struct edid *intel_opregion_get_edid (struct intel_connector *connector); +bool intel_opregion_headless_sku(struct drm_i915_private*i915);
+
#else /* CONFIG_ACPI*/static inline int intel_opregion_setup(struct
drm_i915_private*dev_priv)drivers/gpu/drm/i915/display/intel_opregion.h +0
-0@@ -127,6 +129,11 @@ intel_opregion_get_edid(struct
intel_connector
*connector)
return NULL;
}+bool
intel_opregion_headless_sku(struct drm_i915_private *i915)drivers/gpu/drm/i915/display/intel_opregion.h +4
-0+{ +return false; +} +#endif /* CONFIG_ACPI */ #endif
Signature · 1 line
Jani Nikula, Intel Open Source Graphics Center
Re: [Intel-gfx] [PATCH 1/2] drm/i915/opregion: add function to check if headless sku
Quoted 100 lines · Jani Nikula
Quoted 88 lines · Jose
Quoted 87 lines · Jani Nikula
Quoted 84 lines · Jouni
Quoted 74 lines · Jose
Quoted 64 lines · Jouni
Quoted 34 lines · Jani Nikula
Quoted 27 lines · Jouni Högander
Export headless sku bit (bit 13) from opregion->header-
Quoted 1 line
pcon as
an
interface to check if our device is headless
configuration.Bspec: 53441
Signed-off-by Jouni Högander <[email protected]Quoted 1 line
--- drivers/gpu/drm/i915/display/intel_opregion.c | 12 ++++++++++++ drivers/gpu/drm/i915/display/intel_opregion.h | 7 +++++++ 2 files changed, 19 insertions(+)diff --git
a/drivers/gpu/drm/i915/display/intel_opregion.cb/drivers/gpu/drm/i915/display/intel_opregion.c
indexf31e8c3f8ce0..eab3f2e6b786100644drivers/gpu/drm/i915/display/intel_opregion.c +0
-0@@ -53,6 +53,8 @@ #define MBOX_ASLE_EXTBIT(4)/* Mailbox #5 */ #define MBOX_BACKLIGHTBIT(5)/* Mailbox #2(valid from v3.x) */
Quoted 1 line
+#define
PCON_HEADLESS_SKUBIT(13)Here we go again.
Quoted 5 lines
What does headless mean here? The spec does not say. Does it have
display hardware? Apparently yes, since otherwise we wouldn't be
here.This is for hybrid setup with several display hw and the panel wont
be
connected into device driven by i915 driver.Quoted 12 lines
We have
INTEL_DISPLAY_ENABLED()which should do the right thing
when
you
do have display hardware and have done output setup etc. but want
to
force them disconnected, i.e. you take the hardware over properly,
but
put it to sleep for power savings.Quoted 5 lines
Maybe we should bolt this opregion check in that macro?
Maybe we need to use
INTEL_DISPLAY_ENABLED()also to prevent
polling.Quoted 8 lines
Thank you for pointing this out.
HAS_DISPLAYI already notice and
it's
not suitable for what we want here. I think bolting this check intoINTEL_DISPLAY_ENABLEDas you suggested is enough. That will prevent
waking up the hw into D0 state for polling.Quoted 3 lines
A headless sku should not have any DDI ports enabled, much easier
check for that.Could you please clarify this a bit? What exactly you are thinking
should be checked? Aren't DDI port also disabled when non- headless
setup is in runtime suspend?Quoted 6 lines
Quoted 3 lines
I also think "headless" and "DDI ports enabled" need clarification. They
are overloaded terms.In a properly setup headless sku, VBT should have all ports marked as disabled.
This is what I mean with overloaded terms. Now we're at "properly setup
headless sku", and we're none the wiser. ;)
Quoted 5 lines
Is the hardware there?
If not, okay, but why aren't the pipes fused then? Why a different flag
in opregion?
I understand it as a "master" bit to disable having any display connected to this hardware. To my understanding target use for operegion headless bit is hybrid graphics setup.
Quoted 121 lines
If yes, has the GOP taken over the hardware and put it into power save?
BR,
Jani.Quoted 113 lines
intel_ddi_init() { ... if (!init_dp && !init_hdmi) { drm_dbg_kms(&dev_priv->drm, "VBT says port %c is not DVI/HDMI/DP compatible, respect it\n", port_name(port)); return; }All DDI should return earlier in the above.
So you can use the number of enabled connectors to know if it is a headless sku or not.So you can skip the pooling in case there is no connectors.
Quoted 95 lines
Seems to me the use case here could be the same as
INTEL_DISPLAY_ENABLED(), and that could benefit from polling disable.BR,
Jani.Quoted 87 lines
Quoted 87 lines
Quoted 87 lines
Quoted 5 lines
I certainly would not want to add another mode that's separate
fromHAS_DISPLAY()andINTEL_DISPLAY_ENABLED().No need for this. I think we can go with
INTEL_DISPLAY_ENABLED.Quoted 10 lines
Quoted 10 lines
drivers/gpu/drm/i915/display/intel_opregion.c +1
-0+struct opregion_header {u8 signature[16 ];u32 size;@@ -1135,6 +1137,16 @@ struct edid *intel_opregion_get_edid(struct intel_connector *intel_connector)return new_edid; }Quoted 16 lines
drivers/gpu/drm/i915/display/intel_opregion.c
Quoted 10 lines
drivers/gpu/drm/i915/display/intel_opregion.c +1
-0+bool intel_opregion_headless_sku(struct
drm_i915_private
*i915)drivers/gpu/drm/i915/display/intel_opregion.c +7
-0+{ +struct intel_opregion *opregion = &i915->opregion; + +if (!opregion->header) +return false; + +return opregion->header->pcon &PCON_HEADLESS_SKU ;We should probably start checking for opregion version for this
stuff
too.Yes, I will do this change.
Quoted 50 lines
BR,
Jani.Quoted 47 lines
drivers/gpu/drm/i915/display/intel_opregion.c +2
-0+} + void intel_opregion_register(struct drm_i915_private*i915)
{
structintel_opregion*opregion =&i915->opregion;
diff --gita/drivers/gpu/drm/i915/display/intel_opregion.hb/drivers/gpu/drm/i915/display/intel_opregion.hindex82cc0ba34af7..5ad96e1d8278100644drivers/gpu/drm/i915/display/intel_opregion.h +0
-0@@ -76,6 +76,8 @@ intintel_opregion_notify_adapter(struct
drm_i915_private*dev_priv,
int intel_opregion_get_panel_type(structdrm_i915_private*dev_priv);
struct edid *intel_opregion_get_edid(structintel_connector
*connector);+bool intel_opregion_headless_sku(struct
drm_i915_private
*i915);
+
#else /* CONFIG_ACPI*/static inline int intel_opregion_setup(struct
drm_i915_private*dev_priv)drivers/gpu/drm/i915/display/intel_opregion.h +0
-0@@ -127,6 +129,11 @@ intel_opregion_get_edid(struct
intel_connector
*connector)
return NULL;
}+bool intel_opregion_headless_sku(struct
drm_i915_private
*i915)drivers/gpu/drm/i915/display/intel_opregion.h +4
-0+{ +return false; +} +#endif /* CONFIG_ACPI */ #endif
Re: [Intel-gfx] [PATCH 1/2] drm/i915/opregion: add function to check if headless sku
Quoted 94 lines · Jouni
Quoted 93 lines · Jani Nikula
Quoted 92 lines · Jose
Quoted 90 lines · Jani Nikula
Quoted 79 lines · Jouni
Quoted 74 lines · Jose
Quoted 64 lines · Jouni
Quoted 34 lines · Jani Nikula
Quoted 27 lines · Jouni Högander
Export headless sku bit (bit 13) from opregion->header-
Quoted 1 line
pcon as
an
interface to check if our device is headless
configuration.Bspec: 53441
Signed-off-by Jouni Högander <[email protected]Quoted 1 line
--- drivers/gpu/drm/i915/display/intel_opregion.c | 12 ++++++++++++ drivers/gpu/drm/i915/display/intel_opregion.h | 7 +++++++ 2 files changed, 19 insertions(+)diff --git
a/drivers/gpu/drm/i915/display/intel_opregion.cb/drivers/gpu/drm/i915/display/intel_opregion.c
indexf31e8c3f8ce0..eab3f2e6b786100644drivers/gpu/drm/i915/display/intel_opregion.c +0
-0@@ -53,6 +53,8 @@ #define MBOX_ASLE_EXTBIT(4)/* Mailbox #5 */ #define MBOX_BACKLIGHTBIT(5)/* Mailbox #2(valid from v3.x) */
Quoted 1 line
+#define
PCON_HEADLESS_SKUBIT(13)Here we go again.
Quoted 5 lines
What does headless mean here? The spec does not say. Does it have
display hardware? Apparently yes, since otherwise we wouldn't be
here.This is for hybrid setup with several display hw and the panel wont
be
connected into device driven by i915 driver.Quoted 12 lines
We have
INTEL_DISPLAY_ENABLED()which should do the right thing
when
you
do have display hardware and have done output setup etc. but want
to
force them disconnected, i.e. you take the hardware over properly,
but
put it to sleep for power savings.Quoted 5 lines
Maybe we should bolt this opregion check in that macro?
Maybe we need to use
INTEL_DISPLAY_ENABLED()also to prevent
polling.Quoted 8 lines
Thank you for pointing this out.
HAS_DISPLAYI already notice and
it's
not suitable for what we want here. I think bolting this check intoINTEL_DISPLAY_ENABLEDas you suggested is enough. That will prevent
waking up the hw into D0 state for polling.Quoted 3 lines
A headless sku should not have any DDI ports enabled, much easier
check for that.Quoted 5 lines
Could you please clarify this a bit? What exactly you are thinking
should be checked? Aren't DDI port also disabled when non- headless
setup is in runtime suspend?I also think "headless" and "DDI ports enabled" need clarification. They
are overloaded terms.
Quoted 8 lines
Quoted 8 lines
Quoted 2 lines
In a properly setup headless sku, VBT should have all ports marked as disabled.
This is what I mean with overloaded terms. Now we're at "properly setup
headless sku", and we're none the wiser. ;)Is the hardware there?
All the display hardware it there but none of the DDI ports are connected to physical(DP, HDMI, TC) ports. Display can still be used with Wireless Display in Windows and maybe in future with Linux!
Quoted 12 lines
Quoted 4 lines
If not, okay, but why aren't the pipes fused then? Why a different flag
in opregion?I understand it as a "master" bit to disable having any display connected to this hardware. To my understanding target use for operegion headless bit is hybrid graphics setup.
Quoted 3 lines
If yes, has the GOP taken over the hardware and put it into power save?
This was not happening in a notebook design that I fixed some issues, i915 it the one that needs to do that.
Quoted 119 lines
Quoted 118 lines
BR,
Jani.Quoted 113 lines
intel_ddi_init() { ... if (!init_dp && !init_hdmi) { drm_dbg_kms(&dev_priv->drm, "VBT says port %c is not DVI/HDMI/DP compatible, respect it\n", port_name(port)); return; }All DDI should return earlier in the above.
So you can use the number of enabled connectors to know if it is a headless sku or not.So you can skip the pooling in case there is no connectors.
Quoted 95 lines
Seems to me the use case here could be the same as
INTEL_DISPLAY_ENABLED(), and that could benefit from polling disable.BR,
Jani.Quoted 87 lines
Quoted 87 lines
Quoted 87 lines
Quoted 5 lines
I certainly would not want to add another mode that's separate
fromHAS_DISPLAY()andINTEL_DISPLAY_ENABLED().No need for this. I think we can go with
INTEL_DISPLAY_ENABLED.Quoted 10 lines
Quoted 10 lines
drivers/gpu/drm/i915/display/intel_opregion.c +1
-0+struct opregion_header {u8 signature[16 ];u32 size;@@ -1135,6 +1137,16 @@ struct edid *intel_opregion_get_edid(struct intel_connector *intel_connector)return new_edid; }Quoted 16 lines
drivers/gpu/drm/i915/display/intel_opregion.c
Quoted 10 lines
drivers/gpu/drm/i915/display/intel_opregion.c +1
-0+bool intel_opregion_headless_sku(struct
drm_i915_private
*i915)drivers/gpu/drm/i915/display/intel_opregion.c +7
-0+{ +struct intel_opregion *opregion = &i915->opregion; + +if (!opregion->header) +return false; + +return opregion->header->pcon &PCON_HEADLESS_SKU ;We should probably start checking for opregion version for this
stuff
too.Yes, I will do this change.
Quoted 50 lines
BR,
Jani.Quoted 47 lines
drivers/gpu/drm/i915/display/intel_opregion.c +2
-0+} + void intel_opregion_register(struct drm_i915_private*i915)
{
structintel_opregion*opregion =&i915->opregion;
diff --gita/drivers/gpu/drm/i915/display/intel_opregion.hb/drivers/gpu/drm/i915/display/intel_opregion.hindex82cc0ba34af7..5ad96e1d8278100644drivers/gpu/drm/i915/display/intel_opregion.h +0
-0@@ -76,6 +76,8 @@ intintel_opregion_notify_adapter(struct
drm_i915_private*dev_priv,
int intel_opregion_get_panel_type(structdrm_i915_private*dev_priv);
struct edid *intel_opregion_get_edid(structintel_connector
*connector);+bool intel_opregion_headless_sku(struct
drm_i915_private
*i915);
+
#else /* CONFIG_ACPI*/static inline int intel_opregion_setup(struct
drm_i915_private*dev_priv)drivers/gpu/drm/i915/display/intel_opregion.h +0
-0@@ -127,6 +129,11 @@ intel_opregion_get_edid(struct
intel_connector
*connector)
return NULL;
}+bool intel_opregion_headless_sku(struct
drm_i915_private
*i915)drivers/gpu/drm/i915/display/intel_opregion.h +4
-0+{ +return false; +} +#endif /* CONFIG_ACPI */ #endif
Re: [Intel-gfx] [PATCH 1/2] drm/i915/opregion: add function to check if headless sku
In reply to Souza, JoseQuoted 87 lines · Jose
Quoted 86 lines · Jani Nikula
Quoted 83 lines · Jouni
Quoted 73 lines · Jose
Quoted 63 lines · Jouni
Quoted 33 lines · Jani Nikula
Quoted 26 lines · Jouni Högander
Export headless sku bit (bit 13) from opregion->header-
Quoted 1 line
pcon as
an
interface to check if our device is headless
configuration.Bspec: 53441
Signed-off-by Jouni Högander <[email protected]>--- drivers/gpu/drm/i915/display/intel_opregion.c | 12 ++++++++++++ drivers/gpu/drm/i915/display/intel_opregion.h | 7 +++++++ 2 files changed, 19 insertions(+)diff --git
a/drivers/gpu/drm/i915/display/intel_opregion.cb/drivers/gpu/drm/i915/display/intel_opregion.c
indexf31e8c3f8ce0..eab3f2e6b786100644drivers/gpu/drm/i915/display/intel_opregion.c +0
-0@@ -53,6 +53,8 @@ #define MBOX_ASLE_EXTBIT(4)/* Mailbox #5 */ #define MBOX_BACKLIGHTBIT(5)/* Mailbox #2(valid from v3.x) */
Quoted 1 line
+#define
PCON_HEADLESS_SKUBIT(13)Here we go again.
Quoted 5 lines
What does headless mean here? The spec does not say. Does it have
display hardware? Apparently yes, since otherwise we wouldn't be
here.This is for hybrid setup with several display hw and the panel wont
be
connected into device driven by i915 driver.Quoted 12 lines
We have
INTEL_DISPLAY_ENABLED()which should do the right thing
when
you
do have display hardware and have done output setup etc. but want
to
force them disconnected, i.e. you take the hardware over properly,
but
put it to sleep for power savings.Quoted 5 lines
Maybe we should bolt this opregion check in that macro?
Maybe we need to use
INTEL_DISPLAY_ENABLED()also to prevent
polling.Quoted 8 lines
Thank you for pointing this out.
HAS_DISPLAYI already notice and
it's
not suitable for what we want here. I think bolting this check intoINTEL_DISPLAY_ENABLEDas you suggested is enough. That will prevent
waking up the hw into D0 state for polling.Quoted 3 lines
A headless sku should not have any DDI ports enabled, much easier
check for that.Could you please clarify this a bit? What exactly you are thinking
should be checked? Aren't DDI port also disabled when non- headless
setup is in runtime suspend?
Quoted 6 lines
Quoted 3 lines
I also think "headless" and "DDI ports enabled" need clarification. They
are overloaded terms.In a properly setup headless sku, VBT should have all ports marked as disabled.
Should we take into account headless bit in opregion possibly conflicting with VBT contents?
Now as you pointed out this I started to think intel_opregion_headless_sku check could be also in here as additional check:
if (!init_dp && !init_hdmi || intel_opregion_headless_sku()) {
This would prevent initializing any connector including setting them up for polling?
Quoted 109 lines
intel_ddi_init(){
...if (!init_dp && !init_hdmi) { drm_dbg_kms(&dev_priv->drm,
"VBT says port %c is not DVI/HDMI/DP compatible, respect it\n",port_name(port));
return;
}All DDI should return earlier in the above.
So you can use the number of enabled connectors to know if it is a headless sku or not.So you can skip the pooling in case there is no connectors.
Quoted 91 lines
Seems to me the use case here could be the same as
INTEL_DISPLAY_ENABLED(), and that could benefit from polling disable.BR,
Jani.Quoted 83 lines
Quoted 83 lines
Quoted 83 lines
Quoted 4 lines
I certainly would not want to add another mode that's separate
fromHAS_DISPLAY()andINTEL_DISPLAY_ENABLED().No need for this. I think we can go with
INTEL_DISPLAY_ENABLED.Quoted 10 lines
Quoted 10 lines
drivers/gpu/drm/i915/display/intel_opregion.c +1
-0+struct opregion_header {u8 signature[16 ];u32 size;@@ -1135,6 +1137,16 @@ struct edid *intel_opregion_get_edid(struct intel_connector *intel_connector)return new_edid; }Quoted 15 lines
drivers/gpu/drm/i915/display/intel_opregion.c struct edid · line 1150
Quoted 9 lines
drivers/gpu/drm/i915/display/intel_opregion.c +8
-0+bool intel_opregion_headless_sku (struct drm_i915_private *i915) +{ +struct intel_opregion *opregion = &i915->opregion; + +if (!opregion->header) +return false; + +return opregion->header->pcon &PCON_HEADLESS_SKU ;We should probably start checking for opregion version for this
stuff
too.Yes, I will do this change.
Quoted 48 lines
BR,
Jani.Quoted 45 lines
drivers/gpu/drm/i915/display/intel_opregion.c +2
-0+} +void intel_opregion_register(struct
drm_i915_private
*i915)
{
structintel_opregion*opregion =&i915->opregion;
diff --gita/drivers/gpu/drm/i915/display/intel_opregion.hb/drivers/gpu/drm/i915/display/intel_opregion.hindex82cc0ba34af7..5ad96e1d8278100644drivers/gpu/drm/i915/display/intel_opregion.h +0
-0@@ -76,6 +76,8 @@ intintel_opregion_notify_adapter(struct
drm_i915_private*dev_priv,
int intel_opregion_get_panel_type(structdrm_i915_private*dev_priv);
struct edid *intel_opregion_get_edid(structintel_connector
*connector);+bool
intel_opregion_headless_sku(struct drm_i915_private *i915);
+
#else /* CONFIG_ACPI*/static inline int intel_opregion_setup(struct
drm_i915_private*dev_priv)drivers/gpu/drm/i915/display/intel_opregion.h +0
-0@@ -127,6 +129,11 @@ intel_opregion_get_edid(struct
intel_connector
*connector)
return NULL;
}+bool
intel_opregion_headless_sku(struct drm_i915_private *i915)drivers/gpu/drm/i915/display/intel_opregion.h +4
-0+{ +return false; +} +#endif /* CONFIG_ACPI */ #endif
Re: [Intel-gfx] [PATCH 1/2] drm/i915/opregion: add function to check if headless sku
In reply to Souza, JoseQuoted 105 lines · Jose
Quoted 86 lines · Jani Nikula
Quoted 78 lines · Jouni
Quoted 73 lines · Jose
Quoted 63 lines · Jouni
Quoted 33 lines · Jani Nikula
Quoted 26 lines · Jouni Högander
Export headless sku bit (bit 13) from opregion->header-
Quoted 1 line
pcon as
an
interface to check if our device is headless
configuration.Bspec: 53441
Signed-off-by Jouni Högander <[email protected]>--- drivers/gpu/drm/i915/display/intel_opregion.c | 12 ++++++++++++ drivers/gpu/drm/i915/display/intel_opregion.h | 7 +++++++ 2 files changed, 19 insertions(+)diff --git
a/drivers/gpu/drm/i915/display/intel_opregion.cb/drivers/gpu/drm/i915/display/intel_opregion.c
indexf31e8c3f8ce0..eab3f2e6b786100644drivers/gpu/drm/i915/display/intel_opregion.c +0
-0@@ -53,6 +53,8 @@ #define MBOX_ASLE_EXTBIT(4)/* Mailbox #5 */ #define MBOX_BACKLIGHTBIT(5)/* Mailbox #2(valid from v3.x) */
Quoted 1 line
+#define
PCON_HEADLESS_SKUBIT(13)Here we go again.
Quoted 5 lines
What does headless mean here? The spec does not say. Does it have
display hardware? Apparently yes, since otherwise we wouldn't be
here.This is for hybrid setup with several display hw and the panel wont
be
connected into device driven by i915 driver.Quoted 12 lines
We have
INTEL_DISPLAY_ENABLED()which should do the right thing
when
you
do have display hardware and have done output setup etc. but want
to
force them disconnected, i.e. you take the hardware over properly,
but
put it to sleep for power savings.Quoted 5 lines
Maybe we should bolt this opregion check in that macro?
Maybe we need to use
INTEL_DISPLAY_ENABLED()also to prevent
polling.Quoted 8 lines
Thank you for pointing this out.
HAS_DISPLAYI already notice and
it's
not suitable for what we want here. I think bolting this check intoINTEL_DISPLAY_ENABLEDas you suggested is enough. That will prevent
waking up the hw into D0 state for polling.Quoted 3 lines
A headless sku should not have any DDI ports enabled, much easier
check for that.Quoted 5 lines
Could you please clarify this a bit? What exactly you are thinking
should be checked? Aren't DDI port also disabled when non- headless
setup is in runtime suspend?Quoted 3 lines
I also think "headless" and "DDI ports enabled" need clarification. They
are overloaded terms.In a properly setup headless sku, VBT should have all ports marked as disabled.
intel_ddi_init(){
...if (!init_dp && !init_hdmi) { drm_dbg_kms(&dev_priv->drm,
"VBT says port %c is not DVI/HDMI/DP compatible, respect it\n",port_name(port));
return;
}
Quoted 5 lines
All DDI should return earlier in the above.
So you can use the number of enabled connectors to know if it is a headless sku or not.So you can skip the pooling in case there is no connectors.
I went through this and to my understanding this polling doesn't happen in setup where all ports are marked as disabled in VBT. Connector is not initialized at all -> polling is not enabled when runtime suspend happens.
BR,
Jouni Högander
PATCH 2/2 drm/i915: do not start connector polling when headless sku
In reply to Jouni HöganderConnector polling is waking up the polled device. Polling is unnecessary if our device is known to not have display.
Fix this and Save some power by disabling starting connector polling when we are having headless sku. Use information from opregion.
--- drivers/gpu/drm/i915/display/intel_hotplug.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/gpu/drm/i915/display/intel_hotplug.c +2 -1
@@ -668,7 +668,8 @@ static void i915_hpd_poll_init_work(struct work_struct *work)*/ void intel_hpd_poll_enable (struct drm_i915_private *dev_priv) { -if (!HAS_DISPLAY (dev_priv)) +if (!HAS_DISPLAY (dev_priv) || +intel_opregion_headless_sku (dev_priv))return ;WRITE_ONCE (dev_priv->hotplug.poll_enabled, true);
Signature · 1 line
2.25.1
Patchwork
CI[Intel-gfx] ✗ Fi.CI.SPARSE: warning for Disable connector polling for a headless sku
In reply to Jouni Högander== Series Details ==
== Series Details ==
Series: Disable connector polling for a headless sku
URL : https://patchwork.freedesktop.org/series/104711/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
Patchwork
CI[Intel-gfx] ✓ Fi.CI.BAT: success for Disable connector polling for a headless sku
In reply to Jouni Högander== Series Details ==
== Series Details ==
Series: Disable connector polling for a headless sku
URL : https://patchwork.freedesktop.org/series/104711/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11726 -> Patchwork_104711v1
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/index.html
Participating hosts (43 -> 45)
------------------------------
Additional (4): bat-adln-1 fi-kbl-x1275 bat-dg2-9 bat-atsm-1
Missing (2): bat-dg2-8 bat-jsl-2
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_104711v1:
### IGT changes ###
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses. They do not affect the overall result.
* igt@gem_exec_suspend@basic-s3@smem:
- {bat-adln-1}: NOTRUN -> [DMESG-WARN][1]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/bat-adln-1/igt@gem_exec_suspend@[email protected]
* igt@kms_frontbuffer_tracking@basic:
- {bat-adln-1}: NOTRUN -> [SKIP][2] +19 similar issues
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/bat-adln-1/igt@[email protected]
Known issues
------------
Here are the changes found in Patchwork_104711v1 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_huc_copy@huc-copy:
- fi-kbl-x1275: NOTRUN -> [SKIP][3] ([fdo#109271] / [i915#2190])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/fi-kbl-x1275/igt@[email protected]
* igt@gem_lmem_swapping@verify-random:
- fi-kbl-x1275: NOTRUN -> [SKIP][4] ([fdo#109271] / [i915#4613]) +3 similar issues
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/fi-kbl-x1275/igt@[email protected]
* igt@i915_selftest@live@gem:
- fi-pnv-d510: NOTRUN -> [DMESG-FAIL][5] ([i915#4528])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/fi-pnv-d510/igt@i915_selftest@[email protected]
* igt@i915_selftest@live@gt_engines:
- bat-dg1-5: [PASS][6] -> [INCOMPLETE][7] ([i915#4418])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/bat-dg1-5/igt@i915_selftest@live@gt_engines.html
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/bat-dg1-5/igt@i915_selftest@live@gt_engines.html
* igt@i915_selftest@live@requests:
- fi-blb-e6850: [PASS][8] -> [DMESG-FAIL][9] ([i915#4528])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/fi-blb-e6850/igt@i915_selftest@[email protected]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/fi-blb-e6850/igt@i915_selftest@[email protected]
* igt@kms_chamelium@dp-hpd-fast:
- fi-kbl-x1275: NOTRUN -> [SKIP][10] ([fdo#109271] / [fdo#111827]) +8 similar issues
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/fi-kbl-x1275/igt@[email protected]
* igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d:
- fi-kbl-x1275: NOTRUN -> [SKIP][11] ([fdo#109271] / [i915#533])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/fi-kbl-x1275/igt@[email protected]
* igt@prime_vgem@basic-userptr:
- fi-kbl-x1275: NOTRUN -> [SKIP][12] ([fdo#109271]) +12 similar issues
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/fi-kbl-x1275/igt@[email protected]
#### Possible fixes ####
* igt@gem_exec_suspend@basic-s0@smem:
- {fi-ehl-2}: [DMESG-WARN][13] ([i915#5122]) -> [PASS][14]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/fi-ehl-2/igt@gem_exec_suspend@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/fi-ehl-2/igt@gem_exec_suspend@[email protected]
* igt@i915_selftest@live@requests:
- fi-pnv-d510: [DMESG-FAIL][15] ([i915#4528]) -> [PASS][16]
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/fi-pnv-d510/igt@i915_selftest@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/fi-pnv-d510/igt@i915_selftest@[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#109285]: https://bugs.freedesktop.org/show_bug.cgi?id=109285
[fdo#109295]: https://bugs.freedesktop.org/show_bug.cgi?id=109295
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1072]: https://gitlab.freedesktop.org/drm/intel/issues/1072
[i915#1155]: https://gitlab.freedesktop.org/drm/intel/issues/1155
[i915#1836]: https://gitlab.freedesktop.org/drm/intel/issues/1836
[i915#1849]: https://gitlab.freedesktop.org/drm/intel/issues/1849
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#3282]: https://gitlab.freedesktop.org/drm/intel/issues/3282
[i915#3291]: https://gitlab.freedesktop.org/drm/intel/issues/3291
[i915#3301]: https://gitlab.freedesktop.org/drm/intel/issues/3301
[i915#3555]: https://gitlab.freedesktop.org/drm/intel/issues/3555
[i915#3595]: https://gitlab.freedesktop.org/drm/intel/issues/3595
[i915#3708]: https://gitlab.freedesktop.org/drm/intel/issues/3708
[i915#4077]: https://gitlab.freedesktop.org/drm/intel/issues/4077
[i915#4079]: https://gitlab.freedesktop.org/drm/intel/issues/4079
[i915#4083]: https://gitlab.freedesktop.org/drm/intel/issues/4083
[i915#4103]: https://gitlab.freedesktop.org/drm/intel/issues/4103
[i915#4212]: https://gitlab.freedesktop.org/drm/intel/issues/4212
[i915#4213]: https://gitlab.freedesktop.org/drm/intel/issues/4213
[i915#4215]: https://gitlab.freedesktop.org/drm/intel/issues/4215
[i915#4312]: https://gitlab.freedesktop.org/drm/intel/issues/4312
[i915#4418]: https://gitlab.freedesktop.org/drm/intel/issues/4418
[i915#4528]: https://gitlab.freedesktop.org/drm/intel/issues/4528
[i915#4579]: https://gitlab.freedesktop.org/drm/intel/issues/4579
[i915#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613
[i915#4873]: https://gitlab.freedesktop.org/drm/intel/issues/4873
[i915#5122]: https://gitlab.freedesktop.org/drm/intel/issues/5122
[i915#5174]: https://gitlab.freedesktop.org/drm/intel/issues/5174
[i915#5190]: https://gitlab.freedesktop.org/drm/intel/issues/5190
[i915#5274]: https://gitlab.freedesktop.org/drm/intel/issues/5274
[i915#533]: https://gitlab.freedesktop.org/drm/intel/issues/533
[i915#5763]: https://gitlab.freedesktop.org/drm/intel/issues/5763
[i915#5874]: https://gitlab.freedesktop.org/drm/intel/issues/5874
[i915#5885]: https://gitlab.freedesktop.org/drm/intel/issues/5885
[i915#5903]: https://gitlab.freedesktop.org/drm/intel/issues/5903
[i915#6077]: https://gitlab.freedesktop.org/drm/intel/issues/6077
[i915#6092]: https://gitlab.freedesktop.org/drm/intel/issues/6092
[i915#6093]: https://gitlab.freedesktop.org/drm/intel/issues/6093
[i915#6094]: https://gitlab.freedesktop.org/drm/intel/issues/6094
[i915#6099]: https://gitlab.freedesktop.org/drm/intel/issues/6099
[i915#6133]: https://gitlab.freedesktop.org/drm/intel/issues/6133
[i915#6134]: https://gitlab.freedesktop.org/drm/intel/issues/6134
[i915#6135]: https://gitlab.freedesktop.org/drm/intel/issues/6135
[i915#6136]: https://gitlab.freedesktop.org/drm/intel/issues/6136
[i915#6137]: https://gitlab.freedesktop.org/drm/intel/issues/6137
[i915#6138]: https://gitlab.freedesktop.org/drm/intel/issues/6138
[i915#6166]: https://gitlab.freedesktop.org/drm/intel/issues/6166
Build changes
-------------
* Linux: CI_DRM_11726 -> Patchwork_104711v1
CI-20190529: 20190529
CI_DRM_11726: 74ea63ad8ffc71b8345436147517253dcabd4793 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6505: edb1a467fb622b23b927e28ff603fa43851fea97 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_104711v1: 74ea63ad8ffc71b8345436147517253dcabd4793 @ git://anongit.freedesktop.org/gfx-ci/linux
### Linux commits
2b94b34a3ee6 drm/i915: do not start connector polling when headless sku c3a38221f84a drm/i915/opregion: add function to check if headless sku
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/index.html
Patchwork
CI[Intel-gfx] ✗ Fi.CI.IGT: failure for Disable connector polling for a headless sku
In reply to Jouni Högander== Series Details ==
== Series Details ==
Series: Disable connector polling for a headless sku
URL : https://patchwork.freedesktop.org/series/104711/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11726_full -> Patchwork_104711v1_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_104711v1_full absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in Patchwork_104711v1_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.
Participating hosts (13 -> 13)
------------------------------
No changes in participating hosts
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_104711v1_full:
### IGT changes ###
#### Possible regressions ####
* igt@gem_ctx_persistence@many-contexts:
- shard-tglb: [PASS][1] -> [INCOMPLETE][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-tglb5/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-tglb5/igt@[email protected]
* igt@gem_exec_suspend@basic-s4-devices@smem:
- shard-snb: [PASS][3] -> [INCOMPLETE][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-snb2/igt@gem_exec_suspend@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-snb5/igt@gem_exec_suspend@[email protected]
* igt@kms_hdr@bpc-switch-dpms@pipe-a-dp-1:
- shard-kbl: [PASS][5] -> [FAIL][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-kbl6/igt@kms_hdr@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-kbl4/igt@kms_hdr@[email protected]
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses. They do not affect the overall result.
* igt@kms_flip@wf_vblank-ts-check@a-edp1:
- {shard-rkl}: NOTRUN -> [FAIL][7] +1 similar issue
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-rkl-6/igt@kms_flip@[email protected]
Known issues
------------
Here are the changes found in Patchwork_104711v1_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_ctx_persistence@engines-hang@bcs0:
- shard-skl: NOTRUN -> [SKIP][8] ([fdo#109271]) +111 similar issues
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-skl7/igt@gem_ctx_persistence@[email protected]
* igt@gem_ctx_persistence@idempotent:
- shard-snb: NOTRUN -> [SKIP][9] ([fdo#109271] / [i915#1099])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-snb4/igt@[email protected]
* igt@gem_eio@unwedge-stress:
- shard-iclb: [PASS][10] -> [TIMEOUT][11] ([i915#3070])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-iclb4/igt@[email protected]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-iclb2/igt@[email protected]
* igt@gem_exec_balancer@parallel-bb-first:
- shard-iclb: [PASS][12] -> [SKIP][13] ([i915#4525])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-iclb1/igt@[email protected]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-iclb3/igt@[email protected]
* igt@gem_exec_fair@basic-deadline:
- shard-apl: NOTRUN -> [FAIL][14] ([i915#6141])
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-apl2/igt@[email protected]
* igt@gem_exec_fair@basic-flow@rcs0:
- shard-tglb: [PASS][15] -> [FAIL][16] ([i915#2842]) +1 similar issue
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-tglb1/igt@gem_exec_fair@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-tglb2/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-pace-solo@rcs0:
- shard-iclb: [PASS][17] -> [FAIL][18] ([i915#2842]) +1 similar issue
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-iclb8/igt@gem_exec_fair@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-iclb7/igt@gem_exec_fair@[email protected]
* igt@gem_exec_flush@basic-uc-ro-default:
- shard-snb: [PASS][19] -> [SKIP][20] ([fdo#109271]) +2 similar issues
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-snb5/igt@[email protected]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-snb6/igt@[email protected]
* igt@gem_huc_copy@huc-copy:
- shard-skl: NOTRUN -> [SKIP][21] ([fdo#109271] / [i915#2190])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-skl4/igt@[email protected]
* igt@gem_lmem_swapping@parallel-random-verify-ccs:
- shard-kbl: NOTRUN -> [SKIP][22] ([fdo#109271] / [i915#4613])
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-kbl4/igt@[email protected]
* igt@gem_lmem_swapping@verify-ccs:
- shard-skl: NOTRUN -> [SKIP][23] ([fdo#109271] / [i915#4613])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-skl7/igt@[email protected]
* igt@gem_pread@exhaustion:
- shard-kbl: NOTRUN -> [WARN][24] ([i915#2658])
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-kbl3/igt@[email protected]
* igt@gem_userptr_blits@dmabuf-sync:
- shard-skl: NOTRUN -> [SKIP][25] ([fdo#109271] / [i915#3323])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-skl7/igt@[email protected]
* igt@gem_userptr_blits@input-checking:
- shard-apl: NOTRUN -> [DMESG-WARN][26] ([i915#4991])
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-apl7/igt@[email protected]
* igt@gem_userptr_blits@vma-merge:
- shard-apl: NOTRUN -> [FAIL][27] ([i915#3318])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-apl2/igt@[email protected]
* igt@gen9_exec_parse@allowed-single:
- shard-skl: [PASS][28] -> [DMESG-WARN][29] ([i915#5566] / [i915#716])
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-skl3/igt@[email protected]
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-skl1/igt@[email protected]
* igt@i915_selftest@mock@requests:
- shard-skl: [PASS][30] -> [INCOMPLETE][31] ([i915#5183])
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-skl7/igt@i915_selftest@[email protected]
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-skl6/igt@i915_selftest@[email protected]
* igt@i915_suspend@sysfs-reader:
- shard-apl: [PASS][32] -> [DMESG-WARN][33] ([i915#180]) +1 similar issue
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-apl8/igt@[email protected]
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-apl1/igt@[email protected]
* igt@kms_big_fb@4-tiled-32bpp-rotate-90:
- shard-apl: NOTRUN -> [SKIP][34] ([fdo#109271]) +33 similar issues
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-apl7/igt@[email protected]
* igt@kms_ccs@pipe-a-random-ccs-data-y_tiled_gen12_rc_ccs_cc:
- shard-kbl: NOTRUN -> [SKIP][35] ([fdo#109271] / [i915#3886]) +1 similar issue
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-kbl3/igt@kms_ccs@pipe-a-random-ccs-data-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_ccs@pipe-b-missing-ccs-buffer-y_tiled_gen12_mc_ccs:
- shard-apl: NOTRUN -> [SKIP][36] ([fdo#109271] / [i915#3886]) +2 similar issues
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-apl7/igt@kms_ccs@pipe-b-missing-ccs-buffer-y_tiled_gen12_mc_ccs.html
* igt@kms_ccs@pipe-c-bad-rotation-90-y_tiled_gen12_rc_ccs_cc:
- shard-skl: NOTRUN -> [SKIP][37] ([fdo#109271] / [i915#3886]) +3 similar issues
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-skl7/igt@kms_ccs@pipe-c-bad-rotation-90-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_chamelium@vga-hpd-without-ddc:
- shard-snb: NOTRUN -> [SKIP][38] ([fdo#109271] / [fdo#111827]) +1 similar issue
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-snb4/igt@[email protected]
* igt@kms_color_chamelium@pipe-a-ctm-negative:
- shard-apl: NOTRUN -> [SKIP][39] ([fdo#109271] / [fdo#111827]) +1 similar issue
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-apl7/igt@[email protected]
* igt@kms_color_chamelium@pipe-c-ctm-blue-to-red:
- shard-kbl: NOTRUN -> [SKIP][40] ([fdo#109271] / [fdo#111827]) +7 similar issues
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-kbl4/igt@[email protected]
* igt@kms_color_chamelium@pipe-c-ctm-green-to-red:
- shard-skl: NOTRUN -> [SKIP][41] ([fdo#109271] / [fdo#111827]) +9 similar issues
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-skl7/igt@[email protected]
* igt@kms_content_protection@srm:
- shard-kbl: NOTRUN -> [TIMEOUT][42] ([i915#1319]) +1 similar issue
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-kbl3/igt@[email protected]
* igt@kms_cursor_crc@pipe-b-cursor-suspend:
- shard-skl: [PASS][43] -> [INCOMPLETE][44] ([i915#5713])
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-skl2/igt@[email protected]
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-skl9/igt@[email protected]
* igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions:
- shard-glk: [PASS][45] -> [FAIL][46] ([i915#2346])
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-glk6/igt@[email protected]
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-glk5/igt@[email protected]
- shard-skl: NOTRUN -> [FAIL][47] ([i915#2346])
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-skl7/igt@[email protected]
* igt@kms_cursor_legacy@pipe-d-single-bo:
- shard-skl: NOTRUN -> [SKIP][48] ([fdo#109271] / [i915#533]) +1 similar issue
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-skl7/igt@[email protected]
* igt@kms_flip@flip-vs-expired-vblank-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_11726/shard-skl10/igt@kms_flip@[email protected]
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-skl2/igt@kms_flip@[email protected]
* igt@kms_flip@flip-vs-suspend@c-edp1:
- shard-skl: NOTRUN -> [INCOMPLETE][51] ([i915#4839])
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-skl9/igt@kms_flip@[email protected]
* igt@kms_flip_scaled_crc@flip-32bpp-ytileccs-to-64bpp-ytile-downscaling:
- shard-iclb: [PASS][52] -> [SKIP][53] ([i915#3701]) +1 similar issue
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-iclb4/igt@kms_flip_scaled_crc@flip-32bpp-ytileccs-to-64bpp-ytile-downscaling.html
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-iclb2/igt@kms_flip_scaled_crc@flip-32bpp-ytileccs-to-64bpp-ytile-downscaling.html
* igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-spr-indfb-onoff:
- shard-kbl: NOTRUN -> [SKIP][54] ([fdo#109271]) +122 similar issues
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-kbl6/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbcpsr-rgb101010-draw-blt:
- shard-snb: NOTRUN -> [SKIP][55] ([fdo#109271]) +88 similar issues
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-snb4/igt@[email protected]
* igt@kms_pipe_crc_basic@read-crc-pipe-d-frame-sequence:
- shard-kbl: NOTRUN -> [SKIP][56] ([fdo#109271] / [i915#533])
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-kbl6/igt@[email protected]
* igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c:
- shard-kbl: [PASS][57] -> [DMESG-WARN][58] ([i915#180]) +5 similar issues
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-kbl3/igt@[email protected]
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-kbl7/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-a-alpha-opaque-fb:
- shard-apl: NOTRUN -> [FAIL][59] ([fdo#108145] / [i915#265])
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-apl7/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-a-alpha-transparent-fb:
- shard-skl: NOTRUN -> [FAIL][60] ([i915#265])
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-skl7/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-b-alpha-opaque-fb:
- shard-kbl: NOTRUN -> [FAIL][61] ([fdo#108145] / [i915#265])
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-kbl3/igt@[email protected]
* igt@kms_plane_scaling@planes-downscale-factor-0-5@pipe-a-edp-1:
- shard-iclb: [PASS][62] -> [SKIP][63] ([i915#5235]) +2 similar issues
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-iclb1/igt@kms_plane_scaling@[email protected]
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-iclb2/igt@kms_plane_scaling@[email protected]
* igt@kms_psr2_sf@cursor-plane-move-continuous-exceed-sf:
- shard-skl: NOTRUN -> [SKIP][64] ([fdo#109271] / [i915#658])
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-skl4/igt@[email protected]
* igt@kms_psr2_su@frontbuffer-xrgb8888:
- shard-kbl: NOTRUN -> [SKIP][65] ([fdo#109271] / [i915#658]) +1 similar issue
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-kbl7/igt@[email protected]
- shard-apl: NOTRUN -> [SKIP][66] ([fdo#109271] / [i915#658])
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-apl2/igt@[email protected]
* igt@kms_psr2_su@page_flip-xrgb8888:
- shard-iclb: [PASS][67] -> [SKIP][68] ([fdo#109642] / [fdo#111068] / [i915#658])
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-iclb2/igt@kms_psr2_su@page_flip-xrgb8888.html
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-iclb4/igt@kms_psr2_su@page_flip-xrgb8888.html
* igt@kms_psr@psr2_sprite_plane_move:
- shard-iclb: [PASS][69] -> [SKIP][70] ([fdo#109441]) +2 similar issues
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-iclb2/igt@kms_psr@psr2_sprite_plane_move.html
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-iclb3/igt@kms_psr@psr2_sprite_plane_move.html
* igt@kms_vblank@pipe-b-ts-continuation-suspend:
- shard-kbl: NOTRUN -> [DMESG-WARN][71] ([i915#180]) +1 similar issue
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-kbl4/igt@[email protected]
* igt@perf@short-reads:
- shard-skl: [PASS][72] -> [FAIL][73] ([i915#51])
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-skl6/igt@[email protected]
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-skl4/igt@[email protected]
* igt@sw_sync@sync_multi_timeline_wait:
- shard-snb: NOTRUN -> [FAIL][74] ([i915#6140])
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-snb4/igt@sw_sync@sync_multi_timeline_wait.html
* igt@sysfs_clients@pidname:
- shard-skl: NOTRUN -> [SKIP][75] ([fdo#109271] / [i915#2994])
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-skl7/igt@[email protected]
* igt@sysfs_clients@sema-25:
- shard-kbl: NOTRUN -> [SKIP][76] ([fdo#109271] / [i915#2994])
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-kbl3/igt@[email protected]
#### Possible fixes ####
* igt@device_reset@unbind-reset-rebind:
- shard-iclb: [DMESG-WARN][77] ([i915#2867]) -> [PASS][78]
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-iclb6/igt@[email protected]
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-iclb6/igt@[email protected]
* igt@fbdev@eof:
- {shard-rkl}: [SKIP][79] ([i915#2582]) -> [PASS][80]
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-rkl-1/igt@[email protected]
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-rkl-6/igt@[email protected]
* igt@gem_ctx_isolation@preservation-s3@vcs0:
- shard-kbl: [DMESG-WARN][81] ([i915#180]) -> [PASS][82] +7 similar issues
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-kbl4/igt@gem_ctx_isolation@[email protected]
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-kbl6/igt@gem_ctx_isolation@[email protected]
* igt@gem_exec_balancer@parallel-contexts:
- shard-iclb: [SKIP][83] ([i915#4525]) -> [PASS][84]
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-iclb7/igt@[email protected]
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-iclb1/igt@[email protected]
* igt@gem_exec_fair@basic-none-share@rcs0:
- {shard-tglu}: [FAIL][85] ([i915#2842]) -> [PASS][86]
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-tglu-1/igt@gem_exec_fair@[email protected]
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-tglu-3/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-none@vcs0:
- shard-apl: [FAIL][87] ([i915#2842]) -> [PASS][88]
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-apl4/igt@gem_exec_fair@[email protected]
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-apl8/igt@gem_exec_fair@[email protected]
* igt@gem_exec_flush@basic-uc-pro-default:
- shard-snb: [SKIP][89] ([fdo#109271]) -> [PASS][90] +5 similar issues
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-snb6/igt@[email protected]
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-snb2/igt@[email protected]
* igt@i915_pm_backlight@fade:
- {shard-rkl}: [SKIP][91] ([i915#3012]) -> [PASS][92]
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-rkl-1/igt@[email protected]
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-rkl-6/igt@[email protected]
* igt@i915_pm_dc@dc6-psr:
- shard-iclb: [FAIL][93] ([i915#454]) -> [PASS][94]
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-iclb3/igt@[email protected]
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-iclb8/igt@[email protected]
- {shard-rkl}: [SKIP][95] ([i915#658]) -> [PASS][96]
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-rkl-1/igt@[email protected]
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-rkl-6/igt@[email protected]
* igt@kms_color@pipe-a-ctm-blue-to-red:
- {shard-rkl}: [SKIP][97] ([i915#1149] / [i915#1849] / [i915#4070] / [i915#4098]) -> [PASS][98] +2 similar issues
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-rkl-1/igt@[email protected]
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-rkl-6/igt@[email protected]
* igt@kms_color@pipe-a-legacy-gamma:
- {shard-dg1}: [SKIP][99] ([i915#1836]) -> [PASS][100] +10 similar issues
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-dg1-17/igt@[email protected]
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-dg1-16/igt@[email protected]
* igt@kms_cursor_crc@pipe-a-cursor-64x21-offscreen:
- {shard-rkl}: [SKIP][101] ([fdo#112022] / [i915#4070]) -> [PASS][102] +1 similar issue
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-rkl-1/igt@[email protected]
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-rkl-6/igt@[email protected]
* igt@kms_cursor_legacy@flip-vs-cursor-toggle:
- shard-iclb: [FAIL][103] ([i915#2346]) -> [PASS][104]
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-iclb7/igt@[email protected]
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-iclb8/igt@[email protected]
* igt@kms_cursor_legacy@pipe-c-forked-bo:
- {shard-rkl}: [SKIP][105] ([i915#4070]) -> [PASS][106]
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-rkl-6/igt@[email protected]
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-rkl-5/igt@[email protected]
* igt@kms_draw_crc@draw-method-rgb565-pwrite-xtiled:
- {shard-rkl}: [SKIP][107] ([fdo#111314] / [i915#4098] / [i915#4369]) -> [PASS][108]
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-rkl-1/igt@[email protected]
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-rkl-6/igt@[email protected]
* igt@kms_flip@flip-vs-absolute-wf_vblank@a-edp1:
- shard-skl: [FAIL][109] ([i915#2122]) -> [PASS][110] +1 similar issue
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-skl9/igt@kms_flip@[email protected]
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-skl3/igt@kms_flip@[email protected]
* igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytileccs-upscaling:
- shard-glk: [FAIL][111] ([i915#4911]) -> [PASS][112]
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-glk8/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytileccs-upscaling.html
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-glk9/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytileccs-upscaling.html
* igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs-upscaling:
- {shard-rkl}: [SKIP][113] ([i915#3701]) -> [PASS][114]
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-rkl-1/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs-upscaling.html
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-rkl-6/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs-upscaling.html
* igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-16bpp-ytile-downscaling:
- shard-iclb: [SKIP][115] ([i915#3701]) -> [PASS][116]
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-iclb2/igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-16bpp-ytile-downscaling.html
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-iclb1/igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-16bpp-ytile-downscaling.html
* igt@kms_frontbuffer_tracking@fbc-1p-pri-indfb-multidraw:
- {shard-dg1}: [SKIP][117] ([i915#5721]) -> [PASS][118]
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-dg1-17/igt@[email protected]
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-dg1-16/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbc-2p-primscrn-spr-indfb-draw-blt:
- shard-glk: [FAIL][119] ([i915#1888] / [i915#2546]) -> [PASS][120]
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-glk1/igt@[email protected]
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-glk1/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbcpsr-1p-rte:
- {shard-rkl}: [SKIP][121] ([i915#1849] / [i915#4098]) -> [PASS][122] +14 similar issues
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-rkl-1/igt@[email protected]
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-rkl-6/igt@[email protected]
* igt@kms_hdr@bpc-switch-suspend@pipe-a-dp-1:
- shard-apl: [DMESG-WARN][123] ([i915#180]) -> [PASS][124] +3 similar issues
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-apl8/igt@kms_hdr@[email protected]
[124]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-apl7/igt@kms_hdr@[email protected]
* igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a:
- shard-skl: [INCOMPLETE][125] ([i915#4444]) -> [PASS][126]
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-skl4/igt@[email protected]
[126]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-skl7/igt@[email protected]
* igt@kms_plane@plane-panning-top-left@pipe-b-planes:
- {shard-rkl}: [SKIP][127] ([i915#3558]) -> [PASS][128] +1 similar issue
[127]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-rkl-1/igt@kms_plane@[email protected]
[128]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-rkl-6/igt@kms_plane@[email protected]
* igt@kms_plane_alpha_blend@pipe-a-alpha-opaque-fb:
- {shard-rkl}: [SKIP][129] ([i915#1849] / [i915#4070] / [i915#4098]) -> [PASS][130] +1 similar issue
[129]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-rkl-1/igt@[email protected]
[130]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-rkl-6/igt@[email protected]
* igt@kms_plane_scaling@planes-unity-scaling-downscale-factor-0-5@pipe-a-edp-1:
- shard-iclb: [SKIP][131] ([i915#5235]) -> [PASS][132] +2 similar issues
[131]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-iclb2/igt@kms_plane_scaling@[email protected]
[132]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-iclb3/igt@kms_plane_scaling@[email protected]
* igt@kms_psr@cursor_render:
- {shard-rkl}: [SKIP][133] ([i915#1072]) -> [PASS][134]
[133]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-rkl-1/igt@kms_psr@cursor_render.html
[134]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-rkl-6/igt@kms_psr@cursor_render.html
* igt@kms_psr@psr2_primary_blt:
- shard-iclb: [SKIP][135] ([fdo#109441]) -> [PASS][136]
[135]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-iclb4/igt@kms_psr@psr2_primary_blt.html
[136]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-iclb2/igt@kms_psr@psr2_primary_blt.html
* igt@kms_sequence@get-forked-busy@hdmi-a-1-pipe-b:
- {shard-dg1}: [FAIL][137] -> [PASS][138] +3 similar issues
[137]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-dg1-17/igt@kms_sequence@[email protected]
[138]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-dg1-16/igt@kms_sequence@[email protected]
* igt@kms_vblank@pipe-a-wait-forked-busy-hang:
- {shard-rkl}: [SKIP][139] ([i915#1845] / [i915#4098]) -> [PASS][140] +10 similar issues
[139]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-rkl-1/igt@[email protected]
[140]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-rkl-6/igt@[email protected]
* igt@kms_vblank@pipe-b-wait-busy:
- {shard-dg1}: [FAIL][141] ([i915#4241]) -> [PASS][142] +1 similar issue
[141]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-dg1-17/igt@[email protected]
[142]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-dg1-16/igt@[email protected]
* igt@prime_vgem@basic-fence-flip:
- {shard-rkl}: [SKIP][143] ([fdo#109295] / [i915#3708] / [i915#4098]) -> [PASS][144]
[143]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-rkl-1/igt@[email protected]
[144]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-rkl-6/igt@[email protected]
#### Warnings ####
* igt@gem_exec_fair@basic-none-rrul@rcs0:
- shard-iclb: [FAIL][145] ([i915#2852]) -> [FAIL][146] ([i915#2842])
[145]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-iclb2/igt@gem_exec_fair@[email protected]
[146]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-iclb3/igt@gem_exec_fair@[email protected]
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-draw-blt:
- shard-skl: [SKIP][147] ([fdo#109271] / [i915#1888]) -> [SKIP][148] ([fdo#109271]) +1 similar issue
[147]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-skl7/igt@[email protected]
[148]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-skl9/igt@[email protected]
* igt@kms_psr2_sf@cursor-plane-update-sf:
- shard-iclb: [SKIP][149] ([fdo#111068] / [i915#658]) -> [SKIP][150] ([i915#2920])
[149]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-iclb1/igt@[email protected]
[150]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-iclb2/igt@[email protected]
* igt@kms_psr2_sf@overlay-plane-move-continuous-sf:
- shard-iclb: [SKIP][151] ([i915#2920]) -> [SKIP][152] ([i915#658])
[151]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-iclb2/igt@[email protected]
[152]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-iclb1/igt@[email protected]
* igt@kms_psr2_sf@plane-move-sf-dmg-area:
- shard-iclb: [SKIP][153] ([i915#2920]) -> [SKIP][154] ([fdo#111068] / [i915#658])
[153]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-iclb2/igt@[email protected]
[154]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-iclb3/igt@[email protected]
* igt@kms_psr2_su@page_flip-p010:
- shard-iclb: [SKIP][155] ([fdo#109642] / [fdo#111068] / [i915#658]) -> [FAIL][156] ([i915#5939])
[155]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-iclb4/igt@kms_psr2_su@page_flip-p010.html
[156]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-iclb2/igt@kms_psr2_su@page_flip-p010.html
* igt@runner@aborted:
- shard-skl: ([FAIL][157], [FAIL][158]) ([i915#3002] / [i915#4312] / [i915#5257]) -> ([FAIL][159], [FAIL][160], [FAIL][161], [FAIL][162]) ([i915#2029] / [i915#3002] / [i915#4312] / [i915#5257])
[157]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-skl10/igt@[email protected]
[158]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11726/shard-skl9/igt@[email protected]
[159]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-skl1/igt@[email protected]
[160]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-skl10/igt@[email protected]
[161]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-skl2/igt@[email protected]
[162]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/shard-skl6/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#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109279]: https://bugs.freedesktop.org/show_bug.cgi?id=109279
[fdo#109283]: https://bugs.freedesktop.org/show_bug.cgi?id=109283
[fdo#109291]: https://bugs.freedesktop.org/show_bug.cgi?id=109291
[fdo#109295]: https://bugs.freedesktop.org/show_bug.cgi?id=109295
[fdo#109300]: https://bugs.freedesktop.org/show_bug.cgi?id=109300
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#109642]: https://bugs.freedesktop.org/show_bug.cgi?id=109642
[fdo#110254]: https://bugs.freedesktop.org/show_bug.cgi?id=110254
[fdo#110723]: https://bugs.freedesktop.org/show_bug.cgi?id=110723
[fdo#111068]: https://bugs.freedesktop.org/show_bug.cgi?id=111068
[fdo#111314]: https://bugs.freedesktop.org/show_bug.cgi?id=111314
[fdo#111614]: https://bugs.freedesktop.org/show_bug.cgi?id=111614
[fdo#111615]: https://bugs.freedesktop.org/show_bug.cgi?id=111615
[fdo#111825]: https://bugs.freedesktop.org/show_bug.cgi?id=111825
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[fdo#112022]: https://bugs.freedesktop.org/show_bug.cgi?id=112022
[i915#1072]: https://gitlab.freedesktop.org/drm/intel/issues/1072
[i915#1099]: https://gitlab.freedesktop.org/drm/intel/issues/1099
[i915#1149]: https://gitlab.freedesktop.org/drm/intel/issues/1149
[i915#1257]: https://gitlab.freedesktop.org/drm/intel/issues/1257
[i915#1319]: https://gitlab.freedesktop.org/drm/intel/issues/1319
[i915#132]: https://gitlab.freedesktop.org/drm/intel/issues/132
[i915#1397]: https://gitlab.freedesktop.org/drm/intel/issues/1397
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#1825]: https://gitlab.freedesktop.org/drm/intel/issues/1825
[i915#1836]: https://gitlab.freedesktop.org/drm/intel/issues/1836
[i915#1845]: https://gitlab.freedesktop.org/drm/intel/issues/1845
[i915#1849]: https://gitlab.freedesktop.org/drm/intel/issues/1849
[i915#1888]: https://gitlab.freedesktop.org/drm/intel/issues/1888
[i915#1911]: https://gitlab.freedesktop.org/drm/intel/issues/1911
[i915#2029]: https://gitlab.freedesktop.org/drm/intel/issues/2029
[i915#2122]: https://gitlab.freedesktop.org/drm/intel/issues/2122
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#2346]: https://gitlab.freedesktop.org/drm/intel/issues/2346
[i915#2546]: https://gitlab.freedesktop.org/drm/intel/issues/2546
[i915#2582]: https://gitlab.freedesktop.org/drm/intel/issues/2582
[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#2842]: https://gitlab.freedesktop.org/drm/intel/issues/2842
[i915#2852]: https://gitlab.freedesktop.org/drm/intel/issues/2852
[i915#2867]: https://gitlab.freedesktop.org/drm/intel/issues/2867
[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#3012]: https://gitlab.freedesktop.org/drm/intel/issues/3012
[i915#3070]: https://gitlab.freedesktop.org/drm/intel/issues/3070
[i915#3282]: https://gitlab.freedesktop.org/drm/intel/issues/3282
[i915#3297]: https://gitlab.freedesktop.org/drm/intel/issues/3297
[i915#3318]: https://gitlab.freedesktop.org/drm/intel/issues/3318
[i915#3319]: https://gitlab.freedesktop.org/drm/intel/issues/3319
[i915#3323]: https://gitlab.freedesktop.org/drm/intel/issues/3323
[i915#3359]: https://gitlab.freedesktop.org/drm/intel/issues/3359
[i915#3458]: https://gitlab.freedesktop.org/drm/intel/issues/3458
[i915#3536]: https://gitlab.freedesktop.org/drm/intel/issues/3536
[i915#3555]: https://gitlab.freedesktop.org/drm/intel/issues/3555
[i915#3558]: https://gitlab.freedesktop.org/drm/intel/issues/3558
[i915#3637]: https://gitlab.freedesktop.org/drm/intel/issues/3637
[i915#3638]: https://gitlab.freedesktop.org/drm/intel/issues/3638
[i915#3689]: https://gitlab.freedesktop.org/drm/intel/issues/3689
[i915#3701]: https://gitlab.freedesktop.org/drm/intel/issues/3701
[i915#3708]: https://gitlab.freedesktop.org/drm/intel/issues/3708
[i915#3734]: https://gitlab.freedesktop.org/drm/intel/issues/3734
[i915#3886]: https://gitlab.freedesktop.org/drm/intel/issues/3886
[i915#3963]: https://gitlab.freedesktop.org/drm/intel/issues/3963
[i915#3989]: https://gitlab.freedesktop.org/drm/intel/issues/3989
[i915#4016]: https://gitlab.freedesktop.org/drm/intel/issues/4016
[i915#4032]: https://gitlab.freedesktop.org/drm/intel/issues/4032
[i915#4070]: https://gitlab.freedesktop.org/drm/intel/issues/4070
[i915#4098]: https://gitlab.freedesktop.org/drm/intel/issues/4098
[i915#4241]: https://gitlab.freedesktop.org/drm/intel/issues/4241
[i915#4258]: https://gitlab.freedesktop.org/drm/intel/issues/4258
[i915#4278]: https://gitlab.freedesktop.org/drm/intel/issues/4278
[i915#4312]: https://gitlab.freedesktop.org/drm/intel/issues/4312
[i915#433]: https://gitlab.freedesktop.org/drm/intel/issues/433
[i915#4369]: https://gitlab.freedesktop.org/drm/intel/issues/4369
[i915#4444]: https://gitlab.freedesktop.org/drm/intel/issues/4444
[i915#4494]: https://gitlab.freedesktop.org/drm/intel/issues/4494
[i915#4525]: https://gitlab.freedesktop.org/drm/intel/issues/4525
[i915#4538]: https://gitlab.freedesktop.org/drm/intel/issues/4538
[i915#454]: https://gitlab.freedesktop.org/drm/intel/issues/454
[i915#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613
[i915#4839]: https://gitlab.freedesktop.org/drm/intel/issues/4839
[i915#4911]: https://gitlab.freedesktop.org/drm/intel/issues/4911
[i915#4957]: https://gitlab.freedesktop.org/drm/intel/issues/4957
[i915#4991]: https://gitlab.freedesktop.org/drm/intel/issues/4991
[i915#51]: https://gitlab.freedesktop.org/drm/intel/issues/51
[i915#5176]: https://gitlab.freedesktop.org/drm/intel/issues/5176
[i915#5183]: https://gitlab.freedesktop.org/drm/intel/issues/5183
[i915#5235]: https://gitlab.freedesktop.org/drm/intel/issues/5235
[i915#5257]: https://gitlab.freedesktop.org/drm/intel/issues/5257
[i915#5286]: https://gitlab.freedesktop.org/drm/intel/issues/5286
[i915#5287]: https://gitlab.freedesktop.org/drm/intel/issues/5287
[i915#5289]: https://gitlab.freedesktop.org/drm/intel/issues/5289
[i915#533]: https://gitlab.freedesktop.org/drm/intel/issues/533
[i915#5566]: https://gitlab.freedesktop.org/drm/intel/issues/5566
[i915#5713]: https://gitlab.freedesktop.org/drm/intel/issues/5713
[i915#5721]: https://gitlab.freedesktop.org/drm/intel/issues/5721
[i915#5939]: https://gitlab.freedesktop.org/drm/intel/issues/5939
[i915#6140]: https://gitlab.freedesktop.org/drm/intel/issues/6140
[i915#6141]: https://gitlab.freedesktop.org/drm/intel/issues/6141
[i915#658]: https://gitlab.freedesktop.org/drm/intel/issues/658
[i915#716]: https://gitlab.freedesktop.org/drm/intel/issues/716
Build changes
-------------
* Linux: CI_DRM_11726 -> Patchwork_104711v1
CI-20190529: 20190529
CI_DRM_11726: 74ea63ad8ffc71b8345436147517253dcabd4793 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6505: edb1a467fb622b23b927e28ff603fa43851fea97 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_104711v1: 74ea63ad8ffc71b8345436147517253dcabd4793 @ git://anongit.freedesktop.org/gfx-ci/linux
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_104711v1/index.html