From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: intel-gfx@lists.freedesktop.org, Art Runyan <arthur.j.runyan@intel.com>
Subject: Re: [PATCH v2] drm/i915: Implement display w/a #1143
Date: Wed, 24 Jan 2018 20:18:11 +0200 [thread overview]
Message-ID: <20180124181811.GX5453@intel.com> (raw)
In-Reply-To: <20180122174845.27y4a5xo5ugwrhmr@intel.com>
On Mon, Jan 22, 2018 at 09:48:46AM -0800, Rodrigo Vivi wrote:
> On Mon, Jan 22, 2018 at 05:41:31PM +0000, Ville Syrjala wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > Apparently SKL/KBL/CFL need some manual help to get the
> > programmed HDMI vswing to stick. Implement the relevant
> > workaround (display w/a #1143).
> >
> > Note that the relevant chicken bits live in a transcoder register
> > even though the bits affect a specific DDI port rather than a
> > specific transcoder. Hence we must pick the correct transcoder
> > register instance based on the port rather than based on the
> > cpu_transcoder.
> >
> > Also note that for completeness I included support for DDI A/E
> > in the code even though we never have HDMI on those ports.
> >
> > v2: CFL needs the w/a as well (Rodrigo and Art)
> >
> > Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > Cc: Art Runyan <arthur.j.runyan@intel.com>
> > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Pushed to dinq. Thanks for the review.
>
>
> > ---
> > drivers/gpu/drm/i915/i915_reg.h | 8 ++++++--
> > drivers/gpu/drm/i915/intel_ddi.c | 42 ++++++++++++++++++++++++++++++++++++++++
> > 2 files changed, 48 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/i915_reg.h b/drivers/gpu/drm/i915/i915_reg.h
> > index 10e1269ad6af..2e6d0dc01dc7 100644
> > --- a/drivers/gpu/drm/i915/i915_reg.h
> > +++ b/drivers/gpu/drm/i915/i915_reg.h
> > @@ -7012,8 +7012,12 @@ enum {
> > #define CHICKEN_TRANS_A 0x420c0
> > #define CHICKEN_TRANS_B 0x420c4
> > #define CHICKEN_TRANS(trans) _MMIO_TRANS(trans, CHICKEN_TRANS_A, CHICKEN_TRANS_B)
> > -#define PSR2_VSC_ENABLE_PROG_HEADER (1<<12)
> > -#define PSR2_ADD_VERTICAL_LINE_COUNT (1<<15)
> > +#define DDI_TRAINING_OVERRIDE_ENABLE (1<<19)
> > +#define DDI_TRAINING_OVERRIDE_VALUE (1<<18)
> > +#define DDIE_TRAINING_OVERRIDE_ENABLE (1<<17) /* CHICKEN_TRANS_A only */
> > +#define DDIE_TRAINING_OVERRIDE_VALUE (1<<16) /* CHICKEN_TRANS_A only */
> > +#define PSR2_ADD_VERTICAL_LINE_COUNT (1<<15)
> > +#define PSR2_VSC_ENABLE_PROG_HEADER (1<<12)
> >
> > #define DISP_ARB_CTL _MMIO(0x45000)
> > #define DISP_FBC_MEMORY_WAKE (1<<31)
> > diff --git a/drivers/gpu/drm/i915/intel_ddi.c b/drivers/gpu/drm/i915/intel_ddi.c
> > index 6260a882fbe4..e51559be2e3b 100644
> > --- a/drivers/gpu/drm/i915/intel_ddi.c
> > +++ b/drivers/gpu/drm/i915/intel_ddi.c
> > @@ -2433,6 +2433,48 @@ static void intel_enable_ddi_hdmi(struct intel_encoder *encoder,
> > crtc_state->hdmi_high_tmds_clock_ratio,
> > crtc_state->hdmi_scrambling);
> >
> > + /* Display WA #1143: skl,kbl,cfl */
> > + if (IS_GEN9_BC(dev_priv)) {
> > + /*
> > + * For some reason these chicken bits have been
> > + * stuffed into a transcoder register, event though
> > + * the bits affect a specific DDI port rather than
> > + * a specific transcoder.
> > + */
> > + static const enum transcoder port_to_transcoder[] = {
> > + [PORT_A] = TRANSCODER_EDP,
> > + [PORT_B] = TRANSCODER_A,
> > + [PORT_C] = TRANSCODER_B,
> > + [PORT_D] = TRANSCODER_C,
> > + [PORT_E] = TRANSCODER_A,
> > + };
> > + enum transcoder transcoder = port_to_transcoder[port];
> > + u32 val;
> > +
> > + val = I915_READ(CHICKEN_TRANS(transcoder));
> > +
> > + if (port == PORT_E)
> > + val |= DDIE_TRAINING_OVERRIDE_ENABLE |
> > + DDIE_TRAINING_OVERRIDE_VALUE;
> > + else
> > + val |= DDI_TRAINING_OVERRIDE_ENABLE |
> > + DDI_TRAINING_OVERRIDE_VALUE;
> > +
> > + I915_WRITE(CHICKEN_TRANS(transcoder), val);
> > + POSTING_READ(CHICKEN_TRANS(transcoder));
> > +
> > + udelay(1);
> > +
> > + if (port == PORT_E)
> > + val &= ~(DDIE_TRAINING_OVERRIDE_ENABLE |
> > + DDIE_TRAINING_OVERRIDE_VALUE);
> > + else
> > + val &= ~(DDI_TRAINING_OVERRIDE_ENABLE |
> > + DDI_TRAINING_OVERRIDE_VALUE);
> > +
> > + I915_WRITE(CHICKEN_TRANS(transcoder), val);
> > + }
> > +
> > /* In HDMI/DVI mode, the port width, and swing/emphasis values
> > * are ignored so nothing special needs to be done besides
> > * enabling the port.
> > --
> > 2.13.6
> >
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-01-24 18:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-19 18:45 [PATCH] drm/i915: Implement display w/a #1143 Ville Syrjala
2018-01-19 19:05 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-01-19 20:07 ` [PATCH] " Rodrigo Vivi
2018-01-19 20:39 ` Runyan, Arthur J
2018-01-22 17:39 ` Ville Syrjälä
2018-01-20 1:59 ` ✗ Fi.CI.IGT: failure for " Patchwork
2018-01-22 17:41 ` [PATCH v2] " Ville Syrjala
2018-01-22 17:48 ` Rodrigo Vivi
2018-01-24 18:18 ` Ville Syrjälä [this message]
2018-01-22 18:25 ` ✓ Fi.CI.BAT: success for drm/i915: Implement display w/a #1143 (rev2) Patchwork
2018-01-23 3:40 ` ✗ Fi.CI.IGT: warning " Patchwork
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=20180124181811.GX5453@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=arthur.j.runyan@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@intel.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