Skip to content
  1. Nov 23, 2017
  2. Nov 21, 2017
  3. Nov 20, 2017
    • Jyri Sarha's avatar
      drm/tilcdc: Remove obsolete "ti,tilcdc,slave" dts binding support · 739acd85
      Jyri Sarha authored
      
      
      This patch removes DRM_TILCDC_SLAVE_COMPAT option for supporting the
      obsolete "ti,tilcdc,slave" device tree binding. The new of_graph based
      binding - that is widely used in other drm driver too - has been
      supported since Linux v4.2. Maintaining the the backwards dts
      conversion code in the DRM_TILCDC_SLAVE_COMPAT has become a nuisance
      for the device/of development so the we decided to drop it after Linux
      v4.14, the 2017 LTS.
      
      Signed-off-by: default avatarJyri Sarha <jsarha@ti.com>
      Acked-by: default avatarRob Herring <robh@kernel.org>
      739acd85
    • Thierry Reding's avatar
      drm/tegra: sor: Reimplement pad clock · e1335e2f
      Thierry Reding authored
      
      
      The current implementation of the pad clock isn't quite correct. This
      has the side-effect of being incompatible with the implementation for
      Tegra186 (provided by the BPMP) and therefore would require a massive
      change to the driver to cope with the differences. Instead, simply do
      what Tegra186 does and add some code to fallback to the old behaviour
      for existing device trees.
      
      Signed-off-by: default avatarThierry Reding <treding@nvidia.com>
      e1335e2f
    • Dave Airlie's avatar
      Merge tag 'drm-fsl-dcu-fixes-for-v4.15' of http://git.agner.ch/git/linux-drm-fsl-dcu into drm-next · 5ee72d33
      Dave Airlie authored
      Some cleanup/fixes, some noticed during testing of Noralf Trønnes
      rework of the suspend/resume helper. He will rebase the patchset
      ontop of this.
      
      * tag 'drm-fsl-dcu-fixes-for-v4.15' of http://git.agner.ch/git/linux-drm-fsl-dcu:
        drm/fsl-dcu: enable IRQ before drm_atomic_helper_resume()
        drm/fsl-dcu: avoid disabling pixel clock twice on suspend
        drm/fsl-dcu: Don't set connector DPMS property
      5ee72d33
    • Dave Airlie's avatar
      Merge branch 'drm-next-4.15' of git://people.freedesktop.org/~agd5f/linux into drm-next · 1220a3e5
      Dave Airlie authored
      Misc fixes for 4.15.
      
      * 'drm-next-4.15' of git://people.freedesktop.org/~agd5f/linux:
        drm/amd/pp: fix dpm randomly failed on Vega10
        drm/amdgpu: set f_mapping on exported DMA-bufs
        drm/amdgpu: Properly allocate VM invalidate eng v2
        drm/amd/amdgpu: if visible VRAM allocation fail, fall back to invisible try again
        drm/amd/amdgpu: Fix wave mask in amdgpu_debugfs_wave_read() (v2)
        drm/amdgpu: make AMDGPU_VA_RESERVED_SIZE 64bit
        drm/amdgpu/gfx9: implement wave VGPR reading
        drm/amdgpu: Add common golden settings for GFX9
        drm/amd/powerplay: fix copy-n-paste error on vddci_buf index
        drm/amdgpu: Fix null pointer issue in amdgpu_cs_wait_any_fence
        drm/amdgpu: Remove check which is not valid for certain VBIOS
      1220a3e5
  4. Nov 18, 2017
  5. Nov 17, 2017
  6. Nov 16, 2017
  7. Nov 15, 2017
  8. Nov 14, 2017
  9. Nov 13, 2017
    • Emil Renner Berthing's avatar
      drm/rockchip: analogix_dp: Use mutex rather than spinlock · 44419ce7
      Emil Renner Berthing authored
      
      
      On the Samsung Chromebook Plus I get this error with 4.14-rc3:
      
      BUG: scheduling while atomic: kworker/3:1/50/0x00000002
      Modules linked in:
      CPU: 3 PID: 50 Comm: kworker/3:1 Not tainted 4.14.0-0.rc3-kevin #2
      Hardware name: Google Kevin (DT)
      Workqueue: events analogix_dp_psr_work
      Call trace:
      [<ffffff80080873b0>] dump_backtrace+0x0/0x320
      [<ffffff80080876e4>] show_stack+0x14/0x20
      [<ffffff8008606d38>] dump_stack+0x9c/0xbc
      [<ffffff80080c6b5c>] __schedule_bug+0x4c/0x70
      [<ffffff80086188c0>] __schedule+0x3f0/0x458
      [<ffffff8008618960>] schedule+0x38/0xa0
      [<ffffff800861c20c>] schedule_hrtimeout_range_clock+0x84/0xe8
      [<ffffff800861c2a0>] schedule_hrtimeout_range+0x10/0x18
      [<ffffff800861bcec>] usleep_range+0x64/0x78
      [<ffffff8008415a6c>] analogix_dp_transfer+0x16c/0x340
      [<ffffff8008412550>] analogix_dpaux_transfer+0x10/0x18
      [<ffffff80083ceb14>] drm_dp_dpcd_access+0x4c/0xf0
      [<ffffff80083cf614>] drm_dp_dpcd_write+0x1c/0x28
      [<ffffff8008413b98>] analogix_dp_disable_psr+0x60/0xa8
      [<ffffff800840da3c>] analogix_dp_psr_work+0x4c/0x90
      [<ffffff80080bb09c>] process_one_work+0x1d4/0x348
      [<ffffff80080bb258>] worker_thread+0x48/0x478
      [<ffffff80080c11fc>] kthread+0x12c/0x130
      [<ffffff8008084290>] ret_from_fork+0x10/0x18
      
      Changing rockchip_dp_device::psr_lock to a mutex rather
      than spinlock seems to fix the issue.
      
      Signed-off-by: default avatarEmil Renner Berthing <kernel@esmil.dk>
      Tested-by: default avatarEnric Balletbo i Serra <enric.balletbo@collabora.com>
      Signed-off-by: default avatarMark Yao <mark.yao@rock-chips.com>
      Link: https://patchwork.freedesktop.org/patch/msgid/20171004175346.11956-1-kernel@esmil.dk
      44419ce7
  10. Nov 10, 2017
  11. Nov 09, 2017