1. 04 10月, 2019 5 次提交
  2. 28 9月, 2019 1 次提交
  3. 27 9月, 2019 3 次提交
  4. 23 9月, 2019 3 次提交
  5. 16 9月, 2019 1 次提交
  6. 12 9月, 2019 2 次提交
  7. 11 9月, 2019 4 次提交
  8. 10 9月, 2019 1 次提交
  9. 30 8月, 2019 2 次提交
  10. 24 8月, 2019 3 次提交
  11. 23 8月, 2019 1 次提交
    • J
      drm/i915/psr: Make PSR registers relative to transcoders · 4ab4fa10
      José Roberto de Souza 提交于
      PSR registers are a mess, some have the full address while others just
      have the additional offset from psr_mmio_base.
      
      For BDW+ psr_mmio_base is nothing more than TRANSCODER_EDP_OFFSET +
      0x800 and using it makes more difficult for people with an PSR
      register address or PSR register name from from BSpec as i915 also
      don't match the BSpec names.
      For HSW psr_mmio_base is _DDI_BUF_CTL_A + 0x800 and PSR registers are
      only available in DDIA.
      
      Other reason to make relative to transcoder is that since BDW every
      transcoder have PSR registers, so in theory it should be possible to
      have PSR enabled in a non-eDP transcoder.
      
      So for BDW+ we can use _TRANS2() to get the register offset of any
      PSR register in any transcoder while for HSW we have _HSW_PSR_ADJ
      that will calculate the register offset for the single PSR instance,
      noting that we are already guarded about trying to enable PSR in other
      port than DDIA on HSW by the 'if (dig_port->base.port != PORT_A)' in
      intel_psr_compute_config(), this check should only be valid for HSW
      and will be changed in future.
      PSR2 registers and PSR_EVENT was added after Haswell so that is why
      _PSR_ADJ() is not used in some macros.
      
      The only registers that can not be relative to transcoder are
      PSR_IMR and PSR_IIR that are not relative to anything, so keeping it
      hardcoded. That changed for TGL but it will be handled in another
      patch.
      
      Also removing BDW_EDP_PSR_BASE from GVT because it is not used as it
      is the only PSR register that GVT have.
      
      v5:
      - Macros changed to be more explicit about HSW (Dhinakaran)
      - Squashed with the patch that added the tran parameter to the
      macros (Dhinakaran)
      
      v6:
      - Checking for interruption errors after module reload in the
      transcoder that will be used (Dhinakaran)
      - Using lowercase to the registers offsets
      
      v7:
      - Removing IS_HASWELL() from registers macros(Jani)
      
      Cc: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
      Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
      Cc: Jani Nikula <jani.nikula@linux.intel.com>
      Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
      Cc: Zhi Wang <zhi.a.wang@intel.com>
      Reviewed-by: NLucas De Marchi <lucas.demarchi@intel.com>
      Signed-off-by: NJosé Roberto de Souza <jose.souza@intel.com>
      Signed-off-by: NLucas De Marchi <lucas.demarchi@intel.com>
      Link: https://patchwork.freedesktop.org/patch/msgid/20190820223325.27490-1-jose.souza@intel.com
      4ab4fa10
  12. 22 8月, 2019 1 次提交
  13. 21 8月, 2019 1 次提交
  14. 20 8月, 2019 3 次提交
  15. 17 8月, 2019 3 次提交
  16. 16 8月, 2019 1 次提交
  17. 14 8月, 2019 1 次提交
  18. 13 8月, 2019 1 次提交
  19. 12 8月, 2019 1 次提交
  20. 10 8月, 2019 1 次提交
  21. 09 8月, 2019 1 次提交
    • C
      drm/i915: Replace global bsd_dispatch_index with random seed · 6b86f900
      Chris Wilson 提交于
      We keep a global seed for the legacy BSD round-robin selector, but in
      our testing of multiple simultaneous client workloads, a random seed
      spreads the load more evenly. (As even as an initial round-robin selector
      can be!) Removing the global is one less variable we have to find a home
      for!
      
      We can simulate multi-client (both same and mixed workloads) using
      igt/gem_wsim to work out optimal strategies and then compare our
      simulation with the actual transcoder on multi-engine machines. This
      fixed round-robin turns out to be one of the worst methods.
      
      No user is advised to use this method; the current suggestion is to use
      a virtual engine for agnostic batches, randomised submission or using
      the busyness tracking to select the most idle engine at the time of
      dispatch. At the present time, intel-media is explicit, but libva still
      seems to use it, with the exception of batches that must execute on vcs0.
      Oh well.
      Signed-off-by: NChris Wilson <chris@chris-wilson.co.uk>
      Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
      Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
      Reviewed-by: NJoonas Lahtinen <joonas.lahtinen@linux.intel.com>
      Link: https://patchwork.freedesktop.org/patch/msgid/20190809091010.23281-2-chris@chris-wilson.co.uk
      6b86f900