alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Raymond Yau <superquad.vortex2@gmail.com>
To: ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Re: Problem adding support for digital mixer in codec
Date: Thu, 25 Mar 2010 12:53:38 +0800	[thread overview]
Message-ID: <4f3252891003242153y788a583bs9f6045967f957cc7@mail.gmail.com> (raw)
In-Reply-To: <2256F256009DAA4CBE661E9F41EAC84B904BD8A0@dlee01.ent.ti.com>

2010/3/25 Candelaria Villarreal, Jorge <jorge.candelaria@ti.com>

> Hi,
>
> I am trying to add support for a digital mixer. The digital mixer is
> connected like the following example:
>
>
> Path 1 -------\
> Path 2 --------\
>                    MIXER ------> DAC----> ...
> Path 3 --------/
> Path 4 -------/
>
>
>
> However, I think ALSA does not support this configuration, as the DAC
> should be the first element in a route. I tried adding the DAC to the
> route first, and connected its output to the mixer inputs, like this:
>
>          {"Mixer", "Multimedia Ext Switch", "HSDAC Left"},
>        {"Mixer", "Multimedia Ext Switch", "HSDAC Right"},
>
>        {"Mixer", "Voice Switch", "HSDAC Left"},
>        {"Mixer", "Voice Switch", "HSDAC Right"},
>
>        {"Mixer", "Multimedia Uplink Switch", "HSDAC Left"},
>        {"Mixer", "Multimedia Uplink Switch", "HSDAC Right"},
>
>        {"Mixer", "Multimedia Switch", "HSDAC Left"},
>        {"Mixer", "Multimedia Switch", "HSDAC Right"},
>
> But this does not seem to work. Can anyone give me some tips? Any comment
> would be appreciated.
>
> Thanks,
> Jorge
>


Does your DSP support hardware mixing ?

  reply	other threads:[~2010-03-25  4:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-25  2:33 Problem adding support for digital mixer in codec Candelaria Villarreal, Jorge
2010-03-25  4:53 ` Raymond Yau [this message]
2010-03-25  7:17 ` Peter Ujfalusi
2010-03-25  9:13   ` Liam Girdwood
2010-03-25  9:22     ` Peter Ujfalusi
2010-03-25 16:56     ` Candelaria Villarreal, Jorge
2010-03-25  9:26 ` Mark Brown

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=4f3252891003242153y788a583bs9f6045967f957cc7@mail.gmail.com \
    --to=superquad.vortex2@gmail.com \
    --cc=alsa-devel@alsa-project.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;
as well as URLs for NNTP newsgroup(s).