From: Todd Previte <tprevite@gmail.com>
To: Daniel Vetter <daniel@ffwll.ch>, Paulo Zanoni <przanoni@gmail.com>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 07/17] drm/i915: Add and implement the debugfs 'show' functions for Displayport compliance
Date: Wed, 18 Feb 2015 09:45:32 -0700 [thread overview]
Message-ID: <54E4C1AC.6070901@gmail.com> (raw)
In-Reply-To: <20141217201213.GB2711@phenom.ffwll.local>
On 12/17/14 1:12 PM, Daniel Vetter wrote:
> On Tue, Dec 16, 2014 at 05:00:38PM -0200, Paulo Zanoni wrote:
>> 2014-12-10 21:53 GMT-02:00 Todd Previte<tprevite@gmail.com>:
>>> + if (intel_encoder->type == INTEL_OUTPUT_DISPLAYPORT) {
>>> + if (intel_encoder->new_crtc) {
>>> + crtc_config = &intel_encoder->new_crtc->config;
>>> + pipe_bpp = crtc_config->pipe_bpp;
>>> + mode = &crtc_config->adjusted_mode;
>>> + hres = mode->hdisplay;
>>> + vres = mode->vdisplay;
>>> + } else if (intel_encoder->base.crtc) {
>>> + icrtc = to_intel_crtc(intel_encoder->base.crtc);
>>> + pipe_bpp = icrtc->config.pipe_bpp;
>>> + mode = &icrtc->config.adjusted_mode;
>>> + hres = mode->hdisplay;
>>> + vres = mode->vdisplay;
>>> + } else {
>>> + pipe_bpp = 0;
>>> + hres = vres = 0;
>>> + }
>> Why do you have this new_crtc vs current_crtc vs no crtc distinction
>> here? Is it really necessary? Shouldn't the "DP testing debugfs
>> protocol" establish when exactly the information should be queried,
>> and then give some errors in case information is being requested at
>> the wrong time?
> Presuming adequate locking exists (haven't checked tbh) new_* pointers always
> match the equivalent base pointers. new_ pointers/structures are
> exclusively for modeset code (and specifically state computation). I guess
> the new_crtc case needs to be dropped here.
> -Daniel
I tested this again with the new_crtc case removed and it appears to
work correctly. So the new_crtc case has been removed. The changes have
been integrated into the monster patch.
-T
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-02-18 16:45 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 23:53 [intel-gfx] Displayport Compliance Testing V2 Todd Previte
2014-12-10 23:53 ` [PATCH 01/17] drm/i915: Add automated testing support for Displayport compliance testing Todd Previte
2014-12-12 20:25 ` Paulo Zanoni
2015-02-18 16:36 ` Todd Previte
2014-12-10 23:53 ` [PATCH 02/17] drm/i915: Update intel_dp_check_link_status() " Todd Previte
2014-12-15 16:36 ` Paulo Zanoni
2015-02-18 16:36 ` Todd Previte
2015-04-06 23:52 ` Paulo Zanoni
2014-12-10 23:53 ` [PATCH 03/17] drm/i915: Add a delay in Displayport AUX transactions for " Todd Previte
2014-12-15 17:35 ` Paulo Zanoni
2015-02-18 16:37 ` Todd Previte
2014-12-10 23:53 ` [PATCH 04/17] drm/i915: Add debugfs information for Displayport " Todd Previte
2014-12-15 13:11 ` Jani Nikula
2015-02-18 16:37 ` Todd Previte
2014-12-10 23:53 ` [PATCH 05/17] drm/i915: Add file ops for Displayport configuration in debugfs Todd Previte
2014-12-10 23:53 ` [PATCH 06/17] drm/i915: Add support functions in debugfs for handling Displayport compliance configuration Todd Previte
2014-12-15 19:25 ` Paulo Zanoni
2014-12-10 23:53 ` [PATCH 07/17] drm/i915: Add and implement the debugfs 'show' functions for Displayport compliance Todd Previte
2014-12-16 19:00 ` Paulo Zanoni
2014-12-17 20:12 ` Daniel Vetter
2015-02-18 16:45 ` Todd Previte [this message]
2015-02-18 16:41 ` Todd Previte
2014-12-10 23:53 ` [PATCH 08/17] drm/i915: Add Displayport link configuration structure Todd Previte
2014-12-10 23:53 ` [PATCH 09/17] drm/i915: Add config parsing utilities in debugfs for Displayport compliance Todd Previte
2014-12-10 23:53 ` [PATCH 10/17] drm/i915: Implement the 'open' and 'write' debugfs functions " Todd Previte
2014-12-10 23:53 ` [PATCH 11/17] drm/i915: Update the EDID automated compliance test function Todd Previte
2014-12-17 16:25 ` Paulo Zanoni
2014-12-17 20:20 ` Daniel Vetter
[not found] ` <54E4C490.7080001@gmail.com>
2015-02-20 16:55 ` Daniel Vetter
2015-02-18 16:47 ` Todd Previte
2015-02-23 15:55 ` Daniel Vetter
2014-12-10 23:53 ` [PATCH 12/17] drm/i915: Update intel_dp_compute_config() to handle compliance test requests Todd Previte
2014-12-17 17:04 ` Paulo Zanoni
2015-01-07 19:28 ` Clint Taylor
2015-02-18 16:59 ` Todd Previte
2014-12-10 23:53 ` [PATCH 13/17] drm/i915: Update intel_dp_hpd_pulse() to check link status for non-MST operation Todd Previte
2014-12-17 17:57 ` Paulo Zanoni
2014-12-17 20:30 ` Daniel Vetter
2015-02-18 17:06 ` Todd Previte
2015-02-18 17:06 ` Todd Previte
2014-12-10 23:53 ` [PATCH 14/17] drm/i915: Add debugfs function to check connector status for compliance testing Todd Previte
2014-12-17 18:03 ` Paulo Zanoni
2015-02-18 17:08 ` Todd Previte
2015-02-18 23:09 ` Todd Previte
2014-12-10 23:53 ` [PATCH 15/17] drm/i915: Update debugfs functions for Displayport " Todd Previte
2014-12-10 23:53 ` [PATCH 16/17] drm/i915: Add new debugfs file for Displaypor compliance test control Todd Previte
2014-12-10 23:53 ` [PATCH 17/17] drm/i915: Add debugfs write and test param parsing function for DP " Todd Previte
2014-12-16 7:13 ` shuang.he
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=54E4C1AC.6070901@gmail.com \
--to=tprevite@gmail.com \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=przanoni@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 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.