1. 19 Aug, 2020 1 commit
    • Jessica Clarke's avatar
      XDMA: Mark engine as not running when stopping after timeouts · cf3611e0
      Jessica Clarke authored
      Unlike engine_start, which sets the engine's running field itself,
      engine_stop instead requires its callers to clear the field. However,
      not all of them do, and notably the timeout handlers do not, meaning
      that after a request times out and we stop the engine we never start it
      again, causing all future transfers on the channel to hit the software
      timeout.
      
      Instead, set running to 0 inside xdma_engine_stop to mirror engine_start
      to both fix the bug and prevent future ones creeping in.
      cf3611e0
  2. 12 Aug, 2020 1 commit
  3. 24 Jul, 2020 1 commit
  4. 30 Jun, 2020 3 commits
  5. 23 Jun, 2020 1 commit
  6. 22 Jun, 2020 2 commits
  7. 16 Jun, 2020 1 commit
  8. 09 Jun, 2020 1 commit
    • Julien's avatar
      xdma_thread: fix cpu node bug · 7fc246ee
      Julien authored
      The number of threads is arbitrarily set to 8 and we iterate over 8 cpus
      without knowing if we really have 8 cpus. This causes a call to
      cpu_to_node with an index that is out of bound, thus returning an
      undefined number, which crashes later when calling
      kthread_create_on_node.
      Fix this by iterating over the online cpus stopping when reaching the
      number of threads that is specified.
      7fc246ee
  9. 19 May, 2020 1 commit
  10. 27 Feb, 2020 3 commits
  11. 24 Feb, 2020 1 commit
    • Bryce Hathaway's avatar
      Fixes a design error revealed by running on aarch64. · d1f334b1
      Bryce Hathaway authored
      Simply put, you cannot call wait_event_interruptible_timeout while
      holding a spin_lock. The reason the driver got away with this on
      x86 is because the hardware is somehow fast enough so that the
      condition is never false and hence no scheduling ever needs to
      occur.
      d1f334b1
  12. 03 Feb, 2020 1 commit
  13. 21 Jan, 2020 1 commit
  14. 20 Jan, 2020 1 commit
  15. 17 Jan, 2020 1 commit
  16. 03 Jan, 2020 1 commit
  17. 23 Dec, 2019 5 commits
  18. 20 Dec, 2019 2 commits
  19. 18 Dec, 2019 1 commit
  20. 04 Nov, 2019 1 commit
  21. 22 Aug, 2019 1 commit
  22. 31 Jul, 2019 1 commit
  23. 22 Jul, 2019 2 commits
  24. 17 Jul, 2019 1 commit
  25. 16 Jul, 2019 1 commit
  26. 07 Jun, 2019 3 commits
  27. 16 Apr, 2019 1 commit