1. 10 2月, 2021 1 次提交
  2. 03 11月, 2020 1 次提交
  3. 16 9月, 2020 1 次提交
  4. 27 8月, 2020 1 次提交
  5. 15 8月, 2020 1 次提交
  6. 28 7月, 2020 2 次提交
  7. 16 7月, 2020 1 次提交
  8. 03 7月, 2020 2 次提交
  9. 01 7月, 2020 4 次提交
  10. 02 4月, 2020 1 次提交
    • M
      drm/amdgpu: cleanup all virtualization detection routine · 3aa0115d
      Monk Liu 提交于
      we need to move virt detection much earlier because:
      1) HW team confirms us that RCC_IOV_FUNC_IDENTIFIER will always
      be at DE5 (dw) mmio offset from vega10, this way there is no
      need to implement detect_hw_virt() routine in each nbio/chip file.
      for VI SRIOV chip (tonga & fiji), the BIF_IOV_FUNC_IDENTIFIER is at
      0x1503
      
      2) we need to acknowledged we are SRIOV VF before we do IP discovery because
      the IP discovery content will be updated by host everytime after it recieved
      a new coming "REQ_GPU_INIT_DATA" request from guest (there will be patches
      for this new handshake soon).
      Signed-off-by: NMonk Liu <Monk.Liu@amd.com>
      Reviewed-by: NEmily Deng <Emily.Deng@amd.com>
      Signed-off-by: NAlex Deucher <alexander.deucher@amd.com>
      3aa0115d
  11. 22 11月, 2019 1 次提交
  12. 21 11月, 2019 2 次提交
  13. 20 11月, 2019 1 次提交
  14. 26 10月, 2019 1 次提交
  15. 30 8月, 2019 1 次提交
    • J
      drm/amdgpu/si: fix ASIC tests · 77efe48a
      Jean Delvare 提交于
      Comparing adev->family with CHIP constants is not correct.
      adev->family can only be compared with AMDGPU_FAMILY constants and
      adev->asic_type is the struct member to compare with CHIP constants.
      They are separate identification spaces.
      Signed-off-by: NJean Delvare <jdelvare@suse.de>
      Fixes: 62a37553 ("drm/amdgpu: add si implementation v10")
      Cc: Ken Wang <Qingqing.Wang@amd.com>
      Cc: Alex Deucher <alexander.deucher@amd.com>
      Cc: "Christian König" <christian.koenig@amd.com>
      Cc: "David (ChunMing) Zhou" <David1.Zhou@amd.com>
      Signed-off-by: NAlex Deucher <alexander.deucher@amd.com>
      77efe48a
  16. 31 7月, 2019 1 次提交
  17. 26 6月, 2019 1 次提交
  18. 11 6月, 2019 1 次提交
  19. 25 5月, 2019 1 次提交
  20. 14 2月, 2019 1 次提交
  21. 15 1月, 2019 2 次提交
  22. 11 10月, 2018 1 次提交
  23. 12 4月, 2018 1 次提交
  24. 04 4月, 2018 1 次提交
  25. 15 3月, 2018 1 次提交
  26. 06 3月, 2018 2 次提交
  27. 20 2月, 2018 2 次提交
  28. 18 12月, 2017 2 次提交
  29. 07 12月, 2017 1 次提交
  30. 16 8月, 2017 1 次提交
    • J
      drm/amdgpu: Fix undue fallthroughs in golden registers initialization · 2db93bea
      Jean Delvare 提交于
      As I was staring at the si_init_golden_registers code, I noticed that
      the Pitcairn initialization silently falls through the Cape Verde
      initialization, and the Oland initialization falls through the Hainan
      initialization. However there is no comment stating that this is
      intentional, and the radeon driver doesn't have any such fallthrough,
      so I suspect this is not supposed to happen.
      Signed-off-by: NJean Delvare <jdelvare@suse.de>
      Fixes: 62a37553 ("drm/amdgpu: add si implementation v10")
      Cc: Ken Wang <Qingqing.Wang@amd.com>
      Cc: Alex Deucher <alexander.deucher@amd.com>
      Cc: "Marek Olšák" <maraeo@gmail.com>
      Cc: "Christian König" <christian.koenig@amd.com>
      Cc: Flora Cui <Flora.Cui@amd.com>
      Reviewed-by: NMarek Olšák <marek.olsak@amd.com>
      Signed-off-by: NAlex Deucher <alexander.deucher@amd.com>
      Cc: stable@vger.kernel.org
      2db93bea