From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Feng Ye <fye@broadcom.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: Does amixer has to be used to make a complete path in ASoC?
Date: Mon, 23 May 2011 09:01:18 +0800 [thread overview]
Message-ID: <20110523010116.GA23049@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <9383297B60843144AC17878B479520F1169F03C829@SJEXCHCCR01.corp.ad.broadcom.com>
On Sun, May 22, 2011 at 05:41:14PM -0700, Feng Ye wrote:
Please fix your mail client to word wrap within paragraphs. I've
reflowed your mail for legibility.
> I think the problem may not be in the driver, instead, amixer should
> be used to select the codec mixer settings to build a complete audio
> path (like the LEFT MIXER in wm8750).
Yes, exactly.
> I have following questions:
> 1. Is my understanding correct? amixer has to be used before aplay?
Yes.
> 2. Is there way to do it in the code instead of using amixer?
No.
> 3. If amixer has to be used, where I can find sample wm8750
> amixer setting usage for a simple playback from I2S in to Lout1 &
> Rout1 out?
In general you need to look at the DAPM map in the driver and figure out
how to connect whatever your audio source is to an output - most of the
control will be in the CODEC. Look at the DAPM routes between the
widgets and figure out what to connect - the driver source will have a
routing table like your driver has in the form:
{ destination, control, source }
so if control is not NULL the control with the specified name needs to
be enabled. The debugfs files for the DAPM widgets (look under asoc/ in
debugfs) can help here.
prev parent reply other threads:[~2011-05-23 1:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 0:41 Does amixer has to be used to make a complete path in ASoC? Feng Ye
2011-05-23 1:01 ` 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=20110523010116.GA23049@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=fye@broadcom.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).