1. 15 8月, 2019 1 次提交
  2. 09 4月, 2019 2 次提交
    • D
      drm/vmwgfx: Use preprocessor macro for FIFO allocation · 11c45419
      Deepak Rawat 提交于
      Whenever FIFO allocation fails an error message is printed to dmesg.
      Since this is common operation a lot of similar messages are scattered
      everywhere. Use preprocessor macro to remove this cluttering.
      Signed-off-by: NDeepak Rawat <drawat@vmware.com>
      Reviewed-by: NThomas Hellstrom <thellstrom@vmware.com>
      11c45419
    • T
      drm/vmwgfx: Be more restrictive when dirtying resources · a9f58c45
      Thomas Hellstrom 提交于
      Currently we flag resources as dirty (GPU contents not yet read back to
      the backing MOB) whenever they have been part of a command stream.
      Obviously many resources can't be dirty and others can only be dirty when
      written to by the GPU. That is when they are either bound to the context as
      render-targets, depth-stencil, copy / clear destinations and
      stream-output targets, or similarly when there are corresponding views into
      them.
      So mark resources dirty only in these special cases. Context- and cotable
      resources are always marked dirty when referenced.
      This is important for upcoming emulated coherent memory, since we can avoid
      issuing automatic readbacks to non-dirty resources when the CPU tries to
      access part of the backing MOB.
      
      Testing: Unigine Heaven with max GPU memory set to 256MB resulting in
      heavy resource thrashing.
      ---
      v2: Addressed review comments by Deepak Rawat.
      v3: Added some documentation
      Signed-off-by: NThomas Hellstrom <thellstrom@vmware.com>
      Reviewed-by: NDeepak Rawat <drawat@vmware.com>
      a9f58c45
  3. 05 12月, 2018 8 次提交
  4. 06 10月, 2018 1 次提交
    • D
      drm/atomic-helper: Unexport drm_atomic_helper_best_encoder · 297e30b5
      Daniel Vetter 提交于
      It's the default. The exported version was kinda a transition state,
      before we made this the default.
      
      To stop new atomic drivers from using it (instead of just relying on
      the default) let's unexport it.
      
      v2: rename the default implementation to a more fitting name and add a
      comment (Laurent)
      Signed-off-by: NDaniel Vetter <daniel.vetter@intel.com>
      Cc: Gustavo Padovan <gustavo@padovan.org>
      Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
      Cc: Sean Paul <seanpaul@chromium.org>
      Cc: David Airlie <airlied@linux.ie>
      Cc: VMware Graphics <linux-graphics-maintainer@vmware.com>
      Cc: Sinclair Yeh <syeh@vmware.com>
      Cc: Thomas Hellstrom <thellstrom@vmware.com>
      Cc: Archit Taneja <architt@codeaurora.org>
      Cc: Neil Armstrong <narmstrong@baylibre.com>
      Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
      Cc: Hans Verkuil <hverkuil@xs4all.nl>
      Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
      Cc: Russell King <rmk+kernel@armlinux.org.uk>
      Cc: Jernej Skrabec <jernej.skrabec@siol.net>
      Cc: Jani Nikula <jani.nikula@intel.com>
      Cc: Pierre-Hugues Husson <phh@phh.me>
      Cc: Fabio Estevam <fabio.estevam@nxp.com>
      Reviewed-by: NLaurent Pinchart <laurent.pinchart@ideasonboard.com>
      Link: https://patchwork.freedesktop.org/patch/msgid/20181004202446.22905-3-daniel.vetter@ffwll.ch
      297e30b5
  5. 27 9月, 2018 1 次提交
  6. 14 7月, 2018 1 次提交
  7. 04 7月, 2018 2 次提交
  8. 30 6月, 2018 1 次提交
  9. 12 6月, 2018 1 次提交
  10. 16 5月, 2018 1 次提交
  11. 22 3月, 2018 4 次提交
  12. 21 3月, 2018 1 次提交
    • T
      drm/vmwgfx: Fix a destoy-while-held mutex problem. · 73a88250
      Thomas Hellstrom 提交于
      When validating legacy surfaces, the backup bo might be destroyed at
      surface validate time. However, the kms resource validation code may have
      the bo reserved, so we will destroy a locked mutex. While there shouldn't
      be any other users of that mutex when it is destroyed, it causes a lock
      leak and thus throws a lockdep error.
      
      Fix this by having the kms resource validation code hold a reference to
      the bo while we have it reserved. We do this by introducing a validation
      context which might come in handy when the kms code is extended to validate
      multiple resources or buffers.
      
      Cc: <stable@vger.kernel.org>
      Signed-off-by: NThomas Hellstrom <thellstrom@vmware.com>
      Reviewed-by: NBrian Paul <brianp@vmware.com>
      Reviewed-by: NSinclair Yeh <syeh@vmware.com>
      73a88250
  13. 17 1月, 2018 1 次提交
  14. 21 10月, 2017 1 次提交
    • K
      drm: Reorganize drm_pending_event to support future event types [v2] · bd386e51
      Keith Packard 提交于
      Place drm_event_vblank in a new union that includes that and a bare
      drm_event structure. This will allow new members of that union to be
      added in the future without changing code related to the existing vbl
      event type.
      
      Assignments to the crtc_id field are now done when the event is
      allocated, rather than when delievered. This way, delivery doesn't
      need to have the crtc ID available.
      
      v2:
       * Remove 'dev' argument from create_vblank_event
      
      	It wasn't being used anyways, and if we need it in the future,
      	we can always get it from crtc->dev.
      
       * Check for MODESETTING before looking for crtc in queue_vblank_event
      
      	UMS drivers will oops if we try to get a crtc, so make sure
      	we're modesetting before we try to find a crtc_id to fill into
      	the event.
      Signed-off-by: NKeith Packard <keithp@keithp.com>
      Reviewed-by: NSean Paul <seanpaul@chromium.org>
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      (cherry picked from commit dc695b85fde88eca3ef3b03fcd82f15b6bc6e462)
      bd386e51
  15. 02 8月, 2017 1 次提交
    • B
      drm: Plumb modifiers through plane init · e6fc3b68
      Ben Widawsky 提交于
      This is the plumbing for supporting fb modifiers on planes. Modifiers
      have already been introduced to some extent, but this series will extend
      this to allow querying modifiers per plane. Based on this, the client to
      enable optimal modifications for framebuffers.
      
      This patch simply allows the DRM drivers to initialize their list of
      supported modifiers upon initializing the plane.
      
      v2: A minor addition from Daniel
      
      v3:
      * Updated commit message
      * s/INVALID/DRM_FORMAT_MOD_INVALID (Liviu)
      * Remove some excess newlines (Liviu)
      * Update comment for > 64 modifiers (Liviu)
      
      v4: Minor comment adjustments (Liviu)
      
      v5: Some new platforms added due to rebase
      
      v6: Add some missed plane inits (or maybe they're new - who knows at
      this point) (Daniel)
      Signed-off-by: NBen Widawsky <ben@bwidawsk.net>
      Reviewed-by: Daniel Stone <daniels@collabora.com> (v2)
      Reviewed-by: NLiviu Dudau <Liviu.Dudau@arm.com>
      Signed-off-by: NDaniel Stone <daniels@collabora.com>
      e6fc3b68
  16. 30 6月, 2017 2 次提交
  17. 28 6月, 2017 1 次提交
  18. 27 6月, 2017 1 次提交
  19. 01 4月, 2017 9 次提交