1. 20 5月, 2021 1 次提交
  2. 16 12月, 2020 1 次提交
  3. 10 12月, 2020 1 次提交
    • N
      drm/amdgpu: clean up bo in vce and vcn test · e18d9a2b
      Nirmoy Das 提交于
      BO created with amdgpu_bo_create_reserved() wasn't clean
      properly before, which causes:
      
      [   21.056218] WARNING: CPU: 0 PID: 7 at drivers/gpu/drm/ttm/ttm_bo.c:518 ttm_bo_release+0x2bf/0x310 [ttm]
      <snip>
      [   21.056430] Call Trace:
      [   21.056525]  amdgpu_bo_unref+0x1a/0x30 [amdgpu]
      [   21.056635]  amdgpu_vcn_dec_send_msg+0x1b2/0x270 [amdgpu]
      [   21.056740]  amdgpu_vcn_dec_get_create_msg.constprop.0+0xd8/0x100 [amdgpu]
      [   21.056843]  amdgpu_vcn_dec_ring_test_ib+0x27/0x180 [amdgpu]
      [   21.056936]  amdgpu_ib_ring_tests+0xf1/0x150 [amdgpu]
      [   21.057024]  amdgpu_device_delayed_init_work_handler+0x11/0x30 [amdgpu]
      [   21.057030]  process_one_work+0x1df/0x370
      [   21.057033]  worker_thread+0x46/0x340
      [   21.057034]  ? process_one_work+0x370/0x370
      [   21.057037]  kthread+0x11b/0x140
      [   21.057039]  ? __kthread_bind_mask+0x60/0x60
      [   21.057043]  ret_from_fork+0x22/0x30
      Signed-off-by: NNirmoy Das <nirmoy.das@amd.com>
      Reviewed-by: NChristian König <christian.koenig@amd.com>
      Link: https://patchwork.freedesktop.org/patch/406382/Signed-off-by: NChristian König <christian.koenig@amd.com>
      e18d9a2b
  4. 02 12月, 2020 1 次提交
    • L
      drm/amd/amdgpu/amdgpu_vce: Provide some missing and repair other function params · 184b762d
      Lee Jones 提交于
      Fixes the following W=1 kernel build warning(s):
      
       drivers/gpu/drm/amd/amdgpu/amdgpu_vce.c:97: warning: Function parameter or member 'size' not described in 'amdgpu_vce_sw_init'
       drivers/gpu/drm/amd/amdgpu/amdgpu_vce.c:441: warning: Function parameter or member 'bo' not described in 'amdgpu_vce_get_create_msg'
       drivers/gpu/drm/amd/amdgpu/amdgpu_vce.c:441: warning: Excess function parameter 'adev' description in 'amdgpu_vce_get_create_msg'
       drivers/gpu/drm/amd/amdgpu/amdgpu_vce.c:521: warning: Function parameter or member 'direct' not described in 'amdgpu_vce_get_destroy_msg'
       drivers/gpu/drm/amd/amdgpu/amdgpu_vce.c:521: warning: Excess function parameter 'adev' description in 'amdgpu_vce_get_destroy_msg'
       drivers/gpu/drm/amd/amdgpu/amdgpu_vce.c:588: warning: Function parameter or member 'ib_idx' not described in 'amdgpu_vce_validate_bo'
       drivers/gpu/drm/amd/amdgpu/amdgpu_vce.c:636: warning: Function parameter or member 'ib_idx' not described in 'amdgpu_vce_cs_reloc'
       drivers/gpu/drm/amd/amdgpu/amdgpu_vce.c:636: warning: Function parameter or member 'index' not described in 'amdgpu_vce_cs_reloc'
       drivers/gpu/drm/amd/amdgpu/amdgpu_vce.c:720: warning: Function parameter or member 'ib_idx' not described in 'amdgpu_vce_ring_parse_cs'
       drivers/gpu/drm/amd/amdgpu/amdgpu_vce.c:956: warning: Function parameter or member 'ib_idx' not described in 'amdgpu_vce_ring_parse_cs_vm'
       drivers/gpu/drm/amd/amdgpu/amdgpu_vce.c:1050: warning: Function parameter or member 'job' not described in 'amdgpu_vce_ring_emit_ib'
       drivers/gpu/drm/amd/amdgpu/amdgpu_vce.c:1050: warning: Function parameter or member 'flags' not described in 'amdgpu_vce_ring_emit_ib'
       drivers/gpu/drm/amd/amdgpu/amdgpu_vce.c:1066: warning: Function parameter or member 'addr' not described in 'amdgpu_vce_ring_emit_fence'
       drivers/gpu/drm/amd/amdgpu/amdgpu_vce.c:1066: warning: Function parameter or member 'seq' not described in 'amdgpu_vce_ring_emit_fence'
       drivers/gpu/drm/amd/amdgpu/amdgpu_vce.c:1066: warning: Function parameter or member 'flags' not described in 'amdgpu_vce_ring_emit_fence'
       drivers/gpu/drm/amd/amdgpu/amdgpu_vce.c:1066: warning: Excess function parameter 'fence' description in 'amdgpu_vce_ring_emit_fence'
       drivers/gpu/drm/amd/amdgpu/amdgpu_vce.c:1122: warning: Function parameter or member 'timeout' not described in 'amdgpu_vce_ring_test_ib'
      
      Cc: Alex Deucher <alexander.deucher@amd.com>
      Cc: "Christian König" <christian.koenig@amd.com>
      Cc: David Airlie <airlied@linux.ie>
      Cc: Daniel Vetter <daniel@ffwll.ch>
      Cc: Sumit Semwal <sumit.semwal@linaro.org>
      Cc: amd-gfx@lists.freedesktop.org
      Cc: dri-devel@lists.freedesktop.org
      Cc: linux-media@vger.kernel.org
      Cc: linaro-mm-sig@lists.linaro.org
      Signed-off-by: NLee Jones <lee.jones@linaro.org>
      Signed-off-by: NAlex Deucher <alexander.deucher@amd.com>
      184b762d
  5. 29 4月, 2020 1 次提交
  6. 02 4月, 2020 1 次提交
  7. 28 1月, 2020 1 次提交
  8. 19 12月, 2019 1 次提交
  9. 12 11月, 2019 1 次提交
  10. 26 10月, 2019 2 次提交
  11. 18 10月, 2019 1 次提交
  12. 12 6月, 2019 1 次提交
    • L
      drm/amdgpu: fix ring test failure issue during s3 in vce 3.0 (V2) · 91c9c23e
      Louis Li 提交于
      [What]
      vce ring test fails consistently during resume in s3 cycle, due to
      mismatch read & write pointers.
      On debug/analysis its found that rptr to be compared is not being
      correctly updated/read, which leads to this failure.
      Below is the failure signature:
      	[drm:amdgpu_vce_ring_test_ring] *ERROR* amdgpu: ring 12 test failed
      	[drm:amdgpu_device_ip_resume_phase2] *ERROR* resume of IP block <vce_v3_0> failed -110
      	[drm:amdgpu_device_resume] *ERROR* amdgpu_device_ip_resume failed (-110).
      
      [How]
      fetch rptr appropriately, meaning move its read location further down
      in the code flow.
      With this patch applied the s3 failure is no more seen for >5k s3 cycles,
      which otherwise is pretty consistent.
      
      V2: remove reduntant fetch of rptr
      Signed-off-by: NLouis Li <Ching-shih.Li@amd.com>
      Reviewed-by: NChristian König <christian.koenig@amd.com>
      Signed-off-by: NAlex Deucher <alexander.deucher@amd.com>
      91c9c23e
  13. 11 6月, 2019 2 次提交
  14. 06 6月, 2019 1 次提交
    • L
      drm/amdgpu: fix ring test failure issue during s3 in vce 3.0 (V2) · ce0e22f5
      Louis Li 提交于
      [What]
      vce ring test fails consistently during resume in s3 cycle, due to
      mismatch read & write pointers.
      On debug/analysis its found that rptr to be compared is not being
      correctly updated/read, which leads to this failure.
      Below is the failure signature:
      	[drm:amdgpu_vce_ring_test_ring] *ERROR* amdgpu: ring 12 test failed
      	[drm:amdgpu_device_ip_resume_phase2] *ERROR* resume of IP block <vce_v3_0> failed -110
      	[drm:amdgpu_device_resume] *ERROR* amdgpu_device_ip_resume failed (-110).
      
      [How]
      fetch rptr appropriately, meaning move its read location further down
      in the code flow.
      With this patch applied the s3 failure is no more seen for >5k s3 cycles,
      which otherwise is pretty consistent.
      
      V2: remove reduntant fetch of rptr
      Signed-off-by: NLouis Li <Ching-shih.Li@amd.com>
      Reviewed-by: NChristian König <christian.koenig@amd.com>
      Signed-off-by: NAlex Deucher <alexander.deucher@amd.com>
      Cc: stable@vger.kernel.org
      ce0e22f5
  15. 26 1月, 2019 1 次提交
  16. 06 11月, 2018 3 次提交
  17. 27 9月, 2018 1 次提交
  18. 14 8月, 2018 1 次提交
  19. 26 7月, 2018 1 次提交
  20. 17 7月, 2018 2 次提交
  21. 14 7月, 2018 1 次提交
  22. 06 7月, 2018 2 次提交
  23. 17 5月, 2018 1 次提交
  24. 16 5月, 2018 2 次提交
  25. 12 4月, 2018 1 次提交
  26. 22 3月, 2018 1 次提交
  27. 01 3月, 2018 1 次提交
  28. 17 1月, 2018 1 次提交
  29. 28 12月, 2017 1 次提交
  30. 18 12月, 2017 1 次提交
  31. 08 12月, 2017 1 次提交
  32. 07 12月, 2017 2 次提交