All of lore.kernel.org
 help / color / mirror / Atom feed
From: noman pouigt <variksla@gmail.com>
To: "peter.ujfalusi@ti.com" <peter.ujfalusi@ti.com>,
	"broonie@kernel.org" <broonie@kernel.org>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: recording problem in beagleboard-mcbsp
Date: Tue, 31 Mar 2015 11:41:49 -0700	[thread overview]
Message-ID: <CAES_P+-ufoqcY++WzvS42tyQLfd2zzuANNp2rPwuUk3x_Tn-jg@mail.gmail.com> (raw)
In-Reply-To: <CAES_P+-yk29wzBMhO3uYjr1fnXt8iyskr77QLc=AvwCuX=Najg@mail.gmail.com>

On Fri, Mar 27, 2015 at 2:20 PM, noman pouigt <variksla@gmail.com> wrote:
> On Fri, Mar 27, 2015 at 1:24 PM, noman pouigt <variksla@gmail.com> wrote:
>> Problem: not able to record with any of the devices
>> in beagleboard-xm.
>>
>> Analysis: userspace is stuck in snd_pcm_readi function
>> and kernel space i don't see snd_pcm_update_hw_ptr
>> function being called.
>>
>> Checked the I2S clocks and they are perfect and recording
>> data line is moving based on the data. I am able to do playback
>> though.
>>
>> I am using below command to do recording. Do i need to add
>> additional switches?
>>
>>
>> Linux kernel: 3.19
>>
>> root@arm:~# arecord -t wav -c 2 -r 44100 -f S32_LE -v test.wav
>> Recording WAVE 'test.wav' : Signed 32 bit Little Endian, Rate 44100 Hz, Stereo
>> Plug PCM: Linear conversion PCM (S16_LE)
>> Its setup is:
>>   stream       : CAPTURE
>>   access       : RW_INTERLEAVED
>>   format       : S32_LE
>>   subformat    : STD
>>   channels     : 2
>>   rate         : 44100
>>   exact rate   : 44100 (44100/1)
>>   msbits       : 32
>>   buffer_size  : 27560
>>   period_size  : 5512
>>   period_time  : 124988
>>   tstamp_mode  : NONE
>>   period_step  : 1
>>   avail_min    : 5512
>>   period_event : 0
>>   start_threshold  : 1
>>   stop_threshold   : 27560
>>   silence_threshold: 0
>>   silence_size : 0
>>   boundary     : 1806172160
>> Slave: Hardware PCM card 0 'omap3beagle' device 0 subdevice 0
>> Its setup is:
>>   stream       : CAPTURE
>>   access       : MMAP_INTERLEAVED
>>   format       : S16_LE
>>   subformat    : STD
>>   channels     : 2
>>   rate         : 44100
>>   exact rate   : 44100 (44100/1)
>>   msbits       : 16
>>   buffer_size  : 27560
>>   period_size  : 5512
>>   period_time  : 124988
>>   tstamp_mode  : NONE
>>   period_step  : 1
>>   avail_min    : 5512
>>   period_event : 0
>>   start_threshold  : 1
>>   stop_threshold   : 27560
>>   silence_threshold: 0
>>   silence_size : 0
>>   boundary     : 1806172160
>>   appl_ptr     : 0
>>   hw_ptr       : 0
>>
>> [   74.696319] omap-mcbsp 48074000.mcbsp: **** McBSP255 regs ****
>> [   74.696380] omap-mcbsp 48074000.mcbsp: DRR2:  0xedd0abce
>> [   74.696411] omap-mcbsp 48074000.mcbsp: DRR1:  0x0000
>> [   74.696441] omap-mcbsp 48074000.mcbsp: DXR2:  0x0000
>> [   74.696472] omap-mcbsp 48074000.mcbsp: DXR1:  0x0000
>> [   74.696502] omap-mcbsp 48074000.mcbsp: SPCR2: 0x0230
>> [   74.696533] omap-mcbsp 48074000.mcbsp: SPCR1: 0x0031
>> [   74.696563] omap-mcbsp 48074000.mcbsp: RCR2:  0x8041
>> [   74.696594] omap-mcbsp 48074000.mcbsp: RCR1:  0x0040
>> [   74.696594] omap-mcbsp 48074000.mcbsp: XCR2:  0x8041
>> [   74.696624] omap-mcbsp 48074000.mcbsp: XCR1:  0x0040
>> [   74.696655] omap-mcbsp 48074000.mcbsp: SRGR2: 0x001f
>> [   74.696685] omap-mcbsp 48074000.mcbsp: SRGR1: 0x0f00
>> [   74.696716] omap-mcbsp 48074000.mcbsp: PCR0:  0x000f
>>
>>
>> setup:
>> beagleoboard-xm
>> ubuntu distribution
>> arecord used
>> jaroslav recording application also tried
> using max98090 codec and not using twl.
I was wondering if i can get some help in this?

  reply	other threads:[~2015-03-31 18: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 [this message]
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
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=CAES_P+-ufoqcY++WzvS42tyQLfd2zzuANNp2rPwuUk3x_Tn-jg@mail.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.