Am 03.01.20 um 11:43 schrieb Nirmoy:
On 1/2/20 7:13 PM, Christian König wrote:
Am 02.01.20 um 10:47 schrieb Nirmoy:
On 1/1/20 1:52 PM, Christian König wrote:
Am 19.12.19 um 13:01 schrieb Nirmoy:
Reviewed-by: Nirmoy Das
On 12/19/19 12:42 PM, Le Ma wrote:
This workaround does not affect oth
Hi Alejandro,
yes I've implemented this, but I'm still hunting down some bugs with the
new locks.
I will send out the patches on Monday even if I can't narrow that
problem down further.
Regards,
Christian.
Am 03.01.20 um 05:20 schrieb Sierra Guiza, Alejandro (Alex):
[AMD Official Use Only
This allocation isn't required and can fail when resuming from suspend.
Bug: https://gitlab.freedesktop.org/drm/amd/issues/1009
Signed-off-by: Dor Askayo
---
drivers/gpu/drm/amd/display/dc/core/dc.c | 17 +
1 file changed, 9 insertions(+), 8 deletions(-)
diff --git a/drivers/gpu
On Fri, Jan 3, 2020 at 4:48 AM Evan Quan wrote:
>
> With "dpm=0", there will be no DPM enabled. The code
> needs to be refined to support this.
>
> Change-Id: Ief1561e69a24472135e0499073a27ea5fd8174e2
> Signed-off-by: Evan Quan
Reviewed-by: Alex Deucher
> ---
> drivers/gpu/drm/amd/powerplay/a
On Wed, Jan 1, 2020 at 9:40 PM Evan Quan wrote:
>
> By this, we can avoid to pass in the VRAM address on every table
> transferring. That puts extra unnecessary traffics on SMU on
> some cases(e.g. polling the amdgpu_pm_info sysfs interface).
>
> V2: document what the driver table is for and how i
Hi there,
As you may remember, I was working on porting VCE 1.0 to amdgpu around
the time Piotr Redlewski sent the UVD patches. I would prefer to go the
way proposed by Alex Deucher than to see SI support being dropped. I've
been using the amdgpu on a 280X ever since it was possible. While th
[AMD Official Use Only - Internal Distribution Only]
From: amd-gfx on behalf of Evan Quan
Sent: Thursday, January 2, 2020 10:39 AM
To: amd-gfx@lists.freedesktop.org
Cc: Deucher, Alexander ; Quan, Evan
Subject: [PATCH] drm/amd/powerplay: unified VRAM address
