linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: kernel@martin.sperl.org (Martin Sperl)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/8 v4] bcm2835 DMA slave support
Date: Thu, 17 Mar 2016 14:17:16 +0100	[thread overview]
Message-ID: <56EAAE5C.9060401@martin.sperl.org> (raw)
In-Reply-To: <1458156302-4359-1-git-send-email-eric@anholt.net>

On 16.03.2016 20:24, Eric Anholt wrote:
> Here's the series for DMA slave and memcpy support for 2835, with the
> DT changes to enable the remaining channels dropped out while that
> goes through review.  I had to do some minor conflict resolution, but
> it was pretty mechanical, and I tested again with dmatest on the last
> patch.
>
> Martin Sperl (8):
>    dmaengine: bcm2835: set residue_granularity field
>    dmaengine: bcm2835: remove unnecessary masking of dma channels
>    dmaengine: bcm2835: add additional defines for DMA-registers
>    dmaengine: bcm2835: move cyclic member from bcm2835_chan into
>      bcm2835_desc
>    dmaengine: bcm2835: move controlblock chain generation into separate
>      method
>    dmaengine: bcm2835: limit max length based on channel type
>    dmaengine: bcm2835: add slave_sg support to bcm2835-dma
>    dmaengine: bcm2835: add dma_memcopy support to bcm2835-dma
>
I have successfully tested this modified patch-series
playing BigBuckBunny on:
* fb-tft device (fb_st7735r) - via spi-bcm2835 using slave_sg dma
* I2S Hifiberry DAC (snd_soc_hifiberry_dac) - via bcm2835-i2s using 
cyclic dma

Required additional patches to make this work
(especially I2S support, which is non-working since ):
* the clock-patchsets:
  * [PATCH 0/6] clk: bcm2835: fixes clk-bcm2835 driver issues
     (most are reviewed by Eric)
  * [PATCH 0/3] reorganize clock initialization and add PCM clock
     (no reviewed/acked so far)
* i2s patchset to enable the use of the clock framework
  * [PATCH V2 0/3] ASOC: bcm2835: move bcm2835-i2s to use clock framework
     (if I remember correctly Mark Brown has merged the driver patches)
* out of tree drivers for Hifiberry DAC
    (I guess I should upstream those...)

Tested-by: Martin Sperl <kernel@martin.sperl.org>

  parent reply	other threads:[~2016-03-17 13:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-16 19:24 [PATCH 0/8 v4] bcm2835 DMA slave support Eric Anholt
2016-03-16 19:24 ` [PATCH 1/8] dmaengine: bcm2835: set residue_granularity field Eric Anholt
2016-03-16 19:24 ` [PATCH 2/8] dmaengine: bcm2835: remove unnecessary masking of dma channels Eric Anholt
2016-03-16 19:24 ` [PATCH 3/8] dmaengine: bcm2835: add additional defines for DMA-registers Eric Anholt
2016-03-16 19:24 ` [PATCH 4/8] dmaengine: bcm2835: move cyclic member from bcm2835_chan into bcm2835_desc Eric Anholt
2016-03-16 19:24 ` [PATCH 5/8] dmaengine: bcm2835: move controlblock chain generation into separate method Eric Anholt
2016-03-16 19:25 ` [PATCH 6/8] dmaengine: bcm2835: limit max length based on channel type Eric Anholt
2016-03-16 19:25 ` [PATCH 7/8] dmaengine: bcm2835: add slave_sg support to bcm2835-dma Eric Anholt
2016-03-16 19:25 ` [PATCH 8/8] dmaengine: bcm2835: add dma_memcopy " Eric Anholt
2016-03-17 10:22 ` [PATCH 0/8 v4] bcm2835 DMA slave support Martin Sperl
2016-03-17 13:17 ` Martin Sperl [this message]
2016-04-05 18:03 ` Vinod Koul

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56EAAE5C.9060401@martin.sperl.org \
    --to=kernel@martin.sperl.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).