All of lore.kernel.org
 help / color / mirror / Atom feed
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: Wed, 8 Apr 2015 12:52:17 +0300	[thread overview]
Message-ID: <5524FA51.9060606@ti.com> (raw)
In-Reply-To: <CAES_P+_nr4LvcU-WQ=ZuhNwCSRuUs=xenqKGpupYAgx01fnATg@mail.gmail.com>

On 04/07/2015 09:33 PM, noman pouigt wrote:
> In my setup codec(max98090) is master and mcbsp is slave. I used above
> command and got below error:
> arecord: set_params:1233: Sample format non available
> Available formats:
> - S16_LE

The codec only supports S16_LE or S24_LE.

> So i changed the format to S16_LE and got below error:
> arecord: pcm_read:2031: read error: Input/output error
> 
> I checked the dmesg and found out that interrupt triggered only
> once and after some time all widgets gets powered down.
> Below is part of the dmesg.
> 
> [  174.186431] snd_pcm_lib_read
> [  174.186462] snd_pcm_lib_read1
> [  174.187042] omap-mcbsp 48074000.mcbsp: **** McBSP255 regs ****
> [  174.187072] omap-mcbsp 48074000.mcbsp: DRR2:  0xedd0abce
> [  174.187103] omap-mcbsp 48074000.mcbsp: DRR1:  0x0000
> [  174.187133] omap-mcbsp 48074000.mcbsp: DXR2:  0x0000
> [  174.187164] omap-mcbsp 48074000.mcbsp: DXR1:  0x0000
> [  174.187194] omap-mcbsp 48074000.mcbsp: SPCR2: 0x0230
> [  174.187225] omap-mcbsp 48074000.mcbsp: SPCR1: 0x0031
> [  174.187255] omap-mcbsp 48074000.mcbsp: RCR2:  0x8041
> [  174.187286] omap-mcbsp 48074000.mcbsp: RCR1:  0x0040
> [  174.187316] omap-mcbsp 48074000.mcbsp: XCR2:  0x8041
> [  174.187347] omap-mcbsp 48074000.mcbsp: XCR1:  0x0040
> [  174.187377] omap-mcbsp 48074000.mcbsp: SRGR2: 0x001f
> [  174.187408] omap-mcbsp 48074000.mcbsp: SRGR1: 0x0f00
> [  174.187438] omap-mcbsp 48074000.mcbsp: PCR0:  0x000f
> [  174.187469] omap-mcbsp 48074000.mcbsp: ***********************
> [  174.187499] snd_pcm_update_hw_ptr0
> 
> May i know where am i going wrong?

First check the /proc/asound/card0/pcm0c/sub0/status while the capture is
running and look at the hw_ptr if it has moved at all.

Enable more interrupts in sound/soc/omap/mcbsp.c:omap_mcbsp_config(), like
RUNDFLEN, ROVFLEN and see if you have overflow in McBSP.

If the DMA has not moved it means that McBSP does not received the FS which
would indicate the frame start, thus it will not sample data in, thus it will
not trigger the DMA to read the data out.

Since the capture is working on McBSP2 in McBSP slave (and master also) the
only thing which can be wrong is the way the max98090 is wired up or some mux
issue again as it was before for you.

-- 
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-08  9:52 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 [this message]
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
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=5524FA51.9060606@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.