Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Keith Packard <keithp@keithp.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: apply phase pointer override on SNB+ too
Date: Fri, 29 Jul 2011 12:43:42 -0700	[thread overview]
Message-ID: <20110729124342.68aaffca@jbarnes-desktop> (raw)
In-Reply-To: <yuntya4hqjo.fsf@aiko.keithp.com>

On Fri, 29 Jul 2011 11:47:55 -0700
Keith Packard <keithp@keithp.com> wrote:

> On Fri, 29 Jul 2011 10:50:11 -0700, Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> 
> > +	flags |= FDI_PHASE_SYNC_OVR(pipe);
> > +	I915_WRITE(SOUTH_CHICKEN1, flags); /* once to unlock... */
> > +	flags |= FDI_PHASE_SYNC_EN(pipe);
> > +	I915_WRITE(SOUTH_CHICKEN1, flags); /* then again to enable */
> > +	POSTING_READ(SOUTH_CHICKEN1);
> > +}
> 
> ooh, this even makes the sequence of two writes sound sensible.
> 
> Reviewed-by: Keith Packard <keithp@keithp.com>
> 
> You didn't happen to check the register values after doing this, did
> you? Just to verify that all of the crazy math works, given that we
> can't actually test whether this fixes anything.
> 

Tricky.  I need to call this in the gen6 and ivb training routines
rather than the ilk one...  Bits seem to be getting set correctly with
the last patch.

-- 
Jesse Barnes, Intel Open Source Technology Center

  reply	other threads:[~2011-07-29 19:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-29 17:50 [PATCH] drm/i915: apply phase pointer override on SNB+ too Jesse Barnes
2011-07-29 18:47 ` Keith Packard
2011-07-29 19:43   ` Jesse Barnes [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-07-29 19:42 Jesse Barnes
2011-07-29 21:22 ` Keith Packard
2011-07-29 21:55   ` Jesse Barnes
2011-07-29  0:07 Jesse Barnes
2011-07-29 17:28 ` Keith Packard
2011-07-29  0:06 Jesse Barnes

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=20110729124342.68aaffca@jbarnes-desktop \
    --to=jbarnes@virtuousgeek.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=keithp@keithp.com \
    /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