From: Jani Nikula <jani.nikula@linux.intel.com>
To: Todd Previte <tprevite@gmail.com>, dri-devel@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/dp: Clarify automated test constant and add constant for FAUX test pattern
Date: Mon, 07 Oct 2013 11:05:57 +0300 [thread overview]
Message-ID: <87fvsd33q2.fsf@intel.com> (raw)
In-Reply-To: <1380916743-20352-1-git-send-email-tprevite@gmail.com>
On Fri, 04 Oct 2013, Todd Previte <tprevite@gmail.com> wrote:
> - DP_TEST_LINK_PATTERN is ambiguous, rename to DP_TEST_LINK_VIDEO_PATTERN to clarify
> - Added DP_TEST_LINK_FAUX_PATTERN to support automated testing of Fast AUX
>
> Signed-off-by: Todd Previte <tprevite@gmail.com>
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
> ---
> include/drm/drm_dp_helper.h | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/include/drm/drm_dp_helper.h b/include/drm/drm_dp_helper.h
> index ae8dbfb..34c8202 100644
> --- a/include/drm/drm_dp_helper.h
> +++ b/include/drm/drm_dp_helper.h
> @@ -266,9 +266,10 @@
>
> #define DP_TEST_REQUEST 0x218
> # define DP_TEST_LINK_TRAINING (1 << 0)
> -# define DP_TEST_LINK_PATTERN (1 << 1)
> +# define DP_TEST_LINK_VIDEO_PATTERN (1 << 1)
> # define DP_TEST_LINK_EDID_READ (1 << 2)
> # define DP_TEST_LINK_PHY_TEST_PATTERN (1 << 3) /* DPCD >= 1.1 */
> +# define DP_TEST_LINK_FAUX_PATTERN (1 << 4) /* DPCD >= 1.2 */
>
> #define DP_TEST_LINK_RATE 0x219
> # define DP_LINK_RATE_162 (0x6)
> --
> 1.8.1.2
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2013-10-07 8:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-04 19:59 [PATCH] drm/dp: Clarify automated test constant and add constant for FAUX test pattern Todd Previte
2013-10-07 8:05 ` Jani Nikula [this message]
2013-12-17 19:32 ` Jesse Barnes
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=87fvsd33q2.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--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;
as well as URLs for NNTP newsgroup(s).