From: Sedji Gaouaou <sedji.gaouaou@atmel.com>
To: alsa-devel@alsa-project.org
Subject: Recording problem with ALSA: trying to set up some constraints
Date: Thu, 22 May 2008 11:33:34 +0200 [thread overview]
Message-ID: <48353DEE.1020502@atmel.com> (raw)
Hi,
I have a problem with my recording driver.
I have set up a pcm_hardware structure in which I define the format
supported by my hardware:
static struct snd_pcm_hardware snd_at91_ac97_capture_hw = {
.info = (SNDRV_PCM_INFO_INTERLEAVED
| SNDRV_PCM_INFO_MMAP
| SNDRV_PCM_INFO_MMAP_VALID
| SNDRV_PCM_INFO_BLOCK_TRANSFER),
.formats = (SNDRV_PCM_FMTBIT_S16_LE
| SNDRV_PCM_FMTBIT_S16_BE
| SNDRV_PCM_FMTBIT_S20_3LE
| SNDRV_PCM_FMTBIT_U20_3LE
| SNDRV_PCM_FMTBIT_S20_3BE
| SNDRV_PCM_FMTBIT_U20_3BE
| SNDRV_PCM_FMTBIT_S18_3LE
| SNDRV_PCM_FMTBIT_U18_3LE
| SNDRV_PCM_FMTBIT_S18_3BE
| SNDRV_PCM_FMTBIT_U18_3BE),
.rates = SNDRV_PCM_RATE_CONTINUOUS,
.rate_min = 8000,
.rate_max = 48000,
.channels_min = 1,
.channels_max = 2,
.buffer_bytes_max = 256*1024,
.period_bytes_min = 1024,
.period_bytes_max = 4*1024,
.periods_min = 1,
.periods_max = 64,
};
Then in my open function I pass it to the runtime struct.
Nevertheless if I try to run arecord with this option: arecord -d 1
test.wav, I will have a kernel oops.
The default format is U8, but it is not supported by my Hardware, abd it
is not defined in my structure, so I though that it should exit arecord
but not crash.
Do I miss something when defining my pcm_hardware strucutre, or do I
forgot to use a specific function which should return me an error?
I have try to set up some constraints as well(for the rate and the
format), but still I have the same crash.
Regards,
Sedji
next reply other threads:[~2008-05-22 9:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-22 9:33 Sedji Gaouaou [this message]
2008-05-22 11:03 ` Recording problem with ALSA: trying to set up some constraints Clemens Ladisch
2008-05-23 14:27 ` Sedji Gaouaou
2008-05-23 15:42 ` USB Data Dropping Charles Eidsness
2008-05-26 18:45 ` Charles Eidsness
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=48353DEE.1020502@atmel.com \
--to=sedji.gaouaou@atmel.com \
--cc=alsa-devel@alsa-project.org \
/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.