On Wed, Sep 04, 2013 at 06:25:20PM +0300, [email protected] wrote: > From: Ville Syrjälä <[email protected]> > > The pixel clock should come from adjusted_mode not requested_mode. > In this case the two should be the same as we don't currently > overwrite the clock in the case of HDMI. But let's make the code > safe against such things happening in the future. > > Signed-off-by: Ville Syrjälä <[email protected]>
Reviewed-by: Damien Lespiau <[email protected]> -- Damien > --- > drivers/gpu/drm/i915/intel_hdmi.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/gpu/drm/i915/intel_hdmi.c > b/drivers/gpu/drm/i915/intel_hdmi.c > index 3d833a3..6e87b83 100644 > --- a/drivers/gpu/drm/i915/intel_hdmi.c > +++ b/drivers/gpu/drm/i915/intel_hdmi.c > @@ -865,7 +865,7 @@ bool intel_hdmi_compute_config(struct intel_encoder > *encoder, > struct intel_hdmi *intel_hdmi = enc_to_intel_hdmi(&encoder->base); > struct drm_device *dev = encoder->base.dev; > struct drm_display_mode *adjusted_mode = &pipe_config->adjusted_mode; > - int clock_12bpc = pipe_config->requested_mode.clock * 3 / 2; > + int clock_12bpc = pipe_config->adjusted_mode.clock * 3 / 2; > int portclock_limit = hdmi_portclock_limit(intel_hdmi); > int desired_bpp; > > -- > 1.8.1.5 > > _______________________________________________ > Intel-gfx mailing list > [email protected] > http://lists.freedesktop.org/mailman/listinfo/intel-gfx _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
