Received: by 2002:a05:6a10:a852:0:0:0:0 with SMTP id d18csp498876pxy; Wed, 5 May 2021 07:17:39 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzVVZz7Wg5iFh7m7Ryy6A3+KVtVvh6jbYKGRuNjHHPFemze6If0WRKTay8fT2AeVq8Yy+/l X-Received: by 2002:a50:e809:: with SMTP id e9mr32947911edn.316.1620224257406; Wed, 05 May 2021 07:17:37 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1620224257; cv=none; d=google.com; s=arc-20160816; b=NWmDCKoXMxKLTKfGnBi4K6y3H7eFh5ERTQwaeirh7n8gMfz1VddEFgjdiiJp7F4MVE 1XA9AsczflLCPN5bdVqZgjBOYkhKHdNRSD/rYUc5/wG7P582sCZjk1XAtiqFMCSelCci CBlmoJ1RlcbhL/2LQv5Mhm+Y808t3PQFOz64uHT7FdTCvadOdFuaI83YBJe2rg3ASFCh rH6xJI5YII0ZHTXzMKSYLvpmWFkU2E7IZMZWDAhETxH/UDbAxM0SA6Jby9XxvELRTwxm e9qLb6PE14O19KW/eV71WVgVkfn8TQ7cLesQmMI/Zz+wdGYMRFHXBX396nvD9xQC7rcN aUCA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:to:from; bh=iNhoaAm53H+LoLEq0876Hchr7kmb5yqz0JXqmQHNuOI=; b=RucV3C3uUIYRyU8+JfGN6OQKKchupe8xtjybJws5VcKB0Qg2gUszOC9pYfOY3jnpjS BmB66Ld0m6hZHkza+Zl0Zz5kyzXg8Hwo+2WeY4D9XPOMaZsDzHNzKwnic1iLwpMmRrp+ yJRVBzSUOACZvm8gIxchlN/OZaO6tmJzDQmsh4hrJFB/xBkwfaxHRnmnO5v3Nc70CsbB JSPHEWxRQMM0EqF+qBiv6MaQ+RdvhPH6NT/VBv3LhHE3Af5chyadr2D2jEcThryAm66r jOVJuTkSXhBc6TE6hpX1SnISpSNmflEvvZ2T5yovRjxM/GKj4N63XhqvkJq5TcouUA83 yl7A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id dd4si1769032edb.125.2021.05.05.07.17.12; Wed, 05 May 2021 07:17:37 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233694AbhEEOL4 (ORCPT + 99 others); Wed, 5 May 2021 10:11:56 -0400 Received: from srv6.fidu.org ([159.69.62.71]:60368 "EHLO srv6.fidu.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233592AbhEEOLy (ORCPT ); Wed, 5 May 2021 10:11:54 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by srv6.fidu.org (Postfix) with ESMTP id 65FF5C800A8; Wed, 5 May 2021 16:10:56 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at srv6.fidu.org Received: from srv6.fidu.org ([127.0.0.1]) by localhost (srv6.fidu.org [127.0.0.1]) (amavisd-new, port 10026) with LMTP id xnb4UTLG5bPz; Wed, 5 May 2021 16:10:56 +0200 (CEST) Received: from wsembach-tuxedo.fritz.box (p200300E37F39860005a4018A54F094b9.dip0.t-ipconnect.de [IPv6:2003:e3:7f39:8600:5a4:18a:54f0:94b9]) (Authenticated sender: wse@tuxedocomputers.com) by srv6.fidu.org (Postfix) with ESMTPA id 24AEDC800B7; Wed, 5 May 2021 16:10:56 +0200 (CEST) From: Werner Sembach To: wse@tuxedocomputers.com, ville.syrjala@linux.intel.com, airlied@linux.ie, daniel@ffwll.ch, intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org Subject: [PATCH 3/3] Use YCbCr420 as fallback when RGB fails Date: Wed, 5 May 2021 16:10:52 +0200 Message-Id: <20210505141052.3467-4-wse@tuxedocomputers.com> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20210505141052.3467-1-wse@tuxedocomputers.com> References: <20210505141052.3467-1-wse@tuxedocomputers.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org When encoder validation of a display mode fails, retry with less bandwidth heavy YCbCr420 color mode, if available. This enables some HDMI 1.4 setups to support 4k60Hz output, which previously failed silently. AMDGPU had nearly the exact same issue. This problem description is therefore copied from my commit message of the AMDGPU patch. On some setups, while the monitor and the gpu support display modes with pixel clocks of up to 600MHz, the link encoder might not. This prevents YCbCr444 and RGB encoding for 4k60Hz, but YCbCr420 encoding might still be possible. However, which color mode is used is decided before the link encoder capabilities are checked. This patch fixes the problem by retrying to find a display mode with YCbCr420 enforced and using it, if it is valid. Signed-off-by: Werner Sembach --- I did not include the suggested change at intel_hdmi_mode_valid, because as far as I can tell it doesn't make a difference. From 882afbfd5de6858c01bcef9580305082ce811701 Mon Sep 17 00:00:00 2001 From: Werner Sembach Date: Mon, 3 May 2021 16:23:17 +0200 Subject: [PATCH 3/3] Use YCbCr420 as fallback when RGB fails --- drivers/gpu/drm/i915/display/intel_hdmi.c | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/i915/display/intel_hdmi.c b/drivers/gpu/drm/i915/display/intel_hdmi.c index 2c3b545d5f24..3770ea00930f 100644 --- a/drivers/gpu/drm/i915/display/intel_hdmi.c +++ b/drivers/gpu/drm/i915/display/intel_hdmi.c @@ -1913,7 +1913,7 @@ intel_hdmi_mode_valid(struct drm_connector *connector, clock *= 2; } - if (drm_mode_is_420_only(&connector->display_info, mode)) + if (connector->ycbcr_420_allowed && drm_mode_is_420(&connector->display_info, mode)) clock /= 2; status = intel_hdmi_mode_clock_valid(hdmi, clock, has_hdmi_sink); @@ -2125,6 +2125,14 @@ static int intel_hdmi_compute_output_format(struct intel_encoder *encoder, } ret = intel_hdmi_compute_clock(encoder, crtc_state); + if (ret) { + if (crtc_state->output_format != INTEL_OUTPUT_FORMAT_YCBCR420 && + connector->ycbcr_420_allowed && + drm_mode_is_420_also(&connector->display_info, adjusted_mode)) { + crtc_state->output_format = INTEL_OUTPUT_FORMAT_YCBCR420; + ret = intel_hdmi_compute_clock(encoder, crtc_state); + } + } return ret; } -- 2.25.1