intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Matt Roper <matthew.d.roper@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Set mode->crtc_clock during hardware state readout
Date: Wed, 7 Oct 2015 07:32:43 -0700	[thread overview]
Message-ID: <20151007143243.GA19399@intel.com> (raw)
In-Reply-To: <20151007142603.GM3383@phenom.ffwll.local>

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 sets the .clock).  This causes the subsequent
> > call to drm_calc_timestamping_constants() to complain with messages like
> > "*ERROR* crtc 21: Can't calculate constants, dotclock = 0!"  Ensuring
> > .crtc_clock is set as well eliminates this error.
> > 
> > Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
> 
> Is this fixing the bug Paulo reported? Why is he not on CC? Why is there
> no citation of the commit which broke this?
> -Daniel

This isn't related to the watermark issue he reported, so no (unless
this is a different issue he brought up elsewhere that I haven't seen).

Ville already pointed out that this might already be fixed properly on
nightly; I think I might have got my trees mixed up while building, so
this might not be necessary at all (I'll need to double check today).
But my original thinking (possibly wrong) was that this was just
something we never initialized from day 1, so there was no specific
commit to cite.

Anyway, I think you can probably disregard this patch for now.


Matt

> 
> > ---
> >  drivers/gpu/drm/i915/intel_display.c | 1 +
> >  1 file changed, 1 insertion(+)
> > 
> > diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> > index bbeb6d3..4e481e3 100644
> > --- a/drivers/gpu/drm/i915/intel_display.c
> > +++ b/drivers/gpu/drm/i915/intel_display.c
> > @@ -7752,6 +7752,7 @@ void intel_mode_from_pipe_config(struct drm_display_mode *mode,
> >  	mode->type = DRM_MODE_TYPE_DRIVER;
> >  
> >  	mode->clock = pipe_config->base.adjusted_mode.crtc_clock;
> > +	mode->crtc_clock = pipe_config->base.adjusted_mode.crtc_clock;
> >  	mode->flags |= pipe_config->base.adjusted_mode.flags;
> >  
> >  	mode->hsync = drm_mode_hsync(mode);
> > -- 
> > 2.1.4
> > 
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/intel-gfx
> 
> -- 
> Daniel Vetter
> Software Engineer, Intel Corporation
> http://blog.ffwll.ch

-- 
Matt Roper
Graphics Software Engineer
IoTG Platform Enabling & Development
Intel Corporation
(916) 356-2795
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2015-10-07 14:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-06 16:26 [PATCH] drm/i915: Set mode->crtc_clock during hardware state readout Matt Roper
2015-10-06 16:52 ` Ville Syrjälä
2015-10-07 14:26 ` Daniel Vetter
2015-10-07 14:32   ` Matt Roper [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151007143243.GA19399@intel.com \
    --to=matthew.d.roper@intel.com \
    --cc=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).