From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Bill Gatliff <bgat@billgatliff.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 19:44:02 +0000 [thread overview]
Message-ID: <20091030194402.GA31601@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4AEB38B9.2090204@billgatliff.com>
On Fri, Oct 30, 2009 at 02:04:25PM -0500, Bill Gatliff wrote:
> 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! :)
All I said to do was to take your code to set this via the set_sysclk()
function and use the id that gets passed in to split up the changes to
the master clock and the output clock so the two are adjusted
independently.
> 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),
> ...
This is used to switch on and off the internal system clock in the
CODEC which supplies the clock to all the digital functionaliy in the
device, it's not something that's visible outside the device. The
wm8731 is a much older device and doesn't have this sort of detailed
control.
prev parent reply other threads:[~2009-10-30 19:44 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
2009-10-30 19:44 ` Mark Brown [this message]
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=20091030194402.GA31601@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=bgat@billgatliff.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.