1. 16 Jul, 2020 1 commit
  2. 07 Jul, 2020 1 commit
  3. 31 Dec, 2019 1 commit
    • Imre Deak's avatar
      lib/igt_buf: Extend igt_buf to include two color surfaces · 7ff35cc1
      Imre Deak authored
      UV FBs have two color surfaces so extend the igt_buf struct accordingly
      to support blitting such FBs.
      
      The patch is produced with the coccinelle patch below.
      
      No functional changes.
      
      @@
      @@
      
      struct igt_buf {
      	...
      -	uint32_t stride;
      	...
      -	uint32_t size;
      +	struct {
      +		uint32_t stride;
      +		uint32_t size;
      +	} surface[2];
      	...
      };
      
      @@
      struct igt_buf b;
      @@
      
      <...
      (
      - b.stride
      + b.surface[0].stride
      |
      - b.size
      + b.surface[0].size
      )
      ...>
      
      @@
      struct igt_buf *b;
      @@
      
      <...
      (
      - b->size
      + b->surface[0].size
      |
      - b->stride
      + b->surface[0].stride
      )
      ...>
      
      @@
      identifier I;
      expression E1;
      expression E2;
      @@
      
      (
      struct igt_buf I = {
      -	.size = E1,
      -	.stride = E2,
      +	.surface[0] = {
      +		.size = E1,
      +		.stride = E2,
      +	},
      };
      |
      struct igt_buf I = {
      -	.size = E1,
      +	.surface[0] = {
      +		.size = E1,
      +	},
      };
      |
      struct igt_buf I = {
      -	.stride = E1,
      +	.surface[0] = {
      +		.stride = E1,
      +	},
      };
      )
      
      v2:
      - Rebase on latest upstream. (Mika)
      
      Cc: Mika Kahola <mika.kahola@intel.com>
      Signed-off-by: Imre Deak's avatarImre Deak <imre.deak@intel.com>
      Reviewed-by: default avatarMika Kahola <mika.kahola@intel.com>
      7ff35cc1
  4. 30 Dec, 2019 1 commit
  5. 03 Dec, 2019 1 commit
  6. 28 Nov, 2019 1 commit
  7. 13 Nov, 2019 1 commit
  8. 13 May, 2019 3 commits
  9. 04 Feb, 2019 2 commits
  10. 12 Jan, 2019 1 commit
  11. 01 Oct, 2018 1 commit
  12. 21 Aug, 2018 1 commit
  13. 01 Feb, 2018 1 commit
  14. 03 Jul, 2017 1 commit
  15. 01 Jun, 2017 1 commit
  16. 21 Mar, 2017 3 commits
  17. 31 Jan, 2017 1 commit
  18. 05 Jan, 2017 1 commit
  19. 13 Oct, 2016 1 commit
    • Imre Deak's avatar
      lib/igt_aux: Add support for various system suspend/resume options · 022e6f8a
      Imre Deak authored
      To have a more accurate idea about any suspend/resume issues we can
      perform the s/r until various phases in the s/r sequence. This way we
      can isolate the given problem as being a device driver, kernel core or
      BIOS related issue. Actual subtests using these new s/r phases will be
      added as follow-up.
      
      While at it also add the freeze suspend target, it's something we also
      would need to test.
      Signed-off-by: Imre Deak's avatarImre Deak <imre.deak@intel.com>
      022e6f8a
  20. 16 Oct, 2015 1 commit
  21. 11 Sep, 2015 1 commit
  22. 21 Aug, 2015 1 commit
  23. 11 May, 2015 1 commit
  24. 23 Mar, 2015 3 commits
  25. 12 Mar, 2015 1 commit
  26. 06 Mar, 2015 1 commit
  27. 10 Feb, 2015 1 commit
    • Matt Roper's avatar
      kms_cursor_crc: Kernel now checks for integer overflow · 9ca2cc12
      Matt Roper authored
      As of kernel commit
      
          commit a679064a7e9e8799177a64a31668a34a1bc6a4f1
          Author: Matt Roper <matthew.d.roper@intel.com>
          Date:   Fri Jan 30 16:22:37 2015 -0800
      
              drm/i915: Switch planes from transitional helpers to full atomic helpers
      
      the kernel now checks for cursor coordinates that would result in
      integer overflow and returns -ERANGE, similar to the checking that was
      already done for other plane types.  We update kms_cursor_crc here to
      reflect this small behavior change:
       * Check for success at extreme boundary conditions INT_MAX-{width,height}
         rather than INT_MAX
       * Add new check for success at SHRT_MAX; if the driver were to
         internally use short values and overflow, we could have the cursor
         reappear on the screen.
       * Add a test for failure with proper error code at INT_MAX-{width,height}+1
      Signed-off-by: Matt Roper's avatarMatt Roper <matthew.d.roper@intel.com>
      9ca2cc12
  28. 09 Dec, 2014 2 commits
  29. 24 Nov, 2014 1 commit
    • Daniel Vetter's avatar
      lib/igt_debugfs: Don't setup crc in _new · 57259d71
      Daniel Vetter authored
      The problem is that this causes writes to registers, and if the pipe
      is off they might go nowhere (e.g. when runtime pm is enabled).
      Furthermore we can only really check once the modeset setup is done,
      but again most tests set up the CRC structure before calling
      igt_commit and friends. We could add crc restore support to the
      kernel's rpm code, but that will end up being rather invasive and
      fragile hard-to-test code.
      
      Now originally this was needed back when CRC support wasn't available
      everywhere. But that's fixed now.
      
      So given all this just drop that sanity check and make sure that we
      only touch the debugfs file (and so the hw state) when we know the
      pipe is running in the desired configuration.
      
      A complementary kernel patch will try to catch offenders by returning
      -EIO if the pipe is off.
      
      v2: Forgot to git add one hunk.
      
      Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=86092Signed-off-by: Daniel Vetter's avatarDaniel Vetter <daniel.vetter@intel.com>
      57259d71
  30. 06 Nov, 2014 1 commit
  31. 17 Oct, 2014 1 commit
  32. 30 Sep, 2014 1 commit