1. 15 Feb, 2019 1 commit
  2. 13 Dec, 2018 1 commit
  3. 16 Nov, 2018 1 commit
  4. 23 Oct, 2018 1 commit
  5. 15 Aug, 2018 1 commit
  6. 27 Jul, 2018 2 commits
  7. 20 Jun, 2018 1 commit
    • Daniel Vetter's avatar
      gtkdoc: Remove the build_by_default hack · 4bbfb4fb
      Daniel Vetter authored
      meson 0.45 properly supports generated content_files. Except for the
      minor issue that we're hitting an internal bug in meson. I've made a
      pull request for that
      
      https://github.com/mesonbuild/meson/pull/3189
      
      which has now been addressed in
      
      commit c1f275bfa644beafab9f8572351d4b64d61c148b
      Author: Nirbheek Chauhan <nirbheek@centricular.com>
      Date:   Sun May 6 20:09:49 2018 +0530
      
          gnome.gtkdoc: Allow passing file objects as xml_files
      
          If we pass a source files() object, we will look for it in the build
          directory, which is wrong. If we pass a build files() object (from
          configure_file()), we will find it in the build directory, and then
          try to copy it on top of itself in gtkdochelper.py getting a
          SameFileError.
      
          Add a test for it, and also properly iterate custom target outputs
          when adding to content files.
      
      Downside of this all is that we'd need to up the meson requirements to
      something like 0.47, which isn't even released yet :-/
      
      v2: Rebase and also add version requirement.
      
      v3: I figured out how to make this work with a meson version check!
      
      v4: Remove stray hunk (Petri).
      
      Cc: Eric Anholt <eric@anholt.net>
      Reviewed-by: Petri Latvala's avatarPetri Latvala <petri.latvala@intel.com>
      Signed-off-by: Daniel Vetter's avatarDaniel Vetter <daniel.vetter@intel.com>
      4bbfb4fb
  8. 16 May, 2018 1 commit
  9. 11 Jan, 2018 2 commits
  10. 08 Dec, 2017 1 commit
  11. 05 Dec, 2017 1 commit
    • Daniel Vetter's avatar
      meson: gtkdoc support · 491e8c17
      Daniel Vetter authored
      Bunch of neat improvements:
      
      - xml generates correctly depend upon the test binaries
      - no need to re-run autogen.sh when new chapters/functions get added,
        all handed by meson
      
      Still one issue:
      
      - the gtkdoc target doesn't depend upon the custom_target yet, hacked
        around using build_by_default: true
      
        This is an issue known to upstream already:
      
        https://github.com/mesonbuild/meson/issues/2148
      
      v2: Bump meson version to 0.42, since that's the first release which
      adds the build dir when running the gtkdoc tools, and hence allows
      including generated files.
      
      v2:
      - Undo the bump, it's only needed for generated source files. Other
        generated files as input should work with 0.40 already.
      
      - Generate version.xml from version.xml.in, which allows us to keep
        the &version; entity.
      
      v3: Add github issue link.
      
      v4:
      - Resurrect lost KEYWORDS (Petri)
      - Fix issue when running with a clean build, files() doesn't work on generate
        files (Petri).
      Reviewed-by: Petri Latvala's avatarPetri Latvala <petri.latvala@intel.com>
      Signed-off-by: Daniel Vetter's avatarDaniel Vetter <daniel.vetter@ffwll.ch>
      491e8c17
  12. 19 Oct, 2017 1 commit
  13. 17 Oct, 2017 2 commits
  14. 10 Oct, 2017 1 commit
  15. 02 Oct, 2017 1 commit
  16. 30 Aug, 2017 1 commit
  17. 28 Aug, 2017 2 commits
  18. 21 Aug, 2017 2 commits
  19. 24 Jul, 2017 1 commit
  20. 26 Jan, 2017 1 commit
    • Lyude Paul's avatar
      Add support for hotplug testing with the Chamelium · c99f8b7a
      Lyude Paul authored
      For the purpose of testing things such as hotplugging and bad monitors,
      the ChromeOS team ended up designing a neat little device known as the
      Chamelium. More information on this can be found here:
      
      	https://www.chromium.org/chromium-os/testing/chamelium
      
      This adds support for a couple of things to intel-gpu-tools:
       - igt library functions for connecting to udev and monitoring it for
         hotplug events, loosely based off of the unfinished hotplugging
         implementation in testdisplay
       - Library functions for controlling the chamelium in tests using
         xmlrpc. A couple of RPC calls were ommitted here, mainly because they
         didn't seem very useful for our needs (yet)
       - A set of functions for doing CRC checks and frame comparisons in
         tests
       - A set of basic tests using the Chamelium library.
      
      Cc: Tomeu Vizoso <tomeu@tomeuvizoso.net>
      Signed-off-by: Lyude Paul's avatarLyude <lyude@redhat.com>
      
      Changes since v1:
      - Don't try to guess connector mappings, have the user specify them
        manually using a configuration file
      - Open DRM fd using DRIVER_ANY, not DRIVER_INTEL
      - Lower the hotplug timeout a little bit, since 30 seconds was leftover
        from debugging these tests anyway
      - Don't try to keep track of the original state of the chamelium ports,
        and just leave them plugged in after each run. This makes more sense
        to me, since I'd imagine in automated testing setups using chameliums
        that all of the extra monitors will probably be provided by the
        Chamelium to begin with, so keeping them plugged in would make sure
        tests running afterwards that require >1 monitor don't get skipped.
      - Add wait_for_connector() to the chamelium tests. After some more
        testing, I found that depending on the system some tests would throw
        false negatives due to us not waiting long enough for the system to
        detect that we connected something to it. This mainly happened with
        VGA connectors, since their lack of HPD makes them take significantly
        longer for the hardware to notice. wait_for_connector() fixes this by
        continually reprobing the status of the desired connector (without
        relying on a hpd event happening, since that might never come) until
        we get what we want, or we time out and fail.
      - Use kmstest_get_property() for retrieving EDIDs instead of doing it by
        hand
      - Don't hardcode PIPE_A for bringing up the display, use kmstest to find
        an appropriate CRTC to use.
      Changes since v2:
      - Fix incorrect usage of the list helpers when recording new EDIDs
      - Add missing documentation
      - Make sure documentation actually appears
      - Since we finally got video capture working, add CRC functions and fix
        the ones we couldn't actually test before
      - In the exit handler, reset the xmlrpc env so we can properly reset the
        Chamelium even after an RPC error
      - Make sure compiling without Chamelium support still works
      Changes since v3:
      - Change the config file name from .igt_chamelium_rc to .igtrc
      - Remove chamelium global context
      - Get rid of define_common_connector_tests()
      - Get rid of connector list, expose connectors as opaque objects and
        provide helpers for accessing their attributes
      - Get rid of configure.ac option for Chamelium
      - Add tests for CRC functions
      - Add frame dumping functions + tests
      - Add FSM handling to chamelium_rpc()
      - Use LIBUDEV_LIBS in automake, not UDEV_LIBS
      - Documentation fixes
      - Improve debugging output some more
      - Remove skip_without_suspend_support, we no longer need to check for
        suspend support before calling things
      - Remove unnessecary malloc() checks with igt_assert()
      - Don't use igt_require in chamelium_init, leave it up to the caller
        whether or not to abort when failing to initialize the chamelium
      - Use igt_assert_eq for making assertions about connector's statuses
      - Define suspend/resume delay for tests as constant
      c99f8b7a
  21. 01 Dec, 2016 1 commit
    • Marius Vlad's avatar
      lib/igt_kmod: New library to support driver loading/unloading and additional helpers. · 0268d73b
      Marius Vlad authored
      lib/igt_aux: Added igt_pkill and igt_lsof helper.
      lib/igt_kmod: Added load/unload kmod helpers.
      
      v7:
      - document the case where leaving stray fd from drm_open_driver()
      might fail reloading the driver.
      - list also current opened files from /dev/dri in case we could not
      unload the driver.
      - convert igt_info to igt_warn (Chris Wilson)
      - added KMOD_|PROCPS CFLAGS (Chris Wilson)
      
      v6:
      - include latest modifications from tests/drv_module_reload:
      display all loaded modules and list information about opened
      files by processes (Petri Latvala)
      
      v5:
      - added igt_i915_driver_{load/unload}.
      - added kick_snd_hda_intel() to match current
      tests/drv_module_reload_basic and integrated into
      igt_i915_driver_load/unload.
      - added gtk-doc section for lib/igt_kmod
      
      v4:
      - decided to split libkmod helpers into their own file as there's
      another user lib/igt_gvt or tests/gvt_basic.
      - fixed some gtk-doc documentation.
      
      v3:
      - return -errno (igt_pkill()) in case of failure (Cris Wilson)
      - return bool for igt_kmod_is_loaded(), replaced strncasecmp with strncmp
      (Chris Wilson)
      
      v2:
      - Renamed libkmod helpers (Chris Wilson)
      - Removed SIGTERM/SIGKILL case where we repeatedly tried to terminate the
      process: just call kill(2) once (Chris Wilson)
      - Removed redundant check in igt_kmod_unload(), igt_module_in_use() (Chris
      Wilson)
      - Pass flags to igt_kmod_unload() from the caller (Chris Wilson)
      - Removed useless function igt_kill() which acts just as kill(2) (Chris
      Wilson)
      Signed-off-by: 's avatarMarius Vlad <marius.c.vlad@intel.com>
      0268d73b
  22. 29 Nov, 2016 1 commit
    • Abdiel Janulgue's avatar
      lib: add igt_dummyload · 35fa2ca7
      Abdiel Janulgue authored
      A lot of igt testcases need some GPU workload to make sure a race
      window is big enough. Unfortunately having a fixed amount of
      workload leads to spurious test failures or overly long runtimes
      on some fast/slow platforms. This library contains functionality
      to submit GPU workloads that should consume exactly a specific
      amount of time.
      
      Since v14: Since we are using multiple signals, walk list of batches
      to terminate a batch to avoid using a single global batch. Cycle signals
      between SIGRTMIN and SIGRTMAX properly.
      
      Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
      Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
      Cc: Chris Wilson <chris@chris-wilson.co.uk>
      Cc: tomeu@tomeuvizoso.net
      Reviewed-by: 's avatarTomeu Vizoso <tomeu.vizoso@collabora.com>
      Signed-off-by: Abdiel Janulgue's avatarAbdiel Janulgue <abdiel.janulgue@linux.intel.com>
      35fa2ca7
  23. 27 Jul, 2016 3 commits
  24. 19 Feb, 2016 1 commit
  25. 21 Dec, 2015 1 commit
  26. 02 Dec, 2015 1 commit
  27. 02 Jul, 2015 3 commits
  28. 27 Jun, 2015 1 commit
  29. 14 May, 2015 1 commit
  30. 21 Apr, 2015 1 commit
  31. 14 Apr, 2015 1 commit