From: Mark Brown <broonie@sirena.org.uk>
To: Jarkko Nikula <jhnikula@gmail.com>
Cc: kyungmin.park@samsung.com, alsa-devel@alsa-project.org,
peter.ujfalusi@nokia.com,
Joonyoung Shim <jy0922.shim@samsung.com>,
bhmin@samsung.com
Subject: Re: [PATCH] ASoC: OMAP: Add checking to detect bufferless pcms
Date: Wed, 22 Apr 2009 09:43:49 +0100 [thread overview]
Message-ID: <20090422084349.GB10356@sirena.org.uk> (raw)
In-Reply-To: <bd7b27490904220130g13602721u6ae4fd3dca21fde5@mail.gmail.com>
On Wed, Apr 22, 2009 at 11:30:32AM +0300, Jarkko Nikula wrote:
> On Wed, Apr 22, 2009 at 4:56 AM, Joonyoung Shim <jy0922.shim@samsung.com>wrote:
> > + /* return if this is a bufferless transfer e.g.
> > + * codec <--> BT codec or GSM modem -- lg FIXME */
> > if (!dma_data)
> > - return -ENODEV;
> > + return 0;
> I see exactly similar lines in s3c24xx-pcm.c but don't point now the use
> case where this is used and I don't have idea what is this all about.
The use case is for dummy DAIs used to represent bluetooth and similar -
they aren't going to do any DMA so don't pass anything to the platform.
> Is this something where DAI driver or another end of connection is used to
> provide clocking and the whole setup is then controlled with ALSA PCM API?
> Somehow I have the feeling that would there be a better way to achieve it
> than with dummy bufferless transfer?
The host isn't transferring any data at all in these cases. Ideally
we'd support multiple platforms and there'd be a dummy platform driver
to go with the dummy DAI driver.
next prev parent reply other threads:[~2009-04-22 8:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 1:56 [PATCH] ASoC: OMAP: Add checking to detect bufferless pcms Joonyoung Shim
2009-04-22 8:30 ` Jarkko Nikula
2009-04-22 8:43 ` Mark Brown [this message]
2009-04-22 9:01 ` Jarkko Nikula
2009-04-22 9:26 ` Mark Brown
2009-04-22 9:42 ` Peter Ujfalusi
2009-04-22 9:48 ` Joonyoung Shim
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=20090422084349.GB10356@sirena.org.uk \
--to=broonie@sirena.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=bhmin@samsung.com \
--cc=jhnikula@gmail.com \
--cc=jy0922.shim@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=peter.ujfalusi@nokia.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