From: Daniel Mack <zonque@gmail.com>
To: Sebastian <ehlke@bewatec.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: OMAP4 McBSP AC97 link
Date: Thu, 27 Sep 2012 09:59:36 +0200 [thread overview]
Message-ID: <50640768.7040204@gmail.com> (raw)
In-Reply-To: <loom.20120927T093059-361@post.gmane.org>
On 27.09.2012 09:44, Sebastian wrote:
> Hi All,
>
> i have to support a 2nd Audio Codec with AC97 Interface on McBSP Port2.
> Processor: OMAP4460
>
> If any one have any idea on how to go about this.
> Please let me know.
If you need to support a second codec on a dedicated bus, all you have
to do is set up a new snd_soc_dai_link. Read the documentation in
Documentation/sound/alsa/soc/ and see many of the good example in the
mainline kernel tree.
If your goal is to support a second codec in parallel to another one,
dynamix PCM (DPCM) is what you want to have a look at. It's there in the
kernel since 3.5, but AFAIK there's currently no user of it that can
serve as an example.
HTH,
Daniel
next prev parent reply other threads:[~2012-09-27 7:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-27 7:44 OMAP4 McBSP AC97 link Sebastian
2012-09-27 7:59 ` Daniel Mack [this message]
2012-09-27 8:58 ` Sebastian
2012-09-27 9:10 ` Daniel Mack
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=50640768.7040204@gmail.com \
--to=zonque@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=ehlke@bewatec.de \
/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).