From: Animesh Manna <animesh.manna@intel.com>
To: Manasi Navare <manasi.d.navare@intel.com>
Cc: jani.nikula@intel.com, intel-gfx@lists.freedesktop.org
Subject: Re: [RFC 3/6] drm/i915/dp: Preparation for DP phy compliance auto test.
Date: Tue, 22 Oct 2019 19:42:15 +0530 [thread overview]
Message-ID: <b69f773d-cd93-a5e4-edd2-169e83251058@intel.com> (raw)
In-Reply-To: <20191021232924.GC29989@intel.com>
On 10/22/2019 4:59 AM, Manasi Navare wrote:
> On Thu, Oct 03, 2019 at 08:36:50PM +0530, Animesh Manna wrote:
>> During DP phy compliance auto test mode, sink will request
>> combination of different test pattern with differnt level of
>> vswing, pre-emphasis. Function added to prepare for it.
>>
>> Signed-off-by: Animesh Manna <animesh.manna@intel.com>
> This patch looks good to me, could you add a comment for why
> link_mst is set to false?
Thanks, link_mst is set to false to avoid executing mst related code
during compliance testing... will add as comment.
Regards.
Animesh
>
> Manasi
>
>> ---
>> .../drm/i915/display/intel_display_types.h | 1 +
>> drivers/gpu/drm/i915/display/intel_dp.c | 29 +++++++++++++++++++
>> 2 files changed, 30 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_display_types.h b/drivers/gpu/drm/i915/display/intel_display_types.h
>> index 976669f01a8c..5d6d44fa2594 100644
>> --- a/drivers/gpu/drm/i915/display/intel_display_types.h
>> +++ b/drivers/gpu/drm/i915/display/intel_display_types.h
>> @@ -1142,6 +1142,7 @@ struct intel_dp_compliance_data {
>> u8 video_pattern;
>> u16 hdisplay, vdisplay;
>> u8 bpc;
>> + struct drm_dp_phy_test_params phytest;
>> };
>>
>> struct intel_dp_compliance {
>> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
>> index 7d33e20dfc87..a19141fc672e 100644
>> --- a/drivers/gpu/drm/i915/display/intel_dp.c
>> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
>> @@ -4738,9 +4738,38 @@ static u8 intel_dp_autotest_edid(struct intel_dp *intel_dp)
>> return test_result;
>> }
>>
>> +static u8 intel_dp_prepare_phytest(struct intel_dp *intel_dp)
>> +{
>> + struct drm_dp_phy_test_params *data =
>> + &intel_dp->compliance.test_data.phytest;
>> + u8 link_status[DP_LINK_STATUS_SIZE];
>> +
>> + if (!drm_dp_get_phy_test_pattern(&intel_dp->aux, data)) {
>> + DRM_DEBUG_KMS("DP Phy Test pattern AUX read failure\n");
>> + return DP_TEST_NAK;
>> + }
>> +
>> + if (!intel_dp_get_link_status(intel_dp, link_status)) {
>> + DRM_DEBUG_KMS("failed to get link status\n");
>> + return DP_TEST_NAK;
>> + }
>> +
>> + intel_dp->link_mst = false;
>> +
>> + /* retrieve vswing & pre-emphasis setting */
>> + intel_get_adjust_train(intel_dp, link_status);
>> +
>> + return DP_TEST_ACK;
>> +}
>> +
>> static u8 intel_dp_autotest_phy_pattern(struct intel_dp *intel_dp)
>> {
>> u8 test_result = DP_TEST_NAK;
>> +
>> + test_result = intel_dp_prepare_phytest(intel_dp);
>> + if (test_result != DP_TEST_ACK)
>> + DRM_ERROR("Phy test preparation failed\n");
>> +
>> return test_result;
>> }
>>
>> --
>> 2.22.0
>>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-10-22 14:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-03 15:06 [RFC 0/6] DP Phy compliace auto test Animesh Manna
2019-10-03 15:06 ` [RFC 1/6] drm/dp: get/set phy compliance pattern Animesh Manna
2019-10-21 23:27 ` Manasi Navare
2019-10-22 13:29 ` Animesh Manna
2019-11-05 23:12 ` Manasi Navare
2019-11-05 23:12 ` [Intel-gfx] " Manasi Navare
2019-10-03 15:06 ` [RFC 2/6] drm/i915/dp: Move vswing/pre-emphasis adjustment calculation Animesh Manna
2019-10-21 22:57 ` Manasi Navare
2019-10-22 14:04 ` Animesh Manna
2019-10-22 17:40 ` Manasi Navare
2019-10-24 11:45 ` Animesh Manna
2019-10-24 11:45 ` [Intel-gfx] " Animesh Manna
2019-10-03 15:06 ` [RFC 3/6] drm/i915/dp: Preparation for DP phy compliance auto test Animesh Manna
2019-10-21 23:29 ` Manasi Navare
2019-10-22 14:12 ` Animesh Manna [this message]
2019-10-03 15:06 ` [RFC 4/6] drm/i915/dp: Register definition for DP compliance register Animesh Manna
2019-10-03 15:06 ` [RFC 5/6] drm/i915/dp: Update the pattern as per request Animesh Manna
2019-10-03 15:06 ` [RFC 6/6] drm/i915/dp: Program vswing, pre-emphasis, test-pattern Animesh Manna
2019-10-21 23:47 ` Manasi Navare
2019-10-22 15:07 ` Animesh Manna
2019-10-22 18:41 ` Manasi Navare
2019-10-03 17:36 ` ✓ Fi.CI.BAT: success for DP Phy compliace auto test Patchwork
2019-10-04 3:07 ` ✗ Fi.CI.IGT: failure " 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=b69f773d-cd93-a5e4-edd2-169e83251058@intel.com \
--to=animesh.manna@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=manasi.d.navare@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