From: Todd Previte <tprevite@gmail.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Implement Displayport automated testing
Date: Fri, 04 Oct 2013 11:11:32 -0700 [thread overview]
Message-ID: <524F04D4.2030002@gmail.com> (raw)
In-Reply-To: <20131004104514.GD31587@nuc-i3427.alporthouse.com>
On 10/4/13 3:45 AM, Chris Wilson wrote:
> On Fri, Oct 04, 2013 at 03:32:10AM -0700, Todd Previte wrote:
>> This initial patch adds support for automated testing of the source device
>> to the i915 driver. Most of this patch is infrastructure for the tests;
>> follow up patches will add support for the individual tests with updates
>> to ACK the tests that are supported (or NAK if the test
>> fails/is unsupported).
>>
>> Signed-off-by: Todd Previte <tprevite@gmail.com>
>> ---
>> drivers/gpu/drm/i915/intel_dp.c | 108 +++++++++++++++++++++++++++++++++++++++-
>> include/drm/drm_dp_helper.h | 3 +-
>> 2 files changed, 108 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
>> index 9770160..a042d59 100644
>> --- a/drivers/gpu/drm/i915/intel_dp.c
>> +++ b/drivers/gpu/drm/i915/intel_dp.c
>> @@ -64,6 +64,26 @@ static const struct dp_link_dpll vlv_dpll[] = {
>> { .p1 = 2, .p2 = 2, .n = 1, .m1 = 2, .m2 = 27 } }
>> };
>>
>> +/******************************************************************************
>> +******** Displayport automated testing ********
>> +******************************************************************************/
>> +/* Automated testing function - link training */
>> +static bool
>> +intel_dp_autotest_link_training(struct intel_dp *intel_dp);
> The function comment does little more than spell out the function name.
> What I would prefer to see is a theory-of-operation in the block
> comment. And all these forward declarations can disappear with clear
> ordering in the source code.
> -Chris
>
I wasn't sure which way to go with this and opted for the declarations,
but it's just as easy to reorder the definitions to be prior to their
use in the handler. I'll get that fixed up and add more useful comments
above the functions for V2. Thanks Chris.
-T
next prev parent reply other threads:[~2013-10-04 18:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-04 10:32 [PATCH] drm/i915: Implement Displayport automated testing Todd Previte
2013-10-04 10:45 ` Chris Wilson
2013-10-04 18:11 ` Todd Previte [this message]
2013-10-04 20:39 ` Ben Widawsky
2013-10-04 23:00 ` Todd Previte
2013-10-04 11:49 ` Jani Nikula
2013-10-04 18:11 ` Todd Previte
2013-10-04 19:53 ` [PATCH V2] " Todd Previte
2013-11-01 22:44 ` [PATCH V3] " Todd Previte
2013-11-01 22:44 ` [PATCH] " Todd Previte
2013-11-05 9:21 ` Jani Nikula
2013-11-05 21:01 ` Todd Previte
2013-11-05 21:47 ` Daniel Vetter
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=524F04D4.2030002@gmail.com \
--to=tprevite@gmail.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
/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