All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Lee, Shawn C" <shawn.c.lee@intel.com>
To: "20210707153318.13903-1-shawn.c.lee@intel.com"
	<20210707153318.13903-1-shawn.c.lee@intel.com>,
	"Nikula, Jani" <jani.nikula@intel.com>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>
Cc: "Tseng, William" <william.tseng@intel.com>,
	"Chiou, Cooper" <cooper.chiou@intel.com>
Subject: RE: [PATCH v2] drm/dp: follow DP link CTS spec to read link status back
Date: Mon, 12 Jul 2021 14:16:23 +0000	[thread overview]
Message-ID: <CO6PR11MB5651EA11C5A461BC7F0617DEA3159@CO6PR11MB5651.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CO6PR11MB5651FB25D78B67BFD44E1D80A3199@CO6PR11MB5651.namprd11.prod.outlook.com>


On Wed, 08 Jul 2021, Lee Shawn C <shawn.c.lee@intel.com> wrote:
>On Wed, 07 Jul 2021, 4:14 p.m, Jani Nikula <jani.nikula@intel.com> wrote:
>>On Wed, 07 Jul 2021, Lee Shawn C <shawn.c.lee@intel.com> wrote:
>>> Refer to DP link CTS 1.2/1.4 spec, the following test case request 
>>> source read DPCD 200h - 205h to get latest link status from sink.
>>>
>>> (4.3.2.4) Handling of IRQ HPD Pulse with No Error Status Bits Set
>>> (400.3.2.1) Successful Link Re-training After IRQ HPD Pulse
>>>             Due to Loss of Symbol Lock: HBR2 Extension
>>> (400.3.2.2) Successful Link Re-training After IRQ HPD Pulse Due
>>>             to Loss of Clock Recovery Lock: HBR2 Extension
>>> (400.3.2.3) Successful Link Re-training After IRQ HPD Pulse Due
>>>             to Loss of Inter-lane Alignment Lock: HBR2 Extension
>>>
>>> So far, DRM DP driver just read back the link status from 202h to 
>>> 207h. DPR-120 would judge source can't pass these cases and shows 
>>> below error messages.
>>>
>>> "Test FAILED, Source DUT does not read DPCD registers 200h-205h 
>>> within
>>> 100 ms".
>>
>>Acked-by: Jani Nikula <jani.nikula@intel.com>
>>
>>for making the test pass iff everything else seems to work.
>>
>>The underlying question is, though, should we look at 0x200-0x201 for some status we don't look at?
>>
>
>Look into 200h. While doing link train with DPRX. In my opinion, sink_count and cp_ready status should be constant.
>And sink would trigger HPD to source to notify 201h value was changed. Seems source driver don't need this value at link training stage as well. What do you think?
>
>Best regards,
>Shawn
>

Hi Simon and all, 

Please share your recommendations for this patch to pass DP link layer compliance test. Thanks!

Best regards,
Shawn

>>
>>>
>>> v2: Use sizeof() to retrieve array size.
>>>
>>> Cc: Jani Nikula <jani.nikula@intel.com>
>>> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
>>> Cc: Lyude Paul <lyude@redhat.com>
>>> Cc: Simon Ser <contact@emersion.fr>
>>> Cc: Cooper Chiou <cooper.chiou@intel.com>
>>> Cc: William Tseng <william.tseng@intel.com>
>>> Signed-off-by: Lee Shawn C <shawn.c.lee@intel.com>
>>> ---
>>>  drivers/gpu/drm/drm_dp_helper.c | 10 ++++++----
>>>  1 file changed, 6 insertions(+), 4 deletions(-)
>>>
>>> diff --git a/drivers/gpu/drm/drm_dp_helper.c 
>>> b/drivers/gpu/drm/drm_dp_helper.c index 24bbc710c825..4f03df317d62
>>> 100644
>>> --- a/drivers/gpu/drm/drm_dp_helper.c
>>> +++ b/drivers/gpu/drm/drm_dp_helper.c
>>> @@ -410,17 +410,19 @@ int drm_dp_dpcd_read_phy_link_status(struct drm_dp_aux *aux,
>>>  				     u8 link_status[DP_LINK_STATUS_SIZE])  {
>>>  	int ret;
>>> +	u8 full_link_stat[DP_LINK_STATUS_SIZE + 2];
>>>  
>>>  	if (dp_phy == DP_PHY_DPRX) {
>>>  		ret = drm_dp_dpcd_read(aux,
>>> -				       DP_LANE0_1_STATUS,
>>> -				       link_status,
>>> -				       DP_LINK_STATUS_SIZE);
>>> +				       DP_SINK_COUNT,
>>> +				       full_link_stat,
>>> +				       sizeof(full_link_stat));
>>>  
>>>  		if (ret < 0)
>>>  			return ret;
>>>  
>>> -		WARN_ON(ret != DP_LINK_STATUS_SIZE);
>>> +		memcpy(link_status, full_link_stat + 2, DP_LINK_STATUS_SIZE);
>>> +		WARN_ON(ret != DP_LINK_STATUS_SIZE + 2);
>>>  
>>>  		return 0;
>>>  	}
>>
>>--
>>Jani Nikula, Intel Open Source Graphics Center
>

  reply	other threads:[~2021-07-12 14:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-07 15:00 [PATCH] drm/dp: follow DP link CTS spec to read link status back Lee Shawn C
2021-07-07 15:05 ` Simon Ser
2021-07-07 15:14   ` Lee, Shawn C
2021-07-07 15:33 ` [PATCH v2] " Lee Shawn C
2021-07-07 16:14   ` Jani Nikula
2021-07-08  3:04     ` Lee, Shawn C
2021-07-12 14:16       ` Lee, Shawn C [this message]
2021-08-19  7:55         ` Lee, Shawn C

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=CO6PR11MB5651EA11C5A461BC7F0617DEA3159@CO6PR11MB5651.namprd11.prod.outlook.com \
    --to=shawn.c.lee@intel.com \
    --cc=20210707153318.13903-1-shawn.c.lee@intel.com \
    --cc=cooper.chiou@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=william.tseng@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.