From: Bas Vermeulen <Bas.Vermeulen@novero.com>
To: alsa-devel@alsa-project.org
Subject: ASoC/DAPM: How to make the DAPM routing complete?
Date: Fri, 16 Sep 2011 16:07:13 +0200 [thread overview]
Message-ID: <4E735811.2060002@novero.com> (raw)
I am using a slightly modified version of the 88pm860x-codec.c driver
from 3.x in an android modified 2.6.35 kernel.
I have had to make some changes to allow both capture and playback work
on the same (I2S) interface, but so far things are working.
I am however having some problems getting the DAPM framework to set the
correct switches needed to get the complete route to actually start.
What would be needed to get this working as it should? I can post or
send the driver on request, but basically the same question rises for
the current driver in the 3.x kernel.
I want/need to go from HS1/HS2 to DIN for playback, and from MIC1 to
DOUT for capture. In order to do that, I have to set the following switches:
amixer -q sset 'DAC HS1 Mux' 'Right'
amixer -q sset 'DAC HS2 Mux' 'Left'
amixer -q sset 'I2S Mic Mux' 'ADC'
amixer -q sset 'ADC Left Mux' 'ADCL'
I would like to make this automatic, but I am unsure how to express this
in my dapm routing table.
Note that in order to be able to use playback and capture independently
on the I2S interface (within reason, it is not possible to use a
different rate for instance), I had to add a SUPPLY control to the dapm
widgets that turns on the I2S clock when needed.
Any help, hints or pointers to the right manual to read would be
appreciated.
Bas Vermeulen
next reply other threads:[~2011-09-16 14:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-16 14:07 Bas Vermeulen [this message]
2011-09-17 13:32 ` ASoC/DAPM: How to make the DAPM routing complete? Mark Brown
2011-09-19 11:35 ` [ASoC] 88pm860x - Allow independent use of I2S capture and playback Bas Vermeulen
2011-09-20 11:34 ` Mark Brown
2011-09-21 14:55 ` Mark Brown
2011-09-19 11:38 ` [ASoC] 88pm860x - Incorporate the marvell errata regarding Audio Power-up Delay Bas Vermeulen
2011-09-20 11:34 ` 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=4E735811.2060002@novero.com \
--to=bas.vermeulen@novero.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 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.