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@xxxxxxxxxxxxxxx
_______________________________________________
Alsa-devel mailing list
Alsa-devel@xxxxxxxxxxxxxxxx
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
