From: Timur Tabi <timur@freescale.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com,
Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH] ASoC: wm8960: Support shared LRCLK
Date: Thu, 13 Sep 2012 17:33:16 -0500 [thread overview]
Message-ID: <50525F2C.4080607@freescale.com> (raw)
In-Reply-To: <50522A5A.10006@freescale.com>
Timur Tabi wrote:
>> > + ret = regmap_update_bits(wm8960->regmap, WM8960_ADDCTL2,
>> > + 0x4, 0x4);
> This is not enough to get the codec working on my board.
>
> What is the actual mechanism that enables the clock on the WM8960? I
> don't have an oscilloscope, not it's hard to tell what the hardware is
> actually doing. However, I suspect that the LRCLK is not running.
Never mind, it works now. I understand that the DAPM controls need to be
enabled for the clocks to actually run, as described here:
http://www.alsa-project.org/main/index.php/DAPM#When_things_don.27t_work
On the #alsa-soc, I was told that I could force on the control in my
machine driver. Specifically, I was told this:
"in your board file you can always make an always on output in the DAPM map"
Can you tell me how to do this? Is there an example? I don't want to
have to rely on user-space configuration to get playback to work.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2012-09-13 22:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 3:48 [PATCH] ASoC: wm8960: Support shared LRCLK Mark Brown
2012-09-13 18:47 ` Timur Tabi
2012-09-13 22:33 ` Timur Tabi [this message]
2012-09-14 15:50 ` 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=50525F2C.4080607@freescale.com \
--to=timur@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lrg@ti.com \
--cc=patches@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).