From: Peter Ujfalusi <peter.ujfalusi@nokia.com>
To: ext Mark Brown <broonie@sirena.org.uk>
Cc: "sakoman@gmail.com" <sakoman@gmail.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"Nikula Jarkko (Nokia-D/Helsinki)" <jarkko.nikula@nokia.com>
Subject: Re: [PATCH 3/6] ASoC: TWL4030: Enable all audio paths
Date: Tue, 7 Apr 2009 07:59:19 +0300 [thread overview]
Message-ID: <200904070759.19600.peter.ujfalusi@nokia.com> (raw)
In-Reply-To: <20090406124520.GA14169@sirena.org.uk>
On Monday 06 April 2009 15:45:21 ext Mark Brown wrote:
> On Mon, Apr 06, 2009 at 03:19:29PM +0300, Peter Ujfalusi wrote:
> > Enable all TX and RX paths on the TWL codec.
>
> What does this mean by "enable" - I'm guessing it's powering blocks
> within the CODEC rather than connecting any audio paths?
The TRM calls these as Audio/Voice digital filters.
In effect, they enable the shifting out bits from the Capture path to the bus
and shifting in bits on the Playback side.
The original driver had these filters enabled - all the time - for the digital
filters needed for the i2s mode (AudioRX2 L/r, AudioTX1 L/R), in TDM mode all
4 filters on Capture and Playback need to be enabled.
>
> > This is not so nice, but doing it runtime brings quite a bit
> > of challenge, since for example the Digital loopback also needs
> > the RX and TX paths to be enabled.
>
> What are the problems other than loopback (which really needs digital
> routing to work properly, though I've never seen much demand for it
> outside of testing)? Powering everything is probably fine, I'm just
> wondering if this is due to the hardware or the core.
The digital loopback needs the AudioTX1 L/R and AudioRX2 L/R enabled in order
to function, and I have a requirement, that the codec should support it ;)
I had two other implementation for these:
a) Enable the needed Digital filters in twl4030_startup based on the channel
number and stream type (Playback/Capture). Disable the Digital filters on
twl4030_shutdown, based on the just closed stream's parameters.
b) Adding another widgets to the DAPM routing paths, so it tries to enable
only the needed Digital filters.
There were couple of problems with these:
a) Digital loopback was not functioning
b) It did enabled other filters, than what it is needed (in stereo mode
AudioRX1 L/R and AudioTX2 L/R should not be enabled). I guess this is because
the DAPM knows only about streams, but here we can have 2 channel or 4 channel
streams, which need to be handled a bit differently.
But as I said, this is not so nice thing to do, so it need to be revisited.
--
Péter
next prev parent reply other threads:[~2009-04-07 4:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-06 12:19 [PATCH 0/6] ASoC: 4 channel support for twl4030 and omap-mcbsp Peter Ujfalusi
2009-04-06 12:19 ` [PATCH 1/6] ASoC: OMAP mcbsp: Add DSP_A support Peter Ujfalusi
2009-04-06 12:19 ` [PATCH 2/6] ASoC: OMAP mcbsp: Add 4 channel support Peter Ujfalusi
2009-04-06 12:19 ` [PATCH 3/6] ASoC: TWL4030: Enable all audio paths Peter Ujfalusi
2009-04-06 12:19 ` [PATCH 4/6] ASoC: TWL4030: Add 4 channel TDM support Peter Ujfalusi
2009-04-06 12:19 ` [PATCH 5/6] ASoC: TWL4030: Add constraints for 4 channel mode Peter Ujfalusi
2009-04-06 12:19 ` [PATCH 6/6] ASoC: Beagle: Add support " Peter Ujfalusi
2009-04-06 12:50 ` Mark Brown
2009-04-07 4:45 ` Peter Ujfalusi
2009-04-06 12:45 ` [PATCH 3/6] ASoC: TWL4030: Enable all audio paths Mark Brown
2009-04-07 4:59 ` Peter Ujfalusi [this message]
2009-04-07 9:45 ` Mark Brown
2009-04-07 10:30 ` Peter Ujfalusi
2009-04-07 21:02 ` Mark Brown
2009-04-06 12:22 ` [PATCH 1/6] ASoC: OMAP mcbsp: Add DSP_A support Mark Brown
2009-04-06 12:37 ` Peter Ujfalusi
2009-04-07 5:19 ` Peter Ujfalusi
2009-04-07 22:14 ` Mark Brown
2009-04-08 6:01 ` Peter Ujfalusi
2009-04-08 9:30 ` Mark Brown
2009-04-08 6:08 ` Jarkko Nikula
2009-04-08 9:28 ` Mark Brown
2009-04-07 5:45 ` [PATCH 0/6] ASoC: 4 channel support for twl4030 and omap-mcbsp Jarkko Nikula
2009-04-07 6:32 ` Peter Ujfalusi
2009-04-08 6:23 ` Jarkko Nikula
2009-04-08 9:53 ` 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=200904070759.19600.peter.ujfalusi@nokia.com \
--to=peter.ujfalusi@nokia.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@sirena.org.uk \
--cc=jarkko.nikula@nokia.com \
--cc=sakoman@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.