All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kai Vehmanen <kai.vehmanen@linux.intel.com>
To: alsa-devel@alsa-project.org, perex@perex.cz
Cc: kai.vehmanen@linux.intel.com
Subject: [PATCH 1/2] pcm: add documentation for -ENODATA error code
Date: Fri, 29 May 2020 15:28:16 +0300	[thread overview]
Message-ID: <20200529122817.1198-2-kai.vehmanen@linux.intel.com> (raw)
In-Reply-To: <20200529122817.1198-1-kai.vehmanen@linux.intel.com>

This error code can be used e.g. with echo reference PCM devices
(the SND_USE_CASE_MOD_ECHO_REF UCM token).

Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
---
 src/pcm/pcm.c | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/src/pcm/pcm.c b/src/pcm/pcm.c
index 1064044c9812..488a8dd0493d 100644
--- a/src/pcm/pcm.c
+++ b/src/pcm/pcm.c
@@ -292,6 +292,14 @@ This error can happen when device is physically removed (for example
 some hotplug devices like USB or PCMCIA, CardBus or ExpressCard
 can be removed on the fly).
 
+\par -ENODATA
+
+This error can happen if the device data transfer is dependent on
+an external condition and that condition is not met. For example,
+PCM device for echo reference as described by SND_USE_CASE_MOD_ECHO_REF
+UCM token, may return -ENODATA if the linked playback stream has not been
+started.
+
 \section pcm_params Managing parameters
 
 The ALSA PCM device uses two groups of PCM related parameters. The hardware
-- 
2.26.2


  reply	other threads:[~2020-05-29 12:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-29 12:28 [PATCH 0/2] alsa-lib: -ENODATA documentation Kai Vehmanen
2020-05-29 12:28 ` Kai Vehmanen [this message]
2020-05-29 12:28 ` [PATCH 2/2] pcm: fix spelling in documentation for -EBADFD Kai Vehmanen
2020-06-05  9:56 ` [PATCH 0/2] alsa-lib: -ENODATA documentation Jaroslav Kysela

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=20200529122817.1198-2-kai.vehmanen@linux.intel.com \
    --to=kai.vehmanen@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=perex@perex.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.