On Thu, Nov 12, 2015 at 04:31:58PM -0800, Matt Roper wrote: > We dump during HW state readout, but that's too early to reflect how the > primary plane is actually configured. Hmm. Would be nice if we could read out everything at the same place, and then saniitize later. And maybe we could introduce some kind of NOP FB for planes where we haven't yet reconstructed the BIOS FB (or are unable to do so). That way the plane sanitize could be exactly like a normal modeset? > > Signed-off-by: Matt Roper <matthew.d.roper@xxxxxxxxx> > --- > drivers/gpu/drm/i915/intel_display.c | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c > index d994f52..9fa041c 100644 > --- a/drivers/gpu/drm/i915/intel_display.c > +++ b/drivers/gpu/drm/i915/intel_display.c > @@ -15118,6 +15118,9 @@ void intel_modeset_init(struct drm_device *dev) > * just get the first one. > */ > intel_find_initial_plane_obj(crtc, &plane_config); > + > + intel_dump_pipe_config(crtc, crtc->config, > + "[state after init fb reconstruction]"); > } > } > > -- > 2.1.4 > > _______________________________________________ > Intel-gfx mailing list > Intel-gfx@xxxxxxxxxxxxxxxxxxxxx > http://lists.freedesktop.org/mailman/listinfo/intel-gfx -- Ville Syrjälä Intel OTC _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
