From nobody Thu Mar 5 08:15:13 2026 Received: from mail-ej1-f54.google.com (mail-ej1-f54.google.com [209.85.218.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 74FCC2C3257 for ; Mon, 16 Feb 2026 16:45:30 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.218.54 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771260335; cv=none; b=SVeL9iSk/D0Fki6PXzkQtE7jx8blRdlbXh452H4jYtXZwLSZMg9IrFQUkHAcXrajKPtiDtuZ+BCsaMjrhJFxaBSrStOJv1fZjAEWBV0wat85Z14Ye7Ya7GmFcjJFXHarkidQi0PoGJ6dQsXehScXCNE0IluKvh5ofQCBBMu1Cao= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771260335; c=relaxed/simple; bh=8QXUJfQ38/ErZfuEoJsqf+y8phB0aYi2CVMxiI0O0NE=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=S8Lyur9HJpoQCfIuRIUqTKWvPLw40Q5arH0XeYY+4w6gzd1ace7qfr8c002INB/NCVSgCuKDTAh7dGoXtilpj84nLXhQ9oCFxqA1aoPOgWBPfK3ykK0Vjed2Ua3SIV8XMcVsSr/oi6yEh+JmhsApgXCS5vFTChIlmAsyvcBnyLA= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com; spf=pass smtp.mailfrom=gmail.com; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b=D76iy+bi; arc=none smtp.client-ip=209.85.218.54 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=gmail.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="D76iy+bi" Received: by mail-ej1-f54.google.com with SMTP id a640c23a62f3a-b8f7fd33bd2so48122166b.3 for ; Mon, 16 Feb 2026 08:45:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1771260329; x=1771865129; darn=vger.kernel.org; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:from:to:cc:subject:date :message-id:reply-to; bh=cytjPGPVyEqSdYgwIyq0GlV8NbwaC2+24peBJ4/9eGA=; b=D76iy+bi8iQoZDSqPHzvUPkmsllcqpTmV0VbBW/1jEM7ErGNxRrHhX2xDA8/yaCVdd IZ9iLbNjvfwcT3jdcJvqa8fYRUjO71c++lOeuGQnwfqer3k7TS5sWLE5lIL5DrL3Dlv7 XjUnKYoICD/eq+CeBHUx2B7AL1v9Clfow8sKwpiSmPRa9qObyPXMtEb5fBEYC48AEqv7 7w0h90YcSaBK4NgQDT7dxG5SMqxou7+2HOP8lpjC+8nfQ24+5/ab/bs8ROXzkf5/HjEl 6eTD9Mn1TVpNoeD8KOEv6BxQGz5cJNM2+D7sAWFzlhyAW1QSyzQIArCpu/mqN+RDTH8Z 2m/w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1771260329; x=1771865129; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:x-gm-gg:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=cytjPGPVyEqSdYgwIyq0GlV8NbwaC2+24peBJ4/9eGA=; b=w7pPZaWHFRHNw48egobnACdWrKFFmMpGBzU6pJ9sy+Amj5QtH2awWuO3jtz8vPftse otpi47xMLO6E8BIst/rhaYGHKcqeK21gC1qYQ0HmZu87A8reYY2RlG0GGbOBdhTcEfE4 Y3cMm36IFYqX11ht+njXrwWM+mkwIYgnrL+DW/PYm3zr05n6gPajYuXJgt7GO9SgC9Tr ychbLR1xSWxmXp22bRa6rnJ5A18LvmwGtYquPel0ixBrDqzpoAEasnLSVWcGg48uvlYG N377JjsW+SFo16EgW5/CLl3YTLxEi1Vupm22SCNFk4wVf7xZXOdXMOqJ91tU1VBDU/sJ od0A== X-Forwarded-Encrypted: i=1; AJvYcCWAP74cJ7LyWfzDEc8FeX1lpEO0lLKigXdSMXkE/5B1Ejv/pfzPkQpALKvrU2UVN+FafZMz1vQs7iSIYwI=@vger.kernel.org X-Gm-Message-State: AOJu0YwqyR1Nx5IHRpAHA3kFOqgA6OGClYDfnqylMAEWQKSwPFXDAfMO 6cnTFhtuVTUaIxPCx/jSAiYnQq+4s+m1fH2b0G0S9b8SdCgYrxvSmOh+ X-Gm-Gg: AZuq6aKEQuTmSjG2Qc4MdWcfoODTkYJ5e4Ts+pcVDesJ9u69wDyKvrDMFsFwSWveNP9 szew5NUTIexJWW5YhK422nx8uv5mnHQ1rvM/6lkmTpsGNQi8S967Y2U6LPgg5uUFQ6sv9dixJmu 8K7qOPXTHDcwVnAXj8aD5SMCFhf0/JlxoNN0KTkp5omh5rhbHx3/A5RzD0glgZR147B1DWna14f MtSRzGXP3vQtBYmwdAJ+hK15v3i66PtFEQpSmHYs/RgXzZne9/6fLYoTkEDtFQ7KfrZJCUBKt3U hF5zF9TC4uUI5ISiXeD9UgE/ButN+BinHZmTuimgkazpF/7gT8i6UOBPt27jmhnZbtCUOI9MWQL 1AdyZueHGKL3AvkekSmkuXNqaj6YOLZYYsTomJf+2MQTKdyB3FAh+1k1+xa5iEJuIGkmNYQPad1 xPgDkmbFmGK4Md3/LepJhyoAIkOZB5RwQ7Qe3WinQim5eu3We2HDuKPvwmmzxT1MEuedIpG01YM ipx X-Received: by 2002:a17:907:7f90:b0:b8a:f2d7:9942 with SMTP id a640c23a62f3a-b8face51f34mr359995366b.3.1771260328825; Mon, 16 Feb 2026 08:45:28 -0800 (PST) Received: from laptok.lan (87-205-5-123.static.ip.netia.com.pl. [87.205.5.123]) by smtp.gmail.com with ESMTPSA id a640c23a62f3a-b8fc735d185sm264683866b.14.2026.02.16.08.45.27 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 16 Feb 2026 08:45:28 -0800 (PST) From: =?UTF-8?q?Tomasz=20Paku=C5=82a?= To: 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, tomasz.pakula.oficjalny@gmail.com, bernhard.berger@gmail.com, michel.daenzer@mailbox.org, daniel@fooishbar.org Subject: [PATCH v4 07/27] drm/amd/display: Use bigger VRR range if found in AMD vsdb Date: Mon, 16 Feb 2026 17:44:56 +0100 Message-ID: <20260216164516.36803-8-tomasz.pakula.oficjalny@gmail.com> X-Mailer: git-send-email 2.53.0 In-Reply-To: <20260216164516.36803-1-tomasz.pakula.oficjalny@gmail.com> References: <20260216164516.36803-1-tomasz.pakula.oficjalny@gmail.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable [Why] Some monitors only expose their full VRR range in AMD vsdb for some reason. [How] Compare exposed ranges and use the bigger one. Only adjust lower limit if it doesn't support LFC Closes: https://gitlab.freedesktop.org/drm/amd/-/issues/4177 Signed-off-by: Tomasz Paku=C5=82a --- .../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 31 +++++++++++++++++++ 1 file changed, 31 insertions(+) diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c b/drivers/gp= u/drm/amd/display/amdgpu_dm/amdgpu_dm.c index b3bf5e0c19a5..f36059bb0324 100644 --- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c +++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c @@ -13269,6 +13269,34 @@ static bool copy_range_to_amdgpu_connector(struct = drm_connector *conn) return is_freesync_capable(range); } =20 +static void extend_range_from_vsdb(struct drm_display_info *display, + const struct amdgpu_hdmi_vsdb_info *vsdb) +{ + u16 vrr_min =3D display->monitor_range.min_vfreq; + u16 vrr_max =3D display->monitor_range.max_vfreq; + + /* Always extend upper limit */ + if (vsdb->max_refresh_rate_hz > vrr_max) + vrr_max =3D vsdb->max_refresh_rate_hz; + + /* + * Only extend lower limit if current one disables LFC. + + * During widespread testing, we found that some manufacturers probably + * had issues with their monitors' lower VRR boundaries and adjusted + * them up (Gigabyte X34GS with official range 48 - 180, AMD vsdb 48 - + * 180 yet Monitor Ranges 55 - 180). After setting the lower boundary + * from AMD vsdb, such monitors start having blanking issues. + * + * Work around that by not touching VRR min if it still supports LFC. + */ + if (vsdb->min_refresh_rate_hz < vrr_min && (vrr_min * 2 >=3D vrr_max)) + vrr_min =3D vsdb->min_refresh_rate_hz; + + display->monitor_range.min_vfreq =3D vrr_min; + display->monitor_range.max_vfreq =3D vrr_max; +} + /** * amdgpu_dm_update_freesync_caps - Update Freesync capabilities * @@ -13339,6 +13367,9 @@ void amdgpu_dm_update_freesync_caps(struct drm_conn= ector *connector, if (is_monitor_range_invalid(connector)) monitor_range_from_vsdb(&connector->display_info, &vsdb_info); =20 + /* Try extending range if found in AMD vsdb */ + extend_range_from_vsdb(&connector->display_info, &vsdb_info); + if (dpcd_caps.allow_invalid_MSA_timing_param) freesync_capable =3D copy_range_to_amdgpu_connector(connector); =20 --=20 2.53.0