From: Ander Conselvan De Oliveira <conselvan2@gmail.com>
To: Manasi Navare <manasi.d.navare@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/5] drm/i915: Disable the Link training automation support
Date: Mon, 23 May 2016 11:10:24 +0300 [thread overview]
Message-ID: <1463991024.2807.9.camel@gmail.com> (raw)
In-Reply-To: <1461979695-27113-3-git-send-email-manasi.d.navare@intel.com>
On Fri, 2016-04-29 at 18:28 -0700, Manasi Navare wrote:
> Kernel does not have automation support for DP compliance Link
> training tests. So the Link Training test handler should return
> a TEST_NAK.
Is this test activated by short or long pulse? The commit message of commit
09b1eb130e43 ("drm/i915: Move Displayport test request and sink IRQ logic to
intel_dp_detect()") suggests the latter. In that case, the order of this and
patch 1 should be inverted.
Otherwise, for patches 1 and 2:
Reviewed-by: Ander Conselvan de Oliveira <conselvan2@gmail.com>
>
> Signed-off-by: Manasi Navare <manasi.d.navare@intel.com>
> ---
> drivers/gpu/drm/i915/intel_dp.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
> index 19a95ed..0961f22 100644
> --- a/drivers/gpu/drm/i915/intel_dp.c
> +++ b/drivers/gpu/drm/i915/intel_dp.c
> @@ -4011,7 +4011,7 @@ intel_dp_get_sink_irq_esi(struct intel_dp *intel_dp, u8
> *sink_irq_vector)
>
> static uint8_t intel_dp_autotest_link_training(struct intel_dp *intel_dp)
> {
> - uint8_t test_result = DP_TEST_ACK;
> + uint8_t test_result = DP_TEST_NAK;
> return test_result;
> }
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-05-23 8:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-30 1:28 [PATCH 0/5] Add automation support for DP compliance Tests Manasi Navare
2016-04-30 1:28 ` [PATCH 1/5] drm/i915: Invoke the DP Compliance test request handler in the short pulse path Manasi Navare
2016-05-24 10:02 ` Thulasimani, Sivakumar
2016-04-30 1:28 ` [PATCH 2/5] drm/i915: Disable the Link training automation support Manasi Navare
2016-05-23 8:10 ` Ander Conselvan De Oliveira [this message]
2016-05-25 19:35 ` Manasi Navare
2016-04-30 1:28 ` [PATCH 3/5] drm/i915: Fixes to support the DP Compliance EDID tests Manasi Navare
2016-05-23 8:18 ` Ander Conselvan De Oliveira
2016-05-24 9:31 ` Shubhangi Shrivastava
2016-05-24 9:35 ` Shubhangi Shrivastava
2016-05-26 0:22 ` Manasi Navare
2016-05-26 8:56 ` Ander Conselvan De Oliveira
2016-04-30 1:28 ` [PATCH 4/5] Add support for forcing 6 bpc on DP pipes Manasi Navare
2016-05-02 17:52 ` Jim Bride
2016-05-23 8:22 ` Ander Conselvan De Oliveira
2016-05-23 17:42 ` Jim Bride
2016-05-24 5:45 ` Ander Conselvan De Oliveira
2016-05-26 0:42 ` Manasi Navare
2016-05-26 9:00 ` Ander Conselvan De Oliveira
2016-05-25 19:01 ` Manasi Navare
2016-04-30 1:28 ` [PATCH 5/5] drm/i915: Implement intel_dp_autotest_video_pattern function for DP Video pattern compliance tests Manasi Navare
2016-05-23 12:00 ` Ander Conselvan De Oliveira
2016-05-25 22:46 ` Manasi Navare
2016-05-26 9:10 ` Ander Conselvan De Oliveira
2016-04-30 6:24 ` ✓ Fi.CI.BAT: success for Add automation support for DP compliance Tests 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=1463991024.2807.9.camel@gmail.com \
--to=conselvan2@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
--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 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.