linux-stable.git/drivers/gpu/drm/amd/display/dc, branch v5.10

drm/amd/display: Add wm table for Renoir

2020-12-09T15:06:39+00:00

[Why]
Without additional HostVM Latency, Renoir takes 2us longer to exit
self-refresh. This causes underflow in certain cases.

[How]
Add table for Renoir with updated sr exit latencies for WM set A.

Signed-off-by: Sung Lee 
Reviewed-by: Yongqiang Sun 
Reviewed-by: Roman Li 
Acked-by: Eryk Brol 
Signed-off-by: Alex Deucher

drm/amd/display: Prevent bandwidth overflow

2020-12-09T15:06:39+00:00

[Why]
At very high pixel clock, bandwidth calculation exceeds 32 bit size
and overflow value. This causes the resulting selection of link rate
to be inaccurate.

[How]
Change order of operation and use fixed point to deal with integer
accuracy. Also address bug found when forcing link rate.

Signed-off-by: Chris Park 
Reviewed-by: Wenjing Liu 
Acked-by: Eryk Brol 
Signed-off-by: Alex Deucher

drm/amd/display: Init clock value by current vbios CLKs

2020-12-03T03:53:01+00:00

[Why]
While booting into OS, driver updates DPP/DISP CLKs.
But init clock value is zero which is invalid.

[How]
Get current clocks value to update init clocks.
To avoid underflow.

Signed-off-by: Brandon Syu 
Reviewed-by: Tony Cheng 
Acked-by: Aurabindo Pillai 
Signed-off-by: Alex Deucher

drm/amd/display: Add missing pflip irq for dcn2.0

2020-11-16T18:30:16+00:00

If we have more than 4 displays we will run
into dummy irq calls or flip timout issues.

Reviewed-by: Nicholas Kazlauskas 
Signed-off-by: Alex Deucher 
Cc: stable@vger.kernel.org

drm/amd/display: Add missing pflip irq

2020-11-05T22:54:51+00:00

If we have more than 4 displays we will run
into dummy irq calls or flip timout issues.

Signed-off-by: Bhawanpreet Lakha 
Reviewed-by: Charlene Liu 
Acked-by: Qingqing Zhuo 
Signed-off-by: Alex Deucher 
Cc: stable@vger.kernel.org # 5.9.x

drm/amdgpu/display: remove DRM_AMD_DC_GREEN_SARDINE

2020-11-04T13:43:50+00:00

No need for a separate config option at this point.

Reviewed-by: Luben Tuikov 
Signed-off-by: Alex Deucher

drm/amd/display: Add green_sardine support to DC

2020-11-04T13:40:42+00:00

Display Core support for green_sardine

Signed-off-by: Roman Li 
Acked-by: Hersen Wu 
Reviewed-by: Alex Deucher 
Signed-off-by: Alex Deucher

drm/amd/display: Clean up debug macros

2020-10-26T21:19:30+00:00

This patch simplifies the ASSERT*() and BREAK_TO_DEBUGGER() macros:
- Move the dependency check of CONFIG_KGDB into Kconfig
- Unify the kgdb_breakpoint() call
- Drop the non-existing CONFIG_HAVE_KGDB

Also align the behavior of ASSERT() macro in both cases with and
without CONFIG_DEBUG_KERNEL_DC.

Acked-by: Alex Deucher 
Reviewed-by: Nicholas Kazlauskas 
Signed-off-by: Takashi Iwai 
Signed-off-by: Alex Deucher

drm/amd/display: Don't invoke kgdb_breakpoint() unconditionally

2020-10-26T21:19:15+00:00

ASSERT_CRITICAL() invokes kgdb_breakpoint() whenever either
CONFIG_KGDB or CONFIG_HAVE_KGDB is set.  This, however, may lead to a
kernel panic when no kdb stuff is attached, since the
kgdb_breakpoint() call issues INT3.  It's nothing but a surprise for
normal end-users.

For avoiding the pitfall, make the kgdb_breakpoint() call only when
CONFIG_DEBUG_KERNEL_DC is set.

https://bugzilla.opensuse.org/show_bug.cgi?id=1177973
Cc: 
Acked-by: Alex Deucher 
Reviewed-by: Nicholas Kazlauskas 
Signed-off-by: Takashi Iwai 
Signed-off-by: Alex Deucher

drm/amd/display: Fix kernel panic by dal_gpio_open() error

2020-10-26T21:19:02+00:00

Currently both error code paths handled in dal_gpio_open_ex() issues
ASSERT_CRITICAL(), and this leads to a kernel panic unnecessarily if
CONFIG_KGDB is enabled.  Since basically both are non-critical errors
and can be recovered, drop those assert calls and use a safer one,
BREAK_TO_DEBUGGER(), for allowing the debugging, instead.

BugLink: https://bugzilla.opensuse.org/show_bug.cgi?id=1177973
Cc: 
Acked-by: Alex Deucher 
Reviewed-by: Nicholas Kazlauskas 
Signed-off-by: Takashi Iwai 
Signed-off-by: Alex Deucher