1. 16 Jul, 2019 1 commit
  2. 20 Jun, 2019 1 commit
  3. 23 May, 2019 1 commit
    • Arkadiusz Hiler's avatar
      meson: Start using 'feature' options · 736b0998
      Arkadiusz Hiler authored
      Meson 0.47 comes with a new type of option called 'feature' so instead of:
             type : 'combo',
             value : 'auto',
             choices : ['auto', 'true', 'false'],
      We can:
             type : 'feature',
      
      The main difference is that the feature takes auto, enabled and disabled
      instead of auto, true and false.
      
      get_option() on a feature returns opaque object that can be passed as
      a 'required' argument of a dependency. Auto is equivalent to 'required
      : false', enabled is equivalent to 'required : true' and disabled
      introduces new behavior forcing the dependency to be considered not
      found.
      
      This allows us to streamline a lot of logic regarding optional IGT
      features.
      
      This patch bumps required meson version to 0.47.0
      
      Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
      Cc: Petri Latvala <petri.latvala@intel.com>
      Cc: Simon Ser <simon.ser@intel.com>
      Signed-off-by: Arkadiusz Hiler's avatarArkadiusz Hiler <arkadiusz.hiler@intel.com>
      Reviewed-by: Daniel Vetter's avatarDaniel Vetter <daniel.vetter@ffwll.ch>
      736b0998
  4. 20 Feb, 2019 1 commit
  5. 18 Jul, 2018 1 commit
  6. 09 Mar, 2018 1 commit
  7. 16 Jan, 2018 1 commit
  8. 11 Jan, 2018 1 commit
  9. 04 Oct, 2017 1 commit
  10. 09 Jun, 2017 1 commit
  11. 13 Mar, 2017 1 commit
  12. 02 Dec, 2016 1 commit
  13. 02 Sep, 2016 1 commit
  14. 31 May, 2016 1 commit
  15. 09 May, 2016 1 commit
  16. 20 Apr, 2016 2 commits
  17. 19 Apr, 2016 1 commit
  18. 19 Mar, 2016 1 commit
    • Daniel Vetter's avatar
      lib: Add igt_subtest_group · 72d04b84
      Daniel Vetter authored
      Useful for creating common setup code in igt_fixture which is only
      needed by a subset of tests. And since I'm a good citizen it comes
      with a library testcase/example included.
      
      v2: Make testcase nastier to ensure a subtest group SKIPS when it's
      parent is skipping already. I accidentally got this right, but let's
      make sure.
      Signed-off-by: Daniel Vetter's avatarDaniel Vetter <daniel.vetter@ffwll.ch>
      72d04b84
  19. 01 Mar, 2016 1 commit
  20. 02 Dec, 2015 2 commits
  21. 11 Sep, 2015 2 commits
  22. 23 Jun, 2015 1 commit
  23. 11 Jun, 2015 2 commits
  24. 14 Apr, 2015 1 commit
  25. 13 Mar, 2015 1 commit
  26. 12 Mar, 2015 1 commit
  27. 05 Mar, 2015 1 commit
  28. 13 Feb, 2015 1 commit
  29. 12 Jan, 2015 1 commit
    • Ben Widawsky's avatar
      intel_gpu_frequency: A tool to manipulate Intel GPU frequency · 5fb26d14
      Ben Widawsky authored
      WARNING: very minimally tested
      
      In general you should not need this tool. Its primary purpose is for
      benchmarking, and for debugging performance issues.
      
      For many kernel releases now sysfs has supported reading and writing the GPU
      frequency. Therefore, this tool provides no new functionality. What it does
      provide is an easy to package (for distros) tool that handles the most common
      scenarios.
      
      v2:
      Get rid of -f from the usage message (Jordan)
      Add space before [-s (Jordan)
      Add a -c/--custom example (Jordan)
      Add a setting for resetting to hardware default (Ken)
      Replicate examples in commit message in the source code. (me)
      
      v3:
      Its not It's (me)
      Add --help/-h to usage
      Add Version + man page
      Rename tool to intel_gpu_frequency, from intel_frequency
      Remove "sudo" from the examples
      Signed-off-by: 's avatarBen Widawsky <ben@bwidawsk.net>
      Reviewed-by: Jordan Justen's avatarJordan Justen <jordan.l.justen@intel.com>
      Cc: Kenneth Graunke <kenneth@whitecape.org>
      
      Here are some sample usages:
      $ intel_gpu_frequency --get=cur,min,max,eff
      cur: 200 MHz
      min: 200 MHz
      RP1: 200 MHz
      max: 1200 MHz
      
      $ intel_gpu_frequency -g
      cur: 200 MHz
      min: 200 MHz
      RP1: 200 MHz
      max: 1200 MHz
      
      $ intel_gpu_frequency -geff
      RP1: 200 MHz
      
      $ intel_gpu_frequency --set min=300
      $ intel_gpu_frequency --get min
      cur: 300 MHz
      min: 300 MHz
      RP1: 200 MHz
      max: 1200 MHz
      
      $ intel_gpu_frequency --custom max=900
      $ intel_gpu_frequency --get max
      cur: 300 MHz
      min: 300 MHz
      RP1: 200 MHz
      max: 900 MHz
      
      $ intel_gpu_frequency --max
      $ intel_gpu_frequency -g
      cur: 1200 MHz
      min: 1200 MHz
      RP1: 200 MHz
      max: 1200 MHz
      
      $ intel_gpu_frequency -e
      $ intel_gpu_frequency -g
      cur: 200 MHz
      min: 200 MHz
      RP1: 200 MHz
      max: 200 MHz
      
      $ intel_gpu_frequency --max
      $ intel_gpu_frequency -g
      cur: 1200 MHz
      min: 1200 MHz
      RP1: 200 MHz
      max: 1200 MHz
      
      $ intel_gpu_frequency --min
      $ intel_gpu_frequency -g
      cur: 200 MHz
      min: 200 MHz
      RP1: 200 MHz
      max: 200 MHz
      5fb26d14
  30. 17 Dec, 2014 1 commit
  31. 12 Dec, 2014 2 commits
  32. 10 Dec, 2014 1 commit
  33. 01 Oct, 2014 1 commit
  34. 12 Sep, 2014 1 commit
  35. 09 Sep, 2014 1 commit