From: Adam Jackson <ajax@redhat.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Make G4X-style PLL search more permissive
Date: Fri, 02 Jul 2010 17:10:13 -0400 [thread overview]
Message-ID: <1278105013.15550.42.camel@atropine> (raw)
In-Reply-To: <1278103410-24674-1-git-send-email-ajax@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 1035 bytes --]
On Fri, 2010-07-02 at 16:43 -0400, Adam Jackson wrote:
> Worst dotclock for Ironlake DAC refclk is 350000kHz (error 0.00571)
> Worst dotclock for Ironlake SL-LVDS refclk is 102321kHz (error 0.00524)
> Worst dotclock for Ironlake DL-LVDS refclk is 219642kHz (error 0.00488)
> Worst dotclock for Ironlake SL-LVDS SSC refclk is 84374kHz (error 0.00529)
> Worst dotclock for Ironlake DL-LVDS SSC refclk is 183035kHz (error 0.00488)
> Worst dotclock for G4X SDVO refclk is 50000kHz (error 0.17332)
> Worst dotclock for G4X HDMI refclk is 334400kHz (error 0.00478)
> Worst dotclock for G4X SL-LVDS refclk is 95571kHz (error 0.00449)
> Worst dotclock for G4X DL-LVDS refclk is 224000kHz (error 0.00510)
>
> The SDVO number looks a bit suspicious, which I haven't tracked down
> yet. But it's clear that the old threshold is too tight.
Well, that was easy. We turn on 2x or 4x pixel multiplication below
100MHz. Once I account for that I get:
Worst dotclock for G4X SDVO refclk is 267600kHz (error 0.00448)
- ajax
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2010-07-02 21:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-02 20:43 [PATCH] drm/i915: Make G4X-style PLL search more permissive Adam Jackson
2010-07-02 21:10 ` Adam Jackson [this message]
2010-07-06 1:21 ` Zhenyu Wang
2010-07-22 10:47 ` sconklin Lists
2010-07-26 17:54 ` Eric Anholt
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=1278105013.15550.42.camel@atropine \
--to=ajax@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.