1. 25 10月, 2022 1 次提交
    • A
      drm/amdgpu: fix sdma doorbell init ordering on APUs · 6c16afdc
      Alex Deucher 提交于
      Commit 8795e182 ("PCI/portdrv: Don't disable AER reporting in get_port_device_capability()")
      uncovered a bug in amdgpu that required a reordering of the driver
      init sequence to avoid accessing a special register on the GPU
      before it was properly set up leading to an PCI AER error.  This
      reordering uncovered a different hw programming ordering dependency
      in some APUs where the SDMA doorbells need to be programmed before
      the GFX doorbells. To fix this, move the SDMA doorbell programming
      back into the soc15 common code, but use the actual doorbell range
      values directly rather than the values stored in the ring structure
      since those will not be initialized at this point.
      
      This is a partial revert, but with the doorbell assignment
      fixed so the proper doorbell index is set before it's used.
      
      Fixes: e3163bc8 ("drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega")
      Acked-by: NChristian König <christian.koenig@amd.com>
      Signed-off-by: NAlex Deucher <alexander.deucher@amd.com>
      Cc: skhan@linuxfoundation.org
      6c16afdc
  2. 20 10月, 2022 1 次提交
    • A
      drm/amdgpu: fix sdma doorbell init ordering on APUs · 50b0e4d4
      Alex Deucher 提交于
      Commit 8795e182 ("PCI/portdrv: Don't disable AER reporting in get_port_device_capability()")
      uncovered a bug in amdgpu that required a reordering of the driver
      init sequence to avoid accessing a special register on the GPU
      before it was properly set up leading to an PCI AER error.  This
      reordering uncovered a different hw programming ordering dependency
      in some APUs where the SDMA doorbells need to be programmed before
      the GFX doorbells. To fix this, move the SDMA doorbell programming
      back into the soc15 common code, but use the actual doorbell range
      values directly rather than the values stored in the ring structure
      since those will not be initialized at this point.
      
      This is a partial revert, but with the doorbell assignment
      fixed so the proper doorbell index is set before it's used.
      
      Fixes: e3163bc8 ("drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega")
      Acked-by: NChristian König <christian.koenig@amd.com>
      Signed-off-by: NAlex Deucher <alexander.deucher@amd.com>
      Cc: skhan@linuxfoundation.org
      Cc: stable@vger.kernel.org
      50b0e4d4
  3. 15 9月, 2022 4 次提交
    • A
      drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega · e3163bc8
      Alex Deucher 提交于
      This mirrors what we do for other asics and this way we are
      sure the sdma doorbell range is properly initialized.
      
      There is a comment about the way doorbells on gfx9 work that
      requires that they are initialized for other IPs before GFX
      is initialized.  However, the statement says that it applies to
      multimedia as well, but the VCN code currently initializes
      doorbells after GFX and there are no known issues there.  In my
      testing at least I don't see any problems on SDMA.
      
      This is a prerequisite for fixing the Unsupported Request error
      reported through AER during driver load.
      
      Link: https://bugzilla.kernel.org/show_bug.cgi?id=216373
      
      The error was unnoticed before and got visible because of the commit
      referenced below. This doesn't fix anything in the commit below, rather
      fixes the issue in amdgpu exposed by the commit. The reference is only
      to associate this commit with below one so that both go together.
      
      Fixes: 8795e182 ("PCI/portdrv: Don't disable AER reporting in get_port_device_capability()")
      Acked-by: NChristian König <christian.koenig@amd.com>
      Reviewed-by: NLijo Lazar <lijo.lazar@amd.com>
      Signed-off-by: NAlex Deucher <alexander.deucher@amd.com>
      Cc: stable@vger.kernel.org
      e3163bc8
    • A
      drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega · dc1d85cb
      Alex Deucher 提交于
      This mirrors what we do for other asics and this way we are
      sure the ih doorbell range is properly initialized.
      
      There is a comment about the way doorbells on gfx9 work that
      requires that they are initialized for other IPs before GFX
      is initialized.  In this case IH is initialized before GFX,
      so there should be no issue.
      
      This is a prerequisite for fixing the Unsupported Request error
      reported through AER during driver load.
      
      Link: https://bugzilla.kernel.org/show_bug.cgi?id=216373
      
      The error was unnoticed before and got visible because of the commit
      referenced below. This doesn't fix anything in the commit below, rather
      fixes the issue in amdgpu exposed by the commit. The reference is only
      to associate this commit with below one so that both go together.
      
      Fixes: 8795e182 ("PCI/portdrv: Don't disable AER reporting in get_port_device_capability()")
      Acked-by: NChristian König <christian.koenig@amd.com>
      Reviewed-by: NLijo Lazar <lijo.lazar@amd.com>
      Signed-off-by: NAlex Deucher <alexander.deucher@amd.com>
      Cc: stable@vger.kernel.org
      dc1d85cb
    • A
      drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega · 59c43748
      Alex Deucher 提交于
      This mirrors what we do for other asics and this way we are
      sure the sdma doorbell range is properly initialized.
      
      There is a comment about the way doorbells on gfx9 work that
      requires that they are initialized for other IPs before GFX
      is initialized.  However, the statement says that it applies to
      multimedia as well, but the VCN code currently initializes
      doorbells after GFX and there are no known issues there.  In my
      testing at least I don't see any problems on SDMA.
      
      This is a prerequisite for fixing the Unsupported Request error
      reported through AER during driver load.
      
      Link: https://bugzilla.kernel.org/show_bug.cgi?id=216373
      
      The error was unnoticed before and got visible because of the commit
      referenced below. This doesn't fix anything in the commit below, rather
      fixes the issue in amdgpu exposed by the commit. The reference is only
      to associate this commit with below one so that both go together.
      
      Fixes: 8795e182 ("PCI/portdrv: Don't disable AER reporting in get_port_device_capability()")
      Acked-by: NChristian König <christian.koenig@amd.com>
      Reviewed-by: NLijo Lazar <lijo.lazar@amd.com>
      Signed-off-by: NAlex Deucher <alexander.deucher@amd.com>
      59c43748
    • A
      drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega · db101097
      Alex Deucher 提交于
      This mirrors what we do for other asics and this way we are
      sure the ih doorbell range is properly initialized.
      
      There is a comment about the way doorbells on gfx9 work that
      requires that they are initialized for other IPs before GFX
      is initialized.  In this case IH is initialized before GFX,
      so there should be no issue.
      
      This is a prerequisite for fixing the Unsupported Request error
      reported through AER during driver load.
      
      Link: https://bugzilla.kernel.org/show_bug.cgi?id=216373
      
      The error was unnoticed before and got visible because of the commit
      referenced below. This doesn't fix anything in the commit below, rather
      fixes the issue in amdgpu exposed by the commit. The reference is only
      to associate this commit with below one so that both go together.
      
      Fixes: 8795e182 ("PCI/portdrv: Don't disable AER reporting in get_port_device_capability()")
      Acked-by: NChristian König <christian.koenig@amd.com>
      Reviewed-by: NLijo Lazar <lijo.lazar@amd.com>
      Signed-off-by: NAlex Deucher <alexander.deucher@amd.com>
      db101097
  4. 29 4月, 2022 1 次提交
  5. 09 4月, 2022 1 次提交
  6. 16 3月, 2022 1 次提交
  7. 03 3月, 2022 3 次提交
  8. 24 2月, 2022 1 次提交
  9. 22 2月, 2022 1 次提交
  10. 19 2月, 2022 1 次提交
  11. 18 2月, 2022 3 次提交
  12. 17 2月, 2022 1 次提交
  13. 26 1月, 2022 1 次提交
  14. 15 1月, 2022 1 次提交
  15. 15 12月, 2021 1 次提交
  16. 14 12月, 2021 1 次提交
  17. 25 11月, 2021 1 次提交
  18. 23 11月, 2021 1 次提交
  19. 20 10月, 2021 1 次提交
  20. 05 10月, 2021 4 次提交
  21. 24 9月, 2021 1 次提交
  22. 27 8月, 2021 1 次提交
  23. 06 8月, 2021 1 次提交
  24. 23 7月, 2021 1 次提交
  25. 17 7月, 2021 2 次提交
  26. 01 7月, 2021 1 次提交
  27. 21 5月, 2021 1 次提交
  28. 20 5月, 2021 2 次提交