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 4EF1FC04FF6 for ; Fri, 19 Apr 2024 12:36:05 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 8CE7A10FEB3; Fri, 19 Apr 2024 12:36:04 +0000 (UTC) Authentication-Results: gabe.freedesktop.org; dkim=pass (2048-bit key; unprotected) header.d=intel.com header.i=@intel.com header.b="MRoEviM3"; dkim-atps=neutral Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.15]) by gabe.freedesktop.org (Postfix) with ESMTPS id 88F5E10FEB1; Fri, 19 Apr 2024 12:36:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1713530164; x=1745066164; h=from:to:cc:subject:in-reply-to:references:date: message-id:mime-version; bh=M94cwTmY2wA2rRmUTGrGazaBWg8b1Rrj2b3Uj08EcyQ=; b=MRoEviM3uG/31h3+11wzIaPGxgzbCIQ+AMAz4QEva2lsD+fI4rcW76cX y1zYKbl8cnx+ZM0ELZBCdkE7oFR20jFty5WK0FzSPldwTtAckI16swwis KeDJmfqSDamyfpPAzaLHHunNaPo+2IM+rxClO5tyyiNHKGvVeShLHenGN 3xZNi3Wo6FAEDoSjG7hKFJlYlKvf7bfK5F4RZLcC45pW+zEpvnaQEkPc7 h+/1BuREDTNI2Xjx0twXVo63LwrMjxPDkrKWQucvt71jdnYcSbZpr8S5g w+5rAobq4nQ5pDH85WTUuKR27RNoyrdNofZKMkrHFL5IAdrvwi3IhMKA1 g==; X-CSE-ConnectionGUID: bwstqLIXSVuIzvF+T5NVZw== X-CSE-MsgGUID: nHskEchsR5+4fHwDmmwTHw== X-IronPort-AV: E=McAfee;i="6600,9927,11049"; a="12918898" X-IronPort-AV: E=Sophos;i="6.07,213,1708416000"; d="scan'208";a="12918898" Received: from orviesa010.jf.intel.com ([10.64.159.150]) by orvoesa107.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 19 Apr 2024 05:36:04 -0700 X-CSE-ConnectionGUID: Fo2oSY2US5GSNXTkbtrXjQ== X-CSE-MsgGUID: Yz67tNn2TKWyBw/0EhVAMA== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.07,213,1708416000"; d="scan'208";a="23185924" Received: from agherasi-mobl.ger.corp.intel.com (HELO localhost) ([10.252.46.119]) by orviesa010-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 19 Apr 2024 05:36:00 -0700 From: Jani Nikula To: "Nautiyal, Ankit K" , Maxime Ripard Cc: Mitul Golani , intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org, Maarten Lankhorst , Thomas Zimmermann , Rodrigo Vivi Subject: Re: [PATCH v17 0/9] Enable Adaptive Sync SDP Support for DP In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo References: <20240311094238.3320888-1-mitulkumar.ajitkumar.golani@intel.com> <87a5mvppvd.fsf@intel.com> <20240319-devious-natural-rook-df5f43@houat> Date: Fri, 19 Apr 2024 15:35:55 +0300 Message-ID: <871q71wmvo.fsf@intel.com> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: intel-gfx@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Intel graphics driver community testing & development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: intel-gfx-bounces@lists.freedesktop.org Sender: "Intel-gfx" On Thu, 04 Apr 2024, "Nautiyal, Ankit K" wrote: > On 3/19/2024 3:16 PM, Maxime Ripard wrote: >> On Mon, Mar 18, 2024 at 04:37:58PM +0200, Jani Nikula wrote: >>> On Mon, 11 Mar 2024, Mitul Golani wrote: >>>> An Adaptive-Sync-capable DP protocol converter indicates its >>>> support by setting the related bit in the DPCD register. This >>>> is valid for DP and edp as well. >>>> >>>> Computes AS SDP values based on the display configuration, >>>> ensuring proper handling of Variable Refresh Rate (VRR) >>>> in the context of Adaptive Sync. >>> [snip] >>> >>>> Mitul Golani (9): >>>> drm/dp: Add support to indicate if sink supports AS SDP >>>> drm: Add Adaptive Sync SDP logging >>> Maarten, Maxime, Thomas, ack for merging these two patches via >>> drm-intel-next? >> Ack >> >> Maxime > > Thanks for the patch, ack and reviews, pushed to drm-intel-next. This came up again today [1]. The acks absolutely must be recorded in the commit messages when pushing the patches. dim should complain about applying non-i915 patches without acks. BR, Jani. [1] https://lore.kernel.org/r/Zh_Q72gYKMMbge9A@intel.com -- Jani Nikula, Intel