1. 21 11月, 2015 1 次提交
    • A
      ASoC: samsung: pass filter function as pointer · 9bdca822
      Arnd Bergmann 提交于
      As we are now passing the filter data as pointers to the drivers,
      we can take the final step and also pass the filter function the
      same way. I'm keeping this change separate, as there it's less
      obvious that this is a net win.
      
      Upsides of this are:
      
      - The ASoC drivers are completely independent from the DMA engine
        implementation, which simplifies the Kconfig logic and in theory
        allows the same sound drivers to be built in a kernel that supports
        different kinds of dmaengine drivers.
      
      - Consistency with other subsystems and drivers
      
      On the other hand, we have a few downsides:
      
      - The s3c24xx-dma driver now needs to be built-in for the ac97 platform
        device to be instantiated on s3c2440.
      
      - samsung_dmaengine_pcm_config cannot be marked 'const' any more
        because the filter function pointer needs to be set at runtime.
        This is safe as long we don't have multiple different DMA engines
        in thet same system at runtime, but is nonetheless ugly.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Reviewed-by: NKrzysztof Kozlowski <k.kozlowski@samsung.com>
      Signed-off-by: NMark Brown <broonie@kernel.org>
      9bdca822
  2. 16 11月, 2015 1 次提交
  3. 27 10月, 2015 1 次提交
  4. 14 10月, 2015 1 次提交
  5. 24 9月, 2015 1 次提交
  6. 24 8月, 2015 1 次提交
  7. 23 8月, 2015 1 次提交
    • L
      dmaengine: Add support for the Analog Devices AXI-DMAC DMA controller · 0e3b67b3
      Lars-Peter Clausen 提交于
      Add support for the Analog Devices AXI-DMAC DMA controller. This controller
      is a soft peripheral that can be instantiated in a FPGA and is often used
      in Analog Devices' reference designs for FPGA platforms.
      
      The peripheral has various configuration options that can be selected at
      synthesis time and influence the supported features of the instantiated
      peripheral, those options are represented as device-tree properties to
      allow the driver to behave accordingly.
      
      The peripheral has a zero latency architecture, which means it is possible
      to switch from one to the next descriptor without any delay. This is
      archived by having a internal queue which can hold multiple descriptors.
      The driver supports this, which means it will submit new descriptors
      directly to the hardware until the queue is full and not wait for a
      descriptor to complete before the next one is submitted. Interrupts are
      used for the descriptor queue flow control.
      
      Currently the driver supports SG, cyclic and interleaved slave DMA.
      Signed-off-by: NLars-Peter Clausen <lars@metafoo.de>
      Signed-off-by: NVinod Koul <vinod.koul@intel.com>
      0e3b67b3
  8. 21 8月, 2015 1 次提交
    • D
      dmaengine: ioatdma: fix zero day warning on incompatible pointer type · aaecdebc
      Dave Jiang 提交于
      The 32bit build is creating this warning. Since we don't expect anyone
      actually use this on 32bit, restrict ioatdma to be built only on x86_64.
      This issue has long existed and only reason it's surfacing due to code
      refactoring.
      
         drivers/dma/ioat/dma.c: In function 'ioat_timer_event':
      >> drivers/dma/ioat/dma.c:870:39: warning: passing argument 2 of 'ioat_cleanup_preamble' from incompatible pointer type
           if (ioat_cleanup_preamble(ioat_chan, &phys_complete))
                                                ^
         drivers/dma/ioat/dma.c:577:13: note: expected 'u64 *' but argument is of type 'dma_addr_t *'
          static bool ioat_cleanup_preamble(struct ioatdma_chan *ioat_chan,
                      ^
      Signed-off-by: NDave Jiang <dave.jiang@intel.com>
      Signed-off-by: NVinod Koul <vinod.koul@intel.com>
      aaecdebc
  9. 20 8月, 2015 1 次提交
  10. 19 8月, 2015 1 次提交
  11. 28 7月, 2015 1 次提交
  12. 16 7月, 2015 1 次提交
  13. 26 5月, 2015 1 次提交
    • R
      dmaengine: pxa: add pxa dmaengine driver · a57e16cf
      Robert Jarzmik 提交于
      This is a new driver for pxa SoCs, which is also compatible with the former
      mmp_pdma.
      
      The rationale behind a new driver (as opposed to incremental patching) was :
      
       - the new driver relies on virt-dma, which obsoletes all the internal
         structures of mmp_pdma (sw_desc, hw_desc, ...), and by consequence all the
         functions
      
       - mmp_pdma allocates dma coherent descriptors containing not only hardware
         descriptors but linked list information
         The new driver only puts the dma hardware descriptors (ie. 4 u32) into the
         dma pool allocated memory. This changes completely the way descriptors are
         handled
      
       - the architecture behind the interrupt/tasklet management was rewritten to be
         more conforming to virt-dma
      
       - the buffers alignment is handled differently
         The former driver assumed that the DMA channel stopped between each
         descriptor. The new one chains descriptors to let the channel running. This
         is a necessary guarantee for real-time high bandwidth usecases such as video
         capture on "old" architectures such as pxa.
      
       - hot chaining / cold chaining / no chaining
         Whenever possible, submitting a descriptor "hot chains" it to a running
         channel. There is still no guarantee that the descriptor will be issued, as
         the channel might be stopped just before the descriptor is submitted. Yet
         this allows to submit several video buffers, and resubmit a buffer while
         another is under handling.
         As before, dma_async_issue_pending() is the only guarantee to have all the
         buffers issued.
         When an alignment issue is detected (ie. one address in a descriptor is not
         a multiple of 8), if the already running channel is in "aligned mode", the
         channel will stop, and restarted in "misaligned mode" to finished the issued
         list.
      
       - descriptors reusing
         A submitted, issued and completed descriptor can be reused, ie resubmitted if
         it was prepared with the proper flag (DMA_PREP_ACK).  Only a channel
         resources release will in this case release that buffer.
         This allows a rolling ring of buffers to be reused, where there are several
         thousands of hardware descriptors used (video buffer for example).
      
      Additionally, a set of more casual features is introduced :
       - debugging traces
       - lockless way to know if a descriptor is terminated or not
      
      The driver was tested on zylonite board (pxa3xx) and mioa701 (pxa27x),
      with dmatest, pxa_camera and pxamci.
      Signed-off-by: NRobert Jarzmik <robert.jarzmik@free.fr>
      Signed-off-by: NVinod Koul <vinod.koul@intel.com>
      a57e16cf
  14. 14 5月, 2015 1 次提交
  15. 27 4月, 2015 1 次提交
  16. 02 4月, 2015 2 次提交
  17. 01 4月, 2015 1 次提交
  18. 17 3月, 2015 1 次提交
  19. 07 3月, 2015 1 次提交
  20. 05 2月, 2015 1 次提交
  21. 24 1月, 2015 1 次提交
  22. 17 11月, 2014 2 次提交
  23. 06 11月, 2014 1 次提交
  24. 28 9月, 2014 1 次提交
  25. 23 9月, 2014 1 次提交
  26. 09 8月, 2014 1 次提交
  27. 07 8月, 2014 1 次提交
  28. 04 8月, 2014 1 次提交
  29. 30 7月, 2014 1 次提交
  30. 25 7月, 2014 1 次提交
  31. 17 7月, 2014 1 次提交
  32. 13 7月, 2014 1 次提交
  33. 02 6月, 2014 1 次提交
  34. 22 5月, 2014 1 次提交
  35. 30 4月, 2014 1 次提交
  36. 16 4月, 2014 1 次提交
    • J
      platform: Fix timberdale dependencies · 2dda47d1
      Jean Delvare 提交于
      VIDEO_TIMBERDALE selects TIMB_DMA which itself depends on
      MFD_TIMBERDALE, so VIDEO_TIMBERDALE should either select or depend on
      MFD_TIMBERDALE as well. I chose to make it depend on it because I
      think it makes more sense and it is consistent with what other options
      are doing.
      
      Adding a "|| HAS_IOMEM" to the TIMB_DMA dependencies silenced the
      kconfig warning about unmet direct dependencies but it was wrong:
      without MFD_TIMBERDALE, TIMB_DMA is useless as the driver has no
      device to bind to.
      Signed-off-by: NJean Delvare <jdelvare@suse.de>
      Cc: Vinod Koul <vinod.koul@intel.com>
      Cc: Dan Williams <dan.j.williams@intel.com>
      Cc: Mauro Carvalho Chehab <m.chehab@samsung.com>
      Signed-off-by: NVinod Koul <vinod.koul@intel.com>
      2dda47d1
  37. 05 4月, 2014 1 次提交
  38. 18 2月, 2014 1 次提交