From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Leo Yan <leoy@marvell.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: Questions for dummy codec driver
Date: Wed, 21 Sep 2011 13:56:07 +0100 [thread overview]
Message-ID: <20110921125607.GC25620@sirena.org.uk> (raw)
In-Reply-To: <4E794A96.9040206@marvell.com>
On Wed, Sep 21, 2011 at 10:23:18AM +0800, Leo Yan wrote:
> I have a question for the dummy codec.
Don't start new threads by randomly replying to unrelated mails.
> As you know, sometimes maybe we only need set the timing from the
> processor, and codec just only need tx/rx data; So there do not need
> the codec driver.
Even a dumb CODEC will have some constraints on things like the sample
rates it can support which need to be conveyed to the framework and
ideally the audio routing out of the CODEC should be visible for
integration with any external output drivers or similar.
> After browser the code, there have NO such a dummy codec driver; and
> for soc-core, there have not such flags to support this situation.
> Only what i get is sound/soc/codecs/spdif_transciever.c, but it's
> specific for TI's DaVinci platform.
Not at all, what makes you believe that it is platform specific?
next prev parent reply other threads:[~2011-09-21 12:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-20 7:09 [PATCH] ASoC: fsl: Fix error handling if platform_device_add fails Axel Lin
2011-09-20 11:21 ` Liam Girdwood
2011-09-20 12:04 ` Mark Brown
2011-09-20 16:00 ` Timur Tabi
2011-09-21 2:23 ` Questions for dummy codec driver Leo Yan
2011-09-21 12:56 ` Mark Brown [this message]
2011-09-22 1:42 ` Leo Yan
2011-09-26 21:47 ` Mark Brown
2011-09-27 2:08 ` [PATCH] ASoC: fsl: Fix error handling if platform_device_add fails Tabi Timur-B04825
2011-09-27 2:21 ` Axel Lin
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=20110921125607.GC25620@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=leoy@marvell.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®