From: "Lespiau, Damien" <damien.lespiau@intel.com>
To: Keith Packard <keithp@keithp.com>
Cc: intel-gfx@lists.freedesktop.org,
Daniel Vetter <daniel.vetter@ffwll.ch>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 7/7] drm/i915: Merge FDI RX reg writes during training
Date: Fri, 17 Aug 2012 18:14:50 +0100 [thread overview]
Message-ID: <CAPX-8+-kfzGCZSyGFuWJESEqNoTyzytbxX75=3=-hLP2uAwApw@mail.gmail.com> (raw)
In-Reply-To: <1344918891-6283-8-git-send-email-keithp@keithp.com>
On Tue, Aug 14, 2012 at 5:34 AM, Keith Packard <keithp@keithp.com> wrote:
> @@ -2324,6 +2324,8 @@ static void intel_fdi_normal_train(struct drm_crtc *crtc)
> temp |= FDI_LINK_TRAIN_NONE | FDI_TX_ENHANCE_FRAME_ENABLE;
> }
> I915_WRITE(reg, temp);
> + POSTING_READ(reg);
> + udelay(100);
The docs don't mention a delay between writing the TX and RX training
patterns, the POSTING_READ() seems like a good idea.
> reg = FDI_RX_CTL(pipe);
> temp = I915_READ(reg);
> @@ -2334,16 +2336,15 @@ static void intel_fdi_normal_train(struct drm_crtc *crtc)
> temp &= ~FDI_LINK_TRAIN_NONE;
> temp |= FDI_LINK_TRAIN_NONE;
> }
> + /* IVB wants error correction enabled */
> + if (IS_IVYBRIDGE(dev))
> + temp |= FDI_FS_ERRC_ENABLE | FDI_FE_ERRC_ENABLE;
> +
> I915_WRITE(reg, temp | FDI_RX_ENHANCE_FRAME_ENABLE);
>
> /* wait one idle pattern time */
> POSTING_READ(reg);
> udelay(1000);
> -
> - /* IVB wants error correction enabled */
> - if (IS_IVYBRIDGE(dev))
> - I915_WRITE(reg, I915_READ(reg) | FDI_FS_ERRC_ENABLE |
> - FDI_FE_ERRC_ENABLE);
> }
>
> static void cpt_phase_pointer_enable(struct drm_device *dev, int pipe)
Reviewed-by: Damien Lespiau <damien.lespiau@intel.com>
--
Damien
prev parent reply other threads:[~2012-08-17 17:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1344918891-6283-1-git-send-email-keithp@keithp.com>
[not found] ` <1344918891-6283-2-git-send-email-keithp@keithp.com>
2012-08-15 22:42 ` [PATCH 1/7] drm/i915: Allow VGA on CRTC 2 Daniel Vetter
[not found] ` <1344918891-6283-3-git-send-email-keithp@keithp.com>
2012-08-17 14:45 ` [Intel-gfx] [PATCH 2/7] drm/i915: FDI B/C share 4 lanes on Ivybridge Lespiau, Damien
2012-08-17 15:00 ` Keith Packard
2012-08-17 15:12 ` Lespiau, Damien
[not found] ` <1344918891-6283-5-git-send-email-keithp@keithp.com>
2012-08-17 14:58 ` [Intel-gfx] [PATCH 4/7] drm/i915: Check display_bpc against max_fdi_bpp after display_bpc is set Lespiau, Damien
[not found] ` <1344918891-6283-4-git-send-email-keithp@keithp.com>
2012-08-17 15:34 ` [Intel-gfx] [PATCH 3/7] drm/i915: Delay between FDI link training tries. Clear FDI_RX_IIR before training Lespiau, Damien
[not found] ` <1344918891-6283-6-git-send-email-keithp@keithp.com>
2012-08-17 15:50 ` [Intel-gfx] [PATCH 5/7] drm/i915: Pipe-C only configurations would not get SR Lespiau, Damien
[not found] ` <1344918891-6283-7-git-send-email-keithp@keithp.com>
2012-08-17 16:43 ` [Intel-gfx] [PATCH 6/7] drm/i915: Disable FDI RX before FDI TX Lespiau, Damien
2012-08-17 23:10 ` Keith Packard
[not found] ` <1344918891-6283-8-git-send-email-keithp@keithp.com>
2012-08-17 17:14 ` Lespiau, Damien [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='CAPX-8+-kfzGCZSyGFuWJESEqNoTyzytbxX75=3=-hLP2uAwApw@mail.gmail.com' \
--to=damien.lespiau@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=keithp@keithp.com \
--cc=linux-kernel@vger.kernel.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).