From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Fix VLV analog output shivers
Date: Wed, 12 Jun 2013 11:14:39 +0300 [thread overview]
Message-ID: <20130612081439.GP5004@intel.com> (raw)
In-Reply-To: <20130611161846.3a54e775@jbarnes-desktop>
On Tue, Jun 11, 2013 at 04:18:46PM -0700, Jesse Barnes wrote:
> On Tue, 11 Jun 2013 23:06:59 +0200
> Daniel Vetter <daniel@ffwll.ch> wrote:
>
> > On Tue, Jun 11, 2013 at 11:08:16PM +0300, ville.syrjala@linux.intel.com wrote:
> > > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > >
> > > The current PLL settings produce a rather unstable picture when
> > > I hook up a VLV to my HP ZR24w display via a VGA cable. Switching
> > > the PLL to hybrid mode makes the picture a lot more stable. No
> > > idea if this is truly wise though...
> >
> > Ok, you've just slipped up here and mentioned that the changed bit is for
> > "hybrid mode". Can I have real register defines for this magic now please?
> >
> > Apparently Jesse just weaseled out of real work claiming that it's not
> > documented at all ;-)
> >
>
> There are some bits we could use, but we'd be making up the name. On
> top of that, the hex value is used in the docs, so if we make up bit
> field names, we'll end up double taking everytime we look at these bits.
>
> So there's no good answer here... :/
For this particular register I've not seen any documented "correct"
value. I have no idea where the values used in the code came from. If
you have a document that has them, I'd like to see it.
There are certainly some register values that are specified as raw hex
numbers in some docs, but I've noticed that in some cases even those
don't agree with our code :(
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2013-06-12 8:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-11 20:08 [PATCH] drm/i915: Fix VLV analog output shivers ville.syrjala
2013-06-11 21:06 ` Daniel Vetter
2013-06-11 23:18 ` Jesse Barnes
2013-06-12 8:14 ` Ville Syrjälä [this message]
2013-06-12 8:17 ` 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=20130612081439.GP5004@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.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.