From: Liam Girdwood <lrg@ti.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"patches@opensource.wolfsonmicro.com"
<patches@opensource.wolfsonmicro.com>
Subject: Re: [PATCH] ASoC: WM8996 record paths need AIFCLK
Date: Mon, 22 Aug 2011 11:19:08 +0100 [thread overview]
Message-ID: <4E522D1C.1070301@ti.com> (raw)
In-Reply-To: <1313835445-21910-1-git-send-email-broonie@opensource.wolfsonmicro.com>
On 20/08/11 11:17, Mark Brown wrote:
> Make AIFCLK supply the record paths otherwise record will not work unless
> there is a simultaneous playback.
>
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> ---
> sound/soc/codecs/wm8996.c | 10 ++++++++++
> 1 files changed, 10 insertions(+), 0 deletions(-)
>
> diff --git a/sound/soc/codecs/wm8996.c b/sound/soc/codecs/wm8996.c
> index a44a0e5..0371736 100644
> --- a/sound/soc/codecs/wm8996.c
> +++ b/sound/soc/codecs/wm8996.c
> @@ -1213,6 +1213,16 @@ static const struct snd_soc_dapm_route wm8996_dapm_routes[] = {
> { "AIF2RX0", NULL, "AIFCLK" },
> { "AIF2RX1", NULL, "AIFCLK" },
>
> + { "AIF1TX0", NULL, "AIFCLK" },
> + { "AIF1TX1", NULL, "AIFCLK" },
> + { "AIF1TX2", NULL, "AIFCLK" },
> + { "AIF1TX3", NULL, "AIFCLK" },
> + { "AIF1TX4", NULL, "AIFCLK" },
> + { "AIF1TX5", NULL, "AIFCLK" },
> +
> + { "AIF2TX0", NULL, "AIFCLK" },
> + { "AIF2TX1", NULL, "AIFCLK" },
> +
> { "DSP1RXL", NULL, "SYSDSPCLK" },
> { "DSP1RXR", NULL, "SYSDSPCLK" },
> { "DSP2RXL", NULL, "SYSDSPCLK" },
Acked-by: Liam Girdwood <lrg@ti.com>
prev parent reply other threads:[~2011-08-22 10:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-20 10:17 [PATCH] ASoC: WM8996 record paths need AIFCLK Mark Brown
2011-08-22 10:19 ` Liam Girdwood [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=4E522D1C.1070301@ti.com \
--to=lrg@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.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