From: Bill Gatliff <bgat@billgatliff.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: [PATCH] Add support for CLKOUT to wm8731 codec driver
Date: Fri, 30 Oct 2009 14:04:25 -0500 [thread overview]
Message-ID: <4AEB38B9.2090204@billgatliff.com> (raw)
In-Reply-To: <B3102D86-255A-4DC5-BEDA-28356E5F57AD@opensource.wolfsonmicro.com>
Mark Brown wrote:
> wm8993 supports multiple internal options for sysclk usig the id
> parameter. Could you be more explicit about what you can't follow here
> please? I might be able to help more if I could see what's confusing you.
I guess what it comes down to is, I have no idea what I'm doing as far
as the Alsa SoC APIs are concerned. I understand fully how the hardware
works, but not any of the SND_SOC_* macros. I'm lost! :)
I see in the wm8993 code the following:
static const struct snd_soc_dapm_widget wm8993_dapm_widgets[] = {
SND_SOC_DAPM_SUPPLY("CLK_SYS", WM8993_BUS_CONTROL_1, 1, 0, clk_sys_event,
SND_SOC_DAPM_PRE_PMU | SND_SOC_DAPM_POST_PMD),
...
And I also have looked at the clk_sys_event function in the same file.
And then farther down:
static const struct snd_soc_dapm_route routes[] = {
...
{ "DACL", NULL, "CLK_SYS" },
I guess that the updates to the wm8731 would somehow look like the
above? I don't mind looking at code and macros at all, I'm just not yet
seeing how all this stuff fits together.
b.g.
--
Bill Gatliff
bgat@billgatliff.com
next prev parent reply other threads:[~2009-10-30 19:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-29 15:13 [PATCH] Add CLKOUT support to wm8731 codec driver Bill Gatliff
2009-10-29 15:13 ` [PATCH] Add support for CLKOUT " Bill Gatliff
2009-10-29 16:05 ` Mark Brown
2009-10-29 16:09 ` Bill Gatliff
2009-10-30 16:50 ` Bill Gatliff
2009-10-30 17:00 ` Mark Brown
2009-10-30 18:22 ` Bill Gatliff
2009-10-30 18:32 ` Mark Brown
2009-10-30 19:04 ` Bill Gatliff [this message]
2009-10-30 19:44 ` 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=4AEB38B9.2090204@billgatliff.com \
--to=bgat@billgatliff.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.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.