alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Raymond Yau <superquad.vortex2@gmail.com>
To: alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: [alsa-lib PATCH 2/4] Search-and-replace improve documentation language
Date: Thu, 5 Jan 2012 14:43:31 +0800	[thread overview]
Message-ID: <CAN8cciYsbbMVgsvb3FDDVOob8C8sLNW5KLxb1sx9BRX0LAkZ+w@mail.gmail.com> (raw)
In-Reply-To: <20120104201137.GD9868@foghorn.codeweavers.com>

> /**
>- * \brief Check, if hardware supports pause
>+ * \brief Check if hardware supports pause
> * \param params Configuration space
>- * \return Boolean value
>  * \retval 0 Hardware doesn't support pause
>  * \retval 1 Hardware supports pause
>  *
>- * It is not allowed to call this function when given configuration is not exactly one.
>- * Usually, #snd_pcm_hw_params() function chooses one configuration
>- * from the configuration space.
>+ * This function should only be called when the configuration space
>+ * contains a single configuration. Call #snd_pcm_hw_params to choose
>+ * a single configuration from the configuration space.
>  */
> int snd_pcm_hw_params_can_pause(const snd_pcm_hw_params_t *params)


What is the meaning of the configuration space contains a single configuration ?

since the hardware either support pause or does not support pause

it seem that only need to call snd_pcm_hw_params_any() instead of
snd_pcm_hw_params() before calling snd_pcm_hw_params_can_pause()


err= snd_pcm_open(&pcm, device, stream, SND_PCM_NONBLOCK);

err= snd_pcm_hw_params_any(pcm, pars);

if (snd_pcm_hw_params_can_pause(pars))
      printf("pcm device support pause\n");

  reply	other threads:[~2012-01-05  6:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a0053dfb39d22118fce92031e4d6adac948b02fc.1325707699.git.aeikum@codeweavers.com>
2012-01-04 20:11 ` [alsa-lib PATCH 2/4] Search-and-replace improve documentation language Andrew Eikum
2012-01-05  6:43   ` Raymond Yau [this message]
2012-01-05  8:37     ` Clemens Ladisch
2012-01-04 20:11 ` [alsa-lib PATCH 3/4] Improve hw_params documentation Andrew Eikum
2012-01-04 20:11 ` [alsa-lib PATCH 4/4] Improve snd_device_name_hint documentation Andrew Eikum

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=CAN8cciYsbbMVgsvb3FDDVOob8C8sLNW5KLxb1sx9BRX0LAkZ+w@mail.gmail.com \
    --to=superquad.vortex2@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).