From: Imre Deak <imre.deak@intel.com>
To: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/combo_phy: Add Workaround to avoid flicker with HBR3 eDP Panels
Date: Thu, 4 Aug 2022 18:44:22 +0300 [thread overview]
Message-ID: <YuvpVtJDEdBrEpeH@ideak-desk.fi.intel.com> (raw)
In-Reply-To: <20220804102911.1346064-1-ankit.k.nautiyal@intel.com>
On Thu, Aug 04, 2022 at 03:59:11PM +0530, Ankit Nautiyal wrote:
> WA_14014367875 : When Display PHY is configured in continuous
> DCC calibration mode, the DCC (duty cycle correction) for the clock
> erroneously goes through a state where the DCC code is 0x00 when it is
> supposed to be transitioning from 0x10 to 0x0F. This glitch causes a
> distortion in the clock, which leads to a bit error. The issue is known
> to be causing flickering with eDP HBR3 panels.
>
> The work around configures the DCC in one-time-update mode.
> This mode updates the DCC code one time during training and then
> it does not change. This will prevent on-the-fly updates so that the
> glitch does not occur.
>
> Signed-off-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_combo_phy.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_combo_phy.c b/drivers/gpu/drm/i915/display/intel_combo_phy.c
> index 64890f39c3cc..1b8bdc47671d 100644
> --- a/drivers/gpu/drm/i915/display/intel_combo_phy.c
> +++ b/drivers/gpu/drm/i915/display/intel_combo_phy.c
> @@ -242,9 +242,10 @@ static bool icl_combo_phy_verify_state(struct drm_i915_private *dev_priv,
> ICL_PORT_TX_DW8_ODCC_CLK_SEL |
> ICL_PORT_TX_DW8_ODCC_CLK_DIV_SEL_DIV2);
>
> + /* WA_14014367875 Set DCC calibration mode to Read once*/
The usual format is 'Wa_<lineage>:<platforms>', so Wa_22012718247:...
'read once' is 'run once' afaics.
> ret &= check_phy_reg(dev_priv, phy, ICL_PORT_PCS_DW1_LN(0, phy),
> DCC_MODE_SELECT_MASK,
> - DCC_MODE_SELECT_CONTINUOSLY);
> + ~DCC_MODE_SELECT_MASK);
I can see this WA listed only for ADL_P/N/S and TGL (and not for DG2/RKL
for instance). ~DCC_MODE_SELECT_MASK should be 0, maybe add a
dcc_calibration_mode() that could be used below as well.
Could you file a ticket at
https://gfxspecs.intel.com/Predator/Home/Index/49291
which specifies this programming explicitly for each platform, but is
incorrect now wrt. the above WA?
> }
>
> ret &= icl_verify_procmon_ref_values(dev_priv, phy);
> @@ -366,8 +367,9 @@ static void icl_combo_phys_init(struct drm_i915_private *dev_priv)
> intel_de_write(dev_priv, ICL_PORT_TX_DW8_GRP(phy), val);
>
> val = intel_de_read(dev_priv, ICL_PORT_PCS_DW1_LN(0, phy));
> +
> + /* WA_14014367875 Set DCC calibration mode to Read once*/
> val &= ~DCC_MODE_SELECT_MASK;
> - val |= DCC_MODE_SELECT_CONTINUOSLY;
> intel_de_write(dev_priv, ICL_PORT_PCS_DW1_GRP(phy), val);
> }
>
> --
> 2.25.1
>
next prev parent reply other threads:[~2022-08-04 15:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 10:29 [Intel-gfx] [PATCH] drm/i915/combo_phy: Add Workaround to avoid flicker with HBR3 eDP Panels Ankit Nautiyal
2022-08-04 11:41 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for " Patchwork
2022-08-04 15:44 ` Imre Deak [this message]
2022-08-04 16:00 ` [Intel-gfx] [PATCH] " Nautiyal, Ankit K
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=YuvpVtJDEdBrEpeH@ideak-desk.fi.intel.com \
--to=imre.deak@intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=intel-gfx@lists.freedesktop.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