From: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: <intel-gfx@lists.freedesktop.org>,
<intel-xe@lists.freedesktop.org>, <jani.nikula@linux.intel.com>,
<mitulkumar.ajitkumar.golani@intel.com>
Subject: Re: [PATCH 02/16] drm/i915/dp_mst: Use VRR Timing generator for DP MST for fixed_rr
Date: Tue, 25 Mar 2025 10:05:48 +0530 [thread overview]
Message-ID: <5535b672-0f0c-4ad8-9630-5605236cc5b3@intel.com> (raw)
In-Reply-To: <Z-GZgQMTdRgTD585@intel.com>
On 3/24/2025 11:12 PM, Ville Syrjälä wrote:
> On Mon, Mar 24, 2025 at 07:02:34PM +0530, Ankit Nautiyal wrote:
>> Currently the variable timings are supported only for DP and eDP and not
>> for DP MST. Call intel_vrr_compute_config() for MST which will configure
>> fixed refresh rate timings irrespective of whether VRR is supported or
>> not. Since vrr_capable still doesn't have support for DP MST this will be
>> just treated as non VRR case and vrr.vmin/vmax/flipline will be all set
>> to adjusted_mode->crtc_vtotal.
>>
>> This will help to move away from the legacy timing generator and
>> always use VRR timing generator by default.
>>
>> With this change, we need to exclude MST in intel_vrr_is_capable for
>> now, to avoid having LRR with MST.
>>
>> v2: Exclude MST in intel_vrr_is_capable() for now. (Ville)
>>
>> Signed-off-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
>> ---
>> drivers/gpu/drm/i915/display/intel_dp_mst.c | 3 +++
>> drivers/gpu/drm/i915/display/intel_vrr.c | 2 ++
>> 2 files changed, 5 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_dp_mst.c b/drivers/gpu/drm/i915/display/intel_dp_mst.c
>> index 02f95108c637..bd47cf127b4c 100644
>> --- a/drivers/gpu/drm/i915/display/intel_dp_mst.c
>> +++ b/drivers/gpu/drm/i915/display/intel_dp_mst.c
>> @@ -52,6 +52,7 @@
>> #include "intel_pfit.h"
>> #include "intel_psr.h"
>> #include "intel_vdsc.h"
>> +#include "intel_vrr.h"
>> #include "skl_scaler.h"
>>
>> /*
>> @@ -710,6 +711,8 @@ static int mst_stream_compute_config(struct intel_encoder *encoder,
>> pipe_config->lane_lat_optim_mask =
>> bxt_dpio_phy_calc_lane_lat_optim_mask(pipe_config->lane_count);
>>
>> + intel_vrr_compute_config(pipe_config, conn_state);
>> +
>> intel_dp_audio_compute_config(encoder, pipe_config, conn_state);
>>
>> intel_ddi_compute_min_voltage_level(pipe_config);
>> diff --git a/drivers/gpu/drm/i915/display/intel_vrr.c b/drivers/gpu/drm/i915/display/intel_vrr.c
>> index 6bdcdfed4b9b..c682c487eb25 100644
>> --- a/drivers/gpu/drm/i915/display/intel_vrr.c
>> +++ b/drivers/gpu/drm/i915/display/intel_vrr.c
>> @@ -32,6 +32,8 @@ bool intel_vrr_is_capable(struct intel_connector *connector)
>> return false;
>> fallthrough;
>> case DRM_MODE_CONNECTOR_DisplayPort:
>> + if (connector->mst.dp)
>> + return false;
> The DP spec is pretty vague about this, but it looks to me like it's
> saying that the last MST branch device must support the "ignore MSA"
> bit in order to support adaptive sync. I guess we might need to do that
> stuff via remote DPCD. Or perhaps in the worst case we'd have iterate
> through the whole MST chain.
>
> Looks like there's at least this MST hub that claims adaptive sync
> support:
> https://club-3d.com/en/detail/2486/usb_type_c_3.2_gen_1_multi_stream_transport_(mst)hub_displayport1.4_triple_monitor/
> We should probably get one and see if we can get this working.
As you have highlighted some effort is required for DP + MST.
Thanks for digging up this, I have noted this down and will try to get
or similar device for testing.
>
> In the meantime
> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Thanks again for the suggestion and reviews.
Regards,
Ankit
>
>> intel_dp = intel_attached_dp(connector);
>>
>> if (!drm_dp_sink_can_do_video_without_timing_msa(intel_dp->dpcd))
>> --
>> 2.45.2
next prev parent reply other threads:[~2025-03-25 4:36 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-24 13:32 [PATCH 00/16] Use VRR timing generator for fixed refresh rate modes Ankit Nautiyal
2025-03-24 13:32 ` [PATCH 01/16] drm/i915/hdmi: Use VRR Timing generator for HDMI for fixed_rr Ankit Nautiyal
2025-03-24 13:32 ` [PATCH 02/16] drm/i915/dp_mst: Use VRR Timing generator for DP MST " Ankit Nautiyal
2025-03-24 17:42 ` Ville Syrjälä
2025-03-25 4:35 ` Nautiyal, Ankit K [this message]
2025-03-24 13:32 ` [PATCH 03/16] drm/i915/display: Disable PSR before disabling VRR Ankit Nautiyal
2025-03-24 13:32 ` [PATCH 04/16] drm/i915/display: Move intel_psr_post_plane_update() at the later Ankit Nautiyal
2025-03-24 17:00 ` Nautiyal, Ankit K
2025-03-24 13:32 ` [PATCH 05/16] drm/i915/vrr: Refactor condition for computing vmax and LRR Ankit Nautiyal
2025-03-24 13:32 ` [PATCH 06/16] drm/i915/vrr: Always set vrr vmax/vmin/flipline in vrr_{enable/disable} Ankit Nautiyal
2025-03-24 13:32 ` [PATCH 07/16] drm/i915/vrr: Set vrr.enable for VRR TG with fixed_rr Ankit Nautiyal
2025-03-24 13:32 ` [PATCH 08/16] drm/i915/display: Use fixed_rr timings in modeset sequence Ankit Nautiyal
2025-03-24 13:32 ` [PATCH 09/16] drm/i915/vrr: Use fixed timings for platforms that support VRR Ankit Nautiyal
2025-03-24 13:32 ` [PATCH 10/16] drm/i915/display: Use fixed rr timings in intel_set_transcoder_timings_lrr() Ankit Nautiyal
2025-03-24 13:32 ` [PATCH 11/16] drm/i915/display: Move vrr.guardband/pipeline_full out of !fastset block Ankit Nautiyal
2025-03-24 13:32 ` [PATCH 12/16] drm/i915/vrr: Allow fixed_rr with pipe joiner Ankit Nautiyal
2025-03-24 13:32 ` [PATCH 13/16] drm/i915/vrr: Always use VRR timing generator for PTL+ Ankit Nautiyal
2025-03-24 13:32 ` [PATCH 14/16] drm/i915/vrr: Set trans_vrr_ctl in intel_vrr_set_transcoder_timings() Ankit Nautiyal
2025-03-24 17:55 ` Ville Syrjälä
2025-03-24 13:32 ` [PATCH 15/16] drm/i915/display: Separate out functions to get/set VTOTAL register Ankit Nautiyal
2025-03-24 18:02 ` Ville Syrjälä
2025-03-25 6:22 ` Nautiyal, Ankit K
2025-03-25 13:45 ` Ville Syrjälä
2025-03-25 15:53 ` Nautiyal, Ankit K
2025-03-24 13:32 ` [PATCH 16/16] drm/i915/display: Avoid use of VTOTAL.Vtotal bits Ankit Nautiyal
2025-03-24 14:19 ` ✓ CI.Patch_applied: success for Use VRR timing generator for fixed refresh rate modes (rev11) Patchwork
2025-03-24 14:19 ` ✓ CI.checkpatch: " Patchwork
2025-03-24 14:20 ` ✓ CI.KUnit: " Patchwork
2025-03-24 14:37 ` ✓ CI.Build: " Patchwork
2025-03-24 14:39 ` ✓ CI.Hooks: " Patchwork
2025-03-24 14:41 ` ✗ CI.checksparse: warning " Patchwork
2025-03-24 15:01 ` ✓ Xe.CI.BAT: success " Patchwork
2025-03-24 17:00 ` ✗ Xe.CI.Full: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2025-03-25 11:22 [PATCH 00/16] Use VRR timing generator for fixed refresh rate modes Ankit Nautiyal
2025-03-25 11:22 ` [PATCH 02/16] drm/i915/dp_mst: Use VRR Timing generator for DP MST for fixed_rr Ankit Nautiyal
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=5535b672-0f0c-4ad8-9630-5605236cc5b3@intel.com \
--to=ankit.k.nautiyal@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=mitulkumar.ajitkumar.golani@intel.com \
--cc=ville.syrjala@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox