From: Steve Calfee <stevecalfee@gmail.com>
To: Sanjeev Premi <premi@ti.com>
Cc: linux-omap@vger.kernel.org, Liam Girdwood <lrg@ti.com>
Subject: beagleboardxm 2.6.39rc4 mcbsp problems.
Date: Wed, 11 May 2011 14:31:46 -0700 [thread overview]
Message-ID: <4DCB0042.8040202@gmail.com> (raw)
In-Reply-To: <4DCAD29A.5050408@gmail.com>
On 05/11/11 11:16, Steve Calfee wrote:
New title, more appropriate to the topic.
I was replying to the fix posted by Sanjeev fixing
a/sound/soc/omap/omap-mcbsp.c
I am pretty near the cutting edge kernel, trying to use the latest alsa
changes. I cannot get bbxm to talk to an external codec via mcbsp1.
Has anyone been able to use mcbsp1 on a recent linux-next.
More below.
> Hi,
>
> I removed all but the linux-omap list for my question.
>
> I am trying to get the beagleboardxm to work with an external codec. I
> am trying to use a mcbsp1 via the trainer board where it level shifts to
> 5 volts. I have applied this patch (I am on 2.6.39rc4), but still no
> joy. I have a small analyzer attached to the I/O pins and important
> things like the bit clock does not wiggle.
>
> First a side question. In the arch/arm/mach-omap2/Kconfig when I select
> BEAGLE, it selects OMAP_PACKAGE_CBB - but my bbxm system reference
> manual says "The BeagleBoard-xM processor is the DM3730CBP 1GHz version"
> which to me implies the proper package selection should be
> OMAP_PACKAGE_CBP. The platform file mux34xx.c has different tables for
> them, but I cant quickly tell the difference. Does this matter for mcbspx?
>
Sanjeev pointed me to:
Check this page to find the differences:
http://processors.wiki.ti.com/index.php/OMAP35x_To_AM37x_Hardware_Migration_Guide
Where it appears TI has some new chip naming scheme and maybe the bbxm
is a am3730? In any case it doesn't seem that mcbsp is affected by the
package change.
> Here is a console dump where I try to aplay a file:
> [ 1565.773712] omap_mcbsp_dai_startup: omap-mcbsp-dai.0 bus_id=0 active 0
> [ 1565.781829] omap_pcm_open: ret 1
> [ 1565.785491] asoc: HiFi <-> omap-mcbsp-dai.0 info:
> [ 1565.790527] asoc: rate mask 0x7fe
> [ 1565.794006] asoc: min ch 1 max ch 2
> [ 1565.797760] asoc: min rate 8000 max rate 96000
> [ 1565.826721] bbxm_hw_params: codec_dai=dfbbb9c0 clk 12288000
> [ 1565.832702] bbxm_hw_params 2: codec_dai=dfbbb9c0 clk 12288000
> [ 1565.838867] omap_mcbsp_dai_set_dai_fmt: configured 0
> [ 1565.844146] bbxm_hw_params 3: codec_dai=dfbbb9c0 clk 12288000
> [ 1565.850219] omap_mcbsp_dai_set_dai_sysclk: mcbsp_data=bf00d5b8 in_freq 0
> [ 1565.857299] omap_mcbsp_dai_set_dai_sysclk: mcbsp_data=bf00d5b8 in_freq 0
> [ 1565.864379] omap_mcbsp_dai_set_dai_sysclk: mcbsp_data=bf00d5b8
> in_freq 2048000
> [ 1565.877319] max98095 4-0010: read 2a => 10
> [ 1565.884277] max98095 4-0010: read 27 => 1
> [ 1565.891143] max98095 4-0010: read 2a => 10
> [ 1565.898956] max98095 4-0010: read 2e => 0
> [ 1565.903198] omap_mcbsp_dai_hw_params: format 1
> [ 1565.907958] omap_mcbsp_dai_hw_params: stream Audio Playback
> [ 1565.913909] omap_mcbsp_dai_hw_params: framesize 32 in_freq=2048000
> div=8 rate=8000
> [ 1565.921936] omap-mcbsp omap-mcbsp.1: Configuring McBSP1 phys_base:
> 0x48074000
> [ 1565.929565] omap_pcm_hw_params: ret 0
> [ 1565.934722] omap_pcm_prepare: dma_data bf00d4a0
> [ 1565.945831] max98095 4-0010: read 91 => 0
> [ 1565.950347] max98095 4-0010: write 91 = 3
> [ 1565.958618] max98095 4-0010: read 91 => 3
> [ 1565.963195] max98095 4-0010: write 91 = c3
> [ 1565.972351] snd_pcm_lib_write1: state 2 size 1000
> [ 1565.977691] snd_pcm_lib_write1: offset 0
> [ 1565.981842] snd_pcm_update_state: stream=0 avail=3000
> buffer_size=4000 twake=0 tsleep=1
> [ 1565.992706] snd_pcm_lib_write1: state 2 size 1000
> [ 1565.997985] snd_pcm_lib_write1: offset 0
> [ 1566.002227] snd_pcm_update_state: stream=0 avail=2000
> buffer_size=4000 twake=0 tsleep=1
> [ 1566.011810] snd_pcm_lib_write1: state 2 size 1000
> [ 1566.017120] snd_pcm_lib_write1: offset 0
> [ 1566.021270] snd_pcm_update_state: stream=0 avail=1000
> buffer_size=4000 twake=0 tsleep=1
> [ 1566.033050] snd_pcm_lib_write1: state 2 size 1000
> [ 1566.038360] snd_pcm_lib_write1: offset 0
> [ 1566.042510] snd_pcm_pre_start: state 3
> [ 1566.046447] snd_pcm_do_start: state 3
> [ 1566.050292] omap_pcm_trigger: cmd 1
> [ 1566.053955] omap_start_dma: lch 0
> [ 1566.057891] omap-mcbsp omap-mcbsp.1: **** McBSP1 regs ****
> [ 1566.063629] omap-mcbsp omap-mcbsp.1: DRR2: 0x0000
> [ 1566.068664] omap-mcbsp omap-mcbsp.1: DRR1: 0x0000
> [ 1566.073699] omap-mcbsp omap-mcbsp.1: DXR2: 0x0000
> [ 1566.078735] omap-mcbsp omap-mcbsp.1: DXR1: 0x0000
> [ 1566.083740] omap-mcbsp omap-mcbsp.1: SPCR2: 0x02f5
> [ 1566.088775] omap-mcbsp omap-mcbsp.1: SPCR1: 0x0030
> [ 1566.093811] omap-mcbsp omap-mcbsp.1: RCR2: 0x8041
> [ 1566.098846] omap-mcbsp omap-mcbsp.1: RCR1: 0x0040
> [ 1566.103851] omap-mcbsp omap-mcbsp.1: XCR2: 0x8041
> [ 1566.108886] omap-mcbsp omap-mcbsp.1: XCR1: 0x0040
> [ 1566.113922] omap-mcbsp omap-mcbsp.1: SRGR2: 0x101f
> [ 1566.118927] omap-mcbsp omap-mcbsp.1: SRGR1: 0x0f07
> [ 1566.123962] omap-mcbsp omap-mcbsp.1: PCR0: 0x0f0f
> [ 1566.128997] omap-mcbsp omap-mcbsp.1: ***********************
> [ 1566.134918] snd_pcm_post_start: state 3
> [ 1566.138977] snd_pcm_update_state: stream=0 avail=0 buffer_size=4000
> twake=0 tsleep=1
> [ 1566.148681] snd_pcm_lib_write1: state 3 size 1000
> [ 1566.153625] omap_pcm_pointer: offset 64
> [ 1566.157653] snd_pcm_update_hw_ptr0: old_hw_ptr=0 pos=64 in_int=0
> [ 1566.163970] snd_pcm_update_hw_ptr0: stream=0 new_hw_ptr=64 silence_size=0
> [ 1566.171081] snd_pcm_update_state: stream=0 avail=64 buffer_size=4000
> twake=1000 tsleep=1
> [ 1566.180145] snd_pcm_lib_write1: offset 0
> [ 1566.184295] snd_pcm_lib_write1: state 3 size 936
> [ 1566.189147] omap_pcm_pointer: offset 64
> [ 1566.193176] snd_pcm_update_hw_ptr0: old_hw_ptr=64 pos=64 in_int=0
> [ 1576.194274] ALSA sound/core/pcm_lib.c:1795: playback write error (DMA
> or IRQ trouble?)
> [ 1576.304199] snd_pcm_lib_write1: state 3 size 936
> [ 1576.309051] omap_pcm_pointer: offset 64
> [ 1576.313079] snd_pcm_update_hw_ptr0: old_hw_ptr=64 pos=64 in_int=0
> [ 1586.319274] ALSA sound/core/pcm_lib.c:1795: playback write error (DMA
> or IRQ trouble?)
> [ 1586.337554] omap_pcm_trigger: cmd 0
> [ 1591.342651] pop wq checking: HiFi Playback status: inactive waiting: yes
> [ 1591.351898] max98095 4-0010: read 91 => c3
> [ 1591.356231] max98095 4-0010: write 91 = 3
> [ 1591.362030] max98095 4-0010: read 91 => 3
> [ 1591.366424] max98095 4-0010: write 91 = 0
> [ 1591.373229] max98095 4-0010: read 90 => c
Regards, Steve
next prev parent reply other threads:[~2011-05-11 21:31 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 ` Steve Calfee [this message]
2011-05-12 6:25 ` beagleboardxm 2.6.39rc4 mcbsp problems Jarkko Nikula
2011-05-12 11:01 ` Peter Ujfalusi
2011-05-12 18:43 ` Steve Calfee
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=4DCB0042.8040202@gmail.com \
--to=stevecalfee@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@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).