From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Liam Girdwood <liam.r.girdwood@linux.intel.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"Frkuska, Joshua" <Joshua_Frkuska@mentor.com>
Subject: Re: ASoC: no-pcm (backend) error propagation
Date: Sat, 2 Mar 2013 11:32:07 +0800 [thread overview]
Message-ID: <20130302033205.GC6610@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1362173090.4439.44.camel@loki>
[-- Attachment #1.1: Type: text/plain, Size: 1127 bytes --]
On Fri, Mar 01, 2013 at 09:24:50PM +0000, Liam Girdwood wrote:
> On Thu, 2013-02-28 at 00:49 +0000, Frkuska, Joshua wrote:
Reflowed both sets of text into 80 columns...
> > With architectures that have an audio DSP, I think it makes sense to
> > do it as it is done with OMAP where underruns can be handled
> > internally by the DSP. The need came up for me because in my setup
> > there isn’t a dedicated audio DSP and the BE components are on the
> > same SoC as the FE, running/controlled by linux. (with the exception
> > of the codec)
> So if there is no audio DSP architecture then I assume you have some
> sort of DAI switch matrix/mixers in the HW and you don't do any ASRC ?
The modern Samsung SoCs are an example of this in mainline (currently a
bit bodged rather than using soc-pcm) - they've got a couple of DAIs
with a simple mixer that outputs on a single physical output, requiring
that both streams be at the same sample rate. There's no meaningful
handling of underruns to do except for propagate them back up to the
application layer, each stream can error totally independently.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2013-03-02 3:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 2:21 ASoC: no-pcm (backend) error propagation Frkuska, Joshua
2013-02-27 8:23 ` Liam Girdwood
2013-02-27 15:43 ` Pierre-Louis Bossart
2013-03-01 21:25 ` Liam Girdwood
2013-03-04 1:30 ` Frkuska, Joshua
2013-03-04 19:42 ` Liam Girdwood
2013-03-05 15:34 ` Frkuska, Joshua
2013-02-28 0:49 ` Frkuska, Joshua
2013-03-01 21:24 ` Liam Girdwood
2013-03-02 3:32 ` Mark Brown [this message]
2013-03-04 1:17 ` Frkuska, Joshua
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=20130302033205.GC6610@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=Joshua_Frkuska@mentor.com \
--cc=alsa-devel@alsa-project.org \
--cc=liam.r.girdwood@linux.intel.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;
as well as URLs for NNTP newsgroup(s).