From: Lars-Peter Clausen <lars@metafoo.de>
To: Shawn Guo <shawn.guo@linaro.org>
Cc: alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH] ASoC: generic-dmaengine-pcm: use a more common dma name
Date: Mon, 22 Apr 2013 15:50:10 +0200 [thread overview]
Message-ID: <51754012.4090709@metafoo.de> (raw)
In-Reply-To: <1366638525-27625-1-git-send-email-shawn.guo@linaro.org>
On 04/22/2013 03:48 PM, Shawn Guo wrote:
> The examples in Documentation/devicetree/bindings/dma/dma.txt recommends
> the name for dma channel doing both RX and TX to be "rx-tx". This
> becomes a common pattern that has been adopted by platforms that
> converts to generic DMA bindings. Let's follow this common pattern in
> generic-dmaengine-pcm.
>
> Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
Acked-by: Lars-Peter Clausen <lars@metafoo.de>
Thanks.
> ---
> sound/soc/soc-generic-dmaengine-pcm.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/sound/soc/soc-generic-dmaengine-pcm.c b/sound/soc/soc-generic-dmaengine-pcm.c
> index 5fd5ed4..98e1310 100644
> --- a/sound/soc/soc-generic-dmaengine-pcm.c
> +++ b/sound/soc/soc-generic-dmaengine-pcm.c
> @@ -227,7 +227,7 @@ static void dmaengine_pcm_request_chan_of(struct dmaengine_pcm *pcm,
> return;
>
> if (pcm->flags & SND_DMAENGINE_PCM_FLAG_HALF_DUPLEX) {
> - pcm->chan[0] = of_dma_request_slave_channel(of_node, "tx_rx");
> + pcm->chan[0] = of_dma_request_slave_channel(of_node, "rx-tx");
> pcm->chan[1] = pcm->chan[0];
> } else {
> for (i = SNDRV_PCM_STREAM_PLAYBACK; i <= SNDRV_PCM_STREAM_CAPTURE; i++) {
next prev parent reply other threads:[~2013-04-22 13:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-22 13:48 [PATCH] ASoC: generic-dmaengine-pcm: use a more common dma name Shawn Guo
2013-04-22 13:50 ` Lars-Peter Clausen [this message]
2013-04-23 10:35 ` 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=51754012.4090709@metafoo.de \
--to=lars@metafoo.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=shawn.guo@linaro.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 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.