> > I modified my previous patch for supporting a period_size (rather than
> > period_bytes) constraint with Takashi's suggestion that the fields be
> > non-zero for either constraint to kick in. See file in attachment.
> > It has worked fine on my hardware for the past few days.
>
> you don't need to modify the common code.
> my intention was not to change the common code, too, unless other
> drivers also need this constraint.
I got you wrong, sorry.
> just add the constraint in open callback, such like
>
> int your_pcm_open(snd_pcm_substream_t *substream)
> {
> ...
>
> err = snd_pcm_hw_constraint_minmax(runtime, SNDRV_PCM_HW_PARAM_PERIOD_SIZE,
> your_period_size_min, your_period_size_max);
> ...
> }
>
> this is the cleanest solution.
Sure, but then I also need to define .period_bytes_min and .period_bytes_max in
my snd_pcm_hardware_t, right? This is quite feasible, indeed.
Guilhem.
__________________________________________________
Yahoo! - We Remember
9-11: A tribute to the more than 3,000 lives lost
http://dir.remember.yahoo.com/tribute
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
