public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Bruno Prémont" <bonbons@linux-vserver.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 0/5] drm/i915: Gen2 PLL fixes
Date: Tue, 10 Dec 2013 14:19:36 +0200	[thread overview]
Message-ID: <20131210121936.GN10036@intel.com> (raw)
In-Reply-To: <20131210125227.1d2bb70f@neptune.home>

On Tue, Dec 10, 2013 at 12:52:27PM +0100, Bruno Prémont wrote:
> Hi Ville,
> 
> On Mon, 09 December 2013 ville.syrjala@linux.intel.com wrote:
> > There appear to be some gen2 machines that don't really like the current PLL
> > limits we have. We also have some accuracy problems with the PLL calculations.
> > This series aims to eliminate those problems, and at least my 855 machine
> > seems happier with these patches.
> > 
> > Ville Syrjälä (5):
> >       drm/i915: Extract p2 divider correctly for gen2 LVDS dual channel
> >       drm/i915: Change N divider minimum from 3 to 2 for gen2
> >       drm/i915: Increase gen2 vco frequency limit to 1512 MHz
> >       drm/i915: Fix 66 MHz LVDS SSC freq for gen2
> >       drm/i915: Decrease gen2 vco frequency minimum to 908 MHz
> > 
> >  drivers/gpu/drm/i915/intel_bios.c    |  8 ++++----
> >  drivers/gpu/drm/i915/intel_display.c | 34 +++++++++++++++++++---------------
> >  2 files changed, 23 insertions(+), 19 deletions(-)
> 
> Here is my dmesg with the 5 patches applied (on top of 3.13-rc3 and
> the PLL debug patch).
> 
> The WARN() are not hit anymore.
> 
<snip>
> [   46.584578] [drm:intel_dump_pipe_config], DPLL = 0x0
> [   46.584581] [drm:intel_dump_pipe_config], DPLL_MD = 0x0
> [   46.584583] [drm:intel_dump_pipe_config], FP0 = 0x0
> [   46.584586] [drm:intel_dump_pipe_config], FP1 = 0x0

OK, so I think the problem got fixed, but my debug patch wasn't
all that good since it doesn't dump the values we computed unless
the clock is off.

Can you still run this (as root) when the LVDS output is active:
# intel_reg_read 0x6014 0x6018 0x6040 0x6044 0x6048 0x604c

intel_reg_read is part of intel-gpu-tools.

I just want to confirm we calculated the DPLL registers correctly.
I know we at least got close since ther WARN is gone, but by my
calculations we should get exactly the same as what the BIOS used.

-- 
Ville Syrjälä
Intel OTC

  reply	other threads:[~2013-12-10 12:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-09 16:54 [PATCH 0/5] drm/i915: Gen2 PLL fixes ville.syrjala
2013-12-09 16:54 ` [PATCH 1/5] drm/i915: Extract p2 divider correctly for gen2 LVDS dual channel ville.syrjala
2013-12-09 16:54 ` [PATCH 2/5] drm/i915: Change N divider minimum from 3 to 2 for gen2 ville.syrjala
2013-12-09 16:54 ` [PATCH 3/5] drm/i915: Increase gen2 vco frequency limit to 1512 MHz ville.syrjala
2013-12-09 16:54 ` [PATCH 4/5] drm/i915: Fix 66 MHz LVDS SSC freq for gen2 ville.syrjala
2013-12-09 16:54 ` [PATCH 5/5] drm/i915: Decrease gen2 vco frequency minimum to 908 MHz ville.syrjala
2013-12-10 11:52 ` [PATCH 0/5] drm/i915: Gen2 PLL fixes Bruno Prémont
2013-12-10 12:19   ` Ville Syrjälä [this message]
2013-12-10 12:33     ` Bruno Prémont
2013-12-10 12:47       ` Ville Syrjälä
2013-12-11 10:12         ` Daniel Vetter

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=20131210121936.GN10036@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=bonbons@linux-vserver.org \
    --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