From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: pl bossart <bossart.nospam@gmail.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
hari n <hnagalla@gmail.com>,
"Lopez Cruz, Misael" <x0052729@ti.com>
Subject: Re: <alsa-dev> RFC for OMAP4 audio driver
Date: Thu, 3 Sep 2009 15:06:27 +0100 [thread overview]
Message-ID: <20090903140627.GC1406@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <6160a5130909030656j89cad98x1821f135d526621@mail.gmail.com>
On Thu, Sep 03, 2009 at 08:56:30AM -0500, pl bossart wrote:
> My 2 cents: I find the notion of codec confusing.
> In most products from Wolfson and others, you have a digital/mixing
> part, and a second one for digital/analog conversions. OMAP4 and
> others have a digital part on the application processor, but the
> partition is still the same, only implemented on two chips instead of
> one. It shouldn't really matter software-wise where the digital part
> is done, as long as you can express the connection between these two
> parts. A logical split would avoid having a description of a codec
In this case "codec" is just what ASoC (for historical reasons) calls
any block that isn't a DAI or DMA controller on the CPU. It doesn't
actually need to be a CODEC. There are many cases even the ADCs and
DACs are integrated with the CPU which means that package boundaries
aren't always that helpful either.
prev parent reply other threads:[~2009-09-03 14:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 2:27 <alsa-dev> RFC for OMAP4 audio driver hari n
2009-09-02 12:01 ` Mark Brown
2009-09-03 1:55 ` Lopez Cruz, Misael
2009-09-03 9:10 ` Mark Brown
2009-09-03 13:56 ` pl bossart
2009-09-03 14:06 ` Mark Brown [this message]
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=20090903140627.GC1406@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=bossart.nospam@gmail.com \
--cc=hnagalla@gmail.com \
--cc=x0052729@ti.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.