All of lore.kernel.org
 help / color / mirror / Atom feed
From: Variksla <variksla@gmail.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.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: Tue, 14 Apr 2015 09:41:50 -0700	[thread overview]
Message-ID: <8EE6AA19-869C-4EFD-984E-7BCAADE91D1F@gmail.com> (raw)
In-Reply-To: <552D0A6A.20800@ti.com>





> On Apr 14, 2015, at 5:39 AM, Peter Ujfalusi <peter.ujfalusi@ti.com> wrote:
> 
>> On 04/14/2015 12:39 PM, Peter Ujfalusi wrote:
>> OK, got another SD card.
>> McBSP3 in master mode works (no codec connected) playback and capture as well.
>> 
>> The pins for McBSP3:
>> OMAP3_CORE1_IOPAD(0x2172, PIN_OUTPUT | MUX_MODE0) /* mcbsp3_fsx.mcbsp3_fsx */
>> OMAP3_CORE1_IOPAD(0x2178, PIN_OUTPUT | 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 */
>> 
>> I still not sure why McBSP1 is not working..
> 
> This pinctrl setting is not correct for McBSP3. I was changing the registers
> on the fly, that's why it was working when I replied.
> 
> 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. 
> 
> Which would work in McBSP3 slave mode as well.
> Playback, capture works (McBSP3 master). I have connected DX to DR and
> captured whatever I was playing. Came back fine.
> 
> As for McBSP1 I think this should get it working:
> OMAP3_CORE1_IOPAD(0x2196, PIN_INPUT | MUX_MODE0) /* mcbsp1_fsx.mcbsp1_fsx */
> OMAP3_CORE1_IOPAD(0x218e, PIN_INPUT | MUX_MODE0) /* mcbsp1_fsr.mcbsp1_fsr */
> OMAP3_CORE1_IOPAD(0x2198, PIN_INPUT | MUX_MODE0) /* mcbsp1_clkx.mcbsp1_clkx */
> OMAP3_CORE1_IOPAD(0x218c, PIN_INPUT | MUX_MODE0) /* mcbsp1_clkr.mcbsp1_clkr */
> OMAP3_CORE1_IOPAD(0x2190, PIN_OUTPUT | MUX_MODE0) /* mcbsp1_dx.mcbsp1_dx */
> OMAP3_CORE1_IOPAD(0x2192, PIN_INPUT | MUX_MODE0)  /* mcbsp1_dr.mcbsp1_dr */
> 
> If McBSP1 is slave, then connect the FS to both FSX and FSR and do the same
> for CLK.
> 
> -- 
> Péter
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2015-04-14 16:41 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 [this message]
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=8EE6AA19-869C-4EFD-984E-7BCAADE91D1F@gmail.com \
    --to=variksla@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=peter.ujfalusi@ti.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.