From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org,
Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v2 7/8] drm/i915/mst: update slot information for 128b/132b
Date: Tue, 8 Feb 2022 17:02:53 +0200 [thread overview]
Message-ID: <YgKGHb2Gfg8hI8XQ@intel.com> (raw)
In-Reply-To: <fecbe3e9c93e33a16b24481432de5a524821677d.1643878928.git.jani.nikula@intel.com>
On Thu, Feb 03, 2022 at 11:03:56AM +0200, Jani Nikula wrote:
> 128b/132b supports using 64 slots starting from 0, while 8b/10b reserves
> slot 0 for metadata.
>
> Commit d6c6a76f80a1 ("drm: Update MST First Link Slot Information Based
> on Encoding Format") added support for updating the topology state
> accordingly, and commit 41724ea273cd ("drm/amd/display: Add DP 2.0 MST
> DM Support") started using it in the amd driver.
>
> This feels more than a little cumbersome, especially updating the
> information in atomic check. For i915, add the update to MST connector
> .compute_config hook rather than iterating over all MST managers and
> connectors in global mode config .atomic_check. Fingers crossed.
>
> v2:
> - Update in .compute_config() not .atomic_check (Ville)
>
> Cc: Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com>
> Cc: Lyude Paul <lyude@redhat.com>
> 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>
> ---
> drivers/gpu/drm/i915/display/intel_dp_mst.c | 29 +++++++++++++++++++--
> 1 file changed, 27 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_dp_mst.c b/drivers/gpu/drm/i915/display/intel_dp_mst.c
> index 6b6eab507d30..2959e2c3930b 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp_mst.c
> +++ b/drivers/gpu/drm/i915/display/intel_dp_mst.c
> @@ -99,6 +99,27 @@ static int intel_dp_mst_compute_link_config(struct intel_encoder *encoder,
> return 0;
> }
>
> +static void intel_dp_mst_update_slots(struct intel_encoder *encoder,
> + struct intel_crtc_state *crtc_state,
> + struct drm_connector_state *conn_state)
> +{
> + struct drm_i915_private *i915 = to_i915(encoder->base.dev);
> + struct intel_dp_mst_encoder *intel_mst = enc_to_mst(encoder);
> + struct intel_dp *intel_dp = &intel_mst->primary->dp;
> + struct drm_dp_mst_topology_mgr *mgr = &intel_dp->mst_mgr;
> + struct drm_dp_mst_topology_state *topology_state;
> + u8 link_coding_cap = intel_dp_is_uhbr(crtc_state) ?
> + DP_CAP_ANSI_128B132B : DP_CAP_ANSI_8B10B;
> +
> + topology_state = drm_atomic_get_mst_topology_state(conn_state->state, mgr);
> + if (IS_ERR(topology_state)) {
> + drm_dbg_kms(&i915->drm, "slot update failed\n");
> + return;
We need to propagate the error upwards. Other than that seems about
as as reasonable as it can be given the current state of things.
So with that fixed
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> + }
> +
> + drm_dp_mst_update_slots(topology_state, link_coding_cap);
> +}
> +
> static int intel_dp_mst_compute_config(struct intel_encoder *encoder,
> struct intel_crtc_state *pipe_config,
> struct drm_connector_state *conn_state)
> @@ -155,6 +176,8 @@ static int intel_dp_mst_compute_config(struct intel_encoder *encoder,
> if (ret)
> return ret;
>
> + intel_dp_mst_update_slots(encoder, pipe_config, conn_state);
> +
> pipe_config->limited_color_range =
> intel_dp_limited_color_range(pipe_config, conn_state);
>
> @@ -357,6 +380,7 @@ static void intel_mst_disable_dp(struct intel_atomic_state *state,
> struct intel_connector *connector =
> to_intel_connector(old_conn_state->connector);
> struct drm_i915_private *i915 = to_i915(connector->base.dev);
> + int start_slot = intel_dp_is_uhbr(old_crtc_state) ? 0 : 1;
> int ret;
>
> drm_dbg_kms(&i915->drm, "active links %d\n",
> @@ -366,7 +390,7 @@ static void intel_mst_disable_dp(struct intel_atomic_state *state,
>
> drm_dp_mst_reset_vcpi_slots(&intel_dp->mst_mgr, connector->port);
>
> - ret = drm_dp_update_payload_part1(&intel_dp->mst_mgr, 1);
> + ret = drm_dp_update_payload_part1(&intel_dp->mst_mgr, start_slot);
> if (ret) {
> drm_dbg_kms(&i915->drm, "failed to update payload %d\n", ret);
> }
> @@ -475,6 +499,7 @@ static void intel_mst_pre_enable_dp(struct intel_atomic_state *state,
> struct drm_i915_private *dev_priv = to_i915(encoder->base.dev);
> struct intel_connector *connector =
> to_intel_connector(conn_state->connector);
> + int start_slot = intel_dp_is_uhbr(pipe_config) ? 0 : 1;
> int ret;
> bool first_mst_stream;
>
> @@ -509,7 +534,7 @@ static void intel_mst_pre_enable_dp(struct intel_atomic_state *state,
>
> intel_dp->active_mst_links++;
>
> - ret = drm_dp_update_payload_part1(&intel_dp->mst_mgr, 1);
> + ret = drm_dp_update_payload_part1(&intel_dp->mst_mgr, start_slot);
>
> /*
> * Before Gen 12 this is not done as part of
> --
> 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,
Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 7/8] drm/i915/mst: update slot information for 128b/132b
Date: Tue, 8 Feb 2022 17:02:53 +0200 [thread overview]
Message-ID: <YgKGHb2Gfg8hI8XQ@intel.com> (raw)
In-Reply-To: <fecbe3e9c93e33a16b24481432de5a524821677d.1643878928.git.jani.nikula@intel.com>
On Thu, Feb 03, 2022 at 11:03:56AM +0200, Jani Nikula wrote:
> 128b/132b supports using 64 slots starting from 0, while 8b/10b reserves
> slot 0 for metadata.
>
> Commit d6c6a76f80a1 ("drm: Update MST First Link Slot Information Based
> on Encoding Format") added support for updating the topology state
> accordingly, and commit 41724ea273cd ("drm/amd/display: Add DP 2.0 MST
> DM Support") started using it in the amd driver.
>
> This feels more than a little cumbersome, especially updating the
> information in atomic check. For i915, add the update to MST connector
> .compute_config hook rather than iterating over all MST managers and
> connectors in global mode config .atomic_check. Fingers crossed.
>
> v2:
> - Update in .compute_config() not .atomic_check (Ville)
>
> Cc: Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com>
> Cc: Lyude Paul <lyude@redhat.com>
> 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>
> ---
> drivers/gpu/drm/i915/display/intel_dp_mst.c | 29 +++++++++++++++++++--
> 1 file changed, 27 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_dp_mst.c b/drivers/gpu/drm/i915/display/intel_dp_mst.c
> index 6b6eab507d30..2959e2c3930b 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp_mst.c
> +++ b/drivers/gpu/drm/i915/display/intel_dp_mst.c
> @@ -99,6 +99,27 @@ static int intel_dp_mst_compute_link_config(struct intel_encoder *encoder,
> return 0;
> }
>
> +static void intel_dp_mst_update_slots(struct intel_encoder *encoder,
> + struct intel_crtc_state *crtc_state,
> + struct drm_connector_state *conn_state)
> +{
> + struct drm_i915_private *i915 = to_i915(encoder->base.dev);
> + struct intel_dp_mst_encoder *intel_mst = enc_to_mst(encoder);
> + struct intel_dp *intel_dp = &intel_mst->primary->dp;
> + struct drm_dp_mst_topology_mgr *mgr = &intel_dp->mst_mgr;
> + struct drm_dp_mst_topology_state *topology_state;
> + u8 link_coding_cap = intel_dp_is_uhbr(crtc_state) ?
> + DP_CAP_ANSI_128B132B : DP_CAP_ANSI_8B10B;
> +
> + topology_state = drm_atomic_get_mst_topology_state(conn_state->state, mgr);
> + if (IS_ERR(topology_state)) {
> + drm_dbg_kms(&i915->drm, "slot update failed\n");
> + return;
We need to propagate the error upwards. Other than that seems about
as as reasonable as it can be given the current state of things.
So with that fixed
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> + }
> +
> + drm_dp_mst_update_slots(topology_state, link_coding_cap);
> +}
> +
> static int intel_dp_mst_compute_config(struct intel_encoder *encoder,
> struct intel_crtc_state *pipe_config,
> struct drm_connector_state *conn_state)
> @@ -155,6 +176,8 @@ static int intel_dp_mst_compute_config(struct intel_encoder *encoder,
> if (ret)
> return ret;
>
> + intel_dp_mst_update_slots(encoder, pipe_config, conn_state);
> +
> pipe_config->limited_color_range =
> intel_dp_limited_color_range(pipe_config, conn_state);
>
> @@ -357,6 +380,7 @@ static void intel_mst_disable_dp(struct intel_atomic_state *state,
> struct intel_connector *connector =
> to_intel_connector(old_conn_state->connector);
> struct drm_i915_private *i915 = to_i915(connector->base.dev);
> + int start_slot = intel_dp_is_uhbr(old_crtc_state) ? 0 : 1;
> int ret;
>
> drm_dbg_kms(&i915->drm, "active links %d\n",
> @@ -366,7 +390,7 @@ static void intel_mst_disable_dp(struct intel_atomic_state *state,
>
> drm_dp_mst_reset_vcpi_slots(&intel_dp->mst_mgr, connector->port);
>
> - ret = drm_dp_update_payload_part1(&intel_dp->mst_mgr, 1);
> + ret = drm_dp_update_payload_part1(&intel_dp->mst_mgr, start_slot);
> if (ret) {
> drm_dbg_kms(&i915->drm, "failed to update payload %d\n", ret);
> }
> @@ -475,6 +499,7 @@ static void intel_mst_pre_enable_dp(struct intel_atomic_state *state,
> struct drm_i915_private *dev_priv = to_i915(encoder->base.dev);
> struct intel_connector *connector =
> to_intel_connector(conn_state->connector);
> + int start_slot = intel_dp_is_uhbr(pipe_config) ? 0 : 1;
> int ret;
> bool first_mst_stream;
>
> @@ -509,7 +534,7 @@ static void intel_mst_pre_enable_dp(struct intel_atomic_state *state,
>
> intel_dp->active_mst_links++;
>
> - ret = drm_dp_update_payload_part1(&intel_dp->mst_mgr, 1);
> + ret = drm_dp_update_payload_part1(&intel_dp->mst_mgr, start_slot);
>
> /*
> * Before Gen 12 this is not done as part of
> --
> 2.30.2
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2022-02-08 15:03 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 9:03 [Intel-gfx] [PATCH v2 0/8] drm/dp, drm/i915: 128b/132b updates Jani Nikula
2022-02-03 9:03 ` Jani Nikula
2022-02-03 9:03 ` [Intel-gfx] [PATCH v2 1/8] drm/dp: add drm_dp_128b132b_read_aux_rd_interval() Jani Nikula
2022-02-03 9:03 ` Jani Nikula
2022-02-03 9:03 ` [Intel-gfx] [PATCH v2 2/8] drm/dp: add 128b/132b link status helpers from DP 2.0 E11 Jani Nikula
2022-02-03 9:03 ` Jani Nikula
2022-02-03 9:03 ` [Intel-gfx] [PATCH v2 3/8] drm/dp: add some new DPCD macros " Jani Nikula
2022-02-03 9:03 ` Jani Nikula
2022-02-03 9:03 ` [Intel-gfx] [PATCH v2 4/8] drm/i915/dp: move intel_dp_prepare_link_train() call Jani Nikula
2022-02-03 9:03 ` Jani Nikula
2022-02-03 9:03 ` [Intel-gfx] [PATCH v2 5/8] drm/i915/dp: rewrite DP 2.0 128b/132b link training based on errata Jani Nikula
2022-02-03 9:03 ` Jani Nikula
2022-02-04 11:37 ` [Intel-gfx] " Ville Syrjälä
2022-02-04 11:37 ` Ville Syrjälä
2022-02-08 9:17 ` [Intel-gfx] " Jani Nikula
2022-02-08 9:17 ` Jani Nikula
2022-02-08 9:39 ` [Intel-gfx] " Ville Syrjälä
2022-02-08 9:39 ` Ville Syrjälä
2022-02-08 12:12 ` [Intel-gfx] " Jani Nikula
2022-02-08 12:12 ` Jani Nikula
2022-02-08 12:55 ` [Intel-gfx] " Ville Syrjälä
2022-02-08 12:55 ` Ville Syrjälä
2022-02-08 13:31 ` [Intel-gfx] " Jani Nikula
2022-02-08 13:31 ` Jani Nikula
2022-02-08 13:30 ` [Intel-gfx] [PATCH v3] " Jani Nikula
2022-02-08 13:30 ` Jani Nikula
2022-02-08 14:32 ` [Intel-gfx] [PATCH v4] " Jani Nikula
2022-02-08 14:32 ` Jani Nikula
2022-02-08 14:38 ` [Intel-gfx] " Ville Syrjälä
2022-02-08 14:38 ` Ville Syrjälä
2022-02-03 9:03 ` [Intel-gfx] [PATCH v2 6/8] drm/i915/dp: add 128b/132b support to link status checks Jani Nikula
2022-02-03 9:03 ` Jani Nikula
2022-02-08 15:06 ` [Intel-gfx] " Ville Syrjälä
2022-02-08 15:06 ` Ville Syrjälä
2022-02-09 9:09 ` [Intel-gfx] " Jani Nikula
2022-02-09 9:09 ` Jani Nikula
2022-02-09 9:17 ` [Intel-gfx] " Ville Syrjälä
2022-02-09 9:17 ` Ville Syrjälä
2022-02-11 10:11 ` [Intel-gfx] " Jani Nikula
2022-02-11 10:11 ` Jani Nikula
2022-02-03 9:03 ` [Intel-gfx] [PATCH v2 7/8] drm/i915/mst: update slot information for 128b/132b Jani Nikula
2022-02-03 9:03 ` Jani Nikula
2022-02-08 15:02 ` Ville Syrjälä [this message]
2022-02-08 15:02 ` Ville Syrjälä
2022-02-08 15:23 ` [Intel-gfx] [PATCH v3] " Jani Nikula
2022-02-08 15:23 ` Jani Nikula
2022-02-03 9:03 ` [Intel-gfx] [PATCH v2 8/8] HACK: drm/i915/dp: give more time for CDS Jani Nikula
2022-02-03 9:03 ` Jani Nikula
2022-02-03 13:44 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/dp, drm/i915: 128b/132b updates (rev2) Patchwork
2022-02-03 13:47 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-02-03 14:14 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-02-03 17:31 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-02-08 14:41 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/dp, drm/i915: 128b/132b updates (rev4) Patchwork
2022-02-08 14:43 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-02-08 15:15 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-02-08 16:57 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/dp, drm/i915: 128b/132b updates (rev5) Patchwork
2022-02-08 17:00 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-02-08 17:28 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-02-08 19:51 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/dp, drm/i915: 128b/132b updates (rev6) Patchwork
2022-02-08 19:54 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-02-08 20:20 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-02-08 21:33 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-02-09 9:26 ` [Intel-gfx] [PATCH v2 0/8] drm/dp, drm/i915: 128b/132b updates Jani Nikula
2022-02-09 9:26 ` Jani Nikula
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=YgKGHb2Gfg8hI8XQ@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=Bhawanpreet.Lakha@amd.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.