Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp1672556ybb; Thu, 26 Mar 2020 05:20:56 -0700 (PDT) X-Google-Smtp-Source: ADFU+vtuhwGlz721BWLHwleQFqseeALF/YZ9ohf+0LYLiuuZJ6VfaY9c0vEUIiWJgM0VVI3X50zN X-Received: by 2002:a05:6830:138e:: with SMTP id d14mr6093779otq.248.1585225255882; Thu, 26 Mar 2020 05:20:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1585225255; cv=none; d=google.com; s=arc-20160816; b=UUlqmJinYJGn5UeIYxF9P7+F7mtq2CcYrbdEQWTAQTbU/pe2nESWl+Q2vDj/tKDdyR 1b30E26k2AAolIWNOQvUVkLVhQpxdZpSMGOtMBDmKkFqXwkoK9a9crvVJhSs4/qU2IRW 2jA3VAQGfSEEZC6ISfkpSyq5w8Y2GRqHWxP9hVaElNLFxqpthnn34lL+8yZUWisbHY8O WPJJ/XS9Y8IKdHiqoh1/pdeEv+0DUCIkxfUEjv5CbsMy0JRR3OXvzztPyzceSwEn4NF8 IneuTHmy/A8qXU2f9RG1OezPjw9oM6YjHu+cN/O8Efe4m9QVVzvqikWYU2MsEVjf/wug E8aw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from; bh=hdXrgqNzQbKt8U2P4sHK4OJtFtCpBvDiTgLc7PYzeSw=; b=UI08J2mh7CHIGoBwoEd9dh+U4SY8Es54N8PYFM4x8+L8isEjkiksAAuEWAIEWm41yq t0hweQ4fyw7OMUr3S0pcPxpl1GY8Pb1zdnVuV1pHbku4T9uPrO3qB9aLlv0ThAweMuOd B2Ln5qHpMiedQvco/wSj/X2TeWKi6QcSmJ1mE2QsiZ6wy7sM80TFUaixBNp5BAskU/Nx ZUlQ04W+mTUcalrVZnc3f3Nmpc02B7ggExP8Bw7tIXAsULLbddhws/v3/MvzJ80h/YEy AmXvvxIheJHqwdFghXApAC2DhuTalH6m0UOlmUg1hC4ibxJXyfy+yypD75uTUb929zq4 t3LA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id u1si945298otg.231.2020.03.26.05.20.42; Thu, 26 Mar 2020 05:20:55 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728130AbgCZMUT (ORCPT + 99 others); Thu, 26 Mar 2020 08:20:19 -0400 Received: from mx2.suse.de ([195.135.220.15]:56760 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727560AbgCZMUT (ORCPT ); Thu, 26 Mar 2020 08:20:19 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 4405BB117; Thu, 26 Mar 2020 12:20:17 +0000 (UTC) From: Nicolas Saenz Julienne To: Eric Anholt , Daniel Vetter Cc: maxime@cerno.tech, linux-rpi-kernel@lists.infradead.org, f.fainelli@gmail.com, Nicolas Saenz Julienne , Stefan Wahren , Dave Stevenson , David Airlie , Daniel Vetter , dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org Subject: [PATCH] drm/vc4: Fix HDMI mode validation Date: Thu, 26 Mar 2020 13:20:01 +0100 Message-Id: <20200326122001.22215-1-nsaenzjulienne@suse.de> X-Mailer: git-send-email 2.25.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Current mode validation impedes setting up some video modes which should be supported otherwise. Namely 1920x1200@60Hz. Fix this by lowering the minimum HDMI state machine clock to pixel clock ratio allowed. Fixes: 32e823c63e90 ("drm/vc4: Reject HDMI modes with too high of clocks") Reported-by: Stefan Wahren Suggested-by: Dave Stevenson Signed-off-by: Nicolas Saenz Julienne --- drivers/gpu/drm/vc4/vc4_hdmi.c | 20 ++++++++++++++++---- 1 file changed, 16 insertions(+), 4 deletions(-) diff --git a/drivers/gpu/drm/vc4/vc4_hdmi.c b/drivers/gpu/drm/vc4/vc4_hdmi.c index cea18dc15f77..340719238753 100644 --- a/drivers/gpu/drm/vc4/vc4_hdmi.c +++ b/drivers/gpu/drm/vc4/vc4_hdmi.c @@ -681,11 +681,23 @@ static enum drm_mode_status vc4_hdmi_encoder_mode_valid(struct drm_encoder *crtc, const struct drm_display_mode *mode) { - /* HSM clock must be 108% of the pixel clock. Additionally, - * the AXI clock needs to be at least 25% of pixel clock, but - * HSM ends up being the limiting factor. + /* + * As stated in RPi's vc4 firmware "HDMI state machine (HSM) clock must + * be faster than pixel clock, infinitesimally faster, tested in + * simulation. Otherwise, exact value is unimportant for HDMI + * operation." This conflicts with bcm2835's vc4 documentation, which + * states HSM's clock has to be at least 108% of the pixel clock. + * + * Real life tests reveal that vc4's firmware statement holds up, and + * users are able to use pixel clocks closer to HSM's, namely for + * 1920x1200@60Hz. So it was decided to have leave a 1% margin between + * both clocks. Which, for RPi0-3 implies a maximum pixel clock of + * 162MHz. + * + * Additionally, the AXI clock needs to be at least 25% of + * pixel clock, but HSM ends up being the limiting factor. */ - if (mode->clock > HSM_CLOCK_FREQ / (1000 * 108 / 100)) + if (mode->clock > HSM_CLOCK_FREQ / (1000 * 101 / 100)) return MODE_CLOCK_HIGH; return MODE_OK; -- 2.25.1