From: Kuninori Morimoto <kuninori.morimoto.gx@gmail.com>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>,
Simon <horms@verge.net.au>, Mark Brown <broonie@kernel.org>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: About snd_dmaengine_pcm_trigger()
Date: Mon, 10 Mar 2014 21:47:20 -0700 (PDT) [thread overview]
Message-ID: <87pplttk8d.wl%kuninori.morimoto.gx@gmail.com> (raw)
In-Reply-To: <5316EC79.4090202@metafoo.de>
Hi Lars, Mark
> Make them ASoC components ;) I don't know the hardware, but looking at the
> code it doesn't seem to be that different from other modern host side audio
> processing units. But one step at a time, first maybe try and see if you can
> switch over to using the dmaengine PCM helper functions. Then later thing
> about how this all can be better integrated into the ASoC framework.
In my quick check,
I guess, my drivers (FSI/rcar) can use
${LINUX}/sound/core/pcm_dmaengine.c methods as 1st step.
OTOH, these drivers has PIO transfer too.
So, if ALSA has PIO method like pcm_pio.c (?) which has similar method,
it seems easy to switch over.
But what do you think ?
Best regards
---
Kuninori Morimoto
next prev parent reply other threads:[~2014-03-11 4:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 5:20 About snd_dmaengine_pcm_trigger() Kuninori Morimoto
2014-03-05 7:42 ` Lars-Peter Clausen
2014-03-05 8:32 ` Kuninori Morimoto
2014-03-05 9:20 ` Lars-Peter Clausen
2014-03-06 0:22 ` Kuninori Morimoto
2014-03-06 4:36 ` Mark Brown
2014-03-06 4:39 ` Kuninori Morimoto
2014-03-11 4:47 ` Kuninori Morimoto [this message]
2014-03-11 9:47 ` Lars-Peter Clausen
2014-03-11 9:55 ` Mark Brown
2014-03-12 0:28 ` Kuninori Morimoto
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=87pplttk8d.wl%kuninori.morimoto.gx@gmail.com \
--to=kuninori.morimoto.gx@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=horms@verge.net.au \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox