From nobody Tue Feb 10 21:10:45 2026 Received: from mail-244118.protonmail.ch (mail-244118.protonmail.ch [109.224.244.118]) (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 7A9B93115AE for ; Mon, 29 Dec 2025 22:26:50 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=109.224.244.118 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1767047214; cv=none; b=UJGSJh0K2J3gjfR+uLktr1/3BFeE2n2EOOwAuIinrfZhkJ8fJDeLJtE6WVr4nwBrlyG3CikIF5VpmkiDaoYdDwNxmLeazwXfPh3XuKqJQRFSdxMdM2di1TQJdzkVCE7rQE4sKGkHWYE+2w+B88Th7L6kM3znVVzWG0oGpfeV3gk= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1767047214; c=relaxed/simple; bh=UFvaloWsYGR2eHoLNVAqWMKzdhK5djHV99rDQYKY25A=; h=Date:To:From:Cc:Subject:Message-ID:MIME-Version:Content-Type; b=C+dLUjOBDLmA/wG/+qjJy5RK/SlMC5c50AxBUjTyGmtLqbgA8dxI1+71kr7qmwDQ0k0jZ2rNaQFMiuZvQW5VKHii5WERnUr3sf+Jj8mBeNSAisfgpscvDmvcQVrRFi55A7ucV1GfRQt0uKOCxGg1Y+RVg2OtHNodbdSrt/j9PHc= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=zukunftsfirma.de; spf=pass smtp.mailfrom=zukunftsfirma.de; dkim=pass (2048-bit key) header.d=zukunftsfirma.de header.i=@zukunftsfirma.de header.b=UG8Bntbg; arc=none smtp.client-ip=109.224.244.118 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=zukunftsfirma.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=zukunftsfirma.de Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=zukunftsfirma.de header.i=@zukunftsfirma.de header.b="UG8Bntbg" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zukunftsfirma.de; s=protonmail; t=1767047202; x=1767306402; bh=Yg4kX+P8FMYtSkANlGes/bcs+pX/UGCk4bUyWs0IyMM=; h=Date:To:From:Cc:Subject:Message-ID:Feedback-ID:From:To:Cc:Date: Subject:Reply-To:Feedback-ID:Message-ID:BIMI-Selector; b=UG8Bntbg4Hsgo79TzVdWa2uDog9GknxfwTmcXhLp9wJsW0XUD5O7ia+klrsTxdK3+ pAI5cjOJ8e24U6qOO+dxJVvBecHjxTMsvNER793OT2xg3J+AqGnA1ni9StUUmLxgRv q6gK4mZsm2X+mU6kbyBP2fhGKiX/YCOO/sAvBMm/yOKYku5uMJB08m/ADhsnCmMRyv BLtOJsoQEO7KdWRjZalAN8e+0n9M8+zv/oOupd9YFUsRNb0pixjXjjTQEzm24kvB6Z YX3SwblNgDYSyqGzGm6PiS9vIAS9DEqC21rhsarUx/Dyj6eOXN/4obao3CQuGF7rkz YlTlL4ElYffTg== Date: Mon, 29 Dec 2025 22:26:39 +0000 To: "linux-kernel@vger.kernel.org" From: Andreas Bauer Cc: "dri-devel@lists.freedesktop.org" , "amd-gfx@lists.freedesktop.org" , "harry.wentland@amd.com" , "sunpeng.li@amd.com" , "siqueira@igalia.com" , "alexander.deucher@amd.com" , "christian.koenig@amd.com" , "airlied@gmail.com" , "simona@ffwll.ch" Subject: [PATCH] drm/amd/display: correct AMDGPU Display Core logging logic Message-ID: Feedback-ID: 149865295:user:proton X-Pm-Message-ID: dba1f3d43dc289ce1765e654a5e1784e04fe688e Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" In: drivers/gpu/drm/amd/display/dc/link/protocols/link_dp_capability.c dp_is_lttpr_present() does output a DC_LOG_ERROR() when monitor reports DPCD lane count non zero but no lanes detected, and gracefully falls back to ignoring what the monitor reports. dp_retrieve_lttpr_cap() also logs an DC_LOG_ERROR() when hardware returns wrong count. Fallback means also graceful handling. According to documentation, DC_LOG_WARNING() is supposed to be used for=20 this case (hardware bug with graceful fallback) Change DC_LOG_ERROR() to DC_LOG_WARNING() in both cases. Signed-off-by: Andreas Bauer --- diff -uprN linux-source-6.18.orig/drivers/gpu/drm/amd/display/dc/link/proto= cols/link_dp_capability.c linux-source-6.18.modified/drivers/gpu/drm/amd/di= splay/dc/link/protocols/link_dp_capability.c --- linux-source-6.18.orig/drivers/gpu/drm/amd/display/dc/link/protocols/li= nk_dp_capability.c 2025-12-29 21:03:40.477580191 +0000 +++ linux-source-6.18.modified/drivers/gpu/drm/amd/display/dc/link/protocol= s/link_dp_capability.c 2025-12-29 22:09:47.338435938 +0000 @@ -391,7 +391,8 @@ bool dp_is_lttpr_present(struct dc_link link->dpcd_caps.lttpr_caps.max_lane_count <=3D 4); =20 if (lttpr_count > 0 && !is_lttpr_present) - DC_LOG_ERROR("LTTPR count is nonzero but invalid lane count= reported. Assuming no LTTPR present.\n"); + DC_LOG_WARNING("LTTPR count is nonzero but invalid lane cou= nt reported. " + + "Assuming no LTTPR present.\n"); =20 return is_lttpr_present; } @@ -1638,7 +1639,7 @@ enum dc_status dp_retrieve_lttpr_cap(str /* If you see this message consistently, either the host pl= atform has FIXED_VS flag * incorrectly configured or the sink device is returning a= n invalid count. */ - DC_LOG_ERROR("lttpr_caps phy_repeater_cnt is 0x%x, forcing = it to 0x80.", + DC_LOG_WARNING("lttpr_caps phy_repeater_cnt is 0x%x, forcin= g it to 0x80.", link->dpcd_caps.lttpr_caps.phy_repeater_cnt); link->dpcd_caps.lttpr_caps.phy_repeater_cnt =3D 0x80; lttpr_count =3D 1;