On Tue, Feb 16, 2021 at 02:52:55PM -0500, Alex Deucher wrote:
> On Tue, Feb 16, 2021 at 2:35 PM Dan Carpenter
> wrote:
> >
> > If the kmemdup() fails then this should return a negative error code
> > but it currently returns success.
> >
> > Fixes: b4a7db71ea06 ("drm/amdgpu: add per device user f
Hi,
Is this commit a direct revert from
be7af780ef3cbb8fe1004db48dc66caf2da595cd ?
If so, I recommend you to use the standard way to identify "revert"
commits by using 'Revert "Commit header"' and the message "This reverts
commit HASH" followed by the original commit description.
Thanks
Siqueira
On 2021-02-17 8:40 a.m., Rodrigo Siqueira wrote:
Hi,
Is this commit a direct revert from
be7af780ef3cbb8fe1004db48dc66caf2da595cd ?
If so, I recommend you to use the standard way to identify "revert"
commits by using 'Revert "Commit header"' and the message "This reverts
commit HASH" followe
This reverts commit be7af780ef3cbb8fe1004db48dc66caf2da595cd because the
new proposed sequence for HUBP blanking causes regressions. This change
brings back the old sequence.
Signed-off-by: Aurabindo Pillai
Signed-off-by: Bhawanpreet Lakha
---
.../amd/display/dc/dcn10/dcn10_hw_sequencer.c | 36
Hi All,
Fedora has a (opt-in) system to automatically collect backtraces from software
crashing on users systems.
This includes collecting kernel backtraces (including once triggered by
WARN macros) while looking a the top 10 of the most reported backtrace during
the
last 2 weeks report from ABR
On 02/17, Aurabindo Pillai wrote:
>
>
> On 2021-02-17 8:40 a.m., Rodrigo Siqueira wrote:
> > Hi,
> >
> > Is this commit a direct revert from
> > be7af780ef3cbb8fe1004db48dc66caf2da595cd ?
> >
> > If so, I recommend you to use the standard way to identify "revert"
> > commits by using 'Revert "C
On 2021-02-17 10:29 a.m., Rodrigo Siqueira wrote:
On 02/17, Aurabindo Pillai wrote:
On 2021-02-17 8:40 a.m., Rodrigo Siqueira wrote:
Hi,
Is this commit a direct revert from
be7af780ef3cbb8fe1004db48dc66caf2da595cd ?
If so, I recommend you to use the standard way to identify "revert"
comm
Ping
Andrey
On 2/16/21 12:07 PM, Andrey Grodzovsky wrote:
Problem: If scheduler is already stopped by the time sched_entity
is released and entity's job_queue not empty I encountred
a hang in drm_sched_entity_flush. This is because drm_sched_entity_is_idle
never becomes false.
Fix: In drm_sche
On 2021-02-16 12:28 p.m., Alex Deucher wrote:
Commit 098214999c8f added fetching of the AUX_DPHY register
values from the vbios, but it also changed the default values
in the case when there are no values in the vbios. This causes
problems with displays with high refresh rates. To fix this,
swi
On Wed, 17 Feb 2021, Petr Mladek wrote:
> On Mon 2021-02-15 16:39:26, Andy Shevchenko wrote:
>> +Cc: Sakari and printk people
>>
>> On Mon, Feb 15, 2021 at 4:28 PM Christian König
>> wrote:
>> > Am 15.02.21 um 15:21 schrieb Andy Shevchenko:
>> > > We have already few similar implementation and a
On Mon 2021-02-15 16:39:26, Andy Shevchenko wrote:
> +Cc: Sakari and printk people
>
> On Mon, Feb 15, 2021 at 4:28 PM Christian König
> wrote:
> > Am 15.02.21 um 15:21 schrieb Andy Shevchenko:
> > > We have already few similar implementation and a lot of code that can
> > > benefit
> > > of the
Separate the drm_mm_node walking from the actual handling.
Signed-off-by: Christian König
---
drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c | 65 ++---
1 file changed, 15 insertions(+), 50 deletions(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c
b/drivers/gpu/drm/amd/amd
Separate the drm_mm_node walking from the actual handling.
Signed-off-by: Christian König
---
drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c | 8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c
b/drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c
ind
Separate the drm_mm_node walking from the actual handling.
Signed-off-by: Christian König
---
drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 55 +-
1 file changed, 18 insertions(+), 37 deletions(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
b/drivers/gpu/drm/amd/amdg
Separate the drm_mm_node walking from the actual handling.
Signed-off-by: Christian König
---
drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c | 14 --
1 file changed, 8 insertions(+), 6 deletions(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c
b/drivers/gpu/drm/amd/amdgpu/amdgpu_tt
Allows to walk over the drm_mm nodes in a TTM resource object.
Signed-off-by: Christian König
---
.../gpu/drm/amd/amdgpu/amdgpu_res_cursor.h| 105 ++
1 file changed, 105 insertions(+)
create mode 100644 drivers/gpu/drm/amd/amdgpu/amdgpu_res_cursor.h
diff --git a/drivers/gpu
Separate the drm_mm_node walking from the actual handling.
Signed-off-by: Christian König
---
drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c | 83 +++--
1 file changed, 24 insertions(+), 59 deletions(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c
b/drivers/gpu/drm/amd/amd
Separate the drm_mm_node walking from the actual handling.
Signed-off-by: Christian König
---
drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c | 67 +++--
1 file changed, 18 insertions(+), 49 deletions(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c
b/drivers/gpu/drm/amd/amd
Separate the drm_mm_node walking from the actual handling.
Signed-off-by: Christian König
---
drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c
b/drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c
Fixes the rlc reference clock used for GPU timestamps.
Hardcode for now. The proper fix would be to look up
the values from the proper vbios table. This will be
in a follow up patch.
Bug: https://gitlab.freedesktop.org/drm/amd/-/issues/1480
Signed-off-by: Alex Deucher
---
drivers/gpu/drm/amd/a
[AMD Official Use Only - Internal Distribution Only]
Very nice cleaning! Series is Acked-by: Oak Zeng
Regards,
Oak
> -Original Message-
> From: amd-gfx On Behalf Of
> Christian König
> Sent: Wednesday, February 17, 2021 2:00 PM
> To: Errabolu, Ramesh ; amd-
> g...@lists.freedesktop.org
Am 16.02.21 um 18:07 schrieb Andrey Grodzovsky:
Problem: If scheduler is already stopped by the time sched_entity
is released and entity's job_queue not empty I encountred
a hang in drm_sched_entity_flush. This is because drm_sched_entity_is_idle
never becomes false.
Fix: In drm_sched_fini detac
On 2/17/21 4:32 PM, Christian König wrote:
Am 16.02.21 um 18:07 schrieb Andrey Grodzovsky:
Problem: If scheduler is already stopped by the time sched_entity
is released and entity's job_queue not empty I encountred
a hang in drm_sched_entity_flush. This is because drm_sched_entity_is_idle
never
Am 17.02.21 um 22:36 schrieb Andrey Grodzovsky:
On 2/17/21 4:32 PM, Christian König wrote:
Am 16.02.21 um 18:07 schrieb Andrey Grodzovsky:
Problem: If scheduler is already stopped by the time sched_entity
is released and entity's job_queue not empty I encountred
a hang in drm_sched_entity_fl
Will do.
Andrey
On 2/17/21 4:37 PM, Christian König wrote:
Am 17.02.21 um 22:36 schrieb Andrey Grodzovsky:
On 2/17/21 4:32 PM, Christian König wrote:
Am 16.02.21 um 18:07 schrieb Andrey Grodzovsky:
Problem: If scheduler is already stopped by the time sched_entity
is released and entity's
Problem: If scheduler is already stopped by the time sched_entity
is released and entity's job_queue not empty I encountred
a hang in drm_sched_entity_flush. This is because drm_sched_entity_is_idle
never becomes false.
Fix: In drm_sched_fini detach all sched_entities from the
scheduler's run queu
Fixes the rlc reference clock used for GPU timestamps.
Value is 100Mhz. Confirmed with hardware team.
v2: reword commit message.
Bug: https://gitlab.freedesktop.org/drm/amd/-/issues/1480
Signed-off-by: Alex Deucher
---
drivers/gpu/drm/amd/amdgpu/soc15.c | 2 ++
1 file changed, 2 insertions(+)
From: Mario Kleiner
Spatial dithering to 10 bpc depth was disabled for all DCE's.
Testing on DCE-8.3 and DCE-11.2 did not show any obvious ill
effects, but a measureable precision improvement (via colorimeter)
when displaying a fp16 framebuffer to a 10 bpc DP or HDMI connected
HDR-10 monitor.
v
28 matches
Mail list logo
