1. 20 5月, 2020 2 次提交
  2. 05 9月, 2019 1 次提交
    • R
      drm/msm: Use the correct dma_sync calls harder · 9f614197
      Rob Clark 提交于
      Looks like the dma_sync calls don't do what we want on armv7 either.
      Fixes:
      
        Unable to handle kernel paging request at virtual address 50001000
        pgd = (ptrval)
        [50001000] *pgd=00000000
        Internal error: Oops: 805 [#1] SMP ARM
        Modules linked in:
        CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.3.0-rc6-00271-g9f159ae0 #4
        Hardware name: Freescale i.MX53 (Device Tree Support)
        PC is at v7_dma_clean_range+0x20/0x38
        LR is at __dma_page_cpu_to_dev+0x28/0x90
        pc : [<c011c76c>]    lr : [<c01181c4>]    psr: 20000013
        sp : d80b5a88  ip : de96c000  fp : d840ce6c
        r10: 00000000  r9 : 00000001  r8 : d843e010
        r7 : 00000000  r6 : 00008000  r5 : ddb6c000  r4 : 00000000
        r3 : 0000003f  r2 : 00000040  r1 : 50008000  r0 : 50001000
        Flags: nzCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment none
        Control: 10c5387d  Table: 70004019  DAC: 00000051
        Process swapper/0 (pid: 1, stack limit = 0x(ptrval))
      Signed-off-by: NRob Clark <robdclark@chromium.org>
      Fixes: 3de433c5 ("drm/msm: Use the correct dma_sync calls in msm_gem")
      Tested-by: NFabio Estevam <festevam@gmail.com>
      9f614197
  3. 04 9月, 2019 1 次提交
    • S
      drm/msm: drop use of drmP.h · feea39a8
      Sam Ravnborg 提交于
      Drop the deprecated drmP.h header file, and trim msm_drv.h
      to the relevant include files.
      
      This resulted in a suprisingly many edits as many files relied
      on headers included via msm_drv.h.
      But msm_drv.h is not supposed to carry include files it do not need, so
      the individual files have to include what extra they needs.
      
      v2:
      - Rebased on top of https://gitlab.freedesktop.org/drm/msm.git msm-next
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      Cc: Rob Clark <robdclark@gmail.com>
      Cc: Sean Paul <sean@poorly.run>
      Cc: David Airlie <airlied@linux.ie>
      Cc: Daniel Vetter <daniel@ffwll.ch>
      Cc: Jordan Crouse <jcrouse@codeaurora.org>
      Cc: Jeykumar Sankaran <jsanka@codeaurora.org>
      Cc: Bruce Wang <bzwang@chromium.org>
      Cc: Shayenne Moura <shayenneluzmoura@gmail.com>
      Cc: Mamta Shukla <mamtashukla555@gmail.com>
      Cc: Jonathan Marek <jonathan@marek.ca>
      Cc: Carsten Behling <carsten.behling@googlemail.com>
      Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
      Cc: Maxime Ripard <maxime.ripard@bootlin.com>
      Cc: Paul Kocialkowski <paul.kocialkowski@bootlin.com>
      Cc: Sibi Sankar <sibis@codeaurora.org>
      Cc: Todor Tomov <todor.tomov@linaro.org>
      Cc: linux-arm-msm@vger.kernel.org
      Cc: freedreno@lists.freedesktop.org
      Signed-off-by: NSean Paul <seanpaul@chromium.org>
      Link: https://patchwork.freedesktop.org/patch/msgid/20190804065551.GA5211@ravnborg.org
      feea39a8
  4. 13 8月, 2019 1 次提交
  5. 01 8月, 2019 1 次提交
    • R
      drm/msm: Use the correct dma_sync calls in msm_gem · 3de433c5
      Rob Clark 提交于
      [subject was: drm/msm: shake fist angrily at dma-mapping]
      
      So, using dma_sync_* for our cache needs works out w/ dma iommu ops, but
      it falls appart with dma direct ops.  The problem is that, depending on
      display generation, we can have either set of dma ops (mdp4 and dpu have
      iommu wired to mdss node, which maps to toplevel drm device, but mdp5
      has iommu wired up to the mdp sub-node within mdss).
      
      Fixes this splat on mdp5 devices:
      
         Unable to handle kernel paging request at virtual address ffffffff80000000
         Mem abort info:
           ESR = 0x96000144
           Exception class = DABT (current EL), IL = 32 bits
           SET = 0, FnV = 0
           EA = 0, S1PTW = 0
         Data abort info:
           ISV = 0, ISS = 0x00000144
           CM = 1, WnR = 1
         swapper pgtable: 4k pages, 48-bit VAs, pgdp=00000000810e4000
         [ffffffff80000000] pgd=0000000000000000
         Internal error: Oops: 96000144 [#1] SMP
         Modules linked in: btqcomsmd btqca bluetooth cfg80211 ecdh_generic ecc rfkill libarc4 panel_simple msm wcnss_ctrl qrtr_smd drm_kms_helper venus_enc venus_dec videobuf2_dma_sg videobuf2_memops drm venus_core ipv6 qrtr qcom_wcnss_pil v4l2_mem2mem qcom_sysmon videobuf2_v4l2 qmi_helpers videobuf2_common crct10dif_ce mdt_loader qcom_common videodev qcom_glink_smem remoteproc bmc150_accel_i2c bmc150_magn_i2c bmc150_accel_core bmc150_magn snd_soc_lpass_apq8016 snd_soc_msm8916_analog mms114 mc nf_defrag_ipv6 snd_soc_lpass_cpu snd_soc_apq8016_sbc industrialio_triggered_buffer kfifo_buf snd_soc_lpass_platform snd_soc_msm8916_digital drm_panel_orientation_quirks
         CPU: 2 PID: 33 Comm: kworker/2:1 Not tainted 5.3.0-rc2 #1
         Hardware name: Samsung Galaxy A5U (EUR) (DT)
         Workqueue: events deferred_probe_work_func
         pstate: 80000005 (Nzcv daif -PAN -UAO)
         pc : __clean_dcache_area_poc+0x20/0x38
         lr : arch_sync_dma_for_device+0x28/0x30
         sp : ffff0000115736a0
         x29: ffff0000115736a0 x28: 0000000000000001
         x27: ffff800074830800 x26: ffff000011478000
         x25: 0000000000000000 x24: 0000000000000001
         x23: ffff000011478a98 x22: ffff800009fd1c10
         x21: 0000000000000001 x20: ffff800075ad0a00
         x19: 0000000000000000 x18: ffff0000112b2000
         x17: 0000000000000000 x16: 0000000000000000
         x15: 00000000fffffff0 x14: ffff000011455d70
         x13: 0000000000000000 x12: 0000000000000028
         x11: 0000000000000001 x10: ffff00001106c000
         x9 : ffff7e0001d6b380 x8 : 0000000000001000
         x7 : ffff7e0001d6b380 x6 : ffff7e0001d6b382
         x5 : 0000000000000000 x4 : 0000000000001000
         x3 : 000000000000003f x2 : 0000000000000040
         x1 : ffffffff80001000 x0 : ffffffff80000000
         Call trace:
          __clean_dcache_area_poc+0x20/0x38
          dma_direct_sync_sg_for_device+0xb8/0xe8
          get_pages+0x22c/0x250 [msm]
          msm_gem_get_and_pin_iova+0xdc/0x168 [msm]
          ...
      
      Fixes the combination of two patches:
      
      Fixes: 0036bc73 (drm/msm: stop abusing dma_map/unmap for cache)
      Fixes: 449fa54d (dma-direct: correct the physical addr in dma_direct_sync_sg_for_cpu/device)
      Tested-by: NStephan Gerhold <stephan@gerhold.net>
      Signed-off-by: NRob Clark <robdclark@chromium.org>
      [seanpaul changed subject to something more desriptive]
      Signed-off-by: NSean Paul <seanpaul@chromium.org>
      Link: https://patchwork.freedesktop.org/patch/msgid/20190730214633.17820-1-robdclark@gmail.com
      3de433c5
  6. 23 7月, 2019 1 次提交
    • R
      drm/msm: stop abusing dma_map/unmap for cache · 0036bc73
      Rob Clark 提交于
      Recently splats like this started showing up:
      
         WARNING: CPU: 4 PID: 251 at drivers/iommu/dma-iommu.c:451 __iommu_dma_unmap+0xb8/0xc0
         Modules linked in: ath10k_snoc ath10k_core fuse msm ath mac80211 uvcvideo cfg80211 videobuf2_vmalloc videobuf2_memops vide
         CPU: 4 PID: 251 Comm: kworker/u16:4 Tainted: G        W         5.2.0-rc5-next-20190619+ #2317
         Hardware name: LENOVO 81JL/LNVNB161216, BIOS 9UCN23WW(V1.06) 10/25/2018
         Workqueue: msm msm_gem_free_work [msm]
         pstate: 80c00005 (Nzcv daif +PAN +UAO)
         pc : __iommu_dma_unmap+0xb8/0xc0
         lr : __iommu_dma_unmap+0x54/0xc0
         sp : ffff0000119abce0
         x29: ffff0000119abce0 x28: 0000000000000000
         x27: ffff8001f9946648 x26: ffff8001ec271068
         x25: 0000000000000000 x24: ffff8001ea3580a8
         x23: ffff8001f95ba010 x22: ffff80018e83ba88
         x21: ffff8001e548f000 x20: fffffffffffff000
         x19: 0000000000001000 x18: 00000000c00001fe
         x17: 0000000000000000 x16: 0000000000000000
         x15: ffff000015b70068 x14: 0000000000000005
         x13: 0003142cc1be1768 x12: 0000000000000001
         x11: ffff8001f6de9100 x10: 0000000000000009
         x9 : ffff000015b78000 x8 : 0000000000000000
         x7 : 0000000000000001 x6 : fffffffffffff000
         x5 : 0000000000000fff x4 : ffff00001065dbc8
         x3 : 000000000000000d x2 : 0000000000001000
         x1 : fffffffffffff000 x0 : 0000000000000000
         Call trace:
          __iommu_dma_unmap+0xb8/0xc0
          iommu_dma_unmap_sg+0x98/0xb8
          put_pages+0x5c/0xf0 [msm]
          msm_gem_free_work+0x10c/0x150 [msm]
          process_one_work+0x1e0/0x330
          worker_thread+0x40/0x438
          kthread+0x12c/0x130
          ret_from_fork+0x10/0x18
         ---[ end trace afc0dc5ab81a06bf ]---
      
      Not quite sure what triggered that, but we really shouldn't be abusing
      dma_{map,unmap}_sg() for cache maint.
      
      Cc: Stephen Boyd <sboyd@kernel.org>
      Tested-by: NStephen Boyd <swboyd@chromium.org>
      Reviewed-by: NJordan Crouse <jcrouse@codeaurora.org>
      Signed-off-by: NRob Clark <robdclark@chromium.org>
      Signed-off-by: NSean Paul <seanpaul@chromium.org>
      Link: https://patchwork.freedesktop.org/patch/msgid/20190630124735.27786-1-robdclark@gmail.com
      0036bc73
  7. 26 6月, 2019 1 次提交
  8. 19 6月, 2019 2 次提交
  9. 15 5月, 2019 1 次提交
  10. 20 4月, 2019 1 次提交
  11. 19 4月, 2019 1 次提交
  12. 19 2月, 2019 1 次提交
  13. 29 1月, 2019 1 次提交
  14. 25 1月, 2019 1 次提交
  15. 10 1月, 2019 1 次提交
  16. 12 12月, 2018 11 次提交
  17. 03 8月, 2018 1 次提交
  18. 04 6月, 2018 1 次提交
  19. 19 4月, 2018 1 次提交
  20. 19 3月, 2018 1 次提交
  21. 20 2月, 2018 1 次提交
  22. 14 12月, 2017 1 次提交
  23. 29 10月, 2017 1 次提交
    • R
      drm/msm: add special _get_vaddr_active() for cmdstream dumps · fad33f4b
      Rob Clark 提交于
      Prep work for adding a debugfs file that dumps just submits which
      trigger hangs/faults.  In this case the bo may already be in the
      MADV_DONTNEED state, but will be still on the active list (since
      the submit hasn't completed yet).  So the normal check that the
      bo is in the WILLNEED state does not apply.  (But of course the bo
      should definitely not be in the PURGED state!)
      Signed-off-by: NRob Clark <robdclark@gmail.com>
      fad33f4b
  24. 28 10月, 2017 1 次提交
  25. 13 10月, 2017 1 次提交
  26. 12 10月, 2017 1 次提交
  27. 23 8月, 2017 1 次提交
  28. 02 8月, 2017 1 次提交
    • H
      drm/msm: fix WARN_ON in add_vma() with no iommu · b3949a9a
      Hans Verkuil 提交于
      While I was testing the upcoming adv7533 CEC support with my Dragonboard c410
      I encountered this warning several times during boot:
      
      [    4.408309] WARNING: CPU: 3 PID: 1347 at drivers/gpu/drm/msm/msm_gem.c:312 add_vma+0x78/0x88 [msm]
      [    4.412951] Modules linked in: snd_soc_hdmi_codec adv7511 cec qcom_wcnss_pil msm mdt_loader drm_kms_helper msm_rng rng_core drm
      [    4.421728] CPU: 3 PID: 1347 Comm: kworker/3:3 Not tainted 4.13.0-rc1-dragonboard #111
      [    4.433090] Hardware name: Qualcomm Technologies, Inc. APQ 8016 SBC (DT)
      [    4.441081] Workqueue: events deferred_probe_work_func
      [    4.447929] task: ffff800031243600 task.stack: ffff800003394000
      [    4.453023] PC is at add_vma+0x78/0x88 [msm]
      [    4.458823] LR is at _msm_gem_new+0xd4/0x188 [msm]
      [    4.463207] pc : [<ffff000000ac01f8>] lr : [<ffff000000ac06b4>] pstate: 40000145
      [    4.467811] sp : ffff8000033978a0
      [    4.475357] x29: ffff8000033978a0 x28: ffff8000031dea18
      [    4.478572] x27: ffff800003933a00 x26: ffff800003b39800
      [    4.483953] x25: ffff8000338ff800 x24: 0000000000000001
      [    4.489249] x23: 0000000000000000 x22: ffff800003b39800
      [    4.494544] x21: ffff8000338ff800 x20: 0000000000000000
      [    4.499839] x19: ffff800003932600 x18: 0000000000000001
      [    4.505135] x17: 0000ffff8969e9e0 x16: ffff7e00000ce7a0
      [    4.510429] x15: ffffffffffffffff x14: ffff8000833977ef
      [    4.515724] x13: ffff8000033977f3 x12: 0000000000000038
      [    4.521020] x11: 0101010101010101 x10: ffffff7f7fff7f7f
      [    4.526315] x9 : 0000000000000000 x8 : ffff800003932800
      [    4.531633] x7 : 0000000000000000 x6 : 000000000000003f
      [    4.531644] x5 : 0000000000000040 x4 : 0000000000000000
      [    4.531650] x3 : ffff800031243600 x2 : 0000000000000000
      [    4.531655] x1 : 0000000000000000 x0 : 0000000000000000
      [    4.531670] Call trace:
      [    4.531676] Exception stack(0xffff8000033976c0 to 0xffff8000033977f0)
      [    4.531683] 76c0: ffff800003932600 0001000000000000 ffff8000033978a0 ffff000000ac01f8
      [    4.531688] 76e0: 0000000000000140 0000000000000000 ffff800003932550 ffff800003397780
      [    4.531694] 7700: ffff800003397730 ffff000008261ce8 0000000000000000 ffff8000031d2f80
      [    4.531699] 7720: ffff800003397800 ffff0000081d671c 0000000000000140 0000000000000000
      [    4.531705] 7740: ffff000000ac04c0 0000000000004003 ffff800003397908 00000000014080c0
      [    4.531710] 7760: 0000000000000000 ffff800003b39800 0000000000000000 0000000000000000
      [    4.531716] 7780: 0000000000000000 ffff800031243600 0000000000000000 0000000000000040
      [    4.531721] 77a0: 000000000000003f 0000000000000000 ffff800003932800 0000000000000000
      [    4.531726] 77c0: ffffff7f7fff7f7f 0101010101010101 0000000000000038 ffff8000033977f3
      [    4.531730] 77e0: ffff8000833977ef ffffffffffffffff
      [    4.531881] [<ffff000000ac01f8>] add_vma+0x78/0x88 [msm]
      [    4.532011] [<ffff000000ac06b4>] _msm_gem_new+0xd4/0x188 [msm]
      [    4.532134] [<ffff000000ac1900>] msm_gem_new+0x10/0x18 [msm]
      [    4.532260] [<ffff000000acb274>] msm_dsi_host_modeset_init+0x17c/0x268 [msm]
      [    4.532384] [<ffff000000ac9024>] msm_dsi_modeset_init+0x34/0x1b8 [msm]
      [    4.532504] [<ffff000000ab6168>] modeset_init+0x408/0x488 [msm]
      [    4.532623] [<ffff000000ab6c4c>] mdp5_kms_init+0x2b4/0x338 [msm]
      [    4.532745] [<ffff000000abeff8>] msm_drm_bind+0x218/0x4e8 [msm]
      [    4.532755] [<ffff00000855d744>] try_to_bring_up_master+0x1f4/0x318
      [    4.532762] [<ffff00000855d900>] component_add+0x98/0x180
      [    4.532887] [<ffff000000ac8da0>] dsi_dev_probe+0x18/0x28 [msm]
      [    4.532895] [<ffff000008565fe8>] platform_drv_probe+0x58/0xc0
      [    4.532901] [<ffff00000856410c>] driver_probe_device+0x324/0x458
      [    4.532907] [<ffff00000856440c>] __device_attach_driver+0xac/0x170
      [    4.532913] [<ffff000008561ef4>] bus_for_each_drv+0x4c/0x98
      [    4.532918] [<ffff000008563c38>] __device_attach+0xc0/0x160
      [    4.532924] [<ffff000008564530>] device_initial_probe+0x10/0x18
      [    4.532929] [<ffff000008562f84>] bus_probe_device+0x94/0xa0
      [    4.532934] [<ffff0000085635d4>] deferred_probe_work_func+0x8c/0xe8
      [    4.532941] [<ffff0000080d79bc>] process_one_work+0x1d4/0x330
      [    4.532946] [<ffff0000080d7b60>] worker_thread+0x48/0x468
      [    4.532952] [<ffff0000080ddae4>] kthread+0x12c/0x130
      [    4.532958] [<ffff000008082f10>] ret_from_fork+0x10/0x40
      [    4.532962] ---[ end trace b1ac6888ec40b0bb ]---
      Signed-off-by: NHans Verkuil <hans.verkuil@cisco.com>
      Signed-off-by: NRob Clark <robdclark@gmail.com>
      b3949a9a