From: Mark Brown <broonie@sirena.org.uk>
To: Vasily Khoruzhick <anarsoul@gmail.com>
Cc: alsa-devel@alsa-project.org, Philipp Zabel <philipp.zabel@gmail.com>
Subject: Re: asoc: s3c24xx+uda1380 - some questions
Date: Tue, 27 Jan 2009 15:00:41 +0000 [thread overview]
Message-ID: <20090127150040.GD11870@sirena.org.uk> (raw)
In-Reply-To: <200901271519.47119.anarsoul@gmail.com>
On Tue, Jan 27, 2009 at 03:19:39PM +0200, Vasily Khoruzhick wrote:
> I'm trying to develop asoc driver for hp ipaq rx1950 (s3c24xx + uda1380).
>
> 1st question: where I can enable/disable uda1380 codec power? I need to
> control codec power for powersave reasons.
CCing in Philipp Zabel who wrote the UDA1380 driver. Assuming you mean
control to cut the power to the chip the most standard way of doing it
would be with the regulator API but if the chip isn't being used much in
new designs it might not be worth it.
> I tried to add custom power function call to uda1380_set_bias_level in
> uda1380.c (pointer to power function is stored in codec->private_data), as it
> done for uda134x codec, but after enable-disable-enable cycle (for example,
> after resuming from suspend) driver cannot communicate with codec anymore
> (i2c bus is always busy), only reloading i2c driver helps.
The UDA134x is a bit of a special case since it needs the machine driver
to provide bitbanging functions for the L3 interface.
> 2nd question: for some reason, driver does not produce any sound during first
> aplay invocation, only second and later aplay invocation driver produces
> sound. What can be the reason of this problem?
That sounds like something in the teardown path should be done on
startup as well. Can't think of any obvious gotchas there, though I'd
be looking at the codec and machine drivers since the CPU driver for the
S3C24xx is used in quite a few designs.
next prev parent reply other threads:[~2009-01-27 15:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 13:19 asoc: s3c24xx+uda1380 - some questions Vasily Khoruzhick
2009-01-27 15:00 ` Mark Brown [this message]
2009-01-27 15:19 ` Vasily Khoruzhick
2009-01-27 15:25 ` Mark Brown
2009-01-27 15:49 ` Vasily Khoruzhick
2009-01-27 16:06 ` pHilipp Zabel
2009-01-27 16:22 ` Vasily Khoruzhick
2009-01-27 19:49 ` pHilipp Zabel
2009-01-27 20:32 ` Vasily Khoruzhick
2009-02-02 23:46 ` Vasily Khoruzhick
2009-02-03 11:41 ` Mark Brown
2009-02-03 11:57 ` Vasily Khoruzhick
2009-02-03 12:05 ` Mark Brown
2009-02-03 13:52 ` Vasily Khoruzhick
2009-02-03 16:09 ` pHilipp Zabel
2009-02-03 17:21 ` Mark Brown
2009-01-27 20:00 ` Mark Brown
2009-01-27 20:14 ` Vasily Khoruzhick
2009-01-27 20:19 ` 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=20090127150040.GD11870@sirena.org.uk \
--to=broonie@sirena.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=anarsoul@gmail.com \
--cc=philipp.zabel@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.