From: Jarkko Nikula <jhnikula@gmail.com>
To: Peter Ujfalusi <peter.ujfalusi@nokia.com>
Cc: "Aggarwal, Anuj" <anuj.aggarwal@ti.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Audio capture not working with AIC23/McBSP1 on OMAP3517
Date: Fri, 28 Aug 2009 13:51:03 +0300 [thread overview]
Message-ID: <20090828135103.63ca2343.jhnikula@gmail.com> (raw)
In-Reply-To: <200908280955.01382.peter.ujfalusi@nokia.com>
On Fri, 28 Aug 2009 09:55:01 +0300
Peter Ujfalusi <peter.ujfalusi@nokia.com> wrote:
> > Can you, Peter or who has access to 2420 and 2430 TRMs to verify is the
> > DEVCONF0 bits 3 and 4 selecting there also the McBSP1 CLKR and FSR
> > sources like my patch is now assuming for all OMAP2-3.
>
> On OMAP2:
> DEVCONF:3 MCBSP1_CLKR
> DEVCONF:4 MCBSP1_FSR
>
> So it is correct for both OMAP2 and OMAP3.
>
Good :-)
Are you Mark fine with the patch [] where the snd_soc_dai_set_sysclk
is used to specify source pin for CLKR and FSR?
--
Jarkko
1.
http://mailman.alsa-project.org/pipermail/alsa-devel/2009-August/020771.html
next prev parent reply other threads:[~2009-08-28 10:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-26 13:00 Audio capture not working with AIC23/McBSP1 on OMAP3517 Aggarwal, Anuj
2009-08-26 13:03 ` [alsa-devel] " Mark Brown
2009-08-26 13:19 ` Aggarwal, Anuj
2009-08-26 14:06 ` [alsa-devel] " Graeme Gregory
2009-08-26 13:42 ` Jarkko Nikula
2009-08-26 15:01 ` Jarkko Nikula
2009-08-27 9:37 ` Aggarwal, Anuj
2009-08-27 11:12 ` Jarkko Nikula
2009-08-28 6:55 ` Peter Ujfalusi
2009-08-28 10:51 ` Jarkko Nikula [this message]
2009-08-28 12:05 ` [alsa-devel] " Mark Brown
2009-08-28 12:35 ` [PATCH] ASoC: OMAP: Add functionality to set CLKR and FSR sources in McBSP DAI Jarkko Nikula
2009-08-28 17:41 ` 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=20090828135103.63ca2343.jhnikula@gmail.com \
--to=jhnikula@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=anuj.aggarwal@ti.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@nokia.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.