Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
To: <imre.deak@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 21:30:33 +0530	[thread overview]
Message-ID: <1dbf2ed1-fc2e-e34e-9d95-ca87bc9f60ff@intel.com> (raw)
In-Reply-To: <YuvpVtJDEdBrEpeH@ideak-desk.fi.intel.com>

Thanks Imre, for the comments, please find my response inline:

On 8/4/2022 9:14 PM, Imre Deak wrote:
> 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.

Indeed. Will fix the format and the typo here.


>
>>   		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
Alright, so perhaps need to use Platform check.
> for instance). ~DCC_MODE_SELECT_MASK should be 0, maybe add a
> dcc_calibration_mode() that could be used below as well.

Yes right, I did realize mask should have been 0. Will do the suggested 
changes.

>
> 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?

Makes sense, will file a bspec ticket.

Regards,

Ankit

>
>>   	}
>>   
>>   	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
>>

      reply	other threads:[~2022-08-04 16:03 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 ` [Intel-gfx] [PATCH] " Imre Deak
2022-08-04 16:00   ` Nautiyal, Ankit K [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=1dbf2ed1-fc2e-e34e-9d95-ca87bc9f60ff@intel.com \
    --to=ankit.k.nautiyal@intel.com \
    --cc=imre.deak@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