Received: by 2002:a05:6358:a55:b0:ec:fcf4:3ecf with SMTP id 21csp6288370rwb; Wed, 18 Jan 2023 03:32:38 -0800 (PST) X-Google-Smtp-Source: AMrXdXsgDxrlZZr2UzYZpjtY8pEtaxTdTmXOIP9IgKTBa7whUB1/adLRatN/oB/UvnD3ZZ4J7OrQ X-Received: by 2002:a05:6a21:170e:b0:b8:827c:42c7 with SMTP id nv14-20020a056a21170e00b000b8827c42c7mr6396212pzb.27.1674041556984; Wed, 18 Jan 2023 03:32:36 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1674041556; cv=none; d=google.com; s=arc-20160816; b=AmNnatu4AxOwFu8DEsL8OJ/DnOi+8N8E5ufDeWGSj0qy4iUFigC+I/h6iesqNRP6uM 3+8SQMYxgzIRoXdKqnc1qcmQLQET8PXOO/oKeRatNKvfb4c/fGb121fH4co2XTGFjQsX 4dqu/NL5WssAB+7tlfvVoQy0WgDItu4yDUQ0DdPJlOLE5sW6H87DE7rDaGcoa/mu6+WQ vaGXqx0OaL8lpGlevQYE3Zij228w6TfU48JfbaDIaZoIkdaf3D6rqmoKpf2f4asFyIOK 8mof7zNxck/JSCMXNNYlgdpQYLIZwPDIRp1CiB5NNlcRD7K80A/WeBffY8AeIs9P8Bq0 c4uw== 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 :message-id:date:subject:cc:to:from:dkim-signature; bh=X9erqJru4XPgjOURANw2ncUgTgC8yFwhYsbY0uUOyl8=; b=EBzA3oJFPRn4V/MoGZzBy02naSeEMoexmW2z+js3NIf9XUjFTAiGlUjXknG7IzrMOj +sBJtgxIbZsA8xJzerKDGfRkhyKJikmLQAm352Br88x2z/Ni2kWZFy3G6HYNHpo2AxY2 EfHqB4T99FPjzbkIb+qtjrRoFY8sTjdgtKXG5Dke54rreRnSB663ySh9zzZ/uOB+YfuD 15lEv6vHF4SeODjsH8XFLz6W57kEP2MusCPGuQ9GewfrNXAmN3DeUtX+Welzt+2kZE2c FxmQG6EzPUojNsh3ZSSmsRTzZ09dYXi6zUdqUM4ngU/8PqnN1YG4o92y09UvGbw2FRXZ CPkw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=aetc572J; 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=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id k8-20020a63ff08000000b0049ca23dd532si12758622pgi.109.2023.01.18.03.32.31; Wed, 18 Jan 2023 03:32:36 -0800 (PST) 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=@gmail.com header.s=20210112 header.b=aetc572J; 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=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229463AbjARLGj (ORCPT + 45 others); Wed, 18 Jan 2023 06:06:39 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57232 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230432AbjARLFQ (ORCPT ); Wed, 18 Jan 2023 06:05:16 -0500 Received: from mail-wr1-x42f.google.com (mail-wr1-x42f.google.com [IPv6:2a00:1450:4864:20::42f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A0B0038B42 for ; Wed, 18 Jan 2023 02:11:42 -0800 (PST) Received: by mail-wr1-x42f.google.com with SMTP id e3so24157958wru.13 for ; Wed, 18 Jan 2023 02:11:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:from:to:cc:subject:date:message-id:reply-to; bh=X9erqJru4XPgjOURANw2ncUgTgC8yFwhYsbY0uUOyl8=; b=aetc572Jkz81PofCbQdsfwcHdm8KluXPcZ6+I3ifpv1I/B3j4TBDMH2yjxmIxMAS9R JPeU2+G7hMcQXLsi07akridWxfeGElEi5Yxty1YIXhnbocYaQvn7ClpsEsdS8wjILVAF EmzEdq8u1Pn2LB939plEC4a7yRmCG79QXq2eOeWlz3N9stVyj8iCv6HTbJfdvmTptLvF 1FtOpZ78FLu30c5aPtEeXTTTtgO03BDjT3U+RRrof24v8ktVT/+Q8AvdOMkKpjehrrug +Cr3mbbMIi7LMfR5p0WTyE5dEKPBAVNfh1syL1wW6rd9WoiJtVdoFfWe5kHYFGzHpGBQ axtg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=X9erqJru4XPgjOURANw2ncUgTgC8yFwhYsbY0uUOyl8=; b=pzLD3E2D9/AyeX97r7OckeKdyybo91bUe6jtND/3AwGH4bh+kcuJ6lpllgZ69bxo7n SLgmHNuEcw/zB6N0pXjL69oUVN2e5isRQ/8/6nj1pgrC4ijKI/sR9lBtCd6+zLIdGoAd 3qgtujn5nK+4IIgJGjREInCpdVy7iW3LzeDwW6Xm1RPyOrZlXqSChjcXbDdyb+3js9AH NjM25aS09qUwyBEiit0f7P/4VxPel/YuVF8aXvMGDxtYAK741VGIfl1hG8wk+c/LbQ0G wqmbW9X2+1LAFnfviDQFbKUwVxTDAdSViBmV6Fo799Bo/ASXc006eWlm7dhEHq3UBA8o wo3A== X-Gm-Message-State: AFqh2ko4W3HS29AzUzs0/Wx4jTM0kmfOkxRFDpSBGMo5kRE5g9Y2PxN2 6/aGpVAYvY9UpgqtMnPQ7EhU3PmAca8CH6Bs X-Received: by 2002:a5d:5608:0:b0:2b6:daf8:52ad with SMTP id l8-20020a5d5608000000b002b6daf852admr1567589wrv.52.1674036701073; Wed, 18 Jan 2023 02:11:41 -0800 (PST) Received: from localhost.localdomain ([93.119.166.152]) by smtp.gmail.com with ESMTPSA id y18-20020a5d6152000000b002425be3c9e2sm30323113wrt.60.2023.01.18.02.11.39 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 18 Jan 2023 02:11:40 -0800 (PST) From: Nicu Borta To: Harry Wentland , Leo Li , Rodrigo Siqueira , Alex Deucher , =?UTF-8?q?Christian=20K=C3=B6nig?= , "Pan, Xinhui" , David Airlie , Daniel Vetter Cc: Nicu Borta , amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org Subject: [PATCH] amd/dcn20: Fix high mem clock with multiple displays Date: Wed, 18 Jan 2023 12:11:08 +0200 Message-Id: <20230118101107.10173-1-nicuborta123@gmail.com> X-Mailer: git-send-email 2.38.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-1.8 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS 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 RX5000 series GPUs, using a high refresh rate monitor causes the VRAM to always stay at the highest clock (according to AMD, this is done to prevent flickering). However, when using 2 monitors (e.g. one at 165Hz and another at 60Hz), then disconnecting the high refresh monitor, before this patch the VRAM clock didn't decrease like it should. This patch fixes that bug, and now, when disconnecting the high refresh rate monitor, the VRAM clock jumps to the minimum. Tested for a few months, I haven't noticed any visual artifacts or other errors (RX5700XT). Signed-off-by: Nicu Borta --- drivers/gpu/drm/amd/display/dc/dcn20/dcn20_resource.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/amd/display/dc/dcn20/dcn20_resource.c b/drivers/gpu/drm/amd/display/dc/dcn20/dcn20_resource.c index 8a0dd0d7134b..481a15b02126 100644 --- a/drivers/gpu/drm/amd/display/dc/dcn20/dcn20_resource.c +++ b/drivers/gpu/drm/amd/display/dc/dcn20/dcn20_resource.c @@ -714,7 +714,7 @@ static const struct dc_debug_options debug_defaults_drv = { .timing_trace = false, .clock_trace = true, .disable_pplib_clock_request = true, - .pipe_split_policy = MPC_SPLIT_AVOID_MULT_DISP, + .pipe_split_policy = MPC_SPLIT_DYNAMIC, .force_single_disp_pipe_split = false, .disable_dcc = DCC_ENABLE, .vsr_support = true, -- 2.38.2