From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: 宋宝华 <21cnbao@gmail.com>
Cc: lrg@slimlogic.co.uk, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org,
Mike Frysinger <vapier.adi@gmail.com>
Subject: Re: [PATCH] New ASoC Drivers for ADI AD1938 codec
Date: Mon, 13 Jul 2009 10:15:38 +0100 [thread overview]
Message-ID: <20090713091538.GA6987@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <3c17e3570907130112i128dd0f2o4673200de3125d5d@mail.gmail.com>
On Mon, Jul 13, 2009 at 04:12:14PM +0800, 宋宝华 wrote:
> I want to use ADC/DAC widgets.
> static const struct snd_soc_dapm_widget ad1938_dapm_widgets[] = {
> SND_SOC_DAPM_DAC("DAC", "HiFi Playback", AD1938_DAC_CTRL0, 0, 1),
> SND_SOC_DAPM_ADC("ADC", "HiFi Capture", AD1938_ADC_CTRL0, 0, 1),
> };
> But for this AD1938 codec, DAC's work depends on ADC is powered on in
> hardware. I think there is no any mechanism to handle this kind of
> strange depending now. So is there a generic way to handle this?
Make the ADC power a SND_SOC_DAPM_SUPPLY() supplying both the DAC and
the ADC, with the ADC widget marged as having no power management.
next prev parent reply other threads:[~2009-07-13 9:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 9:28 [PATCH] New ASoC Drivers for ADI AD1938 codec Barry Song
2009-06-19 9:35 ` Liam Girdwood
2009-06-19 9:41 ` Liam Girdwood
2009-06-19 10:47 ` Mark Brown
2009-06-19 11:05 ` Mike Frysinger
2009-06-19 11:13 ` Mark Brown
2009-06-19 11:21 ` Mike Frysinger
2009-06-19 11:56 ` Mark Brown
2009-06-20 23:15 ` [alsa-devel] " Robin Getz
2009-06-21 0:13 ` Mark Brown
[not found] ` <3c17e3570906212008n6071e987sbcd4b9377364ae78@mail.gmail.com>
2009-06-22 10:57 ` Mark Brown
[not found] ` <3c17e3570906220600l3471b6f0rc29c674b4a5ec2df@mail.gmail.com>
2009-06-22 13:11 ` Mark Brown
2009-07-13 8:12 ` 宋宝华
2009-07-13 9:15 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-06-19 5:58 Barry Song
2009-06-19 6:44 ` Mike Frysinger
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=20090713091538.GA6987@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=21cnbao@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=vapier.adi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox