[PATCH v3 0/8] Fixes and updates when using AUX backlight using Luminance

[PATCH v3 0/8] Fixes and updates when using AUX backlight using Luminance

[Suraj Kandpal]

This series aims to fix/update some code with respect to AUX backlight
via luminance values for both VESA and INTEL HDR codepaths.
The below are the major changes made in this series.
- Do not allow 0 brightness  by default which makes the screen go blank
leaving user with no way to see the screen and increase brightness.
- Take into account luminance_set variable when we decide which funcs
need to be enabled
- Update debug logs to make them more concise and help debug which
code path was taken

Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>

Suraj Kandpal (8):
  drm/i915/backlight: Use default/max brightness for VESA AUX backlight
    init
  drm/i915/backlight: Use intel_panel variable instead of
    intel_connector
  drm/i915/backlight: Take luminance_set into account for VESA backlight
  drm/i915/backlight: Check luminance_set when disabling PWM via AUX
    VESA backlight
  drm/i915/backlight: Short circuit intel_dp_aux_supports_hdr_backlight
  drm/i915/backlight: Update debug log during backlight setup
  drm/i915/backlight: Provide clear description on how backlight level
    is controlled
  drm/i915/backlight: Use default/max brightness for INTEL AUX HDR
    backlight init

 .../drm/i915/display/intel_dp_aux_backlight.c | 40 ++++++++++++++-----
 1 file changed, 29 insertions(+), 11 deletions(-)

-- 
2.34.1

[PATCH v3 1/8] drm/i915/backlight: Use default/max brightness for VESA AUX backlight init

[Suraj Kandpal]

If the brightness fetched from VBT/previous state is 0 on backlight
initialization, then set the brightness to a default/max value.
Whenever the minimum brightness is reported as 0 there are chances
we end up with blank screen. This confuses the user into thinking
the display is acting weird. This occurs in eDP 1.5 when
we are using PANEL_LUMINANCE_OVERRIDE mode to mainpulate brightness
via luminance values.

Closes: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/15671
Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
Reviewed-by: Arun R Murthy <arun.r.murthy@intel.com>
---
v1 -> v2:
- Let users set brightness to 0, make it so that it's just not
done by default (Arun)

v2 -> v3:
-Update commit header and message (Arun)

 drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c b/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
index eb05ef4bd9f6..c40ce310ad97 100644
--- a/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
+++ b/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
@@ -564,6 +564,8 @@ static int intel_dp_aux_vesa_setup_backlight(struct intel_connector *connector,
 		}
 		panel->backlight.level = intel_dp_aux_vesa_get_backlight(connector, 0);
 		panel->backlight.enabled = panel->backlight.level != 0;
+		if (!panel->backlight.level)
+			panel->backlight.level = panel->backlight.max;
 		drm_dbg_kms(display->drm,
 			    "[CONNECTOR:%d:%s] AUX VESA Nits backlight level is controlled through DPCD\n",
 			    connector->base.base.id, connector->base.name);
@@ -573,6 +575,8 @@ static int intel_dp_aux_vesa_setup_backlight(struct intel_connector *connector,
 		if (current_mode == DP_EDP_BACKLIGHT_CONTROL_MODE_DPCD) {
 			panel->backlight.level = current_level;
 			panel->backlight.enabled = panel->backlight.level != 0;
+			if (!panel->backlight.level)
+				panel->backlight.level = panel->backlight.max;
 		} else {
 			panel->backlight.level = panel->backlight.max;
 			panel->backlight.enabled = false;
-- 
2.34.1

Re: [PATCH v3 1/8] drm/i915/backlight: Use default/max brightness for VESA AUX backlight init

[Jani Nikula]

On Tue, 24 Feb 2026, Suraj Kandpal <suraj.kandpal@intel.com> wrote:
> If the brightness fetched from VBT/previous state is 0 on backlight
> initialization, then set the brightness to a default/max value.
> Whenever the minimum brightness is reported as 0 there are chances
> we end up with blank screen. This confuses the user into thinking
> the display is acting weird. This occurs in eDP 1.5 when
> we are using PANEL_LUMINANCE_OVERRIDE mode to mainpulate brightness
> via luminance values.
>
> Closes: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/15671
> Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
> Reviewed-by: Arun R Murthy <arun.r.murthy@intel.com>
> ---
> v1 -> v2:
> - Let users set brightness to 0, make it so that it's just not
> done by default (Arun)
>
> v2 -> v3:
> -Update commit header and message (Arun)
>
>  drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c | 4 ++++
>  1 file changed, 4 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c b/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
> index eb05ef4bd9f6..c40ce310ad97 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
> +++ b/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
> @@ -564,6 +564,8 @@ static int intel_dp_aux_vesa_setup_backlight(struct intel_connector *connector,
>  		}
>  		panel->backlight.level = intel_dp_aux_vesa_get_backlight(connector, 0);
>  		panel->backlight.enabled = panel->backlight.level != 0;
> +		if (!panel->backlight.level)
> +			panel->backlight.level = panel->backlight.max;

How does this help when .enabled is still based on level != 0 above?

>  		drm_dbg_kms(display->drm,
>  			    "[CONNECTOR:%d:%s] AUX VESA Nits backlight level is controlled through DPCD\n",
>  			    connector->base.base.id, connector->base.name);
> @@ -573,6 +575,8 @@ static int intel_dp_aux_vesa_setup_backlight(struct intel_connector *connector,
>  		if (current_mode == DP_EDP_BACKLIGHT_CONTROL_MODE_DPCD) {
>  			panel->backlight.level = current_level;
>  			panel->backlight.enabled = panel->backlight.level != 0;
> +			if (!panel->backlight.level)
> +				panel->backlight.level = panel->backlight.max;

Ditto.

>  		} else {
>  			panel->backlight.level = panel->backlight.max;
>  			panel->backlight.enabled = false;

-- 
Jani Nikula, Intel

RE: [PATCH v3 1/8] drm/i915/backlight: Use default/max brightness for VESA AUX backlight init

[Kandpal, Suraj]

> Subject: Re: [PATCH v3 1/8] drm/i915/backlight: Use default/max brightness for
> VESA AUX backlight init
> 
> On Tue, 24 Feb 2026, Suraj Kandpal <suraj.kandpal@intel.com> wrote:
> > If the brightness fetched from VBT/previous state is 0 on backlight
> > initialization, then set the brightness to a default/max value.
> > Whenever the minimum brightness is reported as 0 there are chances we
> > end up with blank screen. This confuses the user into thinking the
> > display is acting weird. This occurs in eDP 1.5 when we are using
> > PANEL_LUMINANCE_OVERRIDE mode to mainpulate brightness via luminance
> > values.
> >
> > Closes: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/15671
> > Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
> > Reviewed-by: Arun R Murthy <arun.r.murthy@intel.com>
> > ---
> > v1 -> v2:
> > - Let users set brightness to 0, make it so that it's just not done by
> > default (Arun)
> >
> > v2 -> v3:
> > -Update commit header and message (Arun)
> >
> >  drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c | 4 ++++
> >  1 file changed, 4 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
> > b/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
> > index eb05ef4bd9f6..c40ce310ad97 100644
> > --- a/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
> > +++ b/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
> > @@ -564,6 +564,8 @@ static int intel_dp_aux_vesa_setup_backlight(struct
> intel_connector *connector,
> >  		}
> >  		panel->backlight.level =
> intel_dp_aux_vesa_get_backlight(connector, 0);
> >  		panel->backlight.enabled = panel->backlight.level != 0;
> > +		if (!panel->backlight.level)
> > +			panel->backlight.level = panel->backlight.max;
> 
> How does this help when .enabled is still based on level != 0 above?
> 

Well we keep the backlight.enabled as false if we read a 0 back from the DPCD or the current level state is 0.
This is to maintain the policy that if during setup we get 0 as backlight value eDP backlight is currently disabled
(which means __intel_backlight_enable needs be called). We then change the current level to max so that when
backlight enable is called after setup from intel_backlight_update, we enable backlight with max level so that we
do not end up with a blank screen. This is also where we set backlight.enabled = true.
This is  to tackle different eDP behavior where, some preserve the last brightness value programmed in them (in that case
users want the same brightness to continue) while others don't and just 0 it out instead of having some default value (in that
case we keep backlight.enabled = false later to be made true during the __intel_backlight_enable call).
We face these scenarios in some compositors during the pass key phase where the compositor is still totally not doing everything and does not send
us any explicit brightness value to set thinking eDP would have some basic default value of it's own . We end up getting a 0 from DPCD and we enable and set the backlight enable with 0 value which anyways later causes us to call backlight disable.
In this case during authentication in some compositors like Fedora there are cases where we do not get a explicitly backlight value till the user has to blindly enter their
Passkey, after which the compositor sends us some sane value which we then program.

Regards,
Suraj Kandpal

> >  		drm_dbg_kms(display->drm,
> >  			    "[CONNECTOR:%d:%s] AUX VESA Nits backlight level
> is controlled through DPCD\n",
> >  			    connector->base.base.id, connector->base.name);
> @@ -573,6
> > +575,8 @@ static int intel_dp_aux_vesa_setup_backlight(struct
> intel_connector *connector,
> >  		if (current_mode ==
> DP_EDP_BACKLIGHT_CONTROL_MODE_DPCD) {
> >  			panel->backlight.level = current_level;
> >  			panel->backlight.enabled = panel->backlight.level != 0;
> > +			if (!panel->backlight.level)
> > +				panel->backlight.level = panel->backlight.max;
> 
> Ditto.
> 
> >  		} else {
> >  			panel->backlight.level = panel->backlight.max;
> >  			panel->backlight.enabled = false;
> 
> --
> Jani Nikula, Intel

RE: [PATCH v3 1/8] drm/i915/backlight: Use default/max brightness for VESA AUX backlight init

[Jani Nikula]

On Wed, 25 Feb 2026, "Kandpal, Suraj" <suraj.kandpal@intel.com> wrote:
>> Subject: Re: [PATCH v3 1/8] drm/i915/backlight: Use default/max brightness for
>> VESA AUX backlight init
>> 
>> On Tue, 24 Feb 2026, Suraj Kandpal <suraj.kandpal@intel.com> wrote:
>> > If the brightness fetched from VBT/previous state is 0 on backlight
>> > initialization, then set the brightness to a default/max value.
>> > Whenever the minimum brightness is reported as 0 there are chances we
>> > end up with blank screen. This confuses the user into thinking the
>> > display is acting weird. This occurs in eDP 1.5 when we are using
>> > PANEL_LUMINANCE_OVERRIDE mode to mainpulate brightness via luminance
>> > values.
>> >
>> > Closes: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/15671
>> > Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
>> > Reviewed-by: Arun R Murthy <arun.r.murthy@intel.com>
>> > ---
>> > v1 -> v2:
>> > - Let users set brightness to 0, make it so that it's just not done by
>> > default (Arun)
>> >
>> > v2 -> v3:
>> > -Update commit header and message (Arun)
>> >
>> >  drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c | 4 ++++
>> >  1 file changed, 4 insertions(+)
>> >
>> > diff --git a/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
>> > b/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
>> > index eb05ef4bd9f6..c40ce310ad97 100644
>> > --- a/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
>> > +++ b/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
>> > @@ -564,6 +564,8 @@ static int intel_dp_aux_vesa_setup_backlight(struct
>> intel_connector *connector,
>> >  		}
>> >  		panel->backlight.level =
>> intel_dp_aux_vesa_get_backlight(connector, 0);
>> >  		panel->backlight.enabled = panel->backlight.level != 0;
>> > +		if (!panel->backlight.level)
>> > +			panel->backlight.level = panel->backlight.max;
>> 
>> How does this help when .enabled is still based on level != 0 above?
>> 
>
> Well we keep the backlight.enabled as false if we read a 0 back from the DPCD or the current level state is 0.
> This is to maintain the policy that if during setup we get 0 as backlight value eDP backlight is currently disabled
> (which means __intel_backlight_enable needs be called). We then change the current level to max so that when
> backlight enable is called after setup from intel_backlight_update, we enable backlight with max level so that we
> do not end up with a blank screen. This is also where we set backlight.enabled = true.
> This is  to tackle different eDP behavior where, some preserve the last brightness value programmed in them (in that case
> users want the same brightness to continue) while others don't and just 0 it out instead of having some default value (in that
> case we keep backlight.enabled = false later to be made true during the __intel_backlight_enable call).
> We face these scenarios in some compositors during the pass key phase where the compositor is still totally not doing everything and does not send
> us any explicit brightness value to set thinking eDP would have some basic default value of it's own . We end up getting a 0 from DPCD and we enable and set the backlight enable with 0 value which anyways later causes us to call backlight disable.
> In this case during authentication in some compositors like Fedora there are cases where we do not get a explicitly backlight value till the user has to blindly enter their
> Passkey, after which the compositor sends us some sane value which we then program.

There's a long history of problems with the PWM backlight unexpectedly
going from 0 to max.

BR,
Jani.

>
> Regards,
> Suraj Kandpal
>
>> >  		drm_dbg_kms(display->drm,
>> >  			    "[CONNECTOR:%d:%s] AUX VESA Nits backlight level
>> is controlled through DPCD\n",
>> >  			    connector->base.base.id, connector->base.name);
>> @@ -573,6
>> > +575,8 @@ static int intel_dp_aux_vesa_setup_backlight(struct
>> intel_connector *connector,
>> >  		if (current_mode ==
>> DP_EDP_BACKLIGHT_CONTROL_MODE_DPCD) {
>> >  			panel->backlight.level = current_level;
>> >  			panel->backlight.enabled = panel->backlight.level != 0;
>> > +			if (!panel->backlight.level)
>> > +				panel->backlight.level = panel->backlight.max;
>> 
>> Ditto.
>> 
>> >  		} else {
>> >  			panel->backlight.level = panel->backlight.max;
>> >  			panel->backlight.enabled = false;
>> 
>> --
>> Jani Nikula, Intel

-- 
Jani Nikula, Intel

RE: [PATCH v3 1/8] drm/i915/backlight: Use default/max brightness for VESA AUX backlight init

[Kandpal, Suraj]

> Subject: RE: [PATCH v3 1/8] drm/i915/backlight: Use default/max brightness for
> VESA AUX backlight init
> 
> On Wed, 25 Feb 2026, "Kandpal, Suraj" <suraj.kandpal@intel.com> wrote:
> >> Subject: Re: [PATCH v3 1/8] drm/i915/backlight: Use default/max
> >> brightness for VESA AUX backlight init
> >>
> >> On Tue, 24 Feb 2026, Suraj Kandpal <suraj.kandpal@intel.com> wrote:
> >> > If the brightness fetched from VBT/previous state is 0 on backlight
> >> > initialization, then set the brightness to a default/max value.
> >> > Whenever the minimum brightness is reported as 0 there are chances
> >> > we end up with blank screen. This confuses the user into thinking
> >> > the display is acting weird. This occurs in eDP 1.5 when we are
> >> > using PANEL_LUMINANCE_OVERRIDE mode to mainpulate brightness via
> >> > luminance values.
> >> >
> >> > Closes:
> >> > https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/15671
> >> > Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
> >> > Reviewed-by: Arun R Murthy <arun.r.murthy@intel.com>
> >> > ---
> >> > v1 -> v2:
> >> > - Let users set brightness to 0, make it so that it's just not done
> >> > by default (Arun)
> >> >
> >> > v2 -> v3:
> >> > -Update commit header and message (Arun)
> >> >
> >> >  drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c | 4 ++++
> >> >  1 file changed, 4 insertions(+)
> >> >
> >> > diff --git a/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
> >> > b/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
> >> > index eb05ef4bd9f6..c40ce310ad97 100644
> >> > --- a/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
> >> > +++ b/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
> >> > @@ -564,6 +564,8 @@ static int
> >> > intel_dp_aux_vesa_setup_backlight(struct
> >> intel_connector *connector,
> >> >  		}
> >> >  		panel->backlight.level =
> >> intel_dp_aux_vesa_get_backlight(connector, 0);
> >> >  		panel->backlight.enabled = panel->backlight.level != 0;
> >> > +		if (!panel->backlight.level)
> >> > +			panel->backlight.level = panel->backlight.max;
> >>
> >> How does this help when .enabled is still based on level != 0 above?
> >>
> >
> > Well we keep the backlight.enabled as false if we read a 0 back from the DPCD
> or the current level state is 0.
> > This is to maintain the policy that if during setup we get 0 as
> > backlight value eDP backlight is currently disabled (which means
> > __intel_backlight_enable needs be called). We then change the current
> > level to max so that when backlight enable is called after setup from
> intel_backlight_update, we enable backlight with max level so that we do not
> end up with a blank screen. This is also where we set backlight.enabled = true.
> > This is  to tackle different eDP behavior where, some preserve the
> > last brightness value programmed in them (in that case users want the
> > same brightness to continue) while others don't and just 0 it out instead of
> having some default value (in that case we keep backlight.enabled = false later
> to be made true during the __intel_backlight_enable call).
> > We face these scenarios in some compositors during the pass key phase
> > where the compositor is still totally not doing everything and does not send
> us any explicit brightness value to set thinking eDP would have some basic
> default value of it's own . We end up getting a 0 from DPCD and we enable and
> set the backlight enable with 0 value which anyways later causes us to call
> backlight disable.
> > In this case during authentication in some compositors like Fedora
> > there are cases where we do not get a explicitly backlight value till the user
> has to blindly enter their Passkey, after which the compositor sends us some
> sane value which we then program.
> 
> There's a long history of problems with the PWM backlight unexpectedly going
> from 0 to max.

Right but at least with this now luminance values will continue if DPCD maintains its state if we get a value back, otherwise we set a
Default value.
Can we proceed with getting this merged ? Would really help the user.

Regards,
Suraj Kandpal

> 
> BR,
> Jani.
> 
> >
> > Regards,
> > Suraj Kandpal
> >
> >> >  		drm_dbg_kms(display->drm,
> >> >  			    "[CONNECTOR:%d:%s] AUX VESA Nits backlight level
> >> is controlled through DPCD\n",
> >> >  			    connector->base.base.id, connector->base.name);
> >> @@ -573,6
> >> > +575,8 @@ static int intel_dp_aux_vesa_setup_backlight(struct
> >> intel_connector *connector,
> >> >  		if (current_mode ==
> >> DP_EDP_BACKLIGHT_CONTROL_MODE_DPCD) {
> >> >  			panel->backlight.level = current_level;
> >> >  			panel->backlight.enabled = panel->backlight.level != 0;
> >> > +			if (!panel->backlight.level)
> >> > +				panel->backlight.level = panel->backlight.max;
> >>
> >> Ditto.
> >>
> >> >  		} else {
> >> >  			panel->backlight.level = panel->backlight.max;
> >> >  			panel->backlight.enabled = false;
> >>
> >> --
> >> Jani Nikula, Intel
> 
> --
> Jani Nikula, Intel

RE: [PATCH v3 1/8] drm/i915/backlight: Use default/max brightness for VESA AUX backlight init

[Jani Nikula]

On Mon, 02 Mar 2026, "Kandpal, Suraj" <suraj.kandpal@intel.com> wrote:
>> Subject: RE: [PATCH v3 1/8] drm/i915/backlight: Use default/max brightness for
>> VESA AUX backlight init
>> 
>> On Wed, 25 Feb 2026, "Kandpal, Suraj" <suraj.kandpal@intel.com> wrote:
>> >> Subject: Re: [PATCH v3 1/8] drm/i915/backlight: Use default/max
>> >> brightness for VESA AUX backlight init
>> >>
>> >> On Tue, 24 Feb 2026, Suraj Kandpal <suraj.kandpal@intel.com> wrote:
>> >> > If the brightness fetched from VBT/previous state is 0 on backlight
>> >> > initialization, then set the brightness to a default/max value.
>> >> > Whenever the minimum brightness is reported as 0 there are chances
>> >> > we end up with blank screen. This confuses the user into thinking
>> >> > the display is acting weird. This occurs in eDP 1.5 when we are
>> >> > using PANEL_LUMINANCE_OVERRIDE mode to mainpulate brightness via
>> >> > luminance values.
>> >> >
>> >> > Closes:
>> >> > https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/15671
>> >> > Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
>> >> > Reviewed-by: Arun R Murthy <arun.r.murthy@intel.com>
>> >> > ---
>> >> > v1 -> v2:
>> >> > - Let users set brightness to 0, make it so that it's just not done
>> >> > by default (Arun)
>> >> >
>> >> > v2 -> v3:
>> >> > -Update commit header and message (Arun)
>> >> >
>> >> >  drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c | 4 ++++
>> >> >  1 file changed, 4 insertions(+)
>> >> >
>> >> > diff --git a/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
>> >> > b/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
>> >> > index eb05ef4bd9f6..c40ce310ad97 100644
>> >> > --- a/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
>> >> > +++ b/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
>> >> > @@ -564,6 +564,8 @@ static int
>> >> > intel_dp_aux_vesa_setup_backlight(struct
>> >> intel_connector *connector,
>> >> >  		}
>> >> >  		panel->backlight.level =
>> >> intel_dp_aux_vesa_get_backlight(connector, 0);
>> >> >  		panel->backlight.enabled = panel->backlight.level != 0;
>> >> > +		if (!panel->backlight.level)
>> >> > +			panel->backlight.level = panel->backlight.max;
>> >>
>> >> How does this help when .enabled is still based on level != 0 above?
>> >>
>> >
>> > Well we keep the backlight.enabled as false if we read a 0 back from the DPCD
>> or the current level state is 0.
>> > This is to maintain the policy that if during setup we get 0 as
>> > backlight value eDP backlight is currently disabled (which means
>> > __intel_backlight_enable needs be called). We then change the current
>> > level to max so that when backlight enable is called after setup from
>> intel_backlight_update, we enable backlight with max level so that we do not
>> end up with a blank screen. This is also where we set backlight.enabled = true.
>> > This is  to tackle different eDP behavior where, some preserve the
>> > last brightness value programmed in them (in that case users want the
>> > same brightness to continue) while others don't and just 0 it out instead of
>> having some default value (in that case we keep backlight.enabled = false later
>> to be made true during the __intel_backlight_enable call).
>> > We face these scenarios in some compositors during the pass key phase
>> > where the compositor is still totally not doing everything and does not send
>> us any explicit brightness value to set thinking eDP would have some basic
>> default value of it's own . We end up getting a 0 from DPCD and we enable and
>> set the backlight enable with 0 value which anyways later causes us to call
>> backlight disable.
>> > In this case during authentication in some compositors like Fedora
>> > there are cases where we do not get a explicitly backlight value till the user
>> has to blindly enter their Passkey, after which the compositor sends us some
>> sane value which we then program.
>> 
>> There's a long history of problems with the PWM backlight unexpectedly going
>> from 0 to max.
>
> Right but at least with this now luminance values will continue if DPCD maintains its state if we get a value back, otherwise we set a
> Default value.

What's the brightness control mode *before* we enable luminance control?

When taking over, we should try to read the current brightness setting
with the current brightness control method. If we're switching to
luminance control, the existing luminance value is meaningless.

AFAICT drm_edp_backlight_probe_state() uses bl->luminance_set to
determine the value to read, not the current mode. At a glance, seems
wrong to me.

Of course, regressions have priority, so a revert should also be a
consideration before quickly going for adding level = max in there.

> Can we proceed with getting this merged ? Would really help the user.

The real problem with quick fixes to help the user is that they have the
potential to make it a lot harder for a lot more users and developers in
the long run.


BR,
Jani.

>
> Regards,
> Suraj Kandpal
>
>> 
>> BR,
>> Jani.
>> 
>> >
>> > Regards,
>> > Suraj Kandpal
>> >
>> >> >  		drm_dbg_kms(display->drm,
>> >> >  			    "[CONNECTOR:%d:%s] AUX VESA Nits backlight level
>> >> is controlled through DPCD\n",
>> >> >  			    connector->base.base.id, connector->base.name);
>> >> @@ -573,6
>> >> > +575,8 @@ static int intel_dp_aux_vesa_setup_backlight(struct
>> >> intel_connector *connector,
>> >> >  		if (current_mode ==
>> >> DP_EDP_BACKLIGHT_CONTROL_MODE_DPCD) {
>> >> >  			panel->backlight.level = current_level;
>> >> >  			panel->backlight.enabled = panel->backlight.level != 0;
>> >> > +			if (!panel->backlight.level)
>> >> > +				panel->backlight.level = panel->backlight.max;
>> >>
>> >> Ditto.
>> >>
>> >> >  		} else {
>> >> >  			panel->backlight.level = panel->backlight.max;
>> >> >  			panel->backlight.enabled = false;
>> >>
>> >> --
>> >> Jani Nikula, Intel
>> 
>> --
>> Jani Nikula, Intel

-- 
Jani Nikula, Intel

RE: [PATCH v3 1/8] drm/i915/backlight: Use default/max brightness for VESA AUX backlight init

[Kandpal, Suraj]

> Subject: RE: [PATCH v3 1/8] drm/i915/backlight: Use default/max brightness for
> VESA AUX backlight init
> 
> On Mon, 02 Mar 2026, "Kandpal, Suraj" <suraj.kandpal@intel.com> wrote:
> >> Subject: RE: [PATCH v3 1/8] drm/i915/backlight: Use default/max
> >> brightness for VESA AUX backlight init
> >>
> >> On Wed, 25 Feb 2026, "Kandpal, Suraj" <suraj.kandpal@intel.com> wrote:
> >> >> Subject: Re: [PATCH v3 1/8] drm/i915/backlight: Use default/max
> >> >> brightness for VESA AUX backlight init
> >> >>
> >> >> On Tue, 24 Feb 2026, Suraj Kandpal <suraj.kandpal@intel.com> wrote:
> >> >> > If the brightness fetched from VBT/previous state is 0 on
> >> >> > backlight initialization, then set the brightness to a default/max value.
> >> >> > Whenever the minimum brightness is reported as 0 there are
> >> >> > chances we end up with blank screen. This confuses the user into
> >> >> > thinking the display is acting weird. This occurs in eDP 1.5
> >> >> > when we are using PANEL_LUMINANCE_OVERRIDE mode to mainpulate
> >> >> > brightness via luminance values.
> >> >> >
> >> >> > Closes:
> >> >> > https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/15671
> >> >> > Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
> >> >> > Reviewed-by: Arun R Murthy <arun.r.murthy@intel.com>
> >> >> > ---
> >> >> > v1 -> v2:
> >> >> > - Let users set brightness to 0, make it so that it's just not
> >> >> > done by default (Arun)
> >> >> >
> >> >> > v2 -> v3:
> >> >> > -Update commit header and message (Arun)
> >> >> >
> >> >> >  drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c | 4 ++++
> >> >> >  1 file changed, 4 insertions(+)
> >> >> >
> >> >> > diff --git
> >> >> > a/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
> >> >> > b/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
> >> >> > index eb05ef4bd9f6..c40ce310ad97 100644
> >> >> > --- a/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
> >> >> > +++ b/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
> >> >> > @@ -564,6 +564,8 @@ static int
> >> >> > intel_dp_aux_vesa_setup_backlight(struct
> >> >> intel_connector *connector,
> >> >> >  		}
> >> >> >  		panel->backlight.level =
> >> >> intel_dp_aux_vesa_get_backlight(connector, 0);
> >> >> >  		panel->backlight.enabled = panel->backlight.level != 0;
> >> >> > +		if (!panel->backlight.level)
> >> >> > +			panel->backlight.level = panel->backlight.max;
> >> >>
> >> >> How does this help when .enabled is still based on level != 0 above?
> >> >>
> >> >
> >> > Well we keep the backlight.enabled as false if we read a 0 back
> >> > from the DPCD
> >> or the current level state is 0.
> >> > This is to maintain the policy that if during setup we get 0 as
> >> > backlight value eDP backlight is currently disabled (which means
> >> > __intel_backlight_enable needs be called). We then change the
> >> > current level to max so that when backlight enable is called after
> >> > setup from
> >> intel_backlight_update, we enable backlight with max level so that we
> >> do not end up with a blank screen. This is also where we set
> backlight.enabled = true.
> >> > This is  to tackle different eDP behavior where, some preserve the
> >> > last brightness value programmed in them (in that case users want
> >> > the same brightness to continue) while others don't and just 0 it
> >> > out instead of
> >> having some default value (in that case we keep backlight.enabled =
> >> false later to be made true during the __intel_backlight_enable call).
> >> > We face these scenarios in some compositors during the pass key
> >> > phase where the compositor is still totally not doing everything
> >> > and does not send
> >> us any explicit brightness value to set thinking eDP would have some
> >> basic default value of it's own . We end up getting a 0 from DPCD and
> >> we enable and set the backlight enable with 0 value which anyways
> >> later causes us to call backlight disable.
> >> > In this case during authentication in some compositors like Fedora
> >> > there are cases where we do not get a explicitly backlight value
> >> > till the user
> >> has to blindly enter their Passkey, after which the compositor sends
> >> us some sane value which we then program.
> >>
> >> There's a long history of problems with the PWM backlight
> >> unexpectedly going from 0 to max.
> >
> > Right but at least with this now luminance values will continue if
> > DPCD maintains its state if we get a value back, otherwise we set a Default
> value.
> 
> What's the brightness control mode *before* we enable luminance control?
> 
> When taking over, we should try to read the current brightness setting with the
> current brightness control method. If we're switching to luminance control, the
> existing luminance value is meaningless.
> 
> AFAICT drm_edp_backlight_probe_state() uses bl->luminance_set to determine
> the value to read, not the current mode. At a glance, seems wrong to me.

Luminance mode is the current mode. Which we determine that by checking different capabilities from the and setting them
In this case aux_set and aux_enable to represent them.

[    1.667694] i915 0000:00:02.0: [drm:drm_edp_backlight_init [drm_display_helper]] AUX A/DDI A/PHY A: Found backlight: aux_set=1 aux_enable=0 mode=0
[    1.667703] i915 0000:00:02.0: [drm:drm_edp_backlight_init [drm_display_helper]] AUX A/DDI A/PHY A: Backlight caps: level=496/496 pwm_freq_pre_divider=0 lsb_reg_used=1

In this case aux_set = 1 and luminance_set = 1 which means we are in luminance mode

> 
> Of course, regressions have priority, so a revert should also be a consideration
> before quickly going for adding level = max in there.
> 

From what I can see
We are in Luminance Mode to begin with. From logs there is a level mentioned in VBT should we use that ?

[    1.665632] i915 0000:00:02.0: [drm:intel_bios_init_panel [i915]] Panel type (VBT): 255
[    1.665770] i915 0000:00:02.0: [drm:pnpid_get_panel_type [i915]] EDID manufacturer name: SDC, product code: 16899, serial number: 0, year of manufacture: 2024
[    1.665890] i915 0000:00:02.0: [drm:pnpid_get_panel_type [i915]] EDID raw product id: 4c 83 03 42 00 00 00 00 00 22
[    1.666006] i915 0000:00:02.0: [drm:intel_bios_init_panel [i915]] Panel type (fallback): 0
[    1.666124] i915 0000:00:02.0: [drm:intel_bios_init_panel [i915]] Selected panel type (fallback): 0
[    1.666235] i915 0000:00:02.0: [drm:intel_bios_init_panel [i915]] DRRS supported mode is seamless
[    1.666346] i915 0000:00:02.0: [drm:intel_bios_init_panel [i915]] Found panel mode in BIOS VBT legacy lfp table: "640x480": 63 25180 640 648 744 784 480 482 484 509 0x8 0xa
[    1.666454] i915 0000:00:02.0: [drm:intel_bios_init_panel [i915]] Panel manufacturer name: @H@, product code: 0, serial number: 0, year of manufacture: 1990
[    1.666560] i915 0000:00:02.0: [drm:intel_bios_init_panel [i915]] Panel name: LFP_PanelName
[    1.666665] i915 0000:00:02.0: [drm:intel_bios_init_panel [i915]] Seamless DRRS min refresh rate: 0 Hz
[    1.666757] i915 0000:00:02.0: [drm:intel_bios_init_panel [i915]] VBT backlight PWM modulation frequency 200 Hz, active high, min brightness 0, level 255, controller 0
[    1.666847] i915 0000:00:02.0: [drm:intel_panel_add_edid_fixed_modes [i915]] [CONNECTOR:502:eDP-1] using preferred EDID fixed mode: "2880x1800": 60 709633 2880 2888 2920 3080 1800 3800 3816 3840 0x48 0xa
[    1.666931] i915 0000:00:02.0: [drm:intel_panel_add_edid_fixed_modes [i915]] [CONNECTOR:502:eDP-1] using alternate EDID fixed mode: "2880x1800": 120 709633 2880 2888 2920 3080 1800 1880 1896 1920 0x40 0xa
[    1.667117] mmc0: SDHCI controller on PCI [0000:58:00.0] using ADMA
[    1.667206] i915 0000:00:02.0: [drm:drm_dp_dpcd_read [drm_display_helper]] AUX A/DDI A/PHY A: 0x007a4 AUX -> (ret=  1) 00
[    1.667223] i915 0000:00:02.0: [drm:intel_dp_aux_init_backlight_funcs [i915]] [CONNECTOR:502:eDP-1] AUX Luminance Based Backlight Control Supported!
[    1.667335] i915 0000:00:02.0: [drm:intel_dp_aux_init_backlight_funcs [i915]] [CONNECTOR:502:eDP-1] Using VESA eDP backlight controls
[    1.667413] i915 0000:00:02.0: [drm:intel_panel_init [i915]] [CONNECTOR:502:eDP-1] DRRS type: none

VBT here says use level 255 would it be okay if we set that to level as VBT level, if no value is returned from DPCD panel.

Regards,
Suraj Kandpal

> > Can we proceed with getting this merged ? Would really help the user.
> 
> The real problem with quick fixes to help the user is that they have the
> potential to make it a lot harder for a lot more users and developers in the long
> run.
> 
> 
> BR,
> Jani.
> 
> >
> > Regards,
> > Suraj Kandpal
> >
> >>
> >> BR,
> >> Jani.
> >>
> >> >
> >> > Regards,
> >> > Suraj Kandpal
> >> >
> >> >> >  		drm_dbg_kms(display->drm,
> >> >> >  			    "[CONNECTOR:%d:%s] AUX VESA Nits
> backlight level
> >> >> is controlled through DPCD\n",
> >> >> >  			    connector->base.base.id, connector-
> >base.name);
> >> >> @@ -573,6
> >> >> > +575,8 @@ static int intel_dp_aux_vesa_setup_backlight(struct
> >> >> intel_connector *connector,
> >> >> >  		if (current_mode ==
> >> >> DP_EDP_BACKLIGHT_CONTROL_MODE_DPCD) {
> >> >> >  			panel->backlight.level = current_level;
> >> >> >  			panel->backlight.enabled = panel-
> >backlight.level != 0;
> >> >> > +			if (!panel->backlight.level)
> >> >> > +				panel->backlight.level = panel-
> >backlight.max;
> >> >>
> >> >> Ditto.
> >> >>
> >> >> >  		} else {
> >> >> >  			panel->backlight.level = panel->backlight.max;
> >> >> >  			panel->backlight.enabled = false;
> >> >>
> >> >> --
> >> >> Jani Nikula, Intel
> >>
> >> --
> >> Jani Nikula, Intel
> 
> --
> Jani Nikula, Intel

RE: [PATCH v3 1/8] drm/i915/backlight: Use default/max brightness for VESA AUX backlight init

[Jani Nikula]

On Mon, 02 Mar 2026, "Kandpal, Suraj" <suraj.kandpal@intel.com> wrote:
>> Subject: RE: [PATCH v3 1/8] drm/i915/backlight: Use default/max brightness for
>> VESA AUX backlight init
>> 
>> On Mon, 02 Mar 2026, "Kandpal, Suraj" <suraj.kandpal@intel.com> wrote:
>> >> Subject: RE: [PATCH v3 1/8] drm/i915/backlight: Use default/max
>> >> brightness for VESA AUX backlight init
>> >>
>> >> On Wed, 25 Feb 2026, "Kandpal, Suraj" <suraj.kandpal@intel.com> wrote:
>> >> >> Subject: Re: [PATCH v3 1/8] drm/i915/backlight: Use default/max
>> >> >> brightness for VESA AUX backlight init
>> >> >>
>> >> >> On Tue, 24 Feb 2026, Suraj Kandpal <suraj.kandpal@intel.com> wrote:
>> >> >> > If the brightness fetched from VBT/previous state is 0 on
>> >> >> > backlight initialization, then set the brightness to a default/max value.
>> >> >> > Whenever the minimum brightness is reported as 0 there are
>> >> >> > chances we end up with blank screen. This confuses the user into
>> >> >> > thinking the display is acting weird. This occurs in eDP 1.5
>> >> >> > when we are using PANEL_LUMINANCE_OVERRIDE mode to mainpulate
>> >> >> > brightness via luminance values.
>> >> >> >
>> >> >> > Closes:
>> >> >> > https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/15671
>> >> >> > Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
>> >> >> > Reviewed-by: Arun R Murthy <arun.r.murthy@intel.com>
>> >> >> > ---
>> >> >> > v1 -> v2:
>> >> >> > - Let users set brightness to 0, make it so that it's just not
>> >> >> > done by default (Arun)
>> >> >> >
>> >> >> > v2 -> v3:
>> >> >> > -Update commit header and message (Arun)
>> >> >> >
>> >> >> >  drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c | 4 ++++
>> >> >> >  1 file changed, 4 insertions(+)
>> >> >> >
>> >> >> > diff --git
>> >> >> > a/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
>> >> >> > b/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
>> >> >> > index eb05ef4bd9f6..c40ce310ad97 100644
>> >> >> > --- a/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
>> >> >> > +++ b/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
>> >> >> > @@ -564,6 +564,8 @@ static int
>> >> >> > intel_dp_aux_vesa_setup_backlight(struct
>> >> >> intel_connector *connector,
>> >> >> >  		}
>> >> >> >  		panel->backlight.level =
>> >> >> intel_dp_aux_vesa_get_backlight(connector, 0);
>> >> >> >  		panel->backlight.enabled = panel->backlight.level != 0;
>> >> >> > +		if (!panel->backlight.level)
>> >> >> > +			panel->backlight.level = panel->backlight.max;
>> >> >>
>> >> >> How does this help when .enabled is still based on level != 0 above?
>> >> >>
>> >> >
>> >> > Well we keep the backlight.enabled as false if we read a 0 back
>> >> > from the DPCD
>> >> or the current level state is 0.
>> >> > This is to maintain the policy that if during setup we get 0 as
>> >> > backlight value eDP backlight is currently disabled (which means
>> >> > __intel_backlight_enable needs be called). We then change the
>> >> > current level to max so that when backlight enable is called after
>> >> > setup from
>> >> intel_backlight_update, we enable backlight with max level so that we
>> >> do not end up with a blank screen. This is also where we set
>> backlight.enabled = true.
>> >> > This is  to tackle different eDP behavior where, some preserve the
>> >> > last brightness value programmed in them (in that case users want
>> >> > the same brightness to continue) while others don't and just 0 it
>> >> > out instead of
>> >> having some default value (in that case we keep backlight.enabled =
>> >> false later to be made true during the __intel_backlight_enable call).
>> >> > We face these scenarios in some compositors during the pass key
>> >> > phase where the compositor is still totally not doing everything
>> >> > and does not send
>> >> us any explicit brightness value to set thinking eDP would have some
>> >> basic default value of it's own . We end up getting a 0 from DPCD and
>> >> we enable and set the backlight enable with 0 value which anyways
>> >> later causes us to call backlight disable.
>> >> > In this case during authentication in some compositors like Fedora
>> >> > there are cases where we do not get a explicitly backlight value
>> >> > till the user
>> >> has to blindly enter their Passkey, after which the compositor sends
>> >> us some sane value which we then program.
>> >>
>> >> There's a long history of problems with the PWM backlight
>> >> unexpectedly going from 0 to max.
>> >
>> > Right but at least with this now luminance values will continue if
>> > DPCD maintains its state if we get a value back, otherwise we set a Default
>> value.
>> 
>> What's the brightness control mode *before* we enable luminance control?
>> 
>> When taking over, we should try to read the current brightness setting with the
>> current brightness control method. If we're switching to luminance control, the
>> existing luminance value is meaningless.
>> 
>> AFAICT drm_edp_backlight_probe_state() uses bl->luminance_set to determine
>> the value to read, not the current mode. At a glance, seems wrong to me.
>
> Luminance mode is the current mode. Which we determine that by checking different capabilities from the and setting them
> In this case aux_set and aux_enable to represent them.

The question is not about the panel's *ability* to use luminance mode,
it's about whether that mode was set and in use by GOP/pre-os.

BR,
Jani.

>
> [    1.667694] i915 0000:00:02.0: [drm:drm_edp_backlight_init [drm_display_helper]] AUX A/DDI A/PHY A: Found backlight: aux_set=1 aux_enable=0 mode=0
> [    1.667703] i915 0000:00:02.0: [drm:drm_edp_backlight_init [drm_display_helper]] AUX A/DDI A/PHY A: Backlight caps: level=496/496 pwm_freq_pre_divider=0 lsb_reg_used=1
>
> In this case aux_set = 1 and luminance_set = 1 which means we are in luminance mode
>
>> 
>> Of course, regressions have priority, so a revert should also be a consideration
>> before quickly going for adding level = max in there.
>> 
>
> From what I can see
> We are in Luminance Mode to begin with. From logs there is a level mentioned in VBT should we use that ?
>
> [    1.665632] i915 0000:00:02.0: [drm:intel_bios_init_panel [i915]] Panel type (VBT): 255
> [    1.665770] i915 0000:00:02.0: [drm:pnpid_get_panel_type [i915]] EDID manufacturer name: SDC, product code: 16899, serial number: 0, year of manufacture: 2024
> [    1.665890] i915 0000:00:02.0: [drm:pnpid_get_panel_type [i915]] EDID raw product id: 4c 83 03 42 00 00 00 00 00 22
> [    1.666006] i915 0000:00:02.0: [drm:intel_bios_init_panel [i915]] Panel type (fallback): 0
> [    1.666124] i915 0000:00:02.0: [drm:intel_bios_init_panel [i915]] Selected panel type (fallback): 0
> [    1.666235] i915 0000:00:02.0: [drm:intel_bios_init_panel [i915]] DRRS supported mode is seamless
> [    1.666346] i915 0000:00:02.0: [drm:intel_bios_init_panel [i915]] Found panel mode in BIOS VBT legacy lfp table: "640x480": 63 25180 640 648 744 784 480 482 484 509 0x8 0xa
> [    1.666454] i915 0000:00:02.0: [drm:intel_bios_init_panel [i915]] Panel manufacturer name: @H@, product code: 0, serial number: 0, year of manufacture: 1990
> [    1.666560] i915 0000:00:02.0: [drm:intel_bios_init_panel [i915]] Panel name: LFP_PanelName
> [    1.666665] i915 0000:00:02.0: [drm:intel_bios_init_panel [i915]] Seamless DRRS min refresh rate: 0 Hz
> [    1.666757] i915 0000:00:02.0: [drm:intel_bios_init_panel [i915]] VBT backlight PWM modulation frequency 200 Hz, active high, min brightness 0, level 255, controller 0
> [    1.666847] i915 0000:00:02.0: [drm:intel_panel_add_edid_fixed_modes [i915]] [CONNECTOR:502:eDP-1] using preferred EDID fixed mode: "2880x1800": 60 709633 2880 2888 2920 3080 1800 3800 3816 3840 0x48 0xa
> [    1.666931] i915 0000:00:02.0: [drm:intel_panel_add_edid_fixed_modes [i915]] [CONNECTOR:502:eDP-1] using alternate EDID fixed mode: "2880x1800": 120 709633 2880 2888 2920 3080 1800 1880 1896 1920 0x40 0xa
> [    1.667117] mmc0: SDHCI controller on PCI [0000:58:00.0] using ADMA
> [    1.667206] i915 0000:00:02.0: [drm:drm_dp_dpcd_read [drm_display_helper]] AUX A/DDI A/PHY A: 0x007a4 AUX -> (ret=  1) 00
> [    1.667223] i915 0000:00:02.0: [drm:intel_dp_aux_init_backlight_funcs [i915]] [CONNECTOR:502:eDP-1] AUX Luminance Based Backlight Control Supported!
> [    1.667335] i915 0000:00:02.0: [drm:intel_dp_aux_init_backlight_funcs [i915]] [CONNECTOR:502:eDP-1] Using VESA eDP backlight controls
> [    1.667413] i915 0000:00:02.0: [drm:intel_panel_init [i915]] [CONNECTOR:502:eDP-1] DRRS type: none
>
> VBT here says use level 255 would it be okay if we set that to level as VBT level, if no value is returned from DPCD panel.
>
> Regards,
> Suraj Kandpal
>
>> > Can we proceed with getting this merged ? Would really help the user.
>> 
>> The real problem with quick fixes to help the user is that they have the
>> potential to make it a lot harder for a lot more users and developers in the long
>> run.
>> 
>> 
>> BR,
>> Jani.
>> 
>> >
>> > Regards,
>> > Suraj Kandpal
>> >
>> >>
>> >> BR,
>> >> Jani.
>> >>
>> >> >
>> >> > Regards,
>> >> > Suraj Kandpal
>> >> >
>> >> >> >  		drm_dbg_kms(display->drm,
>> >> >> >  			    "[CONNECTOR:%d:%s] AUX VESA Nits
>> backlight level
>> >> >> is controlled through DPCD\n",
>> >> >> >  			    connector->base.base.id, connector-
>> >base.name);
>> >> >> @@ -573,6
>> >> >> > +575,8 @@ static int intel_dp_aux_vesa_setup_backlight(struct
>> >> >> intel_connector *connector,
>> >> >> >  		if (current_mode ==
>> >> >> DP_EDP_BACKLIGHT_CONTROL_MODE_DPCD) {
>> >> >> >  			panel->backlight.level = current_level;
>> >> >> >  			panel->backlight.enabled = panel-
>> >backlight.level != 0;
>> >> >> > +			if (!panel->backlight.level)
>> >> >> > +				panel->backlight.level = panel-
>> >backlight.max;
>> >> >>
>> >> >> Ditto.
>> >> >>
>> >> >> >  		} else {
>> >> >> >  			panel->backlight.level = panel->backlight.max;
>> >> >> >  			panel->backlight.enabled = false;
>> >> >>
>> >> >> --
>> >> >> Jani Nikula, Intel
>> >>
>> >> --
>> >> Jani Nikula, Intel
>> 
>> --
>> Jani Nikula, Intel

-- 
Jani Nikula, Intel

RE: [PATCH v3 1/8] drm/i915/backlight: Use default/max brightness for VESA AUX backlight init

[Kandpal, Suraj]

> Subject: RE: [PATCH v3 1/8] drm/i915/backlight: Use default/max brightness for
> VESA AUX backlight init
> 
> On Mon, 02 Mar 2026, "Kandpal, Suraj" <suraj.kandpal@intel.com> wrote:
> >> Subject: RE: [PATCH v3 1/8] drm/i915/backlight: Use default/max
> >> brightness for VESA AUX backlight init
> >>
> >> On Wed, 25 Feb 2026, "Kandpal, Suraj" <suraj.kandpal@intel.com> wrote:
> >> >> Subject: Re: [PATCH v3 1/8] drm/i915/backlight: Use default/max
> >> >> brightness for VESA AUX backlight init
> >> >>
> >> >> On Tue, 24 Feb 2026, Suraj Kandpal <suraj.kandpal@intel.com> wrote:
> >> >> > If the brightness fetched from VBT/previous state is 0 on
> >> >> > backlight initialization, then set the brightness to a default/max value.
> >> >> > Whenever the minimum brightness is reported as 0 there are
> >> >> > chances we end up with blank screen. This confuses the user into
> >> >> > thinking the display is acting weird. This occurs in eDP 1.5
> >> >> > when we are using PANEL_LUMINANCE_OVERRIDE mode to mainpulate
> >> >> > brightness via luminance values.
> >> >> >
> >> >> > Closes:
> >> >> > https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/15671
> >> >> > Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
> >> >> > Reviewed-by: Arun R Murthy <arun.r.murthy@intel.com>
> >> >> > ---
> >> >> > v1 -> v2:
> >> >> > - Let users set brightness to 0, make it so that it's just not
> >> >> > done by default (Arun)
> >> >> >
> >> >> > v2 -> v3:
> >> >> > -Update commit header and message (Arun)
> >> >> >
> >> >> >  drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c | 4 ++++
> >> >> >  1 file changed, 4 insertions(+)
> >> >> >
> >> >> > diff --git
> >> >> > a/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
> >> >> > b/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
> >> >> > index eb05ef4bd9f6..c40ce310ad97 100644
> >> >> > --- a/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
> >> >> > +++ b/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
> >> >> > @@ -564,6 +564,8 @@ static int
> >> >> > intel_dp_aux_vesa_setup_backlight(struct
> >> >> intel_connector *connector,
> >> >> >  		}
> >> >> >  		panel->backlight.level =
> >> >> intel_dp_aux_vesa_get_backlight(connector, 0);
> >> >> >  		panel->backlight.enabled = panel->backlight.level != 0;
> >> >> > +		if (!panel->backlight.level)
> >> >> > +			panel->backlight.level = panel->backlight.max;
> >> >>
> >> >> How does this help when .enabled is still based on level != 0 above?
> >> >>
> >> >
> >> > Well we keep the backlight.enabled as false if we read a 0 back
> >> > from the DPCD
> >> or the current level state is 0.
> >> > This is to maintain the policy that if during setup we get 0 as
> >> > backlight value eDP backlight is currently disabled (which means
> >> > __intel_backlight_enable needs be called). We then change the
> >> > current level to max so that when backlight enable is called after
> >> > setup from
> >> intel_backlight_update, we enable backlight with max level so that we
> >> do not end up with a blank screen. This is also where we set
> backlight.enabled = true.
> >> > This is  to tackle different eDP behavior where, some preserve the
> >> > last brightness value programmed in them (in that case users want
> >> > the same brightness to continue) while others don't and just 0 it
> >> > out instead of
> >> having some default value (in that case we keep backlight.enabled =
> >> false later to be made true during the __intel_backlight_enable call).
> >> > We face these scenarios in some compositors during the pass key
> >> > phase where the compositor is still totally not doing everything
> >> > and does not send
> >> us any explicit brightness value to set thinking eDP would have some
> >> basic default value of it's own . We end up getting a 0 from DPCD and
> >> we enable and set the backlight enable with 0 value which anyways
> >> later causes us to call backlight disable.
> >> > In this case during authentication in some compositors like Fedora
> >> > there are cases where we do not get a explicitly backlight value
> >> > till the user
> >> has to blindly enter their Passkey, after which the compositor sends
> >> us some sane value which we then program.
> >>
> >> There's a long history of problems with the PWM backlight
> >> unexpectedly going from 0 to max.
> >
> > Right but at least with this now luminance values will continue if
> > DPCD maintains its state if we get a value back, otherwise we set a Default
> value.
> 
> What's the brightness control mode *before* we enable luminance control?
> 
> When taking over, we should try to read the current brightness setting with the
> current brightness control method. If we're switching to luminance control, the
> existing luminance value is meaningless.
> 
> AFAICT drm_edp_backlight_probe_state() uses bl->luminance_set to determine
> the value to read, not the current mode. At a glance, seems wrong to me.
> 
> Of course, regressions have priority, so a revert should also be a consideration
> before quickly going for adding level = max in there.
> 

I did some more digging and for aux_set enabled we really do not need to do get_backlight 
And read register again that is filled in probe state and fills up the current_level variable that can be use.
Check drm_edp_backlight_probe_state.
I also found this little comment there

        /*
         * If we're not in DPCD control mode yet, the programmed brightness value is meaningless and
         * the driver should assume max brightness
         */
        return bl->max;

So this was a policy that was decided during VESA AUX Backlight implementation time. Also that Mode will not be DPCD
Initially and will change later during backlight enable so we get to assume max brightness . That should be okay to do with
Luminance_set case too then.

Regards,
Suraj Kandpal

> > Can we proceed with getting this merged ? Would really help the user.
> 
> The real problem with quick fixes to help the user is that they have the
> potential to make it a lot harder for a lot more users and developers in the long
> run.
> 
> 
> BR,
> Jani.
> 
> >
> > Regards,
> > Suraj Kandpal
> >
> >>
> >> BR,
> >> Jani.
> >>
> >> >
> >> > Regards,
> >> > Suraj Kandpal
> >> >
> >> >> >  		drm_dbg_kms(display->drm,
> >> >> >  			    "[CONNECTOR:%d:%s] AUX VESA Nits
> backlight level
> >> >> is controlled through DPCD\n",
> >> >> >  			    connector->base.base.id, connector-
> >base.name);
> >> >> @@ -573,6
> >> >> > +575,8 @@ static int intel_dp_aux_vesa_setup_backlight(struct
> >> >> intel_connector *connector,
> >> >> >  		if (current_mode ==
> >> >> DP_EDP_BACKLIGHT_CONTROL_MODE_DPCD) {
> >> >> >  			panel->backlight.level = current_level;
> >> >> >  			panel->backlight.enabled = panel-
> >backlight.level != 0;
> >> >> > +			if (!panel->backlight.level)
> >> >> > +				panel->backlight.level = panel-
> >backlight.max;
> >> >>
> >> >> Ditto.
> >> >>
> >> >> >  		} else {
> >> >> >  			panel->backlight.level = panel->backlight.max;
> >> >> >  			panel->backlight.enabled = false;
> >> >>
> >> >> --
> >> >> Jani Nikula, Intel
> >>
> >> --
> >> Jani Nikula, Intel
> 
> --
> Jani Nikula, Intel

RE: [PATCH v3 1/8] drm/i915/backlight: Use default/max brightness for VESA AUX backlight init

[Jani Nikula]

On Wed, 04 Mar 2026, "Kandpal, Suraj" <suraj.kandpal@intel.com> wrote:
> I did some more digging and for aux_set enabled we really do not need to do get_backlight 
> And read register again that is filled in probe state and fills up the current_level variable that can be use.
> Check drm_edp_backlight_probe_state.
> I also found this little comment there
>
>         /*
>          * If we're not in DPCD control mode yet, the programmed brightness value is meaningless and
>          * the driver should assume max brightness
>          */
>         return bl->max;
>
> So this was a policy that was decided during VESA AUX Backlight implementation time. Also that Mode will not be DPCD
> Initially and will change later during backlight enable so we get to assume max brightness . That should be okay to do with
> Luminance_set case too then.

The comment says, if the panel is not in DPCD control mode, the value in
DPCD is meaningless.

Ditto, if the panel is not in luminance control mode (or whatever the
specific name for it is), the luminance value in DPCD is meaningless.

However, if the panel is in DPCD control mode but not in luminance
control mode, we should be able to read the non-luminance DPCD
brightness value and use that.

BR,
Jani.


-- 
Jani Nikula, Intel

[PATCH v3 2/8] drm/i915/backlight: Use intel_panel variable instead of intel_connector

[Suraj Kandpal]

Use the intel_panel variable since it has already been declared and
looks cleaner.

Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
Reviewed-by: Arun R Murthy <arun.r.murthy@intel.com>
---
 drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c b/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
index c40ce310ad97..05d6d033f60b 100644
--- a/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
+++ b/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
@@ -459,7 +459,7 @@ static u32 intel_dp_aux_vesa_get_backlight(struct intel_connector *connector, en
 		return val / 1000;
 	}
 
-	return connector->panel.backlight.level;
+	return panel->backlight.level;
 }
 
 static void
-- 
2.34.1

[PATCH v3 3/8] drm/i915/backlight: Take luminance_set into account for VESA backlight

[Suraj Kandpal]

When deciding what functions to enable to help control backlight we
used to only check aux_enable. Now with PANEL_LUMINANCE_OVERRIDE in
picture we need to take care that we do not enable PWM function if
luminance_set is set.

Closes: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/15671
Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
Reviewed-by: Arun R Murthy <arun.r.murthy@intel.com>
---
 drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c b/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
index 05d6d033f60b..cb39696491a1 100644
--- a/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
+++ b/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
@@ -486,7 +486,8 @@ intel_dp_aux_vesa_enable_backlight(const struct intel_crtc_state *crtc_state,
 	struct intel_panel *panel = &connector->panel;
 	struct intel_dp *intel_dp = enc_to_intel_dp(connector->encoder);
 
-	if (!panel->backlight.edp.vesa.info.aux_enable) {
+	if (!(panel->backlight.edp.vesa.info.aux_enable ||
+	      panel->backlight.edp.vesa.info.luminance_set)) {
 		u32 pwm_level;
 
 		if (!panel->backlight.edp.vesa.info.aux_set)
-- 
2.34.1

[PATCH v3 4/8] drm/i915/backlight: Check luminance_set when disabling PWM via AUX VESA backlight

[Suraj Kandpal]

When deciding what if PWM funcs need to be disabled take into account
luminance_set too. We do this since it is also used to decide if
we are enabling PWM backlight funcs or not.

Closes: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/15671
Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
Reviewed-by: Arun R Murthy <arun.r.murthy@intel.com>
---
 drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c b/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
index cb39696491a1..a921bb4ccacf 100644
--- a/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
+++ b/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
@@ -511,7 +511,8 @@ static void intel_dp_aux_vesa_disable_backlight(const struct drm_connector_state
 
 	drm_edp_backlight_disable(&intel_dp->aux, &panel->backlight.edp.vesa.info);
 
-	if (!panel->backlight.edp.vesa.info.aux_enable)
+	if (!(panel->backlight.edp.vesa.info.aux_enable ||
+	      panel->backlight.edp.vesa.info.luminance_set))
 		panel->backlight.pwm_funcs->disable(old_conn_state,
 						    intel_backlight_invert_pwm_level(connector, 0));
 }
-- 
2.34.1

[PATCH v3 5/8] drm/i915/backlight: Short circuit intel_dp_aux_supports_hdr_backlight

[Suraj Kandpal]

intel_dp_aux_supports_hdr_backlight() prints debug message for
intel HDR backlight version. This is fine when dealing with eDP 1.4b
and lower. When we are talking about eDP 1.5 it causes confusion in
logs since we need to use VESA AUX backlight functions but this
print causes confusion as to which path code take.
Short circuit this function with a eDP version check. Make sure this
is only called if eDP <= 1.4b

Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
Reviewed-by: Arun R Murthy <arun.r.murthy@intel.com>
---
 drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c b/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
index a921bb4ccacf..c7143869bafd 100644
--- a/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
+++ b/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
@@ -701,8 +701,8 @@ int intel_dp_aux_init_backlight_funcs(struct intel_connector *connector)
 	 * backlight interface at all. This means that the only sensible way for us to detect both
 	 * interfaces is to probe for Intel's first, and VESA's second.
 	 */
-	if (try_intel_interface && intel_dp_aux_supports_hdr_backlight(connector) &&
-	    intel_dp->edp_dpcd[0] <= DP_EDP_14b) {
+	if (try_intel_interface && intel_dp->edp_dpcd[0] <= DP_EDP_14b &&
+	    intel_dp_aux_supports_hdr_backlight(connector)) {
 		drm_dbg_kms(dev, "[CONNECTOR:%d:%s] Using Intel proprietary eDP backlight controls\n",
 			    connector->base.base.id, connector->base.name);
 		panel->backlight.funcs = &intel_dp_hdr_bl_funcs;
-- 
2.34.1

[PATCH v3 6/8] drm/i915/backlight: Update debug log during backlight setup

[Suraj Kandpal]

With luminance_set which represents PANEL_LUMINANCE_OVERRIDE, we
have another variable to decide if we use PWM or DPCD.
Make drm_dbg_kms log represent that.

Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
Reviewed-by: Arun R Murthy <arun.r.murthy@intel.com>
---
v1 -> v3:
- Make commit message simpler (Arun/Nemesa)

 drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c b/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
index c7143869bafd..043c9aef2ea6 100644
--- a/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
+++ b/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
@@ -539,7 +539,8 @@ static int intel_dp_aux_vesa_setup_backlight(struct intel_connector *connector,
 	drm_dbg_kms(display->drm,
 		    "[CONNECTOR:%d:%s] AUX VESA backlight enable is controlled through %s\n",
 		    connector->base.base.id, connector->base.name,
-		    dpcd_vs_pwm_str(panel->backlight.edp.vesa.info.aux_enable));
+		    dpcd_vs_pwm_str(panel->backlight.edp.vesa.info.aux_enable ||
+				    panel->backlight.edp.vesa.info.luminance_set));
 	drm_dbg_kms(display->drm,
 		    "[CONNECTOR:%d:%s] AUX VESA backlight level is controlled through %s\n",
 		    connector->base.base.id, connector->base.name,
-- 
2.34.1

[PATCH v3 7/8] drm/i915/backlight: Provide clear description on how backlight level is controlled

[Suraj Kandpal]

Currently it takes us multiple log prints to arrive at the conclusion
on how we are actually controlling backlight level. Make the logging
concise.

Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
Reviewed-by: Arun R Murthy <arun.r.murthy@intel.com>
---
 .../drm/i915/display/intel_dp_aux_backlight.c | 19 ++++++++++++++-----
 1 file changed, 14 insertions(+), 5 deletions(-)

diff --git a/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c b/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
index 043c9aef2ea6..aac6cdb5b69b 100644
--- a/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
+++ b/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
@@ -368,6 +368,16 @@ static const char *dpcd_vs_pwm_str(bool aux)
 	return aux ? "DPCD" : "PWM";
 }
 
+static const char *backlight_unit_str(struct intel_panel *panel)
+{
+	if (panel->backlight.edp.vesa.info.luminance_set)
+		return "NITS";
+	else if (panel->backlight.edp.vesa.info.aux_set)
+		return "Brightness %";
+	else
+		return "PWM";
+}
+
 static void
 intel_dp_aux_write_panel_luminance_override(struct intel_connector *connector)
 {
@@ -542,9 +552,11 @@ static int intel_dp_aux_vesa_setup_backlight(struct intel_connector *connector,
 		    dpcd_vs_pwm_str(panel->backlight.edp.vesa.info.aux_enable ||
 				    panel->backlight.edp.vesa.info.luminance_set));
 	drm_dbg_kms(display->drm,
-		    "[CONNECTOR:%d:%s] AUX VESA backlight level is controlled through %s\n",
+		    "[CONNECTOR:%d:%s] AUX VESA backlight level is controlled through %s using %s values\n",
 		    connector->base.base.id, connector->base.name,
-		    dpcd_vs_pwm_str(panel->backlight.edp.vesa.info.aux_set));
+		    dpcd_vs_pwm_str(panel->backlight.edp.vesa.info.aux_set ||
+				    panel->backlight.edp.vesa.info.luminance_set),
+		    backlight_unit_str(panel));
 
 	if (!panel->backlight.edp.vesa.info.aux_set ||
 	    !panel->backlight.edp.vesa.info.aux_enable) {
@@ -569,9 +581,6 @@ static int intel_dp_aux_vesa_setup_backlight(struct intel_connector *connector,
 		panel->backlight.enabled = panel->backlight.level != 0;
 		if (!panel->backlight.level)
 			panel->backlight.level = panel->backlight.max;
-		drm_dbg_kms(display->drm,
-			    "[CONNECTOR:%d:%s] AUX VESA Nits backlight level is controlled through DPCD\n",
-			    connector->base.base.id, connector->base.name);
 	} else if (panel->backlight.edp.vesa.info.aux_set) {
 		panel->backlight.max = panel->backlight.edp.vesa.info.max;
 		panel->backlight.min = 0;
-- 
2.34.1

[PATCH v3 8/8] drm/i915/backlight: Use default/max brightness for INTEL AUX HDR backlight init

[Suraj Kandpal]

If the brightness fetched from VBT/previous state is 0 on backlight
initialization, then set the brightness to a default/max value.
Whenever the minimum brightness is reported as 0 there are chances
we maybe sometimes end up with blank screen. This confuses the user
into thinking the display is acting weird. This occurs in eDP 1.4b
when we use proprietary INTEL AUX HDR DPCD registers to manipulate
brightness via luminance values.

Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
Reviewed-by: Arun R Murthy <arun.r.murthy@intel.com>
---
v1 -> v2:
- Let users set brightness to 0, make it so that it's just not
done by default (Arun)

v1 -> v2:
- Update commit header & message (Arun)

 drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c b/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
index aac6cdb5b69b..725370bcfa3b 100644
--- a/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
+++ b/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
@@ -442,6 +442,8 @@ intel_dp_aux_hdr_setup_backlight(struct intel_connector *connector, enum pipe pi
 
 	panel->backlight.level = intel_dp_aux_hdr_get_backlight(connector, pipe);
 	panel->backlight.enabled = panel->backlight.level != 0;
+	if (!panel->backlight.level)
+		panel->backlight.level = panel->backlight.max;
 
 	return 0;
 }
-- 
2.34.1

Re: [PATCH v3 8/8] drm/i915/backlight: Use default/max brightness for INTEL AUX HDR backlight init

[Jani Nikula]

On Tue, 24 Feb 2026, Suraj Kandpal <suraj.kandpal@intel.com> wrote:
> If the brightness fetched from VBT/previous state is 0 on backlight
> initialization, then set the brightness to a default/max value.
> Whenever the minimum brightness is reported as 0 there are chances
> we maybe sometimes end up with blank screen. This confuses the user
> into thinking the display is acting weird. This occurs in eDP 1.4b
> when we use proprietary INTEL AUX HDR DPCD registers to manipulate
> brightness via luminance values.
>
> Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
> Reviewed-by: Arun R Murthy <arun.r.murthy@intel.com>
> ---
> v1 -> v2:
> - Let users set brightness to 0, make it so that it's just not
> done by default (Arun)
>
> v1 -> v2:
> - Update commit header & message (Arun)
>
>  drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c b/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
> index aac6cdb5b69b..725370bcfa3b 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
> +++ b/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c
> @@ -442,6 +442,8 @@ intel_dp_aux_hdr_setup_backlight(struct intel_connector *connector, enum pipe pi
>  
>  	panel->backlight.level = intel_dp_aux_hdr_get_backlight(connector, pipe);
>  	panel->backlight.enabled = panel->backlight.level != 0;
> +	if (!panel->backlight.level)
> +		panel->backlight.level = panel->backlight.max;

Same here, .enabled is still based on level != 0 above.

>  
>  	return 0;
>  }

-- 
Jani Nikula, Intel

✓ i915.CI.BAT: success for Fixes and updates when using AUX backlight using Luminance (rev3)

[Patchwork]

[-- Attachment #1: Type: text/plain, Size: 2060 bytes --]

== Series Details ==

Series: Fixes and updates when using AUX backlight using Luminance (rev3)
URL   : https://patchwork.freedesktop.org/series/161578/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_18022 -> Patchwork_161578v3
====================================================

Summary
-------

  **SUCCESS**

  No regressions found.

  External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/index.html

Participating hosts (43 -> 41)
------------------------------

  Missing    (2): bat-dg2-13 fi-snb-2520m 

Known issues
------------

  Here are the changes found in Patchwork_161578v3 that come from known issues:

### IGT changes ###

#### Issues hit ####

  * igt@i915_selftest@live@late_gt_pm:
    - fi-cfl-8109u:       [PASS][1] -> [DMESG-WARN][2] ([i915#13735]) +130 other tests dmesg-warn
   [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/fi-cfl-8109u/igt@i915_selftest@live@late_gt_pm.html
   [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/fi-cfl-8109u/igt@i915_selftest@live@late_gt_pm.html

  
#### Possible fixes ####

  * igt@i915_selftest@live@workarounds:
    - bat-arls-6:         [DMESG-FAIL][3] ([i915#12061]) -> [PASS][4] +1 other test pass
   [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/bat-arls-6/igt@i915_selftest@live@workarounds.html
   [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/bat-arls-6/igt@i915_selftest@live@workarounds.html

  
  [i915#12061]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/12061
  [i915#13735]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13735


Build changes
-------------

  * Linux: CI_DRM_18022 -> Patchwork_161578v3

  CI-20190529: 20190529
  CI_DRM_18022: 45a3045fc0dc46a893cb8bbe304afafd4120c904 @ git://anongit.freedesktop.org/gfx-ci/linux
  IGT_8765: 8765
  Patchwork_161578v3: 45a3045fc0dc46a893cb8bbe304afafd4120c904 @ git://anongit.freedesktop.org/gfx-ci/linux

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/index.html

[-- Attachment #2: Type: text/html, Size: 2670 bytes --]

✗ i915.CI.Full: failure for Fixes and updates when using AUX backlight using Luminance (rev3)

[Patchwork]

[-- Attachment #1: Type: text/plain, Size: 72618 bytes --]

== Series Details ==

Series: Fixes and updates when using AUX backlight using Luminance (rev3)
URL   : https://patchwork.freedesktop.org/series/161578/
State : failure

== Summary ==

CI Bug Log - changes from CI_DRM_18022_full -> Patchwork_161578v3_full
====================================================

Summary
-------

  **FAILURE**

  Serious unknown changes coming with Patchwork_161578v3_full absolutely need to be
  verified manually.
  
  If you think the reported changes have nothing to do with the changes
  introduced in Patchwork_161578v3_full, please notify your bug team (I915-ci-infra@lists.freedesktop.org) to allow them
  to document this new failure mode, which will reduce false positives in CI.

  

Participating hosts (9 -> 9)
------------------------------

  No changes in participating hosts

Possible new issues
-------------------

  Here are the unknown changes that may have been introduced in Patchwork_161578v3_full:

### IGT changes ###

#### Possible regressions ####

  * igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size:
    - shard-glk:          NOTRUN -> [FAIL][1]
   [1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-glk1/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html

  * igt@kms_flip@flip-vs-dpms-on-nop@a-hdmi-a1:
    - shard-tglu-1:       NOTRUN -> [FAIL][2] +1 other test fail
   [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-1/igt@kms_flip@flip-vs-dpms-on-nop@a-hdmi-a1.html

  * igt@perf_pmu@module-unload:
    - shard-glk:          NOTRUN -> [ABORT][3]
   [3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-glk6/igt@perf_pmu@module-unload.html

  
Known issues
------------

  Here are the changes found in Patchwork_161578v3_full that come from known issues:

### IGT changes ###

#### Issues hit ####

  * igt@device_reset@cold-reset-bound:
    - shard-tglu:         NOTRUN -> [SKIP][4] ([i915#11078])
   [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-10/igt@device_reset@cold-reset-bound.html

  * igt@gem_ccs@block-copy-compressed:
    - shard-tglu:         NOTRUN -> [SKIP][5] ([i915#3555] / [i915#9323])
   [5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-10/igt@gem_ccs@block-copy-compressed.html

  * igt@gem_ccs@block-multicopy-compressed:
    - shard-rkl:          NOTRUN -> [SKIP][6] ([i915#9323])
   [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-7/igt@gem_ccs@block-multicopy-compressed.html
    - shard-tglu-1:       NOTRUN -> [SKIP][7] ([i915#9323])
   [7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-1/igt@gem_ccs@block-multicopy-compressed.html

  * igt@gem_ccs@suspend-resume@tile4-compressed-compfmt0-smem-lmem0:
    - shard-dg2:          NOTRUN -> [INCOMPLETE][8] ([i915#12392] / [i915#13356])
   [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-dg2-5/igt@gem_ccs@suspend-resume@tile4-compressed-compfmt0-smem-lmem0.html

  * igt@gem_close_race@multigpu-basic-process:
    - shard-snb:          NOTRUN -> [SKIP][9] +66 other tests skip
   [9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-snb1/igt@gem_close_race@multigpu-basic-process.html

  * igt@gem_create@create-ext-set-pat:
    - shard-rkl:          NOTRUN -> [SKIP][10] ([i915#8562])
   [10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-7/igt@gem_create@create-ext-set-pat.html
    - shard-tglu-1:       NOTRUN -> [SKIP][11] ([i915#8562])
   [11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-1/igt@gem_create@create-ext-set-pat.html

  * igt@gem_ctx_freq@sysfs:
    - shard-dg2:          [PASS][12] -> [FAIL][13] ([i915#9561]) +1 other test fail
   [12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-dg2-1/igt@gem_ctx_freq@sysfs.html
   [13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-dg2-1/igt@gem_ctx_freq@sysfs.html

  * igt@gem_ctx_isolation@preservation-s3:
    - shard-rkl:          [PASS][14] -> [INCOMPLETE][15] ([i915#13356]) +1 other test incomplete
   [14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-rkl-8/igt@gem_ctx_isolation@preservation-s3.html
   [15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-6/igt@gem_ctx_isolation@preservation-s3.html

  * igt@gem_ctx_isolation@preservation-s3@rcs0:
    - shard-glk:          NOTRUN -> [INCOMPLETE][16] ([i915#13356]) +2 other tests incomplete
   [16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-glk1/igt@gem_ctx_isolation@preservation-s3@rcs0.html

  * igt@gem_ctx_persistence@hang:
    - shard-snb:          NOTRUN -> [SKIP][17] ([i915#1099])
   [17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-snb1/igt@gem_ctx_persistence@hang.html

  * igt@gem_ctx_sseu@engines:
    - shard-tglu-1:       NOTRUN -> [SKIP][18] ([i915#280])
   [18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-1/igt@gem_ctx_sseu@engines.html

  * igt@gem_ctx_sseu@invalid-sseu:
    - shard-rkl:          NOTRUN -> [SKIP][19] ([i915#280])
   [19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-8/igt@gem_ctx_sseu@invalid-sseu.html

  * igt@gem_eio@in-flight-suspend:
    - shard-glk:          NOTRUN -> [INCOMPLETE][20] ([i915#13390])
   [20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-glk5/igt@gem_eio@in-flight-suspend.html

  * igt@gem_exec_balancer@parallel-keep-submit-fence:
    - shard-rkl:          NOTRUN -> [SKIP][21] ([i915#4525])
   [21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-4/igt@gem_exec_balancer@parallel-keep-submit-fence.html

  * igt@gem_exec_balancer@parallel-ordering:
    - shard-tglu-1:       NOTRUN -> [SKIP][22] ([i915#4525])
   [22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-1/igt@gem_exec_balancer@parallel-ordering.html

  * igt@gem_exec_big@single:
    - shard-mtlp:         NOTRUN -> [DMESG-FAIL][23] ([i915#15478])
   [23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-mtlp-6/igt@gem_exec_big@single.html

  * igt@gem_exec_capture@capture-invisible:
    - shard-rkl:          NOTRUN -> [SKIP][24] ([i915#6334]) +1 other test skip
   [24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-8/igt@gem_exec_capture@capture-invisible.html

  * igt@gem_exec_reloc@basic-gtt-wc-noreloc:
    - shard-rkl:          NOTRUN -> [SKIP][25] ([i915#3281]) +4 other tests skip
   [25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-7/igt@gem_exec_reloc@basic-gtt-wc-noreloc.html

  * igt@gem_exec_suspend@basic-s0@lmem0:
    - shard-dg2:          [PASS][26] -> [INCOMPLETE][27] ([i915#13356]) +1 other test incomplete
   [26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-dg2-8/igt@gem_exec_suspend@basic-s0@lmem0.html
   [27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-dg2-7/igt@gem_exec_suspend@basic-s0@lmem0.html

  * igt@gem_exec_suspend@basic-s4-devices:
    - shard-rkl:          [PASS][28] -> [ABORT][29] ([i915#7975]) +1 other test abort
   [28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-rkl-8/igt@gem_exec_suspend@basic-s4-devices.html
   [29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-1/igt@gem_exec_suspend@basic-s4-devices.html

  * igt@gem_lmem_swapping@heavy-random:
    - shard-mtlp:         NOTRUN -> [SKIP][30] ([i915#4613])
   [30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-mtlp-6/igt@gem_lmem_swapping@heavy-random.html

  * igt@gem_lmem_swapping@parallel-random-verify:
    - shard-tglu:         NOTRUN -> [SKIP][31] ([i915#4613]) +2 other tests skip
   [31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-10/igt@gem_lmem_swapping@parallel-random-verify.html

  * igt@gem_lmem_swapping@verify-ccs:
    - shard-glk:          NOTRUN -> [SKIP][32] ([i915#4613]) +3 other tests skip
   [32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-glk6/igt@gem_lmem_swapping@verify-ccs.html

  * igt@gem_tiled_partial_pwrite_pread@writes:
    - shard-rkl:          NOTRUN -> [SKIP][33] ([i915#3282]) +4 other tests skip
   [33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-4/igt@gem_tiled_partial_pwrite_pread@writes.html

  * igt@gem_userptr_blits@unsync-unmap-cycles:
    - shard-rkl:          NOTRUN -> [SKIP][34] ([i915#3297])
   [34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-8/igt@gem_userptr_blits@unsync-unmap-cycles.html

  * igt@gen9_exec_parse@batch-invalid-length:
    - shard-tglu:         NOTRUN -> [SKIP][35] ([i915#2527] / [i915#2856])
   [35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-10/igt@gen9_exec_parse@batch-invalid-length.html

  * igt@gen9_exec_parse@bb-oversize:
    - shard-rkl:          NOTRUN -> [SKIP][36] ([i915#2527]) +2 other tests skip
   [36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-7/igt@gen9_exec_parse@bb-oversize.html
    - shard-tglu-1:       NOTRUN -> [SKIP][37] ([i915#2527] / [i915#2856]) +2 other tests skip
   [37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-1/igt@gen9_exec_parse@bb-oversize.html

  * igt@i915_module_load@resize-bar:
    - shard-rkl:          NOTRUN -> [SKIP][38] ([i915#6412])
   [38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-8/igt@i915_module_load@resize-bar.html

  * igt@i915_pm_rc6_residency@rc6-fence:
    - shard-tglu-1:       NOTRUN -> [WARN][39] ([i915#13790] / [i915#2681]) +1 other test warn
   [39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-1/igt@i915_pm_rc6_residency@rc6-fence.html

  * igt@i915_pm_rc6_residency@rc6-idle:
    - shard-tglu:         NOTRUN -> [SKIP][40] ([i915#14498])
   [40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-10/igt@i915_pm_rc6_residency@rc6-idle.html

  * igt@i915_suspend@forcewake:
    - shard-glk:          NOTRUN -> [INCOMPLETE][41] ([i915#4817])
   [41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-glk9/igt@i915_suspend@forcewake.html

  * igt@kms_atomic_transition@plane-toggle-modeset-transition:
    - shard-dg2:          [PASS][42] -> [FAIL][43] ([i915#5956]) +1 other test fail
   [42]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-dg2-1/igt@kms_atomic_transition@plane-toggle-modeset-transition.html
   [43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-dg2-1/igt@kms_atomic_transition@plane-toggle-modeset-transition.html

  * igt@kms_big_fb@4-tiled-32bpp-rotate-180:
    - shard-rkl:          NOTRUN -> [SKIP][44] ([i915#5286]) +1 other test skip
   [44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-7/igt@kms_big_fb@4-tiled-32bpp-rotate-180.html

  * igt@kms_big_fb@4-tiled-8bpp-rotate-0:
    - shard-tglu-1:       NOTRUN -> [SKIP][45] ([i915#5286]) +2 other tests skip
   [45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-1/igt@kms_big_fb@4-tiled-8bpp-rotate-0.html

  * igt@kms_big_fb@4-tiled-max-hw-stride-32bpp-rotate-180-async-flip:
    - shard-tglu:         NOTRUN -> [SKIP][46] ([i915#5286]) +1 other test skip
   [46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-10/igt@kms_big_fb@4-tiled-max-hw-stride-32bpp-rotate-180-async-flip.html

  * igt@kms_big_fb@y-tiled-8bpp-rotate-90:
    - shard-rkl:          NOTRUN -> [SKIP][47] ([i915#3638]) +2 other tests skip
   [47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-8/igt@kms_big_fb@y-tiled-8bpp-rotate-90.html

  * igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-0:
    - shard-tglu-1:       NOTRUN -> [SKIP][48] +30 other tests skip
   [48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-1/igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-0.html

  * igt@kms_ccs@bad-aux-stride-4-tiled-mtl-mc-ccs@pipe-a-hdmi-a-4:
    - shard-dg1:          NOTRUN -> [SKIP][49] ([i915#6095]) +199 other tests skip
   [49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-dg1-18/igt@kms_ccs@bad-aux-stride-4-tiled-mtl-mc-ccs@pipe-a-hdmi-a-4.html

  * igt@kms_ccs@bad-rotation-90-y-tiled-gen12-mc-ccs@pipe-c-hdmi-a-2:
    - shard-rkl:          NOTRUN -> [SKIP][50] ([i915#14098] / [i915#6095]) +36 other tests skip
   [50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-4/igt@kms_ccs@bad-rotation-90-y-tiled-gen12-mc-ccs@pipe-c-hdmi-a-2.html

  * igt@kms_ccs@crc-primary-rotation-180-4-tiled-dg2-mc-ccs@pipe-a-hdmi-a-3:
    - shard-dg2:          NOTRUN -> [SKIP][51] ([i915#6095]) +51 other tests skip
   [51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-dg2-3/igt@kms_ccs@crc-primary-rotation-180-4-tiled-dg2-mc-ccs@pipe-a-hdmi-a-3.html

  * igt@kms_ccs@crc-primary-rotation-180-y-tiled-gen12-mc-ccs@pipe-b-hdmi-a-1:
    - shard-glk:          NOTRUN -> [SKIP][52] +249 other tests skip
   [52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-glk6/igt@kms_ccs@crc-primary-rotation-180-y-tiled-gen12-mc-ccs@pipe-b-hdmi-a-1.html

  * igt@kms_ccs@crc-primary-suspend-4-tiled-dg2-rc-ccs-cc@pipe-b-hdmi-a-1:
    - shard-tglu:         NOTRUN -> [SKIP][53] ([i915#6095]) +34 other tests skip
   [53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-10/igt@kms_ccs@crc-primary-suspend-4-tiled-dg2-rc-ccs-cc@pipe-b-hdmi-a-1.html

  * igt@kms_ccs@crc-primary-suspend-4-tiled-lnl-ccs:
    - shard-tglu-1:       NOTRUN -> [SKIP][54] ([i915#12805])
   [54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-1/igt@kms_ccs@crc-primary-suspend-4-tiled-lnl-ccs.html

  * igt@kms_ccs@crc-primary-suspend-4-tiled-mtl-rc-ccs-cc@pipe-c-hdmi-a-1:
    - shard-tglu-1:       NOTRUN -> [SKIP][55] ([i915#6095]) +34 other tests skip
   [55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-1/igt@kms_ccs@crc-primary-suspend-4-tiled-mtl-rc-ccs-cc@pipe-c-hdmi-a-1.html

  * igt@kms_ccs@crc-primary-suspend-y-tiled-ccs:
    - shard-glk10:        NOTRUN -> [INCOMPLETE][56] ([i915#15582]) +1 other test incomplete
   [56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-glk10/igt@kms_ccs@crc-primary-suspend-y-tiled-ccs.html

  * igt@kms_ccs@crc-primary-suspend-y-tiled-gen12-mc-ccs:
    - shard-glk10:        NOTRUN -> [SKIP][57] +140 other tests skip
   [57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-glk10/igt@kms_ccs@crc-primary-suspend-y-tiled-gen12-mc-ccs.html

  * igt@kms_ccs@crc-primary-suspend-y-tiled-gen12-rc-ccs-cc:
    - shard-rkl:          [PASS][58] -> [INCOMPLETE][59] ([i915#15582]) +1 other test incomplete
   [58]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-rkl-4/igt@kms_ccs@crc-primary-suspend-y-tiled-gen12-rc-ccs-cc.html
   [59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-3/igt@kms_ccs@crc-primary-suspend-y-tiled-gen12-rc-ccs-cc.html

  * igt@kms_ccs@crc-sprite-planes-basic-4-tiled-mtl-mc-ccs@pipe-a-hdmi-a-3:
    - shard-dg2:          NOTRUN -> [SKIP][60] ([i915#10307] / [i915#6095]) +130 other tests skip
   [60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-dg2-3/igt@kms_ccs@crc-sprite-planes-basic-4-tiled-mtl-mc-ccs@pipe-a-hdmi-a-3.html

  * igt@kms_ccs@crc-sprite-planes-basic-y-tiled-gen12-rc-ccs@pipe-d-hdmi-a-1:
    - shard-dg2:          NOTRUN -> [SKIP][61] ([i915#10307] / [i915#10434] / [i915#6095])
   [61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-dg2-4/igt@kms_ccs@crc-sprite-planes-basic-y-tiled-gen12-rc-ccs@pipe-d-hdmi-a-1.html

  * igt@kms_ccs@random-ccs-data-4-tiled-mtl-rc-ccs@pipe-b-hdmi-a-2:
    - shard-rkl:          NOTRUN -> [SKIP][62] ([i915#6095]) +57 other tests skip
   [62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-7/igt@kms_ccs@random-ccs-data-4-tiled-mtl-rc-ccs@pipe-b-hdmi-a-2.html

  * igt@kms_cdclk@mode-transition:
    - shard-tglu-1:       NOTRUN -> [SKIP][63] ([i915#3742])
   [63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-1/igt@kms_cdclk@mode-transition.html

  * igt@kms_chamelium_hpd@hdmi-hpd-storm-disable:
    - shard-tglu-1:       NOTRUN -> [SKIP][64] ([i915#11151] / [i915#7828]) +2 other tests skip
   [64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-1/igt@kms_chamelium_hpd@hdmi-hpd-storm-disable.html

  * igt@kms_chamelium_hpd@vga-hpd-for-each-pipe:
    - shard-rkl:          NOTRUN -> [SKIP][65] ([i915#11151] / [i915#7828]) +3 other tests skip
   [65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-8/igt@kms_chamelium_hpd@vga-hpd-for-each-pipe.html

  * igt@kms_chamelium_hpd@vga-hpd-with-enabled-mode:
    - shard-tglu:         NOTRUN -> [SKIP][66] ([i915#11151] / [i915#7828]) +5 other tests skip
   [66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-10/igt@kms_chamelium_hpd@vga-hpd-with-enabled-mode.html

  * igt@kms_content_protection@atomic-dpms:
    - shard-rkl:          NOTRUN -> [SKIP][67] ([i915#6944] / [i915#7118] / [i915#9424])
   [67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-7/igt@kms_content_protection@atomic-dpms.html
    - shard-tglu-1:       NOTRUN -> [SKIP][68] ([i915#6944] / [i915#7116] / [i915#7118] / [i915#9424])
   [68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-1/igt@kms_content_protection@atomic-dpms.html

  * igt@kms_content_protection@dp-mst-type-1:
    - shard-tglu:         NOTRUN -> [SKIP][69] ([i915#15330] / [i915#3116] / [i915#3299])
   [69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-10/igt@kms_content_protection@dp-mst-type-1.html

  * igt@kms_content_protection@dp-mst-type-1-suspend-resume:
    - shard-rkl:          NOTRUN -> [SKIP][70] ([i915#15330])
   [70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-8/igt@kms_content_protection@dp-mst-type-1-suspend-resume.html

  * igt@kms_content_protection@lic-type-1:
    - shard-rkl:          NOTRUN -> [SKIP][71] ([i915#6944] / [i915#9424])
   [71]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-4/igt@kms_content_protection@lic-type-1.html

  * igt@kms_content_protection@mei-interface:
    - shard-tglu-1:       NOTRUN -> [SKIP][72] ([i915#6944] / [i915#9424])
   [72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-1/igt@kms_content_protection@mei-interface.html

  * igt@kms_content_protection@suspend-resume:
    - shard-tglu:         NOTRUN -> [SKIP][73] ([i915#6944])
   [73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-10/igt@kms_content_protection@suspend-resume.html

  * igt@kms_content_protection@uevent-hdcp14@pipe-a-dp-3:
    - shard-dg2:          NOTRUN -> [FAIL][74] ([i915#7173]) +2 other tests fail
   [74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-dg2-11/igt@kms_content_protection@uevent-hdcp14@pipe-a-dp-3.html

  * igt@kms_cursor_crc@cursor-offscreen-512x170:
    - shard-rkl:          NOTRUN -> [SKIP][75] ([i915#13049]) +1 other test skip
   [75]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-8/igt@kms_cursor_crc@cursor-offscreen-512x170.html

  * igt@kms_cursor_crc@cursor-offscreen-512x512:
    - shard-tglu-1:       NOTRUN -> [SKIP][76] ([i915#13049])
   [76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-1/igt@kms_cursor_crc@cursor-offscreen-512x512.html

  * igt@kms_cursor_crc@cursor-onscreen-64x21:
    - shard-rkl:          [PASS][77] -> [FAIL][78] ([i915#13566]) +1 other test fail
   [77]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-rkl-3/igt@kms_cursor_crc@cursor-onscreen-64x21.html
   [78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-3/igt@kms_cursor_crc@cursor-onscreen-64x21.html

  * igt@kms_cursor_crc@cursor-rapid-movement-32x32:
    - shard-rkl:          NOTRUN -> [SKIP][79] ([i915#3555]) +2 other tests skip
   [79]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-8/igt@kms_cursor_crc@cursor-rapid-movement-32x32.html

  * igt@kms_cursor_crc@cursor-sliding-512x512:
    - shard-tglu:         NOTRUN -> [SKIP][80] ([i915#13049])
   [80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-10/igt@kms_cursor_crc@cursor-sliding-512x512.html

  * igt@kms_cursor_legacy@basic-busy-flip-before-cursor-varying-size:
    - shard-rkl:          NOTRUN -> [SKIP][81] ([i915#4103]) +2 other tests skip
   [81]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-7/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-varying-size.html
    - shard-tglu-1:       NOTRUN -> [SKIP][82] ([i915#4103])
   [82]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-1/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-varying-size.html

  * igt@kms_cursor_legacy@cursorb-vs-flipa-legacy:
    - shard-rkl:          NOTRUN -> [SKIP][83] +16 other tests skip
   [83]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-8/igt@kms_cursor_legacy@cursorb-vs-flipa-legacy.html

  * igt@kms_dp_link_training@non-uhbr-mst:
    - shard-tglu-1:       NOTRUN -> [SKIP][84] ([i915#13749])
   [84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-1/igt@kms_dp_link_training@non-uhbr-mst.html

  * igt@kms_dp_link_training@non-uhbr-sst:
    - shard-dg2:          [PASS][85] -> [SKIP][86] ([i915#13749])
   [85]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-dg2-11/igt@kms_dp_link_training@non-uhbr-sst.html
   [86]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-dg2-6/igt@kms_dp_link_training@non-uhbr-sst.html

  * igt@kms_dp_linktrain_fallback@dsc-fallback:
    - shard-tglu-1:       NOTRUN -> [SKIP][87] ([i915#13707])
   [87]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-1/igt@kms_dp_linktrain_fallback@dsc-fallback.html

  * igt@kms_dsc@dsc-fractional-bpp-with-bpc:
    - shard-rkl:          NOTRUN -> [SKIP][88] ([i915#3840])
   [88]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-8/igt@kms_dsc@dsc-fractional-bpp-with-bpc.html

  * igt@kms_dsc@dsc-with-bpc:
    - shard-tglu-1:       NOTRUN -> [SKIP][89] ([i915#3555] / [i915#3840])
   [89]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-1/igt@kms_dsc@dsc-with-bpc.html

  * igt@kms_dsc@dsc-with-bpc-formats:
    - shard-tglu:         NOTRUN -> [SKIP][90] ([i915#3555] / [i915#3840])
   [90]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-10/igt@kms_dsc@dsc-with-bpc-formats.html

  * igt@kms_dsc@dsc-with-output-formats:
    - shard-rkl:          NOTRUN -> [SKIP][91] ([i915#3555] / [i915#3840]) +1 other test skip
   [91]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-4/igt@kms_dsc@dsc-with-output-formats.html

  * igt@kms_fbcon_fbt@psr:
    - shard-tglu-1:       NOTRUN -> [SKIP][92] ([i915#3469])
   [92]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-1/igt@kms_fbcon_fbt@psr.html

  * igt@kms_fbcon_fbt@psr-suspend:
    - shard-rkl:          NOTRUN -> [SKIP][93] ([i915#3955])
   [93]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-8/igt@kms_fbcon_fbt@psr-suspend.html

  * igt@kms_flip@2x-flip-vs-dpms:
    - shard-tglu:         NOTRUN -> [SKIP][94] ([i915#3637] / [i915#9934]) +3 other tests skip
   [94]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-10/igt@kms_flip@2x-flip-vs-dpms.html

  * igt@kms_flip@2x-flip-vs-panning-vs-hang:
    - shard-rkl:          NOTRUN -> [SKIP][95] ([i915#9934]) +2 other tests skip
   [95]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-8/igt@kms_flip@2x-flip-vs-panning-vs-hang.html

  * igt@kms_flip@2x-flip-vs-suspend-interruptible:
    - shard-snb:          [PASS][96] -> [TIMEOUT][97] ([i915#14033] / [i915#14350])
   [96]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-snb6/igt@kms_flip@2x-flip-vs-suspend-interruptible.html
   [97]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-snb1/igt@kms_flip@2x-flip-vs-suspend-interruptible.html

  * igt@kms_flip@2x-flip-vs-suspend-interruptible@ab-vga1-hdmi-a1:
    - shard-snb:          [PASS][98] -> [TIMEOUT][99] ([i915#14033])
   [98]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-snb6/igt@kms_flip@2x-flip-vs-suspend-interruptible@ab-vga1-hdmi-a1.html
   [99]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-snb1/igt@kms_flip@2x-flip-vs-suspend-interruptible@ab-vga1-hdmi-a1.html

  * igt@kms_flip@2x-plain-flip-ts-check:
    - shard-tglu-1:       NOTRUN -> [SKIP][100] ([i915#3637] / [i915#9934])
   [100]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-1/igt@kms_flip@2x-plain-flip-ts-check.html

  * igt@kms_flip@flip-vs-suspend:
    - shard-glk:          NOTRUN -> [INCOMPLETE][101] ([i915#12745] / [i915#4839])
   [101]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-glk9/igt@kms_flip@flip-vs-suspend.html

  * igt@kms_flip@flip-vs-suspend@a-hdmi-a1:
    - shard-glk:          NOTRUN -> [INCOMPLETE][102] ([i915#12745])
   [102]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-glk9/igt@kms_flip@flip-vs-suspend@a-hdmi-a1.html

  * igt@kms_flip_scaled_crc@flip-32bpp-4tile-to-32bpp-4tiledg2rcccs-downscaling:
    - shard-tglu:         NOTRUN -> [SKIP][103] ([i915#15643]) +1 other test skip
   [103]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-10/igt@kms_flip_scaled_crc@flip-32bpp-4tile-to-32bpp-4tiledg2rcccs-downscaling.html

  * igt@kms_flip_scaled_crc@flip-64bpp-4tile-to-16bpp-4tile-downscaling:
    - shard-rkl:          NOTRUN -> [SKIP][104] ([i915#15643]) +1 other test skip
   [104]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-8/igt@kms_flip_scaled_crc@flip-64bpp-4tile-to-16bpp-4tile-downscaling.html

  * igt@kms_flip_scaled_crc@flip-64bpp-yftile-to-32bpp-yftile-downscaling:
    - shard-tglu-1:       NOTRUN -> [SKIP][105] ([i915#15643]) +1 other test skip
   [105]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-1/igt@kms_flip_scaled_crc@flip-64bpp-yftile-to-32bpp-yftile-downscaling.html

  * igt@kms_frontbuffer_tracking@fbc-2p-primscrn-spr-indfb-draw-blt:
    - shard-mtlp:         NOTRUN -> [SKIP][106] ([i915#1825])
   [106]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-mtlp-6/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-spr-indfb-draw-blt.html

  * igt@kms_frontbuffer_tracking@fbc-rgb101010-draw-mmap-gtt:
    - shard-dg2:          NOTRUN -> [SKIP][107] ([i915#8708])
   [107]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-dg2-1/igt@kms_frontbuffer_tracking@fbc-rgb101010-draw-mmap-gtt.html

  * igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-cur-indfb-draw-mmap-gtt:
    - shard-rkl:          NOTRUN -> [SKIP][108] ([i915#1825]) +13 other tests skip
   [108]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-7/igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-cur-indfb-draw-mmap-gtt.html

  * igt@kms_frontbuffer_tracking@psr-1p-offscreen-pri-indfb-draw-mmap-cpu:
    - shard-tglu-1:       NOTRUN -> [SKIP][109] ([i915#15102]) +12 other tests skip
   [109]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-1/igt@kms_frontbuffer_tracking@psr-1p-offscreen-pri-indfb-draw-mmap-cpu.html

  * igt@kms_frontbuffer_tracking@psr-1p-offscreen-pri-indfb-draw-mmap-wc:
    - shard-rkl:          NOTRUN -> [SKIP][110] ([i915#15102]) +3 other tests skip
   [110]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-8/igt@kms_frontbuffer_tracking@psr-1p-offscreen-pri-indfb-draw-mmap-wc.html

  * igt@kms_frontbuffer_tracking@psr-1p-primscrn-pri-indfb-draw-render:
    - shard-rkl:          NOTRUN -> [SKIP][111] ([i915#15102] / [i915#3023]) +7 other tests skip
   [111]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-7/igt@kms_frontbuffer_tracking@psr-1p-primscrn-pri-indfb-draw-render.html

  * igt@kms_frontbuffer_tracking@psr-2p-primscrn-shrfb-pgflip-blt:
    - shard-tglu:         NOTRUN -> [SKIP][112] +32 other tests skip
   [112]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-10/igt@kms_frontbuffer_tracking@psr-2p-primscrn-shrfb-pgflip-blt.html

  * igt@kms_frontbuffer_tracking@psr-rgb565-draw-blt:
    - shard-tglu:         NOTRUN -> [SKIP][113] ([i915#15102]) +8 other tests skip
   [113]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-10/igt@kms_frontbuffer_tracking@psr-rgb565-draw-blt.html

  * igt@kms_hdr@brightness-with-hdr:
    - shard-tglu:         NOTRUN -> [SKIP][114] ([i915#12713])
   [114]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-10/igt@kms_hdr@brightness-with-hdr.html

  * igt@kms_hdr@static-swap:
    - shard-dg2:          [PASS][115] -> [SKIP][116] ([i915#3555] / [i915#8228])
   [115]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-dg2-11/igt@kms_hdr@static-swap.html
   [116]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-dg2-6/igt@kms_hdr@static-swap.html

  * igt@kms_hdr@static-toggle-suspend:
    - shard-rkl:          NOTRUN -> [SKIP][117] ([i915#3555] / [i915#8228])
   [117]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-8/igt@kms_hdr@static-toggle-suspend.html

  * igt@kms_joiner@basic-force-big-joiner:
    - shard-dg2:          [PASS][118] -> [SKIP][119] ([i915#15459])
   [118]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-dg2-11/igt@kms_joiner@basic-force-big-joiner.html
   [119]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-dg2-6/igt@kms_joiner@basic-force-big-joiner.html

  * igt@kms_joiner@basic-max-non-joiner:
    - shard-rkl:          NOTRUN -> [SKIP][120] ([i915#13688])
   [120]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-7/igt@kms_joiner@basic-max-non-joiner.html
    - shard-tglu-1:       NOTRUN -> [SKIP][121] ([i915#13688])
   [121]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-1/igt@kms_joiner@basic-max-non-joiner.html

  * igt@kms_joiner@invalid-modeset-force-big-joiner:
    - shard-rkl:          NOTRUN -> [SKIP][122] ([i915#15459])
   [122]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-8/igt@kms_joiner@invalid-modeset-force-big-joiner.html

  * igt@kms_joiner@invalid-modeset-ultra-joiner:
    - shard-tglu:         NOTRUN -> [SKIP][123] ([i915#15458])
   [123]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-10/igt@kms_joiner@invalid-modeset-ultra-joiner.html

  * igt@kms_plane@pixel-format-4-tiled-dg2-mc-ccs-modifier:
    - shard-tglu-1:       NOTRUN -> [SKIP][124] ([i915#15709]) +2 other tests skip
   [124]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-1/igt@kms_plane@pixel-format-4-tiled-dg2-mc-ccs-modifier.html

  * igt@kms_plane@pixel-format-4-tiled-modifier:
    - shard-tglu:         NOTRUN -> [SKIP][125] ([i915#15709])
   [125]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-10/igt@kms_plane@pixel-format-4-tiled-modifier.html

  * igt@kms_plane@pixel-format-yf-tiled-modifier:
    - shard-rkl:          NOTRUN -> [SKIP][126] ([i915#15709]) +2 other tests skip
   [126]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-4/igt@kms_plane@pixel-format-yf-tiled-modifier.html

  * igt@kms_plane_multiple@2x-tiling-none:
    - shard-rkl:          NOTRUN -> [SKIP][127] ([i915#13958])
   [127]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-8/igt@kms_plane_multiple@2x-tiling-none.html

  * igt@kms_plane_multiple@tiling-4:
    - shard-tglu:         NOTRUN -> [SKIP][128] ([i915#14259])
   [128]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-10/igt@kms_plane_multiple@tiling-4.html

  * igt@kms_plane_scaling@plane-scaler-unity-scaling-with-rotation@pipe-a:
    - shard-tglu-1:       NOTRUN -> [SKIP][129] ([i915#15329]) +4 other tests skip
   [129]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-1/igt@kms_plane_scaling@plane-scaler-unity-scaling-with-rotation@pipe-a.html

  * igt@kms_plane_scaling@plane-scaler-with-clipping-clamping-rotation:
    - shard-tglu:         NOTRUN -> [SKIP][130] ([i915#15329] / [i915#3555])
   [130]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-10/igt@kms_plane_scaling@plane-scaler-with-clipping-clamping-rotation.html

  * igt@kms_plane_scaling@plane-scaler-with-clipping-clamping-rotation@pipe-b:
    - shard-tglu:         NOTRUN -> [SKIP][131] ([i915#15329]) +3 other tests skip
   [131]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-10/igt@kms_plane_scaling@plane-scaler-with-clipping-clamping-rotation@pipe-b.html

  * igt@kms_plane_scaling@plane-upscale-20x20-with-rotation@pipe-a:
    - shard-rkl:          NOTRUN -> [SKIP][132] ([i915#15329]) +7 other tests skip
   [132]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-4/igt@kms_plane_scaling@plane-upscale-20x20-with-rotation@pipe-a.html

  * igt@kms_pm_dc@dc5-retention-flops:
    - shard-tglu:         NOTRUN -> [SKIP][133] ([i915#3828])
   [133]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-10/igt@kms_pm_dc@dc5-retention-flops.html

  * igt@kms_pm_lpsp@kms-lpsp:
    - shard-rkl:          NOTRUN -> [SKIP][134] ([i915#3828])
   [134]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-8/igt@kms_pm_lpsp@kms-lpsp.html

  * igt@kms_pm_rpm@dpms-mode-unset-lpsp:
    - shard-dg2:          [PASS][135] -> [SKIP][136] ([i915#15073])
   [135]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-dg2-4/igt@kms_pm_rpm@dpms-mode-unset-lpsp.html
   [136]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-dg2-11/igt@kms_pm_rpm@dpms-mode-unset-lpsp.html
    - shard-rkl:          [PASS][137] -> [SKIP][138] ([i915#15073])
   [137]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-rkl-5/igt@kms_pm_rpm@dpms-mode-unset-lpsp.html
   [138]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-4/igt@kms_pm_rpm@dpms-mode-unset-lpsp.html

  * igt@kms_pm_rpm@i2c:
    - shard-dg1:          [PASS][139] -> [DMESG-WARN][140] ([i915#4423])
   [139]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-dg1-12/igt@kms_pm_rpm@i2c.html
   [140]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-dg1-16/igt@kms_pm_rpm@i2c.html

  * igt@kms_pm_rpm@modeset-non-lpsp-stress-no-wait:
    - shard-rkl:          NOTRUN -> [SKIP][141] ([i915#15073])
   [141]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-8/igt@kms_pm_rpm@modeset-non-lpsp-stress-no-wait.html

  * igt@kms_pm_rpm@system-suspend-idle:
    - shard-dg2:          [PASS][142] -> [INCOMPLETE][143] ([i915#14419])
   [142]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-dg2-3/igt@kms_pm_rpm@system-suspend-idle.html
   [143]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-dg2-5/igt@kms_pm_rpm@system-suspend-idle.html

  * igt@kms_prime@d3hot:
    - shard-tglu:         NOTRUN -> [SKIP][144] ([i915#6524])
   [144]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-10/igt@kms_prime@d3hot.html

  * igt@kms_psr2_sf@fbc-pr-overlay-plane-move-continuous-exceed-sf:
    - shard-tglu:         NOTRUN -> [SKIP][145] ([i915#11520]) +3 other tests skip
   [145]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-10/igt@kms_psr2_sf@fbc-pr-overlay-plane-move-continuous-exceed-sf.html

  * igt@kms_psr2_sf@fbc-pr-overlay-plane-update-sf-dmg-area:
    - shard-glk:          NOTRUN -> [SKIP][146] ([i915#11520]) +8 other tests skip
   [146]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-glk9/igt@kms_psr2_sf@fbc-pr-overlay-plane-update-sf-dmg-area.html

  * igt@kms_psr2_sf@fbc-psr2-overlay-plane-update-sf-dmg-area:
    - shard-rkl:          NOTRUN -> [SKIP][147] ([i915#11520]) +6 other tests skip
   [147]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-8/igt@kms_psr2_sf@fbc-psr2-overlay-plane-update-sf-dmg-area.html

  * igt@kms_psr2_sf@pr-cursor-plane-move-continuous-exceed-sf:
    - shard-tglu-1:       NOTRUN -> [SKIP][148] ([i915#11520]) +1 other test skip
   [148]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-1/igt@kms_psr2_sf@pr-cursor-plane-move-continuous-exceed-sf.html

  * igt@kms_psr2_sf@pr-overlay-primary-update-sf-dmg-area:
    - shard-snb:          NOTRUN -> [SKIP][149] ([i915#11520])
   [149]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-snb1/igt@kms_psr2_sf@pr-overlay-primary-update-sf-dmg-area.html

  * igt@kms_psr2_sf@pr-primary-plane-update-sf-dmg-area-big-fb:
    - shard-glk10:        NOTRUN -> [SKIP][150] ([i915#11520]) +3 other tests skip
   [150]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-glk10/igt@kms_psr2_sf@pr-primary-plane-update-sf-dmg-area-big-fb.html

  * igt@kms_psr2_su@frontbuffer-xrgb8888:
    - shard-tglu:         NOTRUN -> [SKIP][151] ([i915#9683])
   [151]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-10/igt@kms_psr2_su@frontbuffer-xrgb8888.html

  * igt@kms_psr2_su@page_flip-nv12:
    - shard-rkl:          NOTRUN -> [SKIP][152] ([i915#9683])
   [152]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-8/igt@kms_psr2_su@page_flip-nv12.html

  * igt@kms_psr@fbc-psr-primary-render:
    - shard-tglu-1:       NOTRUN -> [SKIP][153] ([i915#9732]) +9 other tests skip
   [153]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-1/igt@kms_psr@fbc-psr-primary-render.html

  * igt@kms_psr@fbc-psr2-cursor-plane-move:
    - shard-tglu:         NOTRUN -> [SKIP][154] ([i915#9732]) +9 other tests skip
   [154]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-10/igt@kms_psr@fbc-psr2-cursor-plane-move.html

  * igt@kms_psr@pr-sprite-mmap-gtt:
    - shard-rkl:          NOTRUN -> [SKIP][155] ([i915#1072] / [i915#9732]) +10 other tests skip
   [155]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-8/igt@kms_psr@pr-sprite-mmap-gtt.html

  * igt@kms_psr_stress_test@flip-primary-invalidate-overlay:
    - shard-rkl:          NOTRUN -> [SKIP][156] ([i915#9685]) +1 other test skip
   [156]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-8/igt@kms_psr_stress_test@flip-primary-invalidate-overlay.html

  * igt@kms_rotation_crc@primary-yf-tiled-reflect-x-180:
    - shard-tglu:         NOTRUN -> [SKIP][157] ([i915#5289])
   [157]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-10/igt@kms_rotation_crc@primary-yf-tiled-reflect-x-180.html

  * igt@kms_scaling_modes@scaling-mode-center:
    - shard-tglu:         NOTRUN -> [SKIP][158] ([i915#3555]) +4 other tests skip
   [158]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-10/igt@kms_scaling_modes@scaling-mode-center.html

  * igt@kms_scaling_modes@scaling-mode-full:
    - shard-tglu-1:       NOTRUN -> [SKIP][159] ([i915#3555])
   [159]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-1/igt@kms_scaling_modes@scaling-mode-full.html

  * igt@kms_tiled_display@basic-test-pattern:
    - shard-glk:          NOTRUN -> [FAIL][160] ([i915#10959])
   [160]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-glk5/igt@kms_tiled_display@basic-test-pattern.html

  * igt@kms_vrr@seamless-rr-switch-virtual:
    - shard-tglu:         NOTRUN -> [SKIP][161] ([i915#9906])
   [161]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-10/igt@kms_vrr@seamless-rr-switch-virtual.html

  * igt@perf@blocking@0-rcs0:
    - shard-tglu:         [PASS][162] -> [FAIL][163] ([i915#10538]) +1 other test fail
   [162]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-tglu-3/igt@perf@blocking@0-rcs0.html
   [163]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-3/igt@perf@blocking@0-rcs0.html

  * igt@perf@gen8-unprivileged-single-ctx-counters:
    - shard-rkl:          NOTRUN -> [SKIP][164] ([i915#2436])
   [164]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-7/igt@perf@gen8-unprivileged-single-ctx-counters.html

  * igt@perf@per-context-mode-unprivileged:
    - shard-rkl:          NOTRUN -> [SKIP][165] ([i915#2435])
   [165]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-8/igt@perf@per-context-mode-unprivileged.html

  * igt@perf_pmu@rc6-suspend:
    - shard-rkl:          [PASS][166] -> [INCOMPLETE][167] ([i915#13520])
   [166]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-rkl-2/igt@perf_pmu@rc6-suspend.html
   [167]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-6/igt@perf_pmu@rc6-suspend.html

  * igt@prime_vgem@coherency-gtt:
    - shard-rkl:          NOTRUN -> [SKIP][168] ([i915#3708])
   [168]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-7/igt@prime_vgem@coherency-gtt.html

  
#### Possible fixes ####

  * igt@gem_ccs@suspend-resume@linear-compressed-compfmt0-smem-lmem0:
    - shard-dg2:          [INCOMPLETE][169] ([i915#13356]) -> [PASS][170]
   [169]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-dg2-5/igt@gem_ccs@suspend-resume@linear-compressed-compfmt0-smem-lmem0.html
   [170]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-dg2-5/igt@gem_ccs@suspend-resume@linear-compressed-compfmt0-smem-lmem0.html

  * igt@gem_exec_suspend@basic-s0@smem:
    - shard-rkl:          [INCOMPLETE][171] ([i915#13356]) -> [PASS][172] +1 other test pass
   [171]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-rkl-3/igt@gem_exec_suspend@basic-s0@smem.html
   [172]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-8/igt@gem_exec_suspend@basic-s0@smem.html

  * igt@gem_pxp@verify-pxp-key-change-after-suspend-resume:
    - shard-rkl:          [ABORT][173] ([i915#15131]) -> [PASS][174]
   [173]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-rkl-1/igt@gem_pxp@verify-pxp-key-change-after-suspend-resume.html
   [174]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-4/igt@gem_pxp@verify-pxp-key-change-after-suspend-resume.html

  * igt@i915_pm_rps@reset:
    - shard-snb:          [INCOMPLETE][175] ([i915#13821]) -> [PASS][176]
   [175]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-snb6/igt@i915_pm_rps@reset.html
   [176]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-snb1/igt@i915_pm_rps@reset.html

  * igt@i915_power@sanity:
    - shard-mtlp:         [SKIP][177] ([i915#7984]) -> [PASS][178]
   [177]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-mtlp-5/igt@i915_power@sanity.html
   [178]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-mtlp-8/igt@i915_power@sanity.html

  * igt@kms_atomic@plane-invalid-params:
    - shard-dg1:          [DMESG-WARN][179] ([i915#4423]) -> [PASS][180] +1 other test pass
   [179]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-dg1-16/igt@kms_atomic@plane-invalid-params.html
   [180]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-dg1-13/igt@kms_atomic@plane-invalid-params.html

  * igt@kms_cursor_crc@cursor-sliding-128x42:
    - shard-tglu:         [FAIL][181] ([i915#13566]) -> [PASS][182] +3 other tests pass
   [181]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-tglu-7/igt@kms_cursor_crc@cursor-sliding-128x42.html
   [182]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-tglu-7/igt@kms_cursor_crc@cursor-sliding-128x42.html

  * igt@kms_flip@flip-vs-absolute-wf_vblank-interruptible@a-vga1:
    - shard-snb:          [FAIL][183] ([i915#14600]) -> [PASS][184] +1 other test pass
   [183]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-snb6/igt@kms_flip@flip-vs-absolute-wf_vblank-interruptible@a-vga1.html
   [184]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-snb7/igt@kms_flip@flip-vs-absolute-wf_vblank-interruptible@a-vga1.html

  * igt@kms_flip@flip-vs-suspend-interruptible:
    - shard-rkl:          [INCOMPLETE][185] ([i915#6113]) -> [PASS][186]
   [185]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-rkl-6/igt@kms_flip@flip-vs-suspend-interruptible.html
   [186]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-8/igt@kms_flip@flip-vs-suspend-interruptible.html

  * igt@kms_hdr@static-toggle-dpms:
    - shard-dg2:          [SKIP][187] ([i915#3555] / [i915#8228]) -> [PASS][188] +1 other test pass
   [187]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-dg2-4/igt@kms_hdr@static-toggle-dpms.html
   [188]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-dg2-11/igt@kms_hdr@static-toggle-dpms.html

  * igt@kms_pipe_crc_basic@suspend-read-crc:
    - shard-rkl:          [INCOMPLETE][189] ([i915#12756] / [i915#13476]) -> [PASS][190]
   [189]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-rkl-6/igt@kms_pipe_crc_basic@suspend-read-crc.html
   [190]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-7/igt@kms_pipe_crc_basic@suspend-read-crc.html

  * igt@kms_pipe_crc_basic@suspend-read-crc@pipe-a-hdmi-a-2:
    - shard-rkl:          [INCOMPLETE][191] ([i915#13476]) -> [PASS][192]
   [191]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-rkl-6/igt@kms_pipe_crc_basic@suspend-read-crc@pipe-a-hdmi-a-2.html
   [192]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-7/igt@kms_pipe_crc_basic@suspend-read-crc@pipe-a-hdmi-a-2.html

  * igt@kms_pm_rpm@modeset-lpsp:
    - shard-rkl:          [SKIP][193] ([i915#14544] / [i915#15073]) -> [PASS][194]
   [193]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-rkl-6/igt@kms_pm_rpm@modeset-lpsp.html
   [194]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-8/igt@kms_pm_rpm@modeset-lpsp.html

  * igt@kms_pm_rpm@modeset-lpsp-stress:
    - shard-dg1:          [SKIP][195] ([i915#15073]) -> [PASS][196]
   [195]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-dg1-12/igt@kms_pm_rpm@modeset-lpsp-stress.html
   [196]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-dg1-14/igt@kms_pm_rpm@modeset-lpsp-stress.html

  * igt@kms_pm_rpm@modeset-non-lpsp-stress:
    - shard-dg2:          [SKIP][197] ([i915#15073]) -> [PASS][198] +2 other tests pass
   [197]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-dg2-4/igt@kms_pm_rpm@modeset-non-lpsp-stress.html
   [198]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-dg2-11/igt@kms_pm_rpm@modeset-non-lpsp-stress.html

  * igt@kms_pm_rpm@system-suspend-modeset:
    - shard-rkl:          [ABORT][199] ([i915#15132]) -> [PASS][200]
   [199]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-rkl-1/igt@kms_pm_rpm@system-suspend-modeset.html
   [200]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-8/igt@kms_pm_rpm@system-suspend-modeset.html

  * igt@perf_pmu@busy-double-start@vecs1:
    - shard-dg2:          [FAIL][201] ([i915#4349]) -> [PASS][202] +4 other tests pass
   [201]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-dg2-7/igt@perf_pmu@busy-double-start@vecs1.html
   [202]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-dg2-6/igt@perf_pmu@busy-double-start@vecs1.html

  
#### Warnings ####

  * igt@api_intel_bb@object-reloc-purge-cache:
    - shard-rkl:          [SKIP][203] ([i915#14544] / [i915#8411]) -> [SKIP][204] ([i915#8411])
   [203]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-rkl-6/igt@api_intel_bb@object-reloc-purge-cache.html
   [204]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-8/igt@api_intel_bb@object-reloc-purge-cache.html

  * igt@gem_exec_reloc@basic-cpu-gtt-noreloc:
    - shard-rkl:          [SKIP][205] ([i915#3281]) -> [SKIP][206] ([i915#14544] / [i915#3281]) +1 other test skip
   [205]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-rkl-8/igt@gem_exec_reloc@basic-cpu-gtt-noreloc.html
   [206]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-6/igt@gem_exec_reloc@basic-cpu-gtt-noreloc.html

  * igt@gem_lmem_swapping@heavy-verify-multi:
    - shard-rkl:          [SKIP][207] ([i915#4613]) -> [SKIP][208] ([i915#14544] / [i915#4613])
   [207]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-rkl-8/igt@gem_lmem_swapping@heavy-verify-multi.html
   [208]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-6/igt@gem_lmem_swapping@heavy-verify-multi.html

  * igt@gem_lmem_swapping@heavy-verify-random-ccs:
    - shard-rkl:          [SKIP][209] ([i915#14544] / [i915#4613]) -> [SKIP][210] ([i915#4613])
   [209]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-rkl-6/igt@gem_lmem_swapping@heavy-verify-random-ccs.html
   [210]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-8/igt@gem_lmem_swapping@heavy-verify-random-ccs.html

  * igt@gem_pread@display:
    - shard-rkl:          [SKIP][211] ([i915#14544] / [i915#3282]) -> [SKIP][212] ([i915#3282])
   [211]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-rkl-6/igt@gem_pread@display.html
   [212]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-8/igt@gem_pread@display.html

  * igt@gen9_exec_parse@batch-invalid-length:
    - shard-rkl:          [SKIP][213] ([i915#2527]) -> [SKIP][214] ([i915#14544] / [i915#2527])
   [213]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-rkl-8/igt@gen9_exec_parse@batch-invalid-length.html
   [214]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-6/igt@gen9_exec_parse@batch-invalid-length.html

  * igt@kms_big_fb@4-tiled-addfb-size-overflow:
    - shard-rkl:          [SKIP][215] ([i915#5286]) -> [SKIP][216] ([i915#14544] / [i915#5286])
   [215]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-rkl-8/igt@kms_big_fb@4-tiled-addfb-size-overflow.html
   [216]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-6/igt@kms_big_fb@4-tiled-addfb-size-overflow.html

  * igt@kms_big_fb@y-tiled-8bpp-rotate-270:
    - shard-rkl:          [SKIP][217] ([i915#14544] / [i915#3638]) -> [SKIP][218] ([i915#3638])
   [217]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-rkl-6/igt@kms_big_fb@y-tiled-8bpp-rotate-270.html
   [218]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-7/igt@kms_big_fb@y-tiled-8bpp-rotate-270.html

  * igt@kms_ccs@bad-rotation-90-4-tiled-mtl-rc-ccs-cc:
    - shard-rkl:          [SKIP][219] ([i915#14098] / [i915#14544] / [i915#6095]) -> [SKIP][220] ([i915#14098] / [i915#6095])
   [219]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-rkl-6/igt@kms_ccs@bad-rotation-90-4-tiled-mtl-rc-ccs-cc.html
   [220]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-8/igt@kms_ccs@bad-rotation-90-4-tiled-mtl-rc-ccs-cc.html

  * igt@kms_ccs@crc-sprite-planes-basic-4-tiled-lnl-ccs:
    - shard-rkl:          [SKIP][221] ([i915#12313] / [i915#14544]) -> [SKIP][222] ([i915#12313])
   [221]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-rkl-6/igt@kms_ccs@crc-sprite-planes-basic-4-tiled-lnl-ccs.html
   [222]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-8/igt@kms_ccs@crc-sprite-planes-basic-4-tiled-lnl-ccs.html

  * igt@kms_chamelium_frames@hdmi-crc-fast:
    - shard-rkl:          [SKIP][223] ([i915#11151] / [i915#14544] / [i915#7828]) -> [SKIP][224] ([i915#11151] / [i915#7828]) +1 other test skip
   [223]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-rkl-6/igt@kms_chamelium_frames@hdmi-crc-fast.html
   [224]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-7/igt@kms_chamelium_frames@hdmi-crc-fast.html

  * igt@kms_content_protection@atomic:
    - shard-dg2:          [SKIP][225] ([i915#6944] / [i915#7118] / [i915#9424]) -> [FAIL][226] ([i915#7173])
   [225]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-dg2-4/igt@kms_content_protection@atomic.html
   [226]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-dg2-11/igt@kms_content_protection@atomic.html

  * igt@kms_content_protection@content-type-change:
    - shard-rkl:          [SKIP][227] ([i915#14544] / [i915#6944] / [i915#9424]) -> [SKIP][228] ([i915#6944] / [i915#9424])
   [227]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-rkl-6/igt@kms_content_protection@content-type-change.html
   [228]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-8/igt@kms_content_protection@content-type-change.html

  * igt@kms_content_protection@mei-interface:
    - shard-dg1:          [SKIP][229] ([i915#6944] / [i915#9424]) -> [SKIP][230] ([i915#9433])
   [229]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-dg1-16/igt@kms_content_protection@mei-interface.html
   [230]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-dg1-13/igt@kms_content_protection@mei-interface.html

  * igt@kms_content_protection@type1:
    - shard-dg2:          [SKIP][231] ([i915#6944] / [i915#7118] / [i915#7162] / [i915#9424]) -> [SKIP][232] ([i915#6944] / [i915#7118] / [i915#9424])
   [231]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-dg2-11/igt@kms_content_protection@type1.html
   [232]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-dg2-6/igt@kms_content_protection@type1.html

  * igt@kms_content_protection@uevent-hdcp14:
    - shard-dg2:          [SKIP][233] ([i915#6944]) -> [FAIL][234] ([i915#7173]) +1 other test fail
   [233]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-dg2-4/igt@kms_content_protection@uevent-hdcp14.html
   [234]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-dg2-11/igt@kms_content_protection@uevent-hdcp14.html

  * igt@kms_cursor_crc@cursor-rapid-movement-max-size:
    - shard-rkl:          [SKIP][235] ([i915#3555]) -> [SKIP][236] ([i915#14544] / [i915#3555])
   [235]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-rkl-8/igt@kms_cursor_crc@cursor-rapid-movement-max-size.html
   [236]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-6/igt@kms_cursor_crc@cursor-rapid-movement-max-size.html

  * igt@kms_dp_linktrain_fallback@dsc-fallback:
    - shard-rkl:          [SKIP][237] ([i915#13707] / [i915#14544]) -> [SKIP][238] ([i915#13707])
   [237]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-rkl-6/igt@kms_dp_linktrain_fallback@dsc-fallback.html
   [238]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-7/igt@kms_dp_linktrain_fallback@dsc-fallback.html

  * igt@kms_flip@2x-modeset-vs-vblank-race-interruptible:
    - shard-rkl:          [SKIP][239] ([i915#14544] / [i915#9934]) -> [SKIP][240] ([i915#9934]) +1 other test skip
   [239]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-rkl-6/igt@kms_flip@2x-modeset-vs-vblank-race-interruptible.html
   [240]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-8/igt@kms_flip@2x-modeset-vs-vblank-race-interruptible.html

  * igt@kms_force_connector_basic@force-load-detect:
    - shard-mtlp:         [SKIP][241] ([i915#15672]) -> [SKIP][242]
   [241]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-mtlp-1/igt@kms_force_connector_basic@force-load-detect.html
   [242]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-mtlp-3/igt@kms_force_connector_basic@force-load-detect.html

  * igt@kms_frontbuffer_tracking@fbc-2p-primscrn-cur-indfb-draw-blt:
    - shard-rkl:          [SKIP][243] ([i915#14544] / [i915#1825]) -> [SKIP][244] ([i915#1825]) +9 other tests skip
   [243]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-rkl-6/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-cur-indfb-draw-blt.html
   [244]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-8/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-cur-indfb-draw-blt.html

  * igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-pri-shrfb-draw-mmap-wc:
    - shard-rkl:          [SKIP][245] ([i915#1825]) -> [SKIP][246] ([i915#14544] / [i915#1825]) +1 other test skip
   [245]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-rkl-8/igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-pri-shrfb-draw-mmap-wc.html
   [246]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-6/igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-pri-shrfb-draw-mmap-wc.html

  * igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-indfb-draw-blt:
    - shard-dg2:          [SKIP][247] ([i915#15102] / [i915#3458]) -> [SKIP][248] ([i915#10433] / [i915#15102] / [i915#3458]) +1 other test skip
   [247]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-dg2-3/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-indfb-draw-blt.html
   [248]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-dg2-4/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-indfb-draw-blt.html

  * igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-shrfb-draw-mmap-gtt:
    - shard-rkl:          [SKIP][249] ([i915#14544] / [i915#15102] / [i915#3023]) -> [SKIP][250] ([i915#15102] / [i915#3023]) +1 other test skip
   [249]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-rkl-6/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-shrfb-draw-mmap-gtt.html
   [250]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-8/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-shrfb-draw-mmap-gtt.html

  * igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-spr-indfb-draw-blt:
    - shard-dg1:          [SKIP][251] ([i915#15102] / [i915#3458] / [i915#4423]) -> [SKIP][252] ([i915#15102] / [i915#3458])
   [251]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-dg1-17/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-spr-indfb-draw-blt.html
   [252]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-dg1-17/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-spr-indfb-draw-blt.html

  * igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-pri-indfb-draw-blt:
    - shard-dg1:          [SKIP][253] ([i915#4423]) -> [SKIP][254]
   [253]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-dg1-16/igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-pri-indfb-draw-blt.html
   [254]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-dg1-13/igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-pri-indfb-draw-blt.html

  * igt@kms_frontbuffer_tracking@fbcpsr-shrfb-scaledprimary:
    - shard-rkl:          [SKIP][255] ([i915#15102] / [i915#3023]) -> [SKIP][256] ([i915#14544] / [i915#15102] / [i915#3023])
   [255]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-rkl-8/igt@kms_frontbuffer_tracking@fbcpsr-shrfb-scaledprimary.html
   [256]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-6/igt@kms_frontbuffer_tracking@fbcpsr-shrfb-scaledprimary.html

  * igt@kms_frontbuffer_tracking@psr-1p-offscreen-pri-shrfb-draw-mmap-cpu:
    - shard-rkl:          [SKIP][257] ([i915#14544] / [i915#15102]) -> [SKIP][258] ([i915#15102])
   [257]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-rkl-6/igt@kms_frontbuffer_tracking@psr-1p-offscreen-pri-shrfb-draw-mmap-cpu.html
   [258]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-7/igt@kms_frontbuffer_tracking@psr-1p-offscreen-pri-shrfb-draw-mmap-cpu.html

  * igt@kms_frontbuffer_tracking@psr-1p-primscrn-pri-shrfb-draw-blt:
    - shard-dg2:          [SKIP][259] ([i915#10433] / [i915#15102] / [i915#3458]) -> [SKIP][260] ([i915#15102] / [i915#3458]) +2 other tests skip
   [259]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-dg2-4/igt@kms_frontbuffer_tracking@psr-1p-primscrn-pri-shrfb-draw-blt.html
   [260]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-dg2-11/igt@kms_frontbuffer_tracking@psr-1p-primscrn-pri-shrfb-draw-blt.html

  * igt@kms_hdr@brightness-with-hdr:
    - shard-rkl:          [SKIP][261] ([i915#13331]) -> [SKIP][262] ([i915#12713])
   [261]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-rkl-1/igt@kms_hdr@brightness-with-hdr.html
   [262]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-8/igt@kms_hdr@brightness-with-hdr.html

  * igt@kms_pipe_b_c_ivb@disable-pipe-b-enable-pipe-c:
    - shard-rkl:          [SKIP][263] ([i915#14544]) -> [SKIP][264] +1 other test skip
   [263]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-rkl-6/igt@kms_pipe_b_c_ivb@disable-pipe-b-enable-pipe-c.html
   [264]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-8/igt@kms_pipe_b_c_ivb@disable-pipe-b-enable-pipe-c.html

  * igt@kms_pm_dc@dc5-retention-flops:
    - shard-rkl:          [SKIP][265] ([i915#3828]) -> [SKIP][266] ([i915#14544] / [i915#3828])
   [265]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-rkl-8/igt@kms_pm_dc@dc5-retention-flops.html
   [266]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-6/igt@kms_pm_dc@dc5-retention-flops.html

  * igt@kms_pm_rpm@fences:
    - shard-dg1:          [SKIP][267] ([i915#4077] / [i915#4423]) -> [SKIP][268] ([i915#4077])
   [267]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-dg1-12/igt@kms_pm_rpm@fences.html
   [268]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-dg1-16/igt@kms_pm_rpm@fences.html

  * igt@kms_pm_rpm@modeset-non-lpsp:
    - shard-dg1:          [DMESG-WARN][269] ([i915#4423]) -> [SKIP][270] ([i915#15073])
   [269]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-dg1-12/igt@kms_pm_rpm@modeset-non-lpsp.html
   [270]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-dg1-14/igt@kms_pm_rpm@modeset-non-lpsp.html

  * igt@kms_psr@fbc-psr-cursor-mmap-gtt:
    - shard-dg1:          [SKIP][271] ([i915#1072] / [i915#4423] / [i915#9732]) -> [SKIP][272] ([i915#1072] / [i915#9732])
   [271]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-dg1-12/igt@kms_psr@fbc-psr-cursor-mmap-gtt.html
   [272]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-dg1-14/igt@kms_psr@fbc-psr-cursor-mmap-gtt.html

  * igt@kms_psr@psr-cursor-plane-move:
    - shard-rkl:          [SKIP][273] ([i915#1072] / [i915#14544] / [i915#9732]) -> [SKIP][274] ([i915#1072] / [i915#9732]) +2 other tests skip
   [273]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-rkl-6/igt@kms_psr@psr-cursor-plane-move.html
   [274]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-7/igt@kms_psr@psr-cursor-plane-move.html

  * igt@perf@unprivileged-single-ctx-counters:
    - shard-rkl:          [SKIP][275] ([i915#14544] / [i915#2433]) -> [SKIP][276] ([i915#2433])
   [275]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18022/shard-rkl-6/igt@perf@unprivileged-single-ctx-counters.html
   [276]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_161578v3/shard-rkl-8/igt@perf@unprivileged-single-ctx-counters.html

  
  [i915#10307]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/10307
  [i915#10433]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/10433
  [i915#10434]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/10434
  [i915#10538]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/10538
  [i915#1072]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/1072
  [i915#10959]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/10959
  [i915#1099]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/1099
  [i915#11078]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/11078
  [i915#11151]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/11151
  [i915#11520]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/11520
  [i915#12313]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/12313
  [i915#12392]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/12392
  [i915#12713]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/12713
  [i915#12745]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/12745
  [i915#12756]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/12756
  [i915#12805]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/12805
  [i915#13049]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13049
  [i915#13331]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13331
  [i915#13356]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13356
  [i915#13390]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13390
  [i915#13476]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13476
  [i915#13520]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13520
  [i915#13566]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13566
  [i915#13688]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13688
  [i915#13707]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13707
  [i915#13749]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13749
  [i915#13790]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13790
  [i915#13821]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13821
  [i915#13958]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13958
  [i915#14033]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/14033
  [i915#14098]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/14098
  [i915#14259]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/14259
  [i915#14350]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/14350
  [i915#14419]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/14419
  [i915#14498]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/14498
  [i915#14544]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/14544
  [i915#14600]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/14600
  [i915#15073]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/15073
  [i915#15102]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/15102
  [i915#15131]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/15131
  [i915#15132]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/15132
  [i915#15329]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/15329
  [i915#15330]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/15330
  [i915#15458]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/15458
  [i915#15459]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/15459
  [i915#15478]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/15478
  [i915#15582]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/15582
  [i915#15643]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/15643
  [i915#15672]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/15672
  [i915#15709]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/15709
  [i915#1825]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/1825
  [i915#2433]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/2433
  [i915#2435]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/2435
  [i915#2436]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/2436
  [i915#2527]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/2527
  [i915#2681]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/2681
  [i915#280]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/280
  [i915#2856]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/2856
  [i915#3023]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/3023
  [i915#3116]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/3116
  [i915#3281]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/3281
  [i915#3282]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/3282
  [i915#3297]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/3297
  [i915#3299]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/3299
  [i915#3458]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/3458
  [i915#3469]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/3469
  [i915#3555]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/3555
  [i915#3637]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/3637
  [i915#3638]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/3638
  [i915#3708]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/3708
  [i915#3742]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/3742
  [i915#3828]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/3828
  [i915#3840]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/3840
  [i915#3955]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/3955
  [i915#4077]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/4077
  [i915#4103]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/4103
  [i915#4349]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/4349
  [i915#4423]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/4423
  [i915#4525]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/4525
  [i915#4613]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/4613
  [i915#4817]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/4817
  [i915#4839]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/4839
  [i915#5286]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/5286
  [i915#5289]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/5289
  [i915#5956]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/5956
  [i915#6095]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/6095
  [i915#6113]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/6113
  [i915#6334]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/6334
  [i915#6412]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/6412
  [i915#6524]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/6524
  [i915#6944]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/6944
  [i915#7116]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/7116
  [i915#7118]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/7118
  [i915#7162]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/7162
  [i915#7173]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/7173
  [i915#7828]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/7828
  [i915#7975]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/7975
  [i915#7984]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/7984
  [i915#8228]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/8228
  [i915#8411]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/8411
  [i915#8562]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/8562
  [i915#8708]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/8708
  [i915#9323]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/9323
  [i915#9424]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/9424
  [i915#9433]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/9433
  [i915#9561]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/9561
  [i915#9683]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/9683
  [i915#9685]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/9685
  [i915#9732]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/9732
  [i915#9906]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/9906
  [i915#9934]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/9934


Build changes
-------------

  * Linux: CI_DRM_18022 -> Patchwork_161578v3

  CI-20190529: 20190529
  CI_DRM_18022: 45a3045fc0dc46a893cb8bbe304afafd4120c904 @ git://anongit.freedesktop.org/gfx-ci/linux
  IGT_8765: 8765
  Patchwork_161578v3: 45a3045fc0dc46a893cb8bbe304afafd4120c904 @ 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_161578v3/index.html

[-- Attachment #2: Type: text/html, Size: 93586 bytes --]