Re: [Intel-gfx] [PATCH] drm/i915: Set mode->crtc_clock during hardware state readout

2015-10-07 Thread Matt Roper
On Wed, Oct 07, 2015 at 04:26:03PM +0200, Daniel Vetter wrote: > On Tue, Oct 06, 2015 at 09:26:31AM -0700, Matt Roper wrote: > > intel_mode_from_pipe_config() fills in a mode structure from the CRTC > > state that was read out of the hardware, but does not set the > > .crtc_clock field (it only set

Re: [Intel-gfx] [PATCH] drm/i915: Set mode->crtc_clock during hardware state readout

2015-10-07 Thread Daniel Vetter
On Tue, Oct 06, 2015 at 09:26:31AM -0700, Matt Roper wrote: > intel_mode_from_pipe_config() fills in a mode structure from the CRTC > state that was read out of the hardware, but does not set the > .crtc_clock field (it only sets the .clock). This causes the subsequent > call to drm_calc_timestamp

Re: [Intel-gfx] [PATCH] drm/i915: Set mode->crtc_clock during hardware state readout

2015-10-06 Thread Ville Syrjälä
On Tue, Oct 06, 2015 at 09:26:31AM -0700, Matt Roper wrote: > intel_mode_from_pipe_config() fills in a mode structure from the CRTC > state that was read out of the hardware, but does not set the > .crtc_clock field (it only sets the .clock). This causes the subsequent > call to drm_calc_timestamp

[Intel-gfx] [PATCH] drm/i915: Set mode->crtc_clock during hardware state readout

2015-10-06 Thread Matt Roper
intel_mode_from_pipe_config() fills in a mode structure from the CRTC state that was read out of the hardware, but does not set the .crtc_clock field (it only sets the .clock). This causes the subsequent call to drm_calc_timestamping_constants() to complain with messages like "*ERROR* crtc 21: Can