From: Manasi Navare <manasi.d.navare@intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 0/4] Add automation support for DP Compliance (Rev 6)
Date: Mon, 23 Jan 2017 10:39:47 -0800 [thread overview]
Message-ID: <20170123183947.GB15227@intel.com> (raw)
In-Reply-To: <20170123170502.GA15227@intel.com>
On Mon, Jan 23, 2017 at 09:05:02AM -0800, Manasi Navare wrote:
> On Sat, Jan 21, 2017 at 05:16:42PM +0200, Jani Nikula wrote:
> > On Sat, 21 Jan 2017, Manasi Navare <manasi.d.navare@intel.com> wrote:
> > > This patch series addresses all the review comments from the previous series:
> > > https://patchwork.freedesktop.org/series/18256/
> >
> > It does not, and it frustrates me.
> >
> > BR,
> > Jani.
> >
> >
Jani,
I really appreciate all your feedback. I also agree that it is very important
that the patches are correct and improve the driver quality and that non eof the review
comments should be ignored even if it takes many review cycles.
As far as I know, I have addressed the review comments from previous round and answered
the questions/concerns that you had either in the M-L or in IRC.
May be answering them on IRC created some confusion and you thought that it was
unanswered. I will reply to all your review comments from previous round with what
I have chnaged to address it or why it wasnt changed. That way we can make sure that
none of them are getting ignored.
Hope this method works for you.
Regards
Manasi
>
> Hi Jani,
> I have addressed the comments:
>
> * Use link rate instead of link BW, validate the values before storing in the compliance structure
> and return NAK on invalid and read failures.
> * Corrected the definitins in drm_dp_helper.h
>
> Could you please explain which of the comments were not addressed that made it so frustrating?
> It has been frustrating enough for me to be carrying this series of patches for a year almost
> knowing that it passes 100% compliance but still is not merged.
>
> Regards
> Manasi
>
>
> > >
> > > On top of that it also adds a fix for CRC mismatches seen during
> > > 18bpp video pattern compliance testing. This is done by forcing dither
> > > on the pipe to be disabled if it is a 18bpp compliance test request.
> > >
> > > Manasi Navare (4):
> > > drm/i915: Add support for DP link training compliance
> > > drm/i915: Fixes to support DP Compliance EDID tests
> > > drm: Add definitions for DP compliance Video pattern tests
> > > drm/i915: Add support for DP Video pattern compliance tests
> > >
> > > drivers/gpu/drm/i915/i915_debugfs.c | 14 +++-
> > > drivers/gpu/drm/i915/intel_display.c | 7 +-
> > > drivers/gpu/drm/i915/intel_dp.c | 134 +++++++++++++++++++++++++++++++++--
> > > drivers/gpu/drm/i915/intel_dp_mst.c | 7 +-
> > > drivers/gpu/drm/i915/intel_drv.h | 13 ++++
> > > include/drm/drm_dp_helper.h | 57 +++++++++++++++
> > > 6 files changed, 221 insertions(+), 11 deletions(-)
> >
> > --
> > Jani Nikula, Intel Open Source Technology Center
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-01-23 18:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-21 3:09 [PATCH 0/4] Add automation support for DP Compliance (Rev 6) Manasi Navare
2017-01-21 3:09 ` [PATCH 1/4] drm/i915: Add support for DP link training compliance Manasi Navare
2017-01-24 16:16 ` [PATCH v5 " Manasi Navare
2017-01-21 3:09 ` [PATCH 2/4] drm/i915: Fixes to support DP Compliance EDID tests Manasi Navare
2017-01-21 3:09 ` [PATCH 3/4] drm: Add definitions for DP compliance Video pattern tests Manasi Navare
2017-01-24 16:05 ` Jani Nikula
2017-01-21 3:09 ` [PATCH 4/4] drm/i915: Add support for DP Video pattern compliance tests Manasi Navare
2017-01-24 16:21 ` [PATCH v4 " Manasi Navare
2017-01-21 4:24 ` ✓ Fi.CI.BAT: success for Add automation support for DP Compliance (Rev 6) Patchwork
2017-01-21 15:16 ` [PATCH 0/4] " Jani Nikula
2017-01-23 17:05 ` Manasi Navare
2017-01-23 18:39 ` Manasi Navare [this message]
2017-01-24 16:40 ` Jani Nikula
2017-01-24 17:20 ` Manasi Navare
2017-01-24 17:24 ` ✗ Fi.CI.BAT: warning for Add automation support for DP Compliance (Rev 6) (rev3) Patchwork
2017-01-26 14:17 ` [Intel-gfx] [PATCH 0/4] Add automation support for DP Compliance (Rev 6) Jani Nikula
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=20170123183947.GB15227@intel.com \
--to=manasi.d.navare@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.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.