From: Sasha Levin <sashal@kernel.org>
To: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Cc: Paul Hsieh <paul.hsieh@amd.com>,
Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>,
Zaeem Mohamed <zaeem.mohamed@amd.com>,
Daniel Wheeler <daniel.wheeler@amd.com>,
Alex Deucher <alexander.deucher@amd.com>,
Sasha Levin <sashal@kernel.org>,
harry.wentland@amd.com, sunpeng.li@amd.com,
Rodrigo.Siqueira@amd.com, christian.koenig@amd.com,
Xinhui.Pan@amd.com, airlied@gmail.com, daniel@ffwll.ch,
charlene.liu@amd.com, hamza.mahfooz@amd.com,
chiahsuan.chung@amd.com, nicholas.susanto@amd.com,
natanel.roizenman@amd.com, ahmed.ahmed@amd.com,
Qingqing.Zhuo@amd.com, yang.lee@linux.alibaba.com,
syed.hassan@amd.com, jerry.zuo@amd.com,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: [PATCH AUTOSEL 6.9 16/20] drm/amd/display: change dram_clock_latency to 34us for dcn35
Date: Sun, 30 Jun 2024 20:11:21 -0400 [thread overview]
Message-ID: <20240701001209.2920293-16-sashal@kernel.org> (raw)
In-Reply-To: <20240701001209.2920293-1-sashal@kernel.org>
From: Paul Hsieh <paul.hsieh@amd.com>
[ Upstream commit 6071607bfefefc50a3907c0ba88878846960d29a ]
[Why & How]
Current DRAM setting would cause underflow on customer platform.
Modify dram_clock_change_latency_us from 11.72 to 34.0 us as per recommendation from HW team
Reviewed-by: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
Acked-by: Zaeem Mohamed <zaeem.mohamed@amd.com>
Signed-off-by: Paul Hsieh <paul.hsieh@amd.com>
Tested-by: Daniel Wheeler <daniel.wheeler@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
---
drivers/gpu/drm/amd/display/dc/dml/dcn35/dcn35_fpu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/amd/display/dc/dml/dcn35/dcn35_fpu.c b/drivers/gpu/drm/amd/display/dc/dml/dcn35/dcn35_fpu.c
index 53e40d3c48d4b..6716696df7719 100644
--- a/drivers/gpu/drm/amd/display/dc/dml/dcn35/dcn35_fpu.c
+++ b/drivers/gpu/drm/amd/display/dc/dml/dcn35/dcn35_fpu.c
@@ -177,7 +177,7 @@ struct _vcs_dpi_soc_bounding_box_st dcn3_5_soc = {
.urgent_latency_pixel_data_only_us = 4.0,
.urgent_latency_pixel_mixed_with_vm_data_us = 4.0,
.urgent_latency_vm_data_only_us = 4.0,
- .dram_clock_change_latency_us = 11.72,
+ .dram_clock_change_latency_us = 34.0,
.urgent_out_of_order_return_per_channel_pixel_only_bytes = 4096,
.urgent_out_of_order_return_per_channel_pixel_and_vm_bytes = 4096,
.urgent_out_of_order_return_per_channel_vm_only_bytes = 4096,
--
2.43.0
next prev parent reply other threads:[~2024-07-01 0:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 0:11 [PATCH AUTOSEL 6.9 01/20] ALSA: hda: cs35l56: Fix lifecycle of codec pointer Sasha Levin
2024-07-01 0:11 ` [PATCH AUTOSEL 6.9 02/20] wifi: cfg80211: wext: add extra SIOCSIWSCAN data check Sasha Levin
2024-07-01 0:11 ` [PATCH AUTOSEL 6.9 03/20] ALSA: hda: cs35l41: Support Lenovo Thinkbook 16P Gen 5 Sasha Levin
2024-07-01 0:11 ` [PATCH AUTOSEL 6.9 04/20] ALSA: hda: cs35l41: Support Lenovo Thinkbook 13x Gen 4 Sasha Levin
2024-07-01 0:11 ` [PATCH AUTOSEL 6.9 05/20] ALSA: hda/realtek: Support Lenovo Thinkbook 16P Gen 5 Sasha Levin
2024-07-01 0:11 ` [PATCH AUTOSEL 6.9 06/20] ALSA: hda/realtek: Support Lenovo Thinkbook 13x Gen 4 Sasha Levin
2024-07-01 0:11 ` [PATCH AUTOSEL 6.9 07/20] wifi: mac80211: Avoid address calculations via out of bounds array indexing Sasha Levin
2024-07-01 0:11 ` [PATCH AUTOSEL 6.9 08/20] KVM: PPC: Book3S HV: Prevent UAF in kvm_spapr_tce_attach_iommu_group() Sasha Levin
2024-07-01 0:11 ` [PATCH AUTOSEL 6.9 09/20] drm/vmwgfx: Fix missing HYPERVISOR_GUEST dependency Sasha Levin
2024-07-01 0:11 ` [PATCH AUTOSEL 6.9 10/20] ALSA: hda/realtek: Add more codec ID to no shutup pins list Sasha Levin
2024-07-01 0:11 ` [PATCH AUTOSEL 6.9 11/20] spi: Fix OCTAL mode support Sasha Levin
2024-07-01 0:11 ` [PATCH AUTOSEL 6.9 12/20] cpumask: limit FORCE_NR_CPUS to just the UP case Sasha Levin
2024-07-01 0:11 ` [PATCH AUTOSEL 6.9 13/20] selftests: openvswitch: Set value to nla flags Sasha Levin
2024-07-01 0:11 ` [PATCH AUTOSEL 6.9 14/20] drm/amdgpu: Indicate CU havest info to CP Sasha Levin
2024-07-01 0:11 ` [PATCH AUTOSEL 6.9 15/20] drm/amd/display: Change dram_clock_latency to 34us for dcn351 Sasha Levin
2024-07-01 0:11 ` Sasha Levin [this message]
2024-07-01 0:11 ` [PATCH AUTOSEL 6.9 17/20] drm/amdgpu: init TA fw for psp v14 Sasha Levin
2024-07-01 0:11 ` [PATCH AUTOSEL 6.9 18/20] ALSA: hda: cs35l56: Select SERIAL_MULTI_INSTANTIATE Sasha Levin
2024-07-01 0:11 ` [PATCH AUTOSEL 6.9 19/20] mips: fix compat_sys_lseek syscall Sasha Levin
2024-07-01 0:11 ` [PATCH AUTOSEL 6.9 20/20] closures: Change BUG_ON() to WARN_ON() Sasha Levin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240701001209.2920293-16-sashal@kernel.org \
--to=sashal@kernel.org \
--cc=Qingqing.Zhuo@amd.com \
--cc=Rodrigo.Siqueira@amd.com \
--cc=Xinhui.Pan@amd.com \
--cc=ahmed.ahmed@amd.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=charlene.liu@amd.com \
--cc=chiahsuan.chung@amd.com \
--cc=christian.koenig@amd.com \
--cc=daniel.wheeler@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hamza.mahfooz@amd.com \
--cc=harry.wentland@amd.com \
--cc=jerry.zuo@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=natanel.roizenman@amd.com \
--cc=nicholas.kazlauskas@amd.com \
--cc=nicholas.susanto@amd.com \
--cc=paul.hsieh@amd.com \
--cc=stable@vger.kernel.org \
--cc=sunpeng.li@amd.com \
--cc=syed.hassan@amd.com \
--cc=yang.lee@linux.alibaba.com \
--cc=zaeem.mohamed@amd.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox