From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 3/8] drm/dp: add some new DPCD macros from DP 2.0 E11
Date: Thu, 27 Jan 2022 09:31:54 +0200 [thread overview]
Message-ID: <YfJKakOSpVPot0EG@intel.com> (raw)
In-Reply-To: <aaeccfb4f2a8c0995f9b2f29e66829c486205712.1643130139.git.jani.nikula@intel.com>
On Tue, Jan 25, 2022 at 07:03:41PM +0200, Jani Nikula wrote:
> Add some of the new additions from DP 2.0 E11.
>
> Cc: Uma Shankar <uma.shankar@intel.com>
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
> include/drm/dp/drm_dp_helper.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/include/drm/dp/drm_dp_helper.h b/include/drm/dp/drm_dp_helper.h
> index c499d735b992..69487bd8ed56 100644
> --- a/include/drm/dp/drm_dp_helper.h
> +++ b/include/drm/dp/drm_dp_helper.h
> @@ -560,6 +560,7 @@ struct drm_panel;
> # define DP_TRAINING_PATTERN_DISABLE 0
> # define DP_TRAINING_PATTERN_1 1
> # define DP_TRAINING_PATTERN_2 2
> +# define DP_TRAINING_PATTERN_2_CDS 3 /* 2.0 E11 */
> # define DP_TRAINING_PATTERN_3 3 /* 1.2 */
> # define DP_TRAINING_PATTERN_4 7 /* 1.4 */
> # define DP_TRAINING_PATTERN_MASK 0x3
> @@ -1350,6 +1351,7 @@ struct drm_panel;
> # define DP_PHY_REPEATER_128B132B_SUPPORTED (1 << 0)
> /* See DP_128B132B_SUPPORTED_LINK_RATES for values */
> #define DP_PHY_REPEATER_128B132B_RATES 0xf0007 /* 2.0 */
> +#define DP_PHY_REPEATER_EQ_DONE 0xf0008 /* 2.0 E11 */
Wonder if we should look at that at some point? The spec doesn't really
say so. Or maybe we should just dump it out of the link training failed?
>
> enum drm_dp_phy {
> DP_PHY_DPRX,
> --
> 2.30.2
--
Ville Syrjälä
Intel
WARNING: multiple messages have this Message-ID (diff)
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org, uma.shankar@intel.com,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 3/8] drm/dp: add some new DPCD macros from DP 2.0 E11
Date: Thu, 27 Jan 2022 09:31:54 +0200 [thread overview]
Message-ID: <YfJKakOSpVPot0EG@intel.com> (raw)
In-Reply-To: <aaeccfb4f2a8c0995f9b2f29e66829c486205712.1643130139.git.jani.nikula@intel.com>
On Tue, Jan 25, 2022 at 07:03:41PM +0200, Jani Nikula wrote:
> Add some of the new additions from DP 2.0 E11.
>
> Cc: Uma Shankar <uma.shankar@intel.com>
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
> include/drm/dp/drm_dp_helper.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/include/drm/dp/drm_dp_helper.h b/include/drm/dp/drm_dp_helper.h
> index c499d735b992..69487bd8ed56 100644
> --- a/include/drm/dp/drm_dp_helper.h
> +++ b/include/drm/dp/drm_dp_helper.h
> @@ -560,6 +560,7 @@ struct drm_panel;
> # define DP_TRAINING_PATTERN_DISABLE 0
> # define DP_TRAINING_PATTERN_1 1
> # define DP_TRAINING_PATTERN_2 2
> +# define DP_TRAINING_PATTERN_2_CDS 3 /* 2.0 E11 */
> # define DP_TRAINING_PATTERN_3 3 /* 1.2 */
> # define DP_TRAINING_PATTERN_4 7 /* 1.4 */
> # define DP_TRAINING_PATTERN_MASK 0x3
> @@ -1350,6 +1351,7 @@ struct drm_panel;
> # define DP_PHY_REPEATER_128B132B_SUPPORTED (1 << 0)
> /* See DP_128B132B_SUPPORTED_LINK_RATES for values */
> #define DP_PHY_REPEATER_128B132B_RATES 0xf0007 /* 2.0 */
> +#define DP_PHY_REPEATER_EQ_DONE 0xf0008 /* 2.0 E11 */
Wonder if we should look at that at some point? The spec doesn't really
say so. Or maybe we should just dump it out of the link training failed?
>
> enum drm_dp_phy {
> DP_PHY_DPRX,
> --
> 2.30.2
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2022-01-27 7:32 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 17:03 [Intel-gfx] [PATCH 0/8] drm/dp, drm/i915: 128b/132b updates Jani Nikula
2022-01-25 17:03 ` Jani Nikula
2022-01-25 17:03 ` [Intel-gfx] [PATCH 1/8] drm/dp: add drm_dp_128b132b_read_aux_rd_interval() Jani Nikula
2022-01-25 17:03 ` Jani Nikula
2022-01-27 7:26 ` [Intel-gfx] " Ville Syrjälä
2022-01-27 7:26 ` Ville Syrjälä
2022-01-25 17:03 ` [Intel-gfx] [PATCH 2/8] drm/dp: add 128b/132b link status helpers from DP 2.0 E11 Jani Nikula
2022-01-25 17:03 ` Jani Nikula
2022-01-25 17:03 ` [Intel-gfx] [PATCH 3/8] drm/dp: add some new DPCD macros " Jani Nikula
2022-01-25 17:03 ` Jani Nikula
2022-01-27 7:31 ` Ville Syrjälä [this message]
2022-01-27 7:31 ` Ville Syrjälä
2022-01-25 17:03 ` [Intel-gfx] [PATCH 4/8] drm/i915/dp: move intel_dp_prepare_link_train() call Jani Nikula
2022-01-25 17:03 ` Jani Nikula
2022-01-25 17:03 ` [Intel-gfx] [PATCH 5/8] drm/i915/dp: rewrite DP 2.0 128b/132b link training based on errata Jani Nikula
2022-01-25 17:03 ` Jani Nikula
2022-01-26 5:34 ` [Intel-gfx] " Ville Syrjälä
2022-01-26 5:34 ` Ville Syrjälä
2022-02-02 10:22 ` [Intel-gfx] " Jani Nikula
2022-02-02 10:22 ` Jani Nikula
2022-01-27 7:49 ` [Intel-gfx] " Ville Syrjälä
2022-01-27 7:49 ` Ville Syrjälä
2022-02-02 10:23 ` [Intel-gfx] " Jani Nikula
2022-02-02 10:23 ` Jani Nikula
2022-01-25 17:03 ` [Intel-gfx] [PATCH 6/8] drm/i915/dp: add 128b/132b support to link status checks Jani Nikula
2022-01-25 17:03 ` Jani Nikula
2022-01-27 7:50 ` [Intel-gfx] " Ville Syrjälä
2022-01-27 7:50 ` Ville Syrjälä
2022-01-25 17:03 ` [Intel-gfx] [PATCH 7/8] drm/i915/dp: give more time for CDS Jani Nikula
2022-01-25 17:03 ` Jani Nikula
2022-01-25 17:03 ` [Intel-gfx] [PATCH 8/8] drm/i915/mst: update slot information for 128b/132b Jani Nikula
2022-01-25 17:03 ` Jani Nikula
2022-01-25 18:07 ` [Intel-gfx] " Lyude Paul
2022-01-25 18:07 ` Lyude Paul
2022-01-25 17:22 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/dp, drm/i915: 128b/132b updates Patchwork
2022-01-25 17:25 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-01-25 17:57 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-01-25 19:23 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
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=YfJKakOSpVPot0EG@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@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.