From: "Souza, Jose" <jose.souza@intel.com>
To: "Roper, Matthew D" <matthew.d.roper@intel.com>
Cc: "Nikula, Jani" <jani.nikula@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 1/2] drm/i915/ehl/dsi: Set lane latency optimization for DW1
Date: Wed, 19 Jun 2019 23:15:52 +0000 [thread overview]
Message-ID: <483f71eeda257e14059936e491535e7920f33a86.camel@intel.com> (raw)
In-Reply-To: <20190619223804.GJ14321@mdroper-desk.amr.corp.intel.com>
On Wed, 2019-06-19 at 15:38 -0700, Matt Roper wrote:
> On Tue, Jun 18, 2019 at 12:59:59PM -0700, José Roberto de Souza
> wrote:
> > From: Vandita Kulkarni <vandita.kulkarni@intel.com>
> >
> > EHL has 2 additional steps in the DSI sequence, this is one of then
> > the lane latency optimization for DW1.
> >
> > BSpec: 20597
> > Cc: Uma Shankar <uma.shankar@intel.com>
> > Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > Cc: Jani Nikula <jani.nikula@intel.com>
> > Signed-off-by: Vandita Kulkarni <vandita.kulkarni@intel.com>
> > ---
> > drivers/gpu/drm/i915/display/icl_dsi.c | 11 +++++++++++
> > drivers/gpu/drm/i915/i915_reg.h | 2 ++
> > 2 files changed, 13 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/i915/display/icl_dsi.c
> > b/drivers/gpu/drm/i915/display/icl_dsi.c
> > index 74448e6bf749..ee85428b309f 100644
> > --- a/drivers/gpu/drm/i915/display/icl_dsi.c
> > +++ b/drivers/gpu/drm/i915/display/icl_dsi.c
> > @@ -403,6 +403,17 @@ static void
> > gen11_dsi_config_phy_lanes_sequence(struct intel_encoder *encoder)
> > tmp &= ~FRC_LATENCY_OPTIM_MASK;
> > tmp |= FRC_LATENCY_OPTIM_VAL(0x5);
> > I915_WRITE(ICL_PORT_TX_DW2_GRP(port), tmp);
> > + /* For EHL set latency optimization for PCS_DW1 lanes
> > */
> > + if (IS_ELKHARTLAKE(dev_priv)) {
> > + tmp = I915_READ(ICL_PORT_PCS_DW1_AUX(port));
> > + tmp &= ~LATENCY_OPTIM_MASK;
> > + tmp |= LATENCY_OPTIM_VAL(0);
> > + I915_WRITE(ICL_PORT_PCS_DW1_AUX(port), tmp);
> > + tmp = I915_READ(ICL_PORT_PCS_DW1_LN0(port));
> > + tmp &= ~LATENCY_OPTIM_MASK;
> > + tmp |= LATENCY_OPTIM_VAL(0x1);
> > + I915_WRITE(ICL_PORT_PCS_DW1_GRP(port), tmp);
> > + }
>
> Minor nitpick, but these sequences might be slightly easier to read
> if
> there was a blank line separating each R/M/W chunk.
Agreed, I was avoiding change the patch because it is not mine but this
will not hurt anyone.
>
> The changes here look correct according to the description on bspec
> page
> 20597 although it looks like the bspec authors forgot to update the
> 'Valid Values' section for these bits on page 20398; not sure if you
> want to file a bspec defect about that or not.
Well the missing value is 0, that is the default after reset so we are
safe here.
>
> > }
> >
> > }
> > diff --git a/drivers/gpu/drm/i915/i915_reg.h
> > b/drivers/gpu/drm/i915/i915_reg.h
> > index d6483b5dc8e5..1f2c3ebdf87b 100644
> > --- a/drivers/gpu/drm/i915/i915_reg.h
> > +++ b/drivers/gpu/drm/i915/i915_reg.h
> > @@ -1896,6 +1896,8 @@ enum i915_power_well_id {
> > #define ICL_PORT_PCS_DW1_GRP(port) _MMIO(_ICL_PORT_PCS_DW_GRP(1,
> > port))
> > #define ICL_PORT_PCS_DW1_LN0(port) _MMIO(_ICL_PORT_PCS_DW_LN(1, 0,
> > port))
> > #define COMMON_KEEPER_EN (1 << 26)
> > +#define LATENCY_OPTIM_MASK (0x3 << 2)
> > +#define LATENCY_OPTIM_VAL(x) ((x) << 2)
>
> Should we try to include part of the name of the register in these
> definitions (e.g., DW1_LATENCY_OPTIM)? I'm not sure if we should
> worry
> about people mixing up these vs the FRC_LATENCY_OPTIM defines farther
> down for the TX_DW2 register.
I also prefer to include the register name to the bits but the general
rule is keep consistent with around code or fix everything, as this is
not mine patch I left this way.
>
> Up to you on whether you think it's worth clarifying the
> naming. Either
> way,
>
> Reviewed-by: Matt Roper <matthew.d.roper@intel.com>
Thanks
>
> >
> > /* CNL/ICL Port TX registers */
> > #define _CNL_PORT_TX_AE_GRP_OFFSET 0x162340
> > --
> > 2.22.0
> >
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-06-19 23:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 19:59 [PATCH 1/2] drm/i915/ehl/dsi: Set lane latency optimization for DW1 José Roberto de Souza
2019-06-18 20:00 ` [PATCH 2/2] drm/i915/ehl/dsi: Enable AFE over PPI strap José Roberto de Souza
2019-06-19 5:19 ` Kulkarni, Vandita
2019-06-19 5:21 ` Kulkarni, Vandita
2019-06-19 23:25 ` Souza, Jose
2019-06-19 22:52 ` Matt Roper
2019-06-19 23:16 ` Souza, Jose
2019-06-18 21:13 ` ✗ Fi.CI.BAT: failure for series starting with [1/2] drm/i915/ehl/dsi: Set lane latency optimization for DW1 Patchwork
2019-06-19 9:05 ` ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915/ehl/dsi: Set lane latency optimization for DW1 (rev3) Patchwork
2019-06-19 22:38 ` [PATCH 1/2] drm/i915/ehl/dsi: Set lane latency optimization for DW1 Matt Roper
2019-06-19 23:15 ` Souza, Jose [this message]
2019-06-19 23:53 ` ✓ Fi.CI.IGT: success for series starting with [1/2] drm/i915/ehl/dsi: Set lane latency optimization for DW1 (rev3) 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=483f71eeda257e14059936e491535e7920f33a86.camel@intel.com \
--to=jose.souza@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=matthew.d.roper@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