From: Sivakumar Thulasimani <sivakumar.thulasimani@intel.com>
To: tprevite@gmail.com, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: fix checksum write for automated test reply
Date: Mon, 27 Jul 2015 10:11:35 +0530 [thread overview]
Message-ID: <55B5B67F.1080502@intel.com> (raw)
In-Reply-To: <1437570061-29126-1-git-send-email-sivakumar.thulasimani@intel.com>
Any comments for this change ?
On 7/22/2015 6:31 PM, Sivakumar Thulasimani wrote:
> From: "Thulasimani,Sivakumar" <sivakumar.thulasimani@intel.com>
>
> DP spec requires the checksum of the last block read to be written
> when replying to TEST_EDID_READ. This patch fixes the current code
> to do the same.
>
> Signed-off-by: Sivakumar Thulasimani <sivakumar.thulasimani@intel.com>
> ---
> drivers/gpu/drm/i915/intel_dp.c | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
> index f1b9f93..fa6e202 100644
> --- a/drivers/gpu/drm/i915/intel_dp.c
> +++ b/drivers/gpu/drm/i915/intel_dp.c
> @@ -4090,9 +4090,16 @@ static uint8_t intel_dp_autotest_edid(struct intel_dp *intel_dp)
> intel_dp->aux.i2c_defer_count);
> intel_dp->compliance_test_data = INTEL_DP_RESOLUTION_FAILSAFE;
> } else {
> + struct edid *block = intel_connector->detect_edid;
> +
> + /* We have to write the checksum
> + * of the last block read
> + */
> + block += intel_connector->detect_edid->extensions;
> +
> if (!drm_dp_dpcd_write(&intel_dp->aux,
> DP_TEST_EDID_CHECKSUM,
> - &intel_connector->detect_edid->checksum,
> + &block->checksum,
> 1))
> DRM_DEBUG_KMS("Failed to write EDID checksum\n");
>
--
regards,
Sivakumar
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-07-27 4:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 13:01 [PATCH] drm/i915: fix checksum write for automated test reply Sivakumar Thulasimani
2015-07-23 21:47 ` shuang.he
2015-07-27 4:41 ` Sivakumar Thulasimani [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-08-07 9:44 Sivakumar Thulasimani
2015-08-12 6:06 ` Sivakumar Thulasimani
2015-08-12 12:43 ` Daniel Vetter
2015-08-14 8:27 ` Jindal, Sonika
2015-08-14 9:12 ` Daniel Vetter
2015-07-22 10:06 Sivakumar Thulasimani
2015-07-22 12:00 ` Daniel Vetter
2015-07-22 12:59 ` Sivakumar Thulasimani
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=55B5B67F.1080502@intel.com \
--to=sivakumar.thulasimani@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tprevite@gmail.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