1. 20 5月, 2021 1 次提交
  2. 22 4月, 2021 1 次提交
  3. 14 4月, 2021 2 次提交
    • L
      drm/i915/display: rename display version macros · 93e7e61e
      Lucas De Marchi 提交于
      While converting the rest of the driver to use GRAPHICS_VER() and
      MEDIA_VER(), following what was done for display, some discussions went
      back on what we did for display:
      
      	1) Why is the == comparison special that deserves a separate
      	macro instead of just getting the version and comparing directly
      	like is done for >, >=, <=?
      
      	2) IS_DISPLAY_RANGE() is weird in that it omits the "_VER" for
      	brevity. If we remove the current users of IS_DISPLAY_VER(), we
      	could actually repurpose it for a range check
      
      With (1) there could be an advantage if we used gen_mask since multiple
      conditionals be combined by the compiler in a single and instruction and
      check the result. However a) INTEL_GEN() doesn't use the mask since it
      would make the code bigger everywhere else and b) in the cases it made
      sense, it also made sense to convert to the _RANGE() variant.
      
      So here we repurpose IS_DISPLAY_VER() to work with a [ from, to ] range
      like was the IS_DISPLAY_RANGE() and convert the current IS_DISPLAY_VER()
      users to use == and != operators. Aside from the definition changes,
      this was done by the following semantic patch:
      
      	@@ expression dev_priv, E1; @@
      	- !IS_DISPLAY_VER(dev_priv, E1)
      	+ DISPLAY_VER(dev_priv) != E1
      
      	@@ expression dev_priv, E1; @@
      	- IS_DISPLAY_VER(dev_priv, E1)
      	+ DISPLAY_VER(dev_priv) == E1
      
      	@@ expression dev_priv, from, until; @@
      	- IS_DISPLAY_RANGE(dev_priv, from, until)
      	+ IS_DISPLAY_VER(dev_priv, from, until)
      
      Cc: Jani Nikula <jani.nikula@intel.com>
      Cc: Matt Roper <matthew.d.roper@intel.com>
      Reviewed-by: NJani Nikula <jani.nikula@intel.com>
      Signed-off-by: NLucas De Marchi <lucas.demarchi@intel.com>
      [Jani: Minor conflict resolve while applying.]
      Signed-off-by: NJani Nikula <jani.nikula@intel.com>
      Link: http://patchwork.freedesktop.org/patch/msgid/20210413051002.92589-4-lucas.demarchi@intel.com
      93e7e61e
    • M
      drm/i915/display: Eliminate IS_GEN9_{BC,LP} · 2446e1d6
      Matt Roper 提交于
      Now that we've eliminated INTEL_GEN(), IS_GEN_RANGE(), etc. from the
      display code, we should also kill off our use of the IS_GEN9_* macros
      too.  We'll do the conversion manually this time instead of using
      Coccinelle since the most logical substitution can depend heavily on the
      code context, and sometimes we can keep the code simpler if we make
      additional adjustments such as swapping the order of if/else arms.
      
      v2:
       - Restore a lost negation in intel_pll_is_valid().
      
      Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
      Cc: Lucas De Marchi <lucas.demarchi@intel.com>
      Signed-off-by: NMatt Roper <matthew.d.roper@intel.com>
      Reviewed-by: NRadhakrishna Sripada <radhakrishna.sripada@intel.com>
      Link: https://patchwork.freedesktop.org/patch/msgid/20210407203945.1432531-1-matthew.d.roper@intel.com
      (cherry picked from commit 70bfb307)
      [Jani: cherry picked to topic branch to reduce conflicts]
      Signed-off-by: NJani Nikula <jani.nikula@intel.com>
      2446e1d6
  4. 08 4月, 2021 1 次提交
  5. 24 3月, 2021 1 次提交
  6. 02 2月, 2021 1 次提交
  7. 01 2月, 2021 1 次提交
  8. 16 10月, 2020 1 次提交
  9. 18 8月, 2020 1 次提交
  10. 23 6月, 2020 1 次提交
    • J
      drm/i915/params: switch to device specific parameters · 8a25c4be
      Jani Nikula 提交于
      Start using device specific parameters instead of module parameters for
      most things. The module parameters become the immutable initial values
      for i915 parameters. The device specific parameters in i915->params
      start life as a copy of i915_modparams. Any later changes are only
      reflected in the debugfs.
      
      The stragglers are:
      
      * i915.force_probe and i915.modeset. Needed before dev_priv is
        available. This is fine because the parameters are read-only and never
        modified.
      
      * i915.verbose_state_checks. Passing dev_priv to I915_STATE_WARN and
        I915_STATE_WARN_ON would result in massive and ugly churn. This is
        handled by not exposing the parameter via debugfs, and leaving the
        parameter writable in sysfs. This may be fixed up in follow-up work.
      
      * i915.inject_probe_failure. Only makes sense in terms of the module,
        not the device. This is handled by not exposing the parameter via
        debugfs.
      
      v2: Fix uc i915 lookup code (Michał Winiarski)
      
      Cc: Juha-Pekka Heikkilä <juha-pekka.heikkila@intel.com>
      Cc: Venkata Sandeep Dhanalakota <venkata.s.dhanalakota@intel.com>
      Cc: Michał Winiarski <michal.winiarski@intel.com>
      Reviewed-by: NRodrigo Vivi <rodrigo.vivi@intel.com>
      Acked-by: NMichał Winiarski <michal.winiarski@intel.com>
      Signed-off-by: NJani Nikula <jani.nikula@intel.com>
      Link: http://patchwork.freedesktop.org/patch/msgid/20200618150402.14022-1-jani.nikula@intel.com
      8a25c4be
  11. 03 6月, 2020 1 次提交
  12. 20 5月, 2020 1 次提交
  13. 03 3月, 2020 1 次提交
  14. 18 2月, 2020 1 次提交
    • J
      drm/i915/csr: use intel_de_*() functions for register access · 6ae5d1ce
      Jani Nikula 提交于
      The implicit "dev_priv" local variable use has been a long-standing pain
      point in the register access macros I915_READ(), I915_WRITE(),
      POSTING_READ(), I915_READ_FW(), and I915_WRITE_FW().
      
      Replace them with the corresponding new display engine register
      accessors intel_de_read(), intel_de_write(), intel_de_posting_read(),
      intel_de_read_fw(), and intel_de_write_fw().
      
      No functional changes.
      
      Generated using the following semantic patch:
      
      @@
      expression REG, OFFSET;
      @@
      - I915_READ(REG)
      + intel_de_read(dev_priv, REG)
      
      @@
      expression REG, OFFSET;
      @@
      - POSTING_READ(REG)
      + intel_de_posting_read(dev_priv, REG)
      
      @@
      expression REG, OFFSET;
      @@
      - I915_WRITE(REG, OFFSET)
      + intel_de_write(dev_priv, REG, OFFSET)
      
      @@
      expression REG;
      @@
      - I915_READ_FW(REG)
      + intel_de_read_fw(dev_priv, REG)
      
      @@
      expression REG, OFFSET;
      @@
      - I915_WRITE_FW(REG, OFFSET)
      + intel_de_write_fw(dev_priv, REG, OFFSET)
      Reviewed-by: NVille Syrjälä <ville.syrjala@linux.intel.com>
      Signed-off-by: NJani Nikula <jani.nikula@intel.com>
      Link: https://patchwork.freedesktop.org/patch/msgid/20200214140910.23194-1-jani.nikula@intel.com
      6ae5d1ce
  15. 14 2月, 2020 1 次提交
  16. 27 1月, 2020 1 次提交
  17. 22 1月, 2020 1 次提交
  18. 17 1月, 2020 1 次提交
  19. 28 9月, 2019 1 次提交
  20. 21 8月, 2019 1 次提交
  21. 06 8月, 2019 1 次提交
  22. 18 6月, 2019 9 次提交
  23. 14 6月, 2019 1 次提交
  24. 12 6月, 2019 1 次提交
  25. 07 6月, 2019 1 次提交
  26. 02 5月, 2019 1 次提交
  27. 08 4月, 2019 1 次提交
  28. 23 3月, 2019 1 次提交
  29. 21 1月, 2019 1 次提交
  30. 15 1月, 2019 1 次提交
  31. 21 11月, 2018 1 次提交