1. 03 3月, 2022 1 次提交
  2. 18 2月, 2022 1 次提交
  3. 15 1月, 2022 2 次提交
  4. 02 9月, 2021 1 次提交
  5. 10 4月, 2021 1 次提交
  6. 24 3月, 2021 3 次提交
  7. 10 2月, 2021 1 次提交
  8. 14 11月, 2020 1 次提交
  9. 13 11月, 2020 1 次提交
  10. 17 10月, 2020 1 次提交
  11. 16 10月, 2020 1 次提交
  12. 23 9月, 2020 1 次提交
    • S
      drm/amdgpu: update athub interrupt harvesting handle · 3f975d0f
      Stanley.Yang 提交于
      GCEA/MMHUB EA error should not result to DF freeze, this is
      fixed in next generation, but for some reasons the GCEA/MMHUB
      EA error will result to DF freeze in previous generation,
      diver should avoid to indicate GCEA/MMHUB EA error as hw fatal
      error in kernel message by read GCEA/MMHUB err status registers.
      
      Changed from V1:
          make query_ras_error_status function more general
          make read mmhub er status register more friendly
      
      Changed from V2:
          move ras error status query function into do_recovery workqueue
      
      Changed from V3:
          remove useless code from V2, print GCEA error status
          instance number
      Signed-off-by: NStanley.Yang <Stanley.Yang@amd.com>
      Reviewed-by: NHawking Zhang <Hawking.Zhang@amd.com>
      Signed-off-by: NAlex Deucher <alexander.deucher@amd.com>
      3f975d0f
  13. 15 8月, 2020 1 次提交
  14. 22 7月, 2020 1 次提交
  15. 04 6月, 2020 1 次提交
  16. 02 5月, 2020 1 次提交
  17. 24 4月, 2020 1 次提交
    • Y
      drm/amdgpu: request reg_val_offs each kiq read reg · 54208194
      Yintian Tao 提交于
      According to the current kiq read register method,
      there will be race condition when using KIQ to read
      register if multiple clients want to read at same time
      just like the expample below:
      1. client-A start to read REG-0 throguh KIQ
      2. client-A poll the seqno-0
      3. client-B start to read REG-1 through KIQ
      4. client-B poll the seqno-1
      5. the kiq complete these two read operation
      6. client-A to read the register at the wb buffer and
         get REG-1 value
      
      Therefore, use amdgpu_device_wb_get() to request reg_val_offs
      for each kiq read register.
      
      v2: fix the error remove
      v3: fix the print typo
      v4: remove unused variables
      Signed-off-by: NYintian Tao <yttao@amd.com>
      Reviewed-by: NChristian König <christian.koenig@amd.com>
      Signed-off-by: NAlex Deucher <alexander.deucher@amd.com>
      54208194
  18. 09 4月, 2020 1 次提交
    • N
      drm/amdgpu: rework sched_list generation · 1c6d567b
      Nirmoy Das 提交于
      Generate HW IP's sched_list in amdgpu_ring_init() instead of
      amdgpu_ctx.c. This makes amdgpu_ctx_init_compute_sched(),
      ring.has_high_prio and amdgpu_ctx_init_sched() unnecessary.
      This patch also stores sched_list for all HW IPs in one big
      array in struct amdgpu_device which makes amdgpu_ctx_init_entity()
      much more leaner.
      
      v2:
      fix a coding style issue
      do not use drm hw_ip const to populate amdgpu_ring_type enum
      
      v3:
      remove ctx reference and move sched array and num_sched to a struct
      use num_scheds to detect uninitialized scheduler list
      
      v4:
      use array_index_nospec for user space controlled variables
      fix possible checkpatch.pl warnings
      Signed-off-by: NNirmoy Das <nirmoy.das@amd.com>
      Reviewed-by: NChristian König <christian.koenig@amd.com>
      Signed-off-by: NAlex Deucher <alexander.deucher@amd.com>
      1c6d567b
  19. 10 3月, 2020 1 次提交
  20. 05 3月, 2020 1 次提交
  21. 29 2月, 2020 1 次提交
  22. 23 1月, 2020 1 次提交
  23. 17 1月, 2020 1 次提交
  24. 19 12月, 2019 1 次提交
  25. 23 11月, 2019 1 次提交
  26. 19 11月, 2019 1 次提交
  27. 07 11月, 2019 2 次提交
    • C
      drm/amdgpu: add dummy read by engines for some GCVM status registers in gfx10 · 589b64a7
      changzhu 提交于
      The GRBM register interface is now capable of bursting 1 cycle per
      register wr->wr, wr->rd much faster than previous muticycle per
      transaction done interface.  This has caused a problem where
      status registers requiring HW to update have a 1 cycle delay, due
      to the register update having to go through GRBM.
      
      For cp ucode, it has realized dummy read in cp firmware.It covers
      the use of WAIT_REG_MEM operation 1 case only.So it needs to call
      gfx_v10_0_wait_reg_mem in gfx10. Besides it also needs to add warning to
      update firmware in case firmware is too old to have function to realize
      dummy read in cp firmware.
      
      For sdma ucode, it hasn't realized dummy read in sdma firmware. sdma is
      moved to gfxhub in gfx10. So it needs to add dummy read in driver
      between amdgpu_ring_emit_wreg and amdgpu_ring_emit_reg_wait for sdma_v5_0.
      Signed-off-by: Nchangzhu <Changfeng.Zhu@amd.com>
      Reviewed-by: NChristian König <christian.koenig@amd.com>
      Signed-off-by: NAlex Deucher <alexander.deucher@amd.com>
      589b64a7
    • C
      drm/amdgpu: add dummy read by engines for some GCVM status registers in gfx10 · a6522a5c
      changzhu 提交于
      The GRBM register interface is now capable of bursting 1 cycle per
      register wr->wr, wr->rd much faster than previous muticycle per
      transaction done interface.  This has caused a problem where
      status registers requiring HW to update have a 1 cycle delay, due
      to the register update having to go through GRBM.
      
      For cp ucode, it has realized dummy read in cp firmware.It covers
      the use of WAIT_REG_MEM operation 1 case only.So it needs to call
      gfx_v10_0_wait_reg_mem in gfx10. Besides it also needs to add warning to
      update firmware in case firmware is too old to have function to realize
      dummy read in cp firmware.
      
      For sdma ucode, it hasn't realized dummy read in sdma firmware. sdma is
      moved to gfxhub in gfx10. So it needs to add dummy read in driver
      between amdgpu_ring_emit_wreg and amdgpu_ring_emit_reg_wait for sdma_v5_0.
      Signed-off-by: Nchangzhu <Changfeng.Zhu@amd.com>
      Reviewed-by: NChristian König <christian.koenig@amd.com>
      Signed-off-by: NAlex Deucher <alexander.deucher@amd.com>
      a6522a5c
  28. 26 10月, 2019 1 次提交
  29. 03 10月, 2019 6 次提交
  30. 14 9月, 2019 1 次提交
  31. 01 8月, 2019 1 次提交