From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 251EED39416 for ; Thu, 2 Apr 2026 11:04:36 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id E602210E360; Thu, 2 Apr 2026 11:04:34 +0000 (UTC) Authentication-Results: gabe.freedesktop.org; dkim=pass (2048-bit key; unprotected) header.d=intel.com header.i=@intel.com header.b="O+LO9EA1"; dkim-atps=neutral Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.15]) by gabe.freedesktop.org (Postfix) with ESMTPS id 49D1610E2D2; Thu, 2 Apr 2026 11:04:33 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1775127874; x=1806663874; h=date:from:to:cc:subject:message-id:references: mime-version:content-transfer-encoding:in-reply-to; bh=5QiSROOsTZuXNp8vlQNe7yZKYvIH50g7Rz/PT6x3kyA=; b=O+LO9EA1f+XP+urVDXd52z08H1HXuPS2g+hWIq3VJ9n29kGp1ioayAVJ tyAFKJgQm+dd/4sBeCCweQyGgUq64J/K0zSmKp7mxPqk8oLEPz1+rBgSm uQ2FjmjgtNGykxaLX+F0XvrqzBKoIkegWYzPFvhX+DjlDjFBEz7MpzIHg idsnIgNp7MeemrFzKEdE8zylHKFgHKyFAHyapPO8xTG7lPGg7rmDwVzLl NzoilXQQhVfXMmFXA1ZFPdbYf6Q79S5lguOcH6SC4InHlDIZ1uJOd9A0o uO2uzf70huyOybEKsaTDf5nY4TscL7GUc6pFT0tK9f9mNPb4r+s+rE9TD w==; X-CSE-ConnectionGUID: I74UCgBrTf2XulbS19Z1GQ== X-CSE-MsgGUID: GFUV3jqKRAOqwj0KtUcP4w== X-IronPort-AV: E=McAfee;i="6800,10657,11746"; a="76303091" X-IronPort-AV: E=Sophos;i="6.23,155,1770624000"; d="scan'208";a="76303091" Received: from fmviesa010.fm.intel.com ([10.60.135.150]) by fmvoesa109.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 02 Apr 2026 04:04:33 -0700 X-CSE-ConnectionGUID: qumpZOi0Qbi/Pa+UTS0SeA== X-CSE-MsgGUID: SlSyZeIBT1a8e0Pp8+trFg== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.23,155,1770624000"; d="scan'208";a="222592440" Received: from abityuts-desk.ger.corp.intel.com (HELO localhost) ([10.245.245.61]) by fmviesa010-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 02 Apr 2026 04:04:30 -0700 Date: Thu, 2 Apr 2026 14:04:28 +0300 From: Ville =?iso-8859-1?Q?Syrj=E4l=E4?= To: Ankit Nautiyal Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org, jouni.hogander@intel.com, animesh.manna@intel.com Subject: Re: [PATCH 14/23] drm/i915/dp: Add member to intel_dp to store AS SDP v2 support Message-ID: References: <20260402080425.548702-1-ankit.k.nautiyal@intel.com> <20260402080425.548702-15-ankit.k.nautiyal@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20260402080425.548702-15-ankit.k.nautiyal@intel.com> X-Patchwork-Hint: comment Organization: Intel Finland Oy - BIC 0357606-4 - c/o Alberga Business Park, 6 krs Bertel Jungin Aukio 5, 02600 Espoo, Finland X-BeenThere: dri-devel@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Direct Rendering Infrastructure - Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" On Thu, Apr 02, 2026 at 01:34:14PM +0530, Ankit Nautiyal wrote: > DP v2.1 SCR advertises support for FAVT payload fields parsing in DPCD > 0x2214 Bit 2. This indicates the support for Adaptive-Sync SDP version 2 > (AS SDP v2), which allows the source to set the version in HB2[4:0] and the > payload length in HB3[5:0] of the AS SDP header. > > DP v2.1 SCR also introduces ASYNC_VIDEO_TIMING_NOT_SUPPORTED_IN_PR in the > Panel Replay Capability DPCD 0x00b1 (Bit 3). When this bit is set, the sink > does not support asynchronous video timing while in a Panel Replay Active > state and the source is required to keep transmitting Adaptive-Sync > SDPs. The spec mandates that such sinks shall support AS SDP v2. > > Infer AS SDP v2 support from these capabilities and store it in > struct intel_dp for use by subsequent feature enablement changes. Hmm. After some more reading I think we might actually want to consult the DisplayID for this. The presence of the new adaptive sync block there might be a good indication for AS SDP v2 support. While the DisplayID 2.1 spec itself doesn't say that AS SDP v2 must be supported when the block is present, the DP 2.1 spec does at least say the converse. Ie. adaptive sync capable DP 2.1 sink must have the DisplayID block. And DP 2.1 seems to be all about the AS SDP v2 and not AS SDP v1 (that's a DP 2.0 thing really). I think there was a patch posted very recently on dri-devel, adding the adaptive sync DisplayID block parsing. Or at least some DisplayID block related to this. The intel_psr_pr_async_video_timing_supported() check I think we want to keep regardless, because you could have a sink with PR but no adaptive sync. But the FAVT check could perhaps be dropped if we add the DisplayID check. > > v2: Include parsing ASYNC_VIDEO_TIMING_NOT_SUPPORTED_IN_PR bit to > determine AS SDP v2 support. (Ville) > v3: Use helper to determine asynch video timing support. > > Signed-off-by: Ankit Nautiyal > --- > .../drm/i915/display/intel_display_types.h | 1 + > drivers/gpu/drm/i915/display/intel_dp.c | 33 +++++++++++++++++++ > 2 files changed, 34 insertions(+) > > diff --git a/drivers/gpu/drm/i915/display/intel_display_types.h b/drivers/gpu/drm/i915/display/intel_display_types.h > index e2496db1642a..efc609eef4f5 100644 > --- a/drivers/gpu/drm/i915/display/intel_display_types.h > +++ b/drivers/gpu/drm/i915/display/intel_display_types.h > @@ -1870,6 +1870,7 @@ struct intel_dp { > /* connector directly attached - won't be use for modeset in mst world */ > struct intel_connector *attached_connector; > bool as_sdp_supported; > + bool as_sdp_v2_supported; > > struct drm_dp_tunnel *tunnel; > bool tunnel_suspended:1; > diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c > index cec0f3d03c2f..9fd768447f28 100644 > --- a/drivers/gpu/drm/i915/display/intel_dp.c > +++ b/drivers/gpu/drm/i915/display/intel_dp.c > @@ -6306,6 +6306,36 @@ intel_dp_unset_edid(struct intel_dp *intel_dp) > false); > } > > +static bool > +intel_dp_sink_supports_as_sdp_v2(struct intel_dp *intel_dp) > +{ > + u8 rx_features; > + > + /* > + * The DP spec does not explicitly provide the AS SDP v2 capability. > + * So based on the DP v2.1 SCR, we infer it from the following bits: > + * > + * DP_AS_SDP_FAVT_PAYLOAD_FIELDS_PARSING_SUPPORTED indicates support for > + * FAVT, which is explicitly defined to use AS SDP v2. > + * > + * DP_ASYNC_VIDEO_TIMING_NOT_SUPPORTED_IN_PR indicates that the sink > + * does not support asynchronous video timing while in PR Active, > + * requiring the source to keep transmitting Adaptive-Sync SDPs. The > + * spec mandates that such sinks shall support AS SDP v2. > + */ > + if (drm_dp_dpcd_read_byte(&intel_dp->aux, > + DP_DPRX_FEATURE_ENUMERATION_LIST_CONT_1, > + &rx_features) == 1) { > + if (rx_features & DP_AS_SDP_FAVT_PAYLOAD_FIELDS_PARSING_SUPPORTED) > + return true; > + } > + > + if (!intel_psr_pr_async_video_timing_supported(intel_dp)) > + return true; > + > + return false; > +} > + > static void > intel_dp_detect_sdp_caps(struct intel_dp *intel_dp) > { > @@ -6313,6 +6343,9 @@ intel_dp_detect_sdp_caps(struct intel_dp *intel_dp) > > intel_dp->as_sdp_supported = HAS_AS_SDP(display) && > drm_dp_as_sdp_supported(&intel_dp->aux, intel_dp->dpcd); > + > + intel_dp->as_sdp_v2_supported = intel_dp->as_sdp_supported && > + intel_dp_sink_supports_as_sdp_v2(intel_dp); > } > > static bool intel_dp_needs_dpcd_probe(struct intel_dp *intel_dp, bool force_on_external) > -- > 2.45.2 -- Ville Syrjälä Intel