On Mon, Jul 13, 2015 at 04:30:21PM +0200, Maarten Lankhorst wrote: > Signed-off-by: Maarten Lankhorst <[email protected]>
Needs a summary (or just pasting relevant parts of our mail threads) about double-modesets, ways to avoid them and why exactly we ended up opting for this solution here. Especially please highlight the TYPE_DRIVER trick. Thanks, Daniel > --- > drivers/gpu/drm/i915/intel_display.c | 5 +++++ > 1 file changed, 5 insertions(+) > > diff --git a/drivers/gpu/drm/i915/intel_display.c > b/drivers/gpu/drm/i915/intel_display.c > index 118187dc76be..d37f6a93b094 100644 > --- a/drivers/gpu/drm/i915/intel_display.c > +++ b/drivers/gpu/drm/i915/intel_display.c > @@ -7754,9 +7754,14 @@ void intel_mode_from_pipe_config(struct > drm_display_mode *mode, > mode->vsync_end = pipe_config->base.adjusted_mode.crtc_vsync_end; > > mode->flags = pipe_config->base.adjusted_mode.flags; > + mode->type = DRM_MODE_TYPE_DRIVER; > > mode->clock = pipe_config->base.adjusted_mode.crtc_clock; > mode->flags |= pipe_config->base.adjusted_mode.flags; > + > + mode->hsync = drm_mode_hsync(mode); > + mode->vrefresh = drm_mode_vrefresh(mode); > + drm_mode_set_name(mode); > } > > static void i9xx_set_pipeconf(struct intel_crtc *intel_crtc) > -- > 2.1.0 > > _______________________________________________ > Intel-gfx mailing list > [email protected] > http://lists.freedesktop.org/mailman/listinfo/intel-gfx -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
