An error occurred fetching the project authors.
  1. 07 Feb, 2022 2 commits
  2. 09 Dec, 2021 2 commits
  3. 03 Dec, 2021 2 commits
  4. 02 Dec, 2021 2 commits
  5. 01 Dec, 2021 1 commit
    • Tvrtko Ursulin's avatar
      drm/i915: Use per device iommu check · cca08469
      Tvrtko Ursulin authored
      With both integrated and discrete Intel GPUs in a system, the current
      global check of intel_iommu_gfx_mapped, as done from intel_vtd_active()
      may not be completely accurate.
      
      In this patch we add i915 parameter to intel_vtd_active() in order to
      prepare it for multiple GPUs and we also change the check away from Intel
      specific intel_iommu_gfx_mapped (global exported by the Intel IOMMU
      driver) to probing the presence of IOMMU on a specific device using
      device_iommu_mapped().
      
      This will return true both for IOMMU pass-through and address translation
      modes which matches the current behaviour. If in the future we wanted to
      distinguish between these two modes we could either use
      iommu_get_domain_for_dev() and check for __IOMMU_DOMAIN_PAGING bit
      indicating address translation, or ask for a new API to be exported from
      the IOMMU core code.
      
      v2:
        * Check for dmar translation specifically, not just iommu domain. (Baolu)
      
      v3:
       * Go back to plain "any domain" check for now, rewrite commit message.
      
      v4:
       * Use device_iommu_mapped. (Robin, Baolu)
      Signed-off-by: default avatarTvrtko Ursulin <tvrtko.ursulin@intel.com>
      Cc: Lu Baolu <baolu.lu@linux.intel.com>
      Cc: Lucas De Marchi <lucas.demarchi@intel.com>
      Cc: Robin Murphy <robin.murphy@arm.com>
      Acked-by: default avatarRobin Murphy <robin.murphy@arm.com>
      Reviewed-by: default avatarLu Baolu <baolu.lu@linux.intel.com>
      Reviewed-by: default avatarLucas De Marchi <lucas.demarchi@intel.com>
      Link: https://patchwork.freedesktop.org/patch/msgid/20211126141424.493753-1-tvrtko.ursulin@linux.intel.com
      cca08469
  6. 24 Nov, 2021 1 commit
  7. 23 Nov, 2021 1 commit
  8. 19 Nov, 2021 1 commit
  9. 11 Nov, 2021 4 commits
  10. 02 Nov, 2021 1 commit
  11. 01 Nov, 2021 1 commit
  12. 21 Oct, 2021 1 commit
  13. 18 Oct, 2021 1 commit
  14. 14 Oct, 2021 2 commits
  15. 05 Oct, 2021 1 commit
  16. 04 Oct, 2021 2 commits
  17. 29 Sep, 2021 7 commits
  18. 23 Sep, 2021 1 commit
  19. 22 Sep, 2021 3 commits
  20. 25 Aug, 2021 1 commit
  21. 30 Jul, 2021 1 commit
  22. 22 Jul, 2021 1 commit
  23. 21 Jul, 2021 1 commit
    • Matt Roper's avatar
      drm/i915: Make display workaround upper bounds exclusive · 46b0d709
      Matt Roper authored
      Workarounds are documented in the bspec with an exclusive upper bound
      (i.e., a "fixed" stepping that no longer needs the workaround).  This
      makes our driver's use of an inclusive upper bound for stepping ranges
      confusing; the differing notation between code and bspec makes it very
      easy for mistakes to creep in.
      
      Let's switch the upper bound of our IS_{GT,DISP}_STEP macros over to use
      an exclusive upper bound like the bspec does.  This also has the benefit
      of helping make sure workarounds are properly handled for new minor
      steppings that show up (e.g., an A1 between the A0 and B0 we already
      knew about) --- if the new intermediate stepping pulls in hardware fixes
      early, there will be an update to the workaround definition which lets
      us know we need to change our code.  If the new stepping does not pull a
      hardware fix earlier, then the new stepping will already be captured
      properly by the "[begin, fix)" range in the code.
      
      We'll probably need to be extra vigilant in code review of new
      workarounds for the near future to make sure developers notice the new
      semantics of workaround bounds.  But we just migrated a bunch of our
      platforms from the IS_REVID bounds over to IS_{GT,DISP}_STEP, so people
      are already adjusting to the new macros and now is a good time to make
      this change too.
      
      [mattrope: Split out display changes to apply through intel-next tree]
      Signed-off-by: default avatarMatt Roper <matthew.d.roper@intel.com>
      Reviewed-by: default avatarJosé Roberto de Souza <jose.souza@intel.com>
      Link: https://patchwork.freedesktop.org/patch/msgid/20210717051426.4120328-8-matthew.d.roper@intel.com
      46b0d709