From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: noman pouigt <variksla@gmail.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"broonie@kernel.org" <broonie@kernel.org>
Subject: Re: recording problem in beagleboard-mcbsp
Date: Thu, 9 Apr 2015 17:07:45 +0300 [thread overview]
Message-ID: <552687B1.5060108@ti.com> (raw)
In-Reply-To: <55266B38.6030503@ti.com>
On 04/09/2015 03:06 PM, Peter Ujfalusi wrote:
> Hrm, McBSP1 is kind of problematic port since it has 6pin config by default.
> It might worth a try to do something like:
> http://lists.infradead.org/pipermail/linux-arm-kernel/2012-August/113058.html
> has removed.
> Or to switch to use McBSP3.
>
> But for some reason now I can not get the recording working via McBSP1 either.
> I remember that it worked not that long time ago...
One thing I would also try:
use the codec as master and connect the FS to McBSP1 FSX _and_ FSR. Do the
same for the bclk (connect it to BCLKX _and_ BCLKR of McBSP1)
Configure the pin mux for these pins also.
--
Péter
next prev parent reply other threads:[~2015-04-09 14:07 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 20:24 recording problem in beagleboard-mcbsp noman pouigt
2015-03-27 21:20 ` noman pouigt
2015-03-31 18:41 ` noman pouigt
2015-04-01 18:46 ` Peter Ujfalusi
2015-04-07 4:29 ` noman pouigt
2015-04-07 9:22 ` Peter Ujfalusi
2015-04-07 18:33 ` noman pouigt
2015-04-08 9:52 ` Peter Ujfalusi
2015-04-08 23:44 ` noman pouigt
2015-04-09 12:06 ` Peter Ujfalusi
2015-04-09 14:07 ` Peter Ujfalusi [this message]
2015-04-09 23:04 ` noman pouigt
2015-04-10 7:11 ` Peter Ujfalusi
2015-04-10 17:54 ` noman pouigt
2015-04-10 21:42 ` noman pouigt
2015-04-09 23:02 ` noman pouigt
2015-04-10 7:13 ` Peter Ujfalusi
2015-04-10 17:53 ` noman pouigt
2015-04-10 22:58 ` noman pouigt
2015-04-13 15:14 ` Peter Ujfalusi
2015-04-14 9:39 ` Peter Ujfalusi
2015-04-14 12:39 ` Peter Ujfalusi
2015-04-14 16:41 ` Variksla
2015-04-15 6:03 ` Peter Ujfalusi
2015-04-14 22:32 ` noman pouigt
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=552687B1.5060108@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=variksla@gmail.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