From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Bo Shen <voice.shen@atmel.com>
Cc: plagnioj@jcrosoft.com, nicolas.ferre@atmel.com,
linux-arm-kernel@lists.infradead.org,
devicetree-discuss@lists.ozlabs.org, linux-sound@vger.kernel.org,
alsa-devel@alsa-project.org
Subject: Re: [PATCH 2/2] ASoC: atmel-pcm: add dma support
Date: Tue, 20 Nov 2012 17:57:30 +0900 [thread overview]
Message-ID: <20121120085728.GX10560@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1353400698-19384-2-git-send-email-voice.shen@atmel.com>
[-- Attachment #1: Type: text/plain, Size: 386 bytes --]
On Tue, Nov 20, 2012 at 04:38:18PM +0800, Bo Shen wrote:
> Change xfer_size name to apply to PDC and DMA aswell.
> Specify overrun bit in interrupt mask.
> Add dmaengine specific routines and replace PDC ones in
> pcm_ops if appropriate.
> Uses cyclic DMA API for queuing samples.
If you're using dmaengine you really need a *very* good reason not to
use the core dmaengine support...
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Bo Shen <voice.shen@atmel.com>
Cc: plagnioj@jcrosoft.com, nicolas.ferre@atmel.com,
linux-arm-kernel@lists.infradead.org,
devicetree-discuss@lists.ozlabs.org, linux-sound@vger.kernel.org,
alsa-devel@alsa-project.org
Subject: Re: [PATCH 2/2] ASoC: atmel-pcm: add dma support
Date: Tue, 20 Nov 2012 08:57:30 +0000 [thread overview]
Message-ID: <20121120085728.GX10560@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1353400698-19384-2-git-send-email-voice.shen@atmel.com>
[-- Attachment #1: Type: text/plain, Size: 386 bytes --]
On Tue, Nov 20, 2012 at 04:38:18PM +0800, Bo Shen wrote:
> Change xfer_size name to apply to PDC and DMA aswell.
> Specify overrun bit in interrupt mask.
> Add dmaengine specific routines and replace PDC ones in
> pcm_ops if appropriate.
> Uses cyclic DMA API for queuing samples.
If you're using dmaengine you really need a *very* good reason not to
use the core dmaengine support...
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ASoC: atmel-pcm: add dma support
Date: Tue, 20 Nov 2012 17:57:30 +0900 [thread overview]
Message-ID: <20121120085728.GX10560@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1353400698-19384-2-git-send-email-voice.shen@atmel.com>
On Tue, Nov 20, 2012 at 04:38:18PM +0800, Bo Shen wrote:
> Change xfer_size name to apply to PDC and DMA aswell.
> Specify overrun bit in interrupt mask.
> Add dmaengine specific routines and replace PDC ones in
> pcm_ops if appropriate.
> Uses cyclic DMA API for queuing samples.
If you're using dmaengine you really need a *very* good reason not to
use the core dmaengine support...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20121120/54b17acb/attachment.sig>
next prev parent reply other threads:[~2012-11-20 8:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-20 8:38 [PATCH 1/2] ASoC: atmel-ssc: add phybase in device structure Bo Shen
2012-11-20 8:38 ` Bo Shen
2012-11-20 8:38 ` Bo Shen
2012-11-20 8:38 ` [PATCH 2/2] ASoC: atmel-pcm: add dma support Bo Shen
2012-11-20 8:38 ` Bo Shen
2012-11-20 8:38 ` Bo Shen
2012-11-20 8:57 ` Mark Brown [this message]
2012-11-20 8:57 ` Mark Brown
2012-11-20 8:57 ` Mark Brown
2012-11-20 9:22 ` Bo Shen
2012-11-20 9:22 ` Bo Shen
2012-11-20 9:22 ` Bo Shen
2012-11-20 9:24 ` Mark Brown
2012-11-20 9:24 ` Mark Brown
2012-11-20 9:24 ` Mark Brown
2012-11-20 9:21 ` [PATCH 1/2] ASoC: atmel-ssc: add phybase in device structure Mark Brown
2012-11-20 9:21 ` Mark Brown
2012-11-20 9:21 ` Mark Brown
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=20121120085728.GX10560@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-sound@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=plagnioj@jcrosoft.com \
--cc=voice.shen@atmel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.