From: Patrick Lai <plai@codeaurora.org>
To: rashmi narayan <rashmi.nyn@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Configuring an audio path within ALSA
Date: Mon, 25 Jun 2012 19:56:34 -0700 [thread overview]
Message-ID: <4FE924E2.2010504@codeaurora.org> (raw)
In-Reply-To: <CABTnDnPfGF8AddTSQ4GPyyvosQVa7K6Koda2cz79dknxWMaTVg@mail.gmail.com>
On 6/25/2012 5:26 AM, rashmi narayan wrote:
> Dear ALSA Folks,
>
> I am a newbie to ALSA .I am trying to configure a path within the driver to
> open up /power up the path within the codec from MIC-IN to LineOUT. How can
> I do this within ALSA. Please send me some pointers.
>
If your CODEC driver is written to plug into ASoC framework, ASoC
dynamic audio power management(DAPM) will be able to link MIC-IN to
Lineout. After a set of ALSA mixer commands is issued to create a path
from one end point to another end point, DAPM will kick in and enable
the path according to widgets and audio routing map defined in the
CODEC driver.
> Thank you,
> Rashmi
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2012-06-26 2:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-25 12:26 Configuring an audio path within ALSA rashmi narayan
2012-06-26 2:56 ` Patrick Lai [this message]
2012-06-26 7:52 ` rashmi narayan
2012-06-26 9:43 ` Vinod Koul
2012-06-27 5:27 ` Patrick Lai
2012-06-27 12:04 ` rashmi narayan
2012-06-27 12:04 ` rashmi narayan
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=4FE924E2.2010504@codeaurora.org \
--to=plai@codeaurora.org \
--cc=alsa-devel@alsa-project.org \
--cc=rashmi.nyn@gmail.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.