From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Daniel Mack <daniel@caiaq.de>
Cc: alsa-devel@alsa-project.org,
Tabi Timur-B04825 <B04825@freescale.com>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH] ALSA: ASoc: Add regulator support to CS4270 codec driver
Date: Mon, 30 Nov 2009 16:12:09 +0000 [thread overview]
Message-ID: <20091130161209.GD18944@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <20091130155742.GI14091@buzzloop.caiaq.de>
On Mon, Nov 30, 2009 at 04:57:42PM +0100, Daniel Mack wrote:
> The current aproach does not work reliably, unfortunately. It turns out
> that the codec necessarily needs its analogue supply to maintain its
> state. For all other operations (iow, any of the volatges not applied),
> it has to be held in reset mode. I did that manually by driving the GPIO
> directly before, but with the current regulator framework support,
> that's not possible anymore.
This is one of the reasons why your previous code looked suspect to me,
actually - since the CODEC driver had no idea that you'd suspended the
device it'd do things like try to write volume updates to the device
while you were keeping the power off.
> Hence, we can only power down the codec when we're in system suspend,
When runtime PM hits in 2.6.33 I intend to try to enable support for it
in ASoC, it's relatively straightforward I think. Unfortunately it'll
end up depending on the platform bus on the relevant platform being
capable of runtime pm but that should become more widely supported as
things progress.
Given this I would suggest doing the same thing the other drivers are
doing and only turning things off when the device is suspended (either
via the explicit functions or via set_bias_level()) and then let the
ASoC core deal with actually doing the suspend - it's probably less
hassle for you that way. Converting to use the shared register I/O code
in soc-cache.c might also help here.
> which is a pitty. But even for that, we should still drive the RESET
> signal low. Can we make the GPIO pin number available to the codec
> driver?
Of course, use platform data.
next prev parent reply other threads:[~2009-11-30 16:12 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 14:36 [PATCH] ALSA: ASoc: Add regulator support to CS4270 codec driver Daniel Mack
2009-11-25 15:01 ` Mark Brown
2009-11-25 15:20 ` Daniel Mack
2009-11-25 15:38 ` Mark Brown
2009-11-25 15:46 ` Daniel Mack
2009-11-26 15:48 ` Daniel Mack
2009-11-26 16:03 ` Mark Brown
2009-11-26 17:42 ` Daniel Mack
2009-11-27 11:25 ` Mark Brown
2009-11-27 12:41 ` Daniel Mack
2009-11-27 13:32 ` Mark Brown
2009-11-28 20:23 ` Timur Tabi
2009-11-28 20:31 ` Mark Brown
2009-11-28 22:18 ` Timur Tabi
2009-11-29 0:44 ` Daniel Mack
2009-11-29 4:34 ` Timur Tabi
2009-11-29 8:35 ` Daniel Mack
2009-11-30 10:12 ` Daniel Mack
[not found] ` <5610599F537DD74A8D1F5CC946A7507303478C40@az33exm25.fsl.freescale.net>
2009-11-30 12:01 ` Mark Brown
2009-11-30 12:36 ` Daniel Mack
2009-11-30 15:57 ` Daniel Mack
2009-11-30 16:12 ` Mark Brown [this message]
2009-11-30 16:51 ` Daniel Mack
2009-11-30 16:56 ` Daniel Mack
2009-12-04 12:00 ` Daniel Mack
2009-12-04 12:07 ` Mark Brown
2009-12-05 2:54 ` Timur Tabi
2009-12-05 3:51 ` Mark Brown
2009-12-05 17:03 ` Timur Tabi
2009-12-07 13:16 ` 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=20091130161209.GD18944@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=B04825@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=daniel@caiaq.de \
--cc=lrg@slimlogic.co.uk \
/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.