All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sedji Gaouaou <sedji.gaouaou@atmel.com>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: Recording problem with ALSA: trying to set up some constraints
Date: Fri, 23 May 2008 16:27:19 +0200	[thread overview]
Message-ID: <4836D447.5030903@atmel.com> (raw)
In-Reply-To: <48355305.1090808@ladisch.de>

Clemens Ladisch a écrit :
> Sedji Gaouaou wrote:
>> 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:
>> ...
>>     .formats        = (SNDRV_PCM_FMTBIT_S16_LE
>>                    | SNDRV_PCM_FMTBIT_S16_BE
>>                    | SNDRV_PCM_FMTBIT_S20_3LE
>>                    ...
>>
>> 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.
> 
> The default device will do automatic sample format conversion, i.e.,
> your driver will see a request for S16_LE.
> 
> This looks like a bug somewhere else in your driver.
> 
> 
> Regards,
> Clemens
> 
That means that if the format is no supported, it should not return an 
error, but just use another format which is supported?

  reply	other threads:[~2008-05-23 14:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-22  9:33 Recording problem with ALSA: trying to set up some constraints Sedji Gaouaou
2008-05-22 11:03 ` Clemens Ladisch
2008-05-23 14:27   ` Sedji Gaouaou [this message]
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=4836D447.5030903@atmel.com \
    --to=sedji.gaouaou@atmel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.de \
    /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.