From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mout-p-103.mailbox.org (mout-p-103.mailbox.org [80.241.56.161]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 9AEAD33993 for ; Tue, 17 Feb 2026 08:22:02 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=80.241.56.161 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771316524; cv=none; b=UdwY1kETfjhNGHlzF3ejm6DvqoTSh6xmp4OuJgAB1D3FnQshFq3i65lMaUtS4t4viD4vBujbF2DElOpPa7uj9EnqlLWdWi6AtmxVskYwGEfrK9SX1IQ1zcU2zESUMJuIaa8DbD2uhTac1pJ3TPuadRKGgr9DV1C5VEsg0beNFSk= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771316524; c=relaxed/simple; bh=krlvfIadZSHDlgzm5uAyGXSnk2hBuOCg7tXvZ5b9Mmc=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=GdB1+OFuzmI1UR8e5BtJ+usm2bUVrnRUnOlya7G/Ci3xCZolDEYAaGbTmRBfGsFa1Qn5PTHK9TJDuNJDD6043E7ON9KmjQK6A4+17olaQbrK9SIvIwZeHLmhHmJs4vKriaIhDFFa2sU+MX2AocWlleQ/iWM649kgzfuoYriFr7c= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=mailbox.org; spf=pass smtp.mailfrom=mailbox.org; dkim=pass (2048-bit key) header.d=mailbox.org header.i=@mailbox.org header.b=J014N6Ua; arc=none smtp.client-ip=80.241.56.161 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=mailbox.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=mailbox.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=mailbox.org header.i=@mailbox.org header.b="J014N6Ua" Received: from smtp2.mailbox.org (smtp2.mailbox.org [10.196.197.2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-p-103.mailbox.org (Postfix) with ESMTPS id 4fFXg513Dfz9t5M; Tue, 17 Feb 2026 09:21:53 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mailbox.org; s=mail20150812; t=1771316513; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Pi28vdSvaRdgQlZvv9XjaVuEVLRh69xvypyxyKxT0lc=; b=J014N6UaPVvmn7gwPG+BTYpubqlD2QsIK4jg8FBkOuzaC6QFwdu1TvSHl8fstX2aqRwJB/ fIUvEJlbfaIqN2hKXCrhIzfsa5iwFHnwThEm86ekPhiAy0XezA2l47AVoCqhi0gzIqNRKv Eq91lCoWbWQyca0/e9T+sd6gAr09IX3t0VJdKo85MA3wqKOjwpX7sgNOKWbidL1gbVF/ru MSaRfzt4+FzW/o12SxFt70rQ512+bt199Rj2Pi+hkBt6rxnc4vdAsuACfBSIhMn9RWqXbn m9YtGajhbFCPYIGivvOuJfc9XWT1Ig2Zbf2E/ch9hZ+0nO1F5i4X7W0C+CTe5A== Message-ID: Date: Tue, 17 Feb 2026 09:21:46 +0100 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Subject: Re: [PATCH v4 23/27] drm: Add passive_vrr_disabled property to crtc To: =?UTF-8?Q?Tomasz_Paku=C5=82a?= , alexander.deucher@amd.com, harry.wentland@amd.com, sunpeng.li@amd.com Cc: maarten.lankhorst@linux.intel.com, mripard@kernel.org, tzimmermann@suse.de, airlied@gmail.com, simona@ffwll.ch, siqueira@igalia.com, dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org, bernhard.berger@gmail.com, daniel@fooishbar.org References: <20260216164516.36803-1-tomasz.pakula.oficjalny@gmail.com> <20260216164516.36803-24-tomasz.pakula.oficjalny@gmail.com> From: =?UTF-8?Q?Michel_D=C3=A4nzer?= Content-Language: en-CA In-Reply-To: <20260216164516.36803-24-tomasz.pakula.oficjalny@gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-MBO-RS-ID: bab2b5f730da6c68bdb X-MBO-RS-META: e7z64sqjybjr64r3sok1s13kged1xk8c On 2/16/26 17:45, Tomasz Pakuła wrote: > Many TVs and other HDMI sinks suffer from blanking and possibly other > glitches when VRR is toggled. With VRR present on such sinks and > vrr_on_desktop enabled, they behave like the signal is always variable, > even in fixed refresh rate situations. DisplayPort and eDP enforce > seamless VRR transitions but HDMI unfortunately doesn't. > > Keep VRR toggled if it's supported and not explicitly disabled. It can > be used for any VRR sinks, but this is mainly targeted for HDMI. > > Functionally, for an end user, this is the same as normal, fixed refresh > rate mode. The only difference is that sink is kept in VRR state which > enables seamless transitions into/out of variable refresh rate. > > Basically, the driver shouldn't change it's behavior around VRR_ENABLED > set to false, jut keep sending info packets/frames with VRR/FreeSync/ > G-Sync/HDMI VRR active. > > Enabled by default for sinks that claim it's support Having a negation term like "disabled" in the property name can be confusing (as it involves double negation when the property value is 0) and is better avoided. -- Earthling Michel Dänzer \ GNOME / Xwayland / Mesa developer https://redhat.com \ Libre software enthusiast