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 0/2] alsa-lib: -ENODATA documentation
Date: Fri, 29 May 2020 15:28:15 +0300	[thread overview]
Message-ID: <20200529122817.1198-1-kai.vehmanen@linux.intel.com> (raw)

Hello all,

here's patch to document -ENODATA error as a PCM error code.
We have recently merged patches to SOF firmware to use
this error code:
  https://github.com/thesofproject/sof/pull/2918

Some additional background on the use-case:
  https://github.com/thesofproject/sof/issues/2564

In thread "Functionality of pcm_notify in snd-aloop?"
https://mailman.alsa-project.org/pipermail/alsa-devel/2020-April/166974.html

.. we discussed the possibility for ALSA to provide a mechanism
for application to wait for the condition to change, but at least
for the currently known usages, the synchronization responsibility
will be in user-space (UCM file will describe the PCM dependencies).
Anyways, this is orthogonal to documenting -ENODATA, so sending
this now.

Kai Vehmanen (2):
  pcm: add documentation for -ENODATA error code
  pcm: fix spelling in documentation for -EBADFD

 src/pcm/pcm.c | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

-- 
2.26.2


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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-29 12:28 Kai Vehmanen [this message]
2020-05-29 12:28 ` [PATCH 1/2] pcm: add documentation for -ENODATA error code Kai Vehmanen
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-1-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.