From: Manasi Navare <manasi.d.navare@intel.com> To: Animesh Manna <animesh.manna@intel.com> Cc: jani.nikula@intel.com, nidhi1.gupta@intel.com, intel-gfx@lists.freedesktop.org Subject: Re: [RFC 3/7] drm/i915/dp: Preparation for DP phy compliance auto test Date: Sun, 17 Nov 2019 20:47:41 -0800 [thread overview] Message-ID: <20191118044740.GB1135@intel.com> (raw) In-Reply-To: <20191115152549.23047-4-animesh.manna@intel.com> On Fri, Nov 15, 2019 at 08:55:45PM +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 looks good to me, Reviewed-by: Manasi Navare <manasi.d.navare@intel.com> Manasi > --- > .../drm/i915/display/intel_display_types.h | 1 + > drivers/gpu/drm/i915/display/intel_dp.c | 24 +++++++++++++++++++ > 2 files changed, 25 insertions(+) > > diff --git a/drivers/gpu/drm/i915/display/intel_display_types.h b/drivers/gpu/drm/i915/display/intel_display_types.h > index 83ea04149b77..c17866f126c9 100644 > --- a/drivers/gpu/drm/i915/display/intel_display_types.h > +++ b/drivers/gpu/drm/i915/display/intel_display_types.h > @@ -1205,6 +1205,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 cc8e0d1a73af..338d3744c5d5 100644 > --- a/drivers/gpu/drm/i915/display/intel_dp.c > +++ b/drivers/gpu/drm/i915/display/intel_dp.c > @@ -4936,9 +4936,33 @@ 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; > + > + 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; > + } > + > + /* > + * link_mst is set to false to avoid executing mst related code > + * during compliance testing. > + */ > + intel_dp->link_mst = false; > + > + 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
WARNING: multiple messages have this Message-ID (diff)
From: Manasi Navare <manasi.d.navare@intel.com> To: Animesh Manna <animesh.manna@intel.com> Cc: jani.nikula@intel.com, nidhi1.gupta@intel.com, intel-gfx@lists.freedesktop.org Subject: Re: [Intel-gfx] [RFC 3/7] drm/i915/dp: Preparation for DP phy compliance auto test Date: Sun, 17 Nov 2019 20:47:41 -0800 [thread overview] Message-ID: <20191118044740.GB1135@intel.com> (raw) Message-ID: <20191118044741.0rYeQNY9VsdV_-8PxayxbqyfA-5FBwYwfH-EA-IowtE@z> (raw) In-Reply-To: <20191115152549.23047-4-animesh.manna@intel.com> On Fri, Nov 15, 2019 at 08:55:45PM +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 looks good to me, Reviewed-by: Manasi Navare <manasi.d.navare@intel.com> Manasi > --- > .../drm/i915/display/intel_display_types.h | 1 + > drivers/gpu/drm/i915/display/intel_dp.c | 24 +++++++++++++++++++ > 2 files changed, 25 insertions(+) > > diff --git a/drivers/gpu/drm/i915/display/intel_display_types.h b/drivers/gpu/drm/i915/display/intel_display_types.h > index 83ea04149b77..c17866f126c9 100644 > --- a/drivers/gpu/drm/i915/display/intel_display_types.h > +++ b/drivers/gpu/drm/i915/display/intel_display_types.h > @@ -1205,6 +1205,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 cc8e0d1a73af..338d3744c5d5 100644 > --- a/drivers/gpu/drm/i915/display/intel_dp.c > +++ b/drivers/gpu/drm/i915/display/intel_dp.c > @@ -4936,9 +4936,33 @@ 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; > + > + 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; > + } > + > + /* > + * link_mst is set to false to avoid executing mst related code > + * during compliance testing. > + */ > + intel_dp->link_mst = false; > + > + 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-11-18 4:44 UTC|newest] Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-11-15 15:25 [RFC 0/7] DP Phy compliace auto test Animesh Manna 2019-11-15 15:25 ` [Intel-gfx] " Animesh Manna 2019-11-15 15:25 ` [RFC 1/7] drm/dp: get/set phy compliance pattern Animesh Manna 2019-11-15 15:25 ` [Intel-gfx] " Animesh Manna 2019-11-18 4:04 ` Manasi Navare 2019-11-18 4:04 ` [Intel-gfx] " Manasi Navare 2019-11-18 18:39 ` Animesh Manna 2019-11-18 18:39 ` [Intel-gfx] " Animesh Manna 2019-11-15 15:25 ` [RFC 2/7] drm/i915/dp: Move vswing/pre-emphasis adjustment calculation Animesh Manna 2019-11-15 15:25 ` [Intel-gfx] " Animesh Manna 2019-11-15 15:25 ` [RFC 3/7] drm/i915/dp: Preparation for DP phy compliance auto test Animesh Manna 2019-11-15 15:25 ` [Intel-gfx] " Animesh Manna 2019-11-18 4:47 ` Manasi Navare [this message] 2019-11-18 4:47 ` Manasi Navare 2019-11-15 15:25 ` [RFC 4/7] drm/i915/dp: Notify testapp using uevent and debugfs entry Animesh Manna 2019-11-15 15:25 ` [Intel-gfx] " Animesh Manna 2019-11-18 4:58 ` Manasi Navare 2019-11-18 4:58 ` [Intel-gfx] " Manasi Navare 2019-11-18 5:06 ` Manasi Navare 2019-11-18 5:06 ` [Intel-gfx] " Manasi Navare 2019-11-18 18:45 ` Animesh Manna 2019-11-18 18:45 ` [Intel-gfx] " Animesh Manna 2019-11-15 15:25 ` [RFC 5/7] drm/i915/dp: Register definition for DP compliance register Animesh Manna 2019-11-15 15:25 ` [Intel-gfx] " Animesh Manna 2019-11-18 5:00 ` Manasi Navare 2019-11-18 5:00 ` [Intel-gfx] " Manasi Navare 2019-11-15 15:25 ` [RFC 6/7] drm/i915/dp: Update the pattern as per request Animesh Manna 2019-11-15 15:25 ` [Intel-gfx] " Animesh Manna 2019-11-18 6:41 ` Manasi Navare 2019-11-18 6:41 ` [Intel-gfx] " Manasi Navare 2019-11-18 18:47 ` Animesh Manna 2019-11-18 18:47 ` [Intel-gfx] " Animesh Manna 2019-12-11 23:44 ` Manasi Navare 2019-11-15 15:25 ` [RFC 7/7] drm/i915/dp: Program vswing, pre-emphasis, test-pattern Animesh Manna 2019-11-15 15:25 ` [Intel-gfx] " Animesh Manna 2019-11-18 7:53 ` Manasi Navare 2019-11-18 7:53 ` [Intel-gfx] " Manasi Navare 2019-12-11 23:50 ` Manasi Navare 2019-12-13 17:24 ` Animesh Manna 2020-01-14 21:38 ` Manasi Navare 2020-01-20 13:53 ` Manna, Animesh 2020-01-24 0:56 ` Manasi Navare 2019-11-15 19:27 ` ✗ Fi.CI.BUILD: failure for DP Phy compliace auto test Patchwork 2019-11-15 19:27 ` [Intel-gfx] " 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=20191118044740.GB1135@intel.com \ --to=manasi.d.navare@intel.com \ --cc=animesh.manna@intel.com \ --cc=intel-gfx@lists.freedesktop.org \ --cc=jani.nikula@intel.com \ --cc=nidhi1.gupta@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: linkBe 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.