1. 11 2月, 2015 1 次提交
  2. 05 2月, 2015 2 次提交
    • D
      Merge tag 'drm-amdkfd-next-fixes-2015-02-03' of... · 2f899790
      Dave Airlie 提交于
      Merge tag 'drm-amdkfd-next-fixes-2015-02-03' of git://people.freedesktop.org/~gabbayo/linux into drm-next
      
      - Fixing accounting of active queues
      - Preserving a register internal state
      
      * tag 'drm-amdkfd-next-fixes-2015-02-03' of git://people.freedesktop.org/~gabbayo/linux:
        drm/amdkfd: Preserve CP_MQD_IQ_RPTR internal state
        drm/amdkfd: Fix dqm->queue_count tracking
      2f899790
    • D
      Merge branch 'drm-intel-next' of git://anongit.freedesktop.org/drm-intel into drm-next · 225963dd
      Dave Airlie 提交于
      drm-intel-next-2015-01-30:
      - chv rps improvements from Ville
      - atomic state handling prep work from Ander
      - execlist request tracking refactoring from Nick Hoath
      - forcewake code consolidation from Chris&Mika
      - fastboot plane config refactoring and skl support from Damien
      - some more skl pm patches all over (Damien)
      - refactor dsi code to use drm dsi helpers and drm_panel infrastructure (Jani)
      - first cut at experimental atomic plane updates (Matt Roper)
      - piles of smaller things all over, as usual
      
      * 'drm-intel-next' of git://anongit.freedesktop.org/drm-intel: (102 commits)
        drm/i915: Remove bogus locking check in the hangcheck code
        drm/i915: Update DRIVER_DATE to 20150130
        drm/i915: Use pipe_config's cpu_transcoder for reading encoder hw state
        drm/i915: Fix a use-after-free in intel_execlists_retire_requests
        drm/i915: Split shared dpll setup out of __intel_set_mode()
        drm/i915: Don't do posting reads on getting forcewake
        drm/i915: Do uncore early sanitize after domain init
        drm/i915: Handle CHV in vlv_set_rps_idle()
        drm/i915: Remove nested work in gpu error handling
        drm/i915/documentation: Add intel_uncore.c to drm.tmpl
        drm/i915/dsi: remove intel_dsi_cmd.c and the unused functions therein
        drm/i915/dsi: move dpi_send_cmd() to intel_dsi.c and make it static
        drm/i915/dsi: remove old read/write functions in favor of new stuff
        drm/i915/dsi: make the vbt panel driver use mipi_dsi_device for transfers
        drm/i915/dsi: add drm mipi dsi host support
        drm/i915/dsi: switch to drm_panel interface
        drm/i915/skl: Enabling PSR on Skylake
        Revert "drm/i915: Fix mutex->owner inspection race under DEBUG_MUTEXES"
        drm/i915: Be consistent on printing seqnos
        drm/i915: Display current hangcheck status in debugfs
        ...
      225963dd
  3. 04 2月, 2015 3 次提交
    • T
      drm: Use static attribute groups for managing connector sysfs entries · 335f1a62
      Takashi Iwai 提交于
      Instead of manual calls of device_create_file() and
      device_remove_file(), assign the static attribute groups to the device
      with device_create_with_groups().  The conditionally built sysfs
      entries are handled via is_visible callback.
      
      This simplifies the code and also avoids the possible races.
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      Signed-off-by: NDaniel Vetter <daniel.vetter@ffwll.ch>
      335f1a62
    • D
      drm: remove DRM_FORMAT_NV12MT · 083500ba
      Daniel Vetter 提交于
      So this has been merged originally in
      
      commit 83052d4d
      Author: Seung-Woo Kim <sw0312.kim@samsung.com>
      Date:   Thu Dec 15 15:40:55 2011 +0900
      
          drm: Add multi buffer plane pixel formats
      
      which hasn't seen a lot of review really. The problem is that it's not
      a real pixel format, but just a different way to lay out NV12 pixels
      in macroblocks, i.e. a tiling format.
      
      The new way of doing this is with the soon-to-be-merged fb modifiers.
      
      This was brough up in some long irc discussion around the entire
      topic, as an example of where things have gone wrong. Luckily we can
      correct the mistake:
      - The kms side support for NV12MT is all dead code because
        format_check in drm_crtc.c never accepted NV12MT.
      - The gem side for the gsc support doesn't look better: The code
        forgets to set the pixel format and makes a big mess with the tiling
        mode bits, inadvertedly setting them all.
      
      Conclusion: This never really worked (at least not in upstream) and
      hence we can safely correct our mistake here.
      
      Cc: Seung-Woo Kim <sw0312.kim@samsung.com>
      Cc: Inki Dae <inki.dae@samsung.com>
      Cc: Kyungmin Park <kyungmin.park@samsung.com>
      Cc: Rob Clark <robclark@freedesktop.org>
      Cc: Daniel Stone <daniel@fooishbar.org>
      Cc: Damien Lespiau <damien.lespiau@intel.com>
      Reviewed-by: NRob Clark <robclark@freedesktop.org>
      Reviewed-by: NGustavo Padovan <gustavo.padovan@collabora.co.uk>
      Acked-by: NJoonyoung Shim <jy0922.shim@samsung.com>
      Acked-by: NSeung-Woo Kim <sw0312.kim@samsung.com>
      Signed-off-by: NDaniel Vetter <daniel.vetter@intel.com>
      083500ba
    • D
      drm/i915: Remove bogus locking check in the hangcheck code · b838cbee
      Daniel Vetter 提交于
      You can _never_ assert that a lock is not held, except in some very
      restricted corner cases where it's guranteed that your code is running
      single-threade (e.g. driver load before you've published any pointers
      leading to that lock).
      
      In addition the early return breaks a bunch of testcases since with
      highly concurrent hangcheck stress tests the reset fails to work and
      the test doesn't recover and time out.
      
      This regression has been introduced in
      
      commit b8d24a06
      Author: Mika Kuoppala <mika.kuoppala@linux.intel.com>
      Date:   Wed Jan 28 17:03:14 2015 +0200
      
          drm/i915: Remove nested work in gpu error handling
      
      Aside: It is possible to check whether a given task doesn't hold a
      lock, but only when lockdep is enabled, using the lockdep_assert_held
      stuff.
      
      Cc: Chris Wilson <chris@chris-wilson.co.uk>
      Cc: Mika Kuoppala <mika.kuoppala@intel.com>
      Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=88908Reviewed-by: NMika Kuoppala <mika.kuoppala@intel.com>
      Signed-off-by: NDaniel Vetter <daniel.vetter@intel.com>
      b838cbee
  4. 03 2月, 2015 3 次提交
    • V
      drm/modes: Print the mode status in human readable form · f79d1548
      Ville Syrjälä 提交于
      Currently when a mode is rejected the reason is printed as a raw number.
      Having to manually decode that to a enum drm_mode_status value is
      tiresome. Have the code do the decoding instead and print the result
      in a human readable format.
      
      Just having an array of strings indexed with the mode status doesn't
      work since the enum includes negative values. So we offset the status
      by +3 which makes all the indexes non-negative. Also add a bit of
      paranoia into the code to catch out of bounds accesses in case
      someone adds more enum values but forgets to update the code.
      Signed-off-by: NVille Syrjälä <ville.syrjala@linux.intel.com>
      Reviewed-by: NAlex Deucher <alexander.deucher@amd.com>
      Signed-off-by: NDaniel Vetter <daniel.vetter@ffwll.ch>
      f79d1548
    • V
      drm/modes: Print the mode status in human readable form · e4bf44b3
      Ville Syrjälä 提交于
      Currently when a mode is rejected the reason is printed as a raw number.
      Having to manually decode that to a enum drm_mode_status value is
      tiresome. Have the code do the decoding instead and print the result
      in a human readable format.
      
      Just having an array of strings indexed with the mode status doesn't
      work since the enum includes negative values. So we offset the status
      by +3 which makes all the indexes non-negative. Also add a bit of
      paranoia into the code to catch out of bounds accesses in case
      someone adds more enum values but forgets to update the code.
      Signed-off-by: NVille Syrjälä <ville.syrjala@linux.intel.com>
      Reviewed-by: NAlex Deucher <alexander.deucher@amd.com>
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      e4bf44b3
    • C
      drm: Kconfig: Let all DRM_GEM_CMA_HELPER related macros depend on HAVE_DMA_ATTRS · db88c8f4
      Chen Gang S 提交于
      DRM_GEM_CMA_HELPER is depend on HAVE_DMA_ATTRS, or it will break the
      building. The related error (with allmodconfig under xtensa):
      
          CC [M]  drivers/gpu/drm/drm_gem_cma_helper.o
        drivers/gpu/drm/drm_gem_cma_helper.c: In function 'drm_gem_cma_create':
        drivers/gpu/drm/drm_gem_cma_helper.c:110:19: error: implicit declaration of function 'dma_alloc_writecombine' [-Werror=implicit-function-declaration]
          cma_obj->vaddr = dma_alloc_writecombine(drm->dev, size,
                           ^
        drivers/gpu/drm/drm_gem_cma_helper.c:110:17: warning: assignment makes pointer from integer without a cast [-Wint-conversion]
          cma_obj->vaddr = dma_alloc_writecombine(drm->dev, size,
                         ^
        drivers/gpu/drm/drm_gem_cma_helper.c: In function 'drm_gem_cma_free_object':
        drivers/gpu/drm/drm_gem_cma_helper.c:193:3: error: implicit declaration of function 'dma_free_writecombine' [-Werror=implicit-function-declaration]
           dma_free_writecombine(gem_obj->dev->dev, cma_obj->base.size,
           ^
        drivers/gpu/drm/drm_gem_cma_helper.c: In function 'drm_gem_cma_mmap_obj':
        drivers/gpu/drm/drm_gem_cma_helper.c:330:8: error: implicit declaration of function 'dma_mmap_writecombine' [-Werror=implicit-function-declaration]
          ret = dma_mmap_writecombine(cma_obj->base.dev->dev, vma,
                ^
      Signed-off-by: NChen Gang <gang.chen.5i5j@gmail.com>
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      db88c8f4
  5. 02 2月, 2015 23 次提交
  6. 31 1月, 2015 8 次提交