(In reply to comment #13)
> Daniel,
>
> I'm already running drm-intel-nightly which includes that commit.
> That particular hack does indeed run (see attached dmesg log at the
> beginning) but the panel is still blank. I saw the same hack at
> intel_dp_get_config, but in my machine intel_dp_get_config does not get
> called at all.
>
> The culprit is clamping bpp from 24 to 18 bpp at intel_dp_compute_config.
> When the bpp clamping code is disabled and the panel runs at 24 bpp there
> are no more blank screen issues.
Please try this on drm-intel-nightly, and report what the debug says:
(In reply to comment #13) get_config, but in my machine intel_dp_get_config does not get compute_ config.
> Daniel,
>
> I'm already running drm-intel-nightly which includes that commit.
> That particular hack does indeed run (see attached dmesg log at the
> beginning) but the panel is still blank. I saw the same hack at
> intel_dp_
> called at all.
>
> The culprit is clamping bpp from 24 to 18 bpp at intel_dp_
> When the bpp clamping code is disabled and the panel runs at 24 bpp there
> are no more blank screen issues.
Please try this on drm-intel-nightly, and report what the debug says:
diff --git a/drivers/ gpu/drm/ i915/intel_ ddi.c b/drivers/ gpu/drm/ i915/intel_ ddi.c gpu/drm/ i915/intel_ ddi.c gpu/drm/ i915/intel_ ddi.c get_config( struct intel_encoder *encoder,
break;
index 74749c6..dbc5a16 100644
--- a/drivers/
+++ b/drivers/
@@ -1491,6 +1491,10 @@ void intel_ddi_
}
+ DRM_DEBUG_ KMS("encoder type %d, pipe_bpp %d, vbt.edp_bpp %d, ddi ctl %08x\n", >pipe_bpp, >vbt.edp_ bpp, temp); >vbt.edp_ bpp &&
pipe_ config- >pipe_bpp > dev_priv- >vbt.edp_ bpp) {
+ encoder->type, pipe_config-
+ dev_priv-
+
if (encoder->type == INTEL_OUTPUT_EDP && dev_priv-
/*