All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Guilhem Tardy <guilhem_tardy@yahoo.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: updated patch for period_size constraint
Date: Tue, 10 Sep 2002 19:11:30 +0200	[thread overview]
Message-ID: <s5hznuppy65.wl@alsa2.suse.de> (raw)
In-Reply-To: <20020910170631.58483.qmail@web11504.mail.yahoo.com>

At Tue, 10 Sep 2002 10:06:31 -0700 (PDT),
Guilhem Tardy wrote:
> 
> > 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.

yes.  they can be 0 and MAX_INT, so that they never restrict the
condition, if you don't want these parameters affecting the behavior.
(this is not tested but should work ;)


Takashi


-------------------------------------------------------
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

      reply	other threads:[~2002-09-10 17:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <s5hsn0z9h55.wl@alsa2.suse.de>
2002-08-29 20:57 ` struct _snd_pcm_hardware Guilhem Tardy
2002-08-30 15:53   ` Jaroslav Kysela
2002-09-06 16:28   ` snd_pcm_hardware_t NOT pre-initialized Guilhem Tardy
2002-09-06 16:43     ` Takashi Iwai
2002-09-06 16:58       ` Guilhem Tardy
2002-09-09 14:22     ` Jaroslav Kysela
2002-09-10 15:29       ` updated patch for period_size constraint Guilhem Tardy
2002-09-10 16:47         ` Takashi Iwai
2002-09-10 17:06           ` Guilhem Tardy
2002-09-10 17:11             ` Takashi Iwai [this message]

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=s5hznuppy65.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=guilhem_tardy@yahoo.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.