Received: by 2002:a05:6358:1087:b0:cb:c9d3:cd90 with SMTP id j7csp920999rwi; Wed, 26 Oct 2022 08:43:04 -0700 (PDT) X-Google-Smtp-Source: AMsMyM6FL0HFt6G/B6k5aE/MfqAzTUrzME/s2EsN8qIAEdwZ5gkT9UUb8cOFaI/355g0TYVEayO2 X-Received: by 2002:a05:6a00:1912:b0:564:f6be:11fd with SMTP id y18-20020a056a00191200b00564f6be11fdmr43744390pfi.32.1666798984287; Wed, 26 Oct 2022 08:43:04 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1666798984; cv=none; d=google.com; s=arc-20160816; b=bof1asRJIy9pHll+AdHxWXnDPttjfv+Vdlcm2hKHXZJEZIGM0i6Tv7sGSuHl/Mb0Bq makZVm4a3tF1czkpDtZx3GaafH0qpgp+0bXuX6nD8yhUAThMJI9DNfSHBKO6EH002f6Y uQukv6zHqu1zgZWC/P5egdZfvrJGdeq+bvLFUFftHDkTfSIrlKd36IbqbQTnmOSMlhe9 IRPqXSaXI4HLvCWb2pBWOZCg6JkZnouglh/Ic9pBOJ506UDNybrIJl+cEHhFV9UpsqFF VO4OEigAjYOq9cCkTm4xzGURVr07wn2JgjRD0EBovgxJyDBdUECwIt+iHZeY2TlwN3YA fYwg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=F6j1fHe9OYs4e+5UqU3Og3KPmdDBG92hQv3wiQCuJoA=; b=vGMSJFbajfQqmkJvt0cxlNihW3mmgKghu4nd9gpAJxPBwHxDy5nXcbg/+huICV/TdP fFTSnlJt+c/5Knpeb0VghCcNWvHenq6hFIsgJUCHsT49papOjE6W9CKVqEbbPOhAHOcZ I7IPND/872G9v/OvQnoZAWFeFaH/DFRFwGcPVdwfhRp78+aQtFfOYLmB/Qxhq1tirusY x3kseuQxuMC+OGpDyA6sSoASJzobMiEd48XIJAZv8MsmxlhcyMlSzqh/mLneMexC712O eHwPPHH/d2wjX+bGskqE9aFmPNfrF7V7FHlB6J/qtWU1SoKdS/Yai1Mjv1rXfq/G+aKG mlyw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@raspberrypi.com header.s=google header.b=kWE3JZ1p; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=raspberrypi.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id y12-20020a1709029b8c00b0017deb323079si6276555plp.142.2022.10.26.08.42.50; Wed, 26 Oct 2022 08:43:04 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@raspberrypi.com header.s=google header.b=kWE3JZ1p; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=raspberrypi.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234553AbiJZP2R (ORCPT + 99 others); Wed, 26 Oct 2022 11:28:17 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38306 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234547AbiJZP2O (ORCPT ); Wed, 26 Oct 2022 11:28:14 -0400 Received: from mail-ej1-x62d.google.com (mail-ej1-x62d.google.com [IPv6:2a00:1450:4864:20::62d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0867E130D44 for ; Wed, 26 Oct 2022 08:28:13 -0700 (PDT) Received: by mail-ej1-x62d.google.com with SMTP id 13so22323688ejn.3 for ; Wed, 26 Oct 2022 08:28:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raspberrypi.com; s=google; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=F6j1fHe9OYs4e+5UqU3Og3KPmdDBG92hQv3wiQCuJoA=; b=kWE3JZ1ps1qMWp6E0WTYFDG5RgPeN0Ibtu1R/f81JmR5OjPwN1QedbbuJQO+F0r3Du B5wvmn+JzhXgiHl3FJrdOjv8u0gWeNfoTW6/FvqbRLTMM4RofN/Z5q6kGkvmpFyxgV0R twTuJQrEEVetK9ZsaW7Qwgbpk7jx1ULTaEko7L5vjRPb3vNvAgjXp7BVBlUw3EnhKBTo Acsx92BI6QFMvGI3qqNfsqdpW/yd4bLW4e5e0g/c12IFbjC+hjorj8UtYB8Ig8NNbC6G ATHmRLI4nXUw638h3aB8SAVeTRCf6BIvolek3NzKK9jF7iOL0BLpEtANPFWIiZOAp0d8 n+lA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=F6j1fHe9OYs4e+5UqU3Og3KPmdDBG92hQv3wiQCuJoA=; b=EWXsdlt3BlyqFPSkvdBEI1vGLV4QzkPiF0QlvHqzfjNnGC4ffGBcjJ44fGClmpeHbW PKshkhsY6wp4ylv1DXiIbgD5M69VPgBYoJpGqpZBRx8fZqqRr7dVZSVVS/kS1t7h9n2K +8Ch2qNO5t7EHXGR8COwt6g8NwrkUD6vU3PVJu6XgVTlmDXkmzrQUPV3FKCd7leQYUC0 Qb+hta+42IDS0SAe4i/YXjAF9ajpE3mav2cd996XSCttZKAQcv1qB6UOABNO+4DqBJZZ SSv3EFLa503oQUmNKpmHvua7tMxIk4hCCIXzrRRrcNhFWqgb8T9+B66rh2LxWYFG205i n2kw== X-Gm-Message-State: ACrzQf1T2byonyTbw8nX2gxjXpuLktO6gWG+v2KlUZCXja+XDgSapPtB SJvT+x8YRUAZsqFxgmPNVbaUx0C0DHdR8BWR2FSTwQ== X-Received: by 2002:a17:907:1c98:b0:78d:3b08:33ef with SMTP id nb24-20020a1709071c9800b0078d3b0833efmr39091535ejc.175.1666798091611; Wed, 26 Oct 2022 08:28:11 -0700 (PDT) MIME-Version: 1.0 References: <20220815-rpi-fix-4k-60-v4-0-a1b40526df3e@cerno.tech> <20220815-rpi-fix-4k-60-v4-4-a1b40526df3e@cerno.tech> In-Reply-To: <20220815-rpi-fix-4k-60-v4-4-a1b40526df3e@cerno.tech> From: Dave Stevenson Date: Wed, 26 Oct 2022 16:27:56 +0100 Message-ID: Subject: Re: [PATCH v4 4/7] drm/vc4: hdmi: Fix hdmi_enable_4kp60 detection To: maxime@cerno.tech Cc: Daniel Vetter , Emma Anholt , Michael Turquette , Stephen Boyd , Maxime Ripard , Ray Jui , Florian Fainelli , David Airlie , Broadcom internal kernel review list , Scott Branden , Stefan Wahren , linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, Dom Cobley , linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-rpi-kernel@lists.infradead.org Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 20 Oct 2022 at 10:14, wrote: > > In order to support higher HDMI frequencies, users have to set the > hdmi_enable_4kp60 parameter in their config.txt file. > > We were detecting this so far by calling clk_round_rate() on the core > clock with the frequency we're supposed to run at when one of those > modes is enabled. Whether or not the parameter was enabled could then be > inferred by the returned rate since the maximum clock rate reported by > the firmware was one of the side effect of setting that parameter. > > However, the recent clock rework we did changed what clk_round_rate() > was returning to always return the minimum allowed, and thus this test > wasn't reliable anymore. > > Let's use the new clk_get_max_rate() function to reliably determine the > maximum rate allowed on that clock and fix the 4k@60Hz output. > > Fixes: e9d6cea2af1c ("clk: bcm: rpi: Run some clocks at the minimum rate allowed") > Signed-off-by: Maxime Ripard Reviewed-by: Dave Stevenson > --- > drivers/gpu/drm/vc4/vc4_hdmi.c | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/drivers/gpu/drm/vc4/vc4_hdmi.c b/drivers/gpu/drm/vc4/vc4_hdmi.c > index 64f9feabf43e..87961d4de5aa 100644 > --- a/drivers/gpu/drm/vc4/vc4_hdmi.c > +++ b/drivers/gpu/drm/vc4/vc4_hdmi.c > @@ -46,6 +46,7 @@ > #include > #include > #include > +#include > #include > #include > #include > @@ -3429,7 +3430,7 @@ static int vc4_hdmi_bind(struct device *dev, struct device *master, void *data) > > if (variant->max_pixel_clock == 600000000) { > struct vc4_dev *vc4 = to_vc4_dev(drm); > - long max_rate = clk_round_rate(vc4->hvs->core_clk, 550000000); > + unsigned long max_rate = rpi_firmware_clk_get_max_rate(vc4->hvs->core_clk); > > if (max_rate < 550000000) > vc4_hdmi->disable_4kp60 = true; > > -- > b4 0.10.1