From: Takashi Iwai <tiwai@suse.de>
To: Guilhem Tardy <guilhem_tardy@yahoo.com>
Cc: Jaroslav Kysela <perex@suse.cz>, alsa-devel@alsa-project.org
Subject: Re: updated patch for period_size constraint
Date: Tue, 10 Sep 2002 18:47:01 +0200 [thread overview]
Message-ID: <s5h65xdzta2.wl@alsa2.suse.de> (raw)
In-Reply-To: <20020910152959.91672.qmail@web11503.mail.yahoo.com>
Hi Guilhem,
At Tue, 10 Sep 2002 08:29:59 -0700 (PDT),
Guilhem Tardy wrote:
>
> Hi all,
>
> 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.
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.
ciao,
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
next prev parent reply other threads:[~2002-09-10 16:47 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 [this message]
2002-09-10 17:06 ` Guilhem Tardy
2002-09-10 17:11 ` Takashi Iwai
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=s5h65xdzta2.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=guilhem_tardy@yahoo.com \
--cc=perex@suse.cz \
/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.