From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: matthew.s.atwood@intel.com
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/dp: add extended receiver capability field present bit
Date: Thu, 19 Jul 2018 14:04:06 -0700 [thread overview]
Message-ID: <20180719210406.GO31791@intel.com> (raw)
In-Reply-To: <20180719203549.28266-1-matthew.s.atwood@intel.com>
On Thu, Jul 19, 2018 at 01:35:48PM -0700, matthew.s.atwood@intel.com wrote:
> From: Matt Atwood <matthew.s.atwood@intel.com>
>
> This bit was added to DP Training Aux RD interval sometime between DP
> 1.2 and DP 1.3.
I understand that some 1.2 version that I had here that caused
all the trouble around XXX 1.2, but since one of the requests
from Jani was to clarify and remove the 1.2 I went there to check
again and that version that I had here doesn't work anymore.
So I went to VESA site and checked and it is not there on latest
official 1.2a.
It is there on 1.3.
This message should be updated now.
> Via description of the spec this field indicates the
> panels true capabilities are described in DPCD address space 02200h
> through 022FFh.
>
> v2: version comment update
>
> Signed-off-by: Matt Atwood <matthew.s.atwood@intel.com>
> ---
> include/drm/drm_dp_helper.h | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/include/drm/drm_dp_helper.h b/include/drm/drm_dp_helper.h
> index c01564991a9f..28061c69136b 100644
> --- a/include/drm/drm_dp_helper.h
> +++ b/include/drm/drm_dp_helper.h
> @@ -123,8 +123,9 @@
> # define DP_FRAMING_CHANGE_CAP (1 << 1)
> # define DP_DPCD_DISPLAY_CONTROL_CAPABLE (1 << 3) /* edp v1.2 or higher */
>
> -#define DP_TRAINING_AUX_RD_INTERVAL 0x00e /* XXX 1.2? */
> -# define DP_TRAINING_AUX_RD_MASK 0x7F /* XXX 1.2? */
> +#define DP_TRAINING_AUX_RD_INTERVAL 0x00e /* XXX 1.2? */
> +# define DP_TRAINING_AUX_RD_MASK 0x7F /* XXX 1.3? */
> +# define DP_EXTENDED_RECEIVER_CAP_FIELD_PRESENT (1 << 7)/* XXX 1.3? */
Since that is the official and clear thing we should now remove XXX
and add /* DP 1.3 */
I believe that during 1.2 times we might had seen a lot of those
bizare cases when one version has it and another doesn't, and probably
that was the cause of many /* XXX 1.2? */ we have on the driver.
But please note that there is no XXX for 1.3 and 1.4, since things
are very clear and organized.
>
> #define DP_ADAPTER_CAP 0x00f /* 1.2 */
> # define DP_FORCE_LOAD_SENSE_CAP (1 << 0)
> --
> 2.17.1
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-07-19 21:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 21:49 [PATCH 1/2] drm/dp: add extended receiver capability field present bit matthew.s.atwood
2018-07-17 21:49 ` [PATCH 2/2] drm/i915: implement EXTENDED_RECEIVER_CAPABILITY_FIELD_PRESENT matthew.s.atwood
2018-07-17 22:34 ` [Intel-gfx] " Dhinakaran Pandiyan
2018-07-17 22:36 ` Rodrigo Vivi
2018-07-17 23:01 ` Dhinakaran Pandiyan
2018-07-19 20:35 ` [PATCH 1/2] drm/dp: add extended receiver capability field present bit matthew.s.atwood
2018-07-19 20:35 ` [PATCH 2/2] drm/i915: implement EXTENDED_RECEIVER_CAPABILITY_FIELD_PRESENT matthew.s.atwood
2018-07-19 21:07 ` Rodrigo Vivi
2018-07-19 21:47 ` Atwood, Matthew S
2018-07-19 22:06 ` Rodrigo Vivi
2018-07-19 21:04 ` Rodrigo Vivi [this message]
2018-07-17 22:00 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/2] drm/dp: add extended receiver capability field present bit Patchwork
2018-07-17 22:24 ` ✓ Fi.CI.BAT: success " Patchwork
2018-07-18 6:05 ` ✓ Fi.CI.IGT: " Patchwork
2018-07-18 22:36 ` [PATCH 1/2] " Rodrigo Vivi
2018-07-19 21:31 ` ✗ Fi.CI.BAT: failure for series starting with [1/2] drm/dp: add extended receiver capability field present bit (rev3) Patchwork
-- strict thread matches above, loose matches on Subject: below --
2018-07-20 16:18 [PATCH 1/2] drm/dp: add extended receiver capability field present bit matthew.s.atwood
2018-07-20 17:46 ` Rodrigo Vivi
2018-07-23 21:27 matthew.s.atwood
2018-07-24 16:29 ` Rodrigo Vivi
2018-08-14 23:25 ` Manasi Navare
2018-08-14 23:56 ` Manasi Navare
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=20180719210406.GO31791@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.s.atwood@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.