1. 02 12月, 2017 1 次提交
    • P
      drm/etnaviv: make THERMAL selectable · 49b82c38
      Philipp Zabel 提交于
      The etnaviv driver causes a link failure if it is built-in but THERMAL
      is built as a module:
      
        drivers/gpu/drm/etnaviv/etnaviv_gpu.o: In function `etnaviv_gpu_bind':
        etnaviv_gpu.c:(.text+0x4c4): undefined reference to `thermal_of_cooling_device_register'
        etnaviv_gpu.c:(.text+0x600): undefined reference to `thermal_cooling_device_unregister'
        drivers/gpu/drm/etnaviv/etnaviv_gpu.o: In function `etnaviv_gpu_unbind':
        etnaviv_gpu.c:(.text+0x2aac): undefined reference to `thermal_cooling_device_unregister'
      
      Adding a Kconfig dependency on THERMAL || !THERMAL to avoid this causes
      a dependency loop on x86_64:
      
        drivers/gpu/drm/tve200/Kconfig:1:error: recursive dependency detected!
        For a resolution refer to Documentation/kbuild/kconfig-language.txt
        subsection "Kconfig recursive dependency limitations"
        drivers/gpu/drm/tve200/Kconfig:1:       symbol DRM_TVE200 depends on CMA
        For a resolution refer to Documentation/kbuild/kconfig-language.txt
        subsection "Kconfig recursive dependency limitations"
        mm/Kconfig:489: symbol CMA is selected by DRM_ETNAVIV
        For a resolution refer to Documentation/kbuild/kconfig-language.txt
        subsection "Kconfig recursive dependency limitations"
        drivers/gpu/drm/etnaviv/Kconfig:2:      symbol DRM_ETNAVIV depends on THERMAL
        For a resolution refer to Documentation/kbuild/kconfig-language.txt
        subsection "Kconfig recursive dependency limitations"
        drivers/thermal/Kconfig:5:      symbol THERMAL is selected by ACPI_VIDEO
        For a resolution refer to Documentation/kbuild/kconfig-language.txt
        subsection "Kconfig recursive dependency limitations"
        drivers/acpi/Kconfig:189:       symbol ACPI_VIDEO is selected by BACKLIGHT_CLASS_DEVICE
        For a resolution refer to Documentation/kbuild/kconfig-language.txt
        subsection "Kconfig recursive dependency limitations"
        drivers/video/backlight/Kconfig:158:    symbol BACKLIGHT_CLASS_DEVICE is selected by DRM_PARADE_PS8622
        For a resolution refer to Documentation/kbuild/kconfig-language.txt
        subsection "Kconfig recursive dependency limitations"
        drivers/gpu/drm/bridge/Kconfig:62:      symbol DRM_PARADE_PS8622 depends on DRM_BRIDGE
        For a resolution refer to Documentation/kbuild/kconfig-language.txt
        subsection "Kconfig recursive dependency limitations"
        drivers/gpu/drm/bridge/Kconfig:1:       symbol DRM_BRIDGE is selected by DRM_TVE200
      
      To work around this, add a new option DRM_ETNAVIV_THERMAL to optionally
      enable thermal throttling support and make DRM_ETNAVIV select THERMAL
      at the same time.
      Reported-by: NStephen Rothwell <sfr@canb.auug.org.au>
      Signed-off-by: NPhilipp Zabel <p.zabel@pengutronix.de>
      Signed-off-by: NLucas Stach <l.stach@pengutronix.de>
      49b82c38
  2. 03 11月, 2017 1 次提交
    • K
      drm/etnaviv: Convert timers to use timer_setup() · 43b70524
      Kees Cook 提交于
      In preparation for unconditionally passing the struct timer_list pointer to
      all timer callbacks, switch to using the new timer_setup() and from_timer()
      to pass the timer pointer explicitly.
      
      Cc: Lucas Stach <l.stach@pengutronix.de>
      Cc: Russell King <linux+etnaviv@armlinux.org.uk>
      Cc: Christian Gmeiner <christian.gmeiner@gmail.com>
      Cc: David Airlie <airlied@linux.ie>
      Cc: etnaviv@lists.freedesktop.org
      Cc: dri-devel@lists.freedesktop.org
      Signed-off-by: NKees Cook <keescook@chromium.org>
      43b70524
  3. 10 10月, 2017 12 次提交
  4. 15 8月, 2017 1 次提交
  5. 05 5月, 2017 2 次提交
  6. 12 4月, 2017 1 次提交
  7. 29 3月, 2017 5 次提交
  8. 02 2月, 2017 3 次提交
  9. 30 1月, 2017 1 次提交
  10. 03 12月, 2016 1 次提交
  11. 25 10月, 2016 1 次提交
    • C
      dma-buf: Rename struct fence to dma_fence · f54d1867
      Chris Wilson 提交于
      I plan to usurp the short name of struct fence for a core kernel struct,
      and so I need to rename the specialised fence/timeline for DMA
      operations to make room.
      
      A consensus was reached in
      https://lists.freedesktop.org/archives/dri-devel/2016-July/113083.html
      that making clear this fence applies to DMA operations was a good thing.
      Since then the patch has grown a bit as usage increases, so hopefully it
      remains a good thing!
      
      (v2...: rebase, rerun spatch)
      v3: Compile on msm, spotted a manual fixup that I broke.
      v4: Try again for msm, sorry Daniel
      
      coccinelle script:
      @@
      
      @@
      - struct fence
      + struct dma_fence
      @@
      
      @@
      - struct fence_ops
      + struct dma_fence_ops
      @@
      
      @@
      - struct fence_cb
      + struct dma_fence_cb
      @@
      
      @@
      - struct fence_array
      + struct dma_fence_array
      @@
      
      @@
      - enum fence_flag_bits
      + enum dma_fence_flag_bits
      @@
      
      @@
      (
      - fence_init
      + dma_fence_init
      |
      - fence_release
      + dma_fence_release
      |
      - fence_free
      + dma_fence_free
      |
      - fence_get
      + dma_fence_get
      |
      - fence_get_rcu
      + dma_fence_get_rcu
      |
      - fence_put
      + dma_fence_put
      |
      - fence_signal
      + dma_fence_signal
      |
      - fence_signal_locked
      + dma_fence_signal_locked
      |
      - fence_default_wait
      + dma_fence_default_wait
      |
      - fence_add_callback
      + dma_fence_add_callback
      |
      - fence_remove_callback
      + dma_fence_remove_callback
      |
      - fence_enable_sw_signaling
      + dma_fence_enable_sw_signaling
      |
      - fence_is_signaled_locked
      + dma_fence_is_signaled_locked
      |
      - fence_is_signaled
      + dma_fence_is_signaled
      |
      - fence_is_later
      + dma_fence_is_later
      |
      - fence_later
      + dma_fence_later
      |
      - fence_wait_timeout
      + dma_fence_wait_timeout
      |
      - fence_wait_any_timeout
      + dma_fence_wait_any_timeout
      |
      - fence_wait
      + dma_fence_wait
      |
      - fence_context_alloc
      + dma_fence_context_alloc
      |
      - fence_array_create
      + dma_fence_array_create
      |
      - to_fence_array
      + to_dma_fence_array
      |
      - fence_is_array
      + dma_fence_is_array
      |
      - trace_fence_emit
      + trace_dma_fence_emit
      |
      - FENCE_TRACE
      + DMA_FENCE_TRACE
      |
      - FENCE_WARN
      + DMA_FENCE_WARN
      |
      - FENCE_ERR
      + DMA_FENCE_ERR
      )
       (
       ...
       )
      Signed-off-by: NChris Wilson <chris@chris-wilson.co.uk>
      Reviewed-by: NGustavo Padovan <gustavo.padovan@collabora.co.uk>
      Acked-by: NSumit Semwal <sumit.semwal@linaro.org>
      Acked-by: NChristian König <christian.koenig@amd.com>
      Signed-off-by: NDaniel Vetter <daniel.vetter@ffwll.ch>
      Link: http://patchwork.freedesktop.org/patch/msgid/20161025120045.28839-1-chris@chris-wilson.co.uk
      f54d1867
  12. 15 9月, 2016 11 次提交