From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Variksla <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: Wed, 15 Apr 2015 09:03:31 +0300 [thread overview]
Message-ID: <552DFF33.3050404@ti.com> (raw)
In-Reply-To: <8EE6AA19-869C-4EFD-984E-7BCAADE91D1F@gmail.com>
On 04/14/2015 07:41 PM, Variksla wrote:
>> In McBSP3 master mode, you need:
>> OMAP3_CORE1_IOPAD(0x2172, PIN_INPUT | MUX_MODE0) /* mcbsp3_fsx.mcbsp3_fsx */
>> OMAP3_CORE1_IOPAD(0x2178, PIN_INPUT | MUX_MODE1) /* uart2_tx.mcbsp3_clkx */
>> OMAP3_CORE1_IOPAD(0x2174, PIN_OUTPUT | MUX_MODE1) /* uart2_cts.mcbsp3_dx */
>> OMAP3_CORE1_IOPAD(0x2176, PIN_INPUT | MUX_MODE1) /* uart2_rts.mcbsp3_dr */
>
> Weird. If mcbsp3 is master I am wondering why we are configuring fsx and clkx as input.
When we configure the pads, we set the input enable bit which will set the pin
to bidirectional mode.
The 4pin McBSP ports will get their FSR/CLKR from the actual pin. If the pin
is set to output only, no signal will come back to McBSP -> capture will not
work. This is why we need to set input enable, so that the signal going out
will be able to get back to McBSP's FSR/CLKR internal line.
--
Péter
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2015-04-15 6:03 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
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 [this message]
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=552DFF33.3050404@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 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.