1. 23 6月, 2021 1 次提交
  2. 01 2月, 2021 2 次提交
  3. 08 1月, 2021 1 次提交
  4. 05 11月, 2020 1 次提交
  5. 13 9月, 2020 2 次提交
  6. 23 8月, 2020 1 次提交
  7. 31 7月, 2020 2 次提交
  8. 19 5月, 2020 2 次提交
  9. 03 1月, 2020 1 次提交
  10. 05 11月, 2019 1 次提交
    • A
      drm/msm/adreno: Add support for Adreno 510 GPU · e20c9284
      AngeloGioacchino Del Regno 提交于
      The Adreno 510 GPU is a stripped version of the Adreno 5xx,
      found in low-end SoCs like 8x56 and 8x76, which has 256K of
      GMEM, with no GPMU nor ZAP.
      Also, since the Adreno 5xx part of this driver seems to be
      developed with high-end Adreno GPUs in mind, and since this
      is a lower end one, add a comment making clear which GPUs
      which support is not implemented yet is not using the GPMU
      related hw init code, so that future developers will not go
      crazy with that.
      
      By the way, the lower end Adreno GPUs with no GPMU are:
      A505/A506/A510 (usually no ZAP firmware)
      A508/A509/A512 (usually with ZAP firmware)
      Signed-off-by: NAngeloGioacchino Del Regno <kholk11@gmail.com>
      Signed-off-by: NRob Clark <robdclark@chromium.org>
      e20c9284
  11. 04 9月, 2019 1 次提交
  12. 19 6月, 2019 3 次提交
  13. 21 4月, 2019 1 次提交
    • J
      drm/msm/a6xx: Add zap shader load · abccb9fe
      Jordan Crouse 提交于
      The a6xx GPU powers on in secure mode which restricts what memory it can
      write to. To get out of secure mode the GPU driver can write to
      REG_A6XX_RBBM_SECVID_TRUST_CNTL but on targets that are "secure" that
      register region is blocked and writes will cause the system to go down.
      
      For those targets we need to execute a special sequence that involves
      loadinga special shader that clears the GPU registers and use a PM4
      sequence to pull the GPU out of secure. Add support for loading the zap
      shader and executing the secure sequence. For targets that do not support
      SCM or the specific SCM sequence this should fail and we would fall back
      to writing the register.
      Signed-off-by: NJordan Crouse <jcrouse@codeaurora.org>
      Signed-off-by: NRob Clark <robdclark@chromium.org>
      abccb9fe
  14. 20 4月, 2019 1 次提交
  15. 12 12月, 2018 4 次提交
  16. 04 10月, 2018 1 次提交
  17. 11 8月, 2018 2 次提交
  18. 25 7月, 2018 2 次提交
  19. 04 5月, 2018 1 次提交
  20. 19 3月, 2018 1 次提交
    • A
      drm/msm: fix building without debugfs · 288e5c88
      Arnd Bergmann 提交于
      The adreno driver stopped building when CONFIG_DEBUGFS is disabled:
      
      drivers/gpu/drm/msm/adreno/adreno_device.c: In function 'adreno_load_gpu':
      drivers/gpu/drm/msm/adreno/adreno_device.c:153:16: error: 'const struct msm_gpu_funcs' has no member named 'debugfs_init'
        if (gpu->funcs->debugfs_init) {
                      ^~
      drivers/gpu/drm/msm/adreno/adreno_device.c:154:13: error: 'const struct msm_gpu_funcs' has no member named 'debugfs_init'
         gpu->funcs->debugfs_init(gpu, dev->primary);
                   ^~
      
      This adds an #ifdef around the code that references the hidden
      pointer.
      
      Fixes: 331dc0bc ("drm/msm: add a5xx specific debugfs")
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Signed-off-by: NRob Clark <robdclark@gmail.com>
      288e5c88
  21. 20 2月, 2018 3 次提交
  22. 10 1月, 2018 4 次提交
  23. 03 1月, 2018 1 次提交
  24. 14 12月, 2017 1 次提交