From: Steve Calfee <stevecalfee@gmail.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: Jarkko Nikula <jhnikula@gmail.com>,
"Premi, Sanjeev" <premi@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Girdwood, Liam" <lrg@ti.com>
Subject: Re: beagleboardxm 2.6.39rc4 mcbsp problems.
Date: Thu, 12 May 2011 11:43:20 -0700 [thread overview]
Message-ID: <4DCC2A48.7070602@gmail.com> (raw)
In-Reply-To: <201105121401.44607.peter.ujfalusi@ti.com>
On 05/12/11 04:01, Peter Ujfalusi wrote:
> On Thursday 12 May 2011 09:25:55 Jarkko Nikula wrote:
>> Of course for this you need to use omap as a master and codec as a
>> slave. One example for this is sound/soc/omap/omap3pandora.c.
>>
>> static struct omap_board_mux board_mux[] __initdata = {
>> + OMAP3_MUX(MCBSP1_FSX, OMAP_MUX_MODE0 | OMAP_PIN_OUTPUT),
>> + OMAP3_MUX(MCBSP1_CLKX, OMAP_MUX_MODE0 | OMAP_PIN_OUTPUT),
>> + OMAP3_MUX(MCBSP1_DR, OMAP_MUX_MODE0 | OMAP_PIN_INPUT),
>> + OMAP3_MUX(MCBSP1_DX, OMAP_MUX_MODE0 | OMAP_PIN_OUTPUT),
>> +
>
> I think the CLKX, FSX need to be input, since the config suggests,t that
> McBSP1 is the slave port:
>
>> [ 1566.123962] omap-mcbsp omap-mcbsp.1: PCR0: 0x0f0f
>
Hi, thanks for trying to help.
I already tried that, but it still did not xmit. Now I wonder about
master/slave. I thought that the omap is set up as a master. I looked at
PCR0 docs in the tech ref manual and I get:
11 FSXM Transmit Frame-Synchronization Mode RW 0x0
0x0: Frame-synchronization signal derived from an
external source
0x1: Frame synchronization is determined by the SRG
frame-synchronization mode bit FSGM in SRGR2.
10 FSRM Receive Frame-Synchronization Mode RW 0x0
0x0: Frame-Synchronization pulses generated by an
external device. FSR is an input pin.
0x1: Frame synchronization generated internally by SRG.
FSR is an output pin except when GSYNC=1 in SRGR.
Etc.
Since it is set to 0xF0F, doesn't this set it as master?
Also, spelunking the kernel sources, I cannot seem to find the source
for mcbsp_data->regs -- do you know where it gets set initially?
next prev parent reply other threads:[~2011-05-12 18:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 13:55 [PATCH] ASoC: omap-mcbsp: Remove restrictive checks for cpu type Sanjeev Premi
2011-05-11 13:57 ` Mark Brown
2011-05-11 14:44 ` Peter Ujfalusi
2011-05-11 15:38 ` Jarkko Nikula
2011-05-11 18:16 ` [alsa-devel] " Steve Calfee
2011-05-11 19:19 ` Premi, Sanjeev
2011-05-11 21:31 ` beagleboardxm 2.6.39rc4 mcbsp problems Steve Calfee
2011-05-12 6:25 ` Jarkko Nikula
2011-05-12 11:01 ` Peter Ujfalusi
2011-05-12 18:43 ` Steve Calfee [this message]
2011-05-13 5:59 ` Peter Ujfalusi
2011-05-14 2:47 ` Steve Calfee
2011-05-16 8:54 ` Peter Ujfalusi
2011-05-16 18:07 ` Steve Calfee
2011-05-17 6:37 ` Jarkko Nikula
2011-05-19 1:06 ` Steve Calfee
2011-05-20 0:58 ` Steve Calfee
2011-05-20 6:29 ` Jarkko Nikula
2011-05-20 7:03 ` Peter Ujfalusi
2011-05-21 0:55 ` Steve Calfee
2011-05-17 10:42 ` Peter Ujfalusi
2011-05-19 0:30 ` Steve Calfee
2011-05-19 11:28 ` Peter Ujfalusi
2011-05-19 23:58 ` Steve Calfee
2011-05-20 6:56 ` Peter Ujfalusi
2011-05-13 12:13 ` [PATCH] ASoC: omap-mcbsp: Remove restrictive checks for cpu type Liam Girdwood
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=4DCC2A48.7070602@gmail.com \
--to=stevecalfee@gmail.com \
--cc=jhnikula@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=premi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).