From: Adam Miartus <amiartus@de.adit-jv.com>
To: patch@alsa-project.org
Cc: alsa-devel@alsa-project.org
Subject: [PATCH 0/2 v2] Open Alsa dshare without channel binding
Date: Wed, 24 Jul 2019 12:12:58 +0200 [thread overview]
Message-ID: <1563963180-416-1-git-send-email-amiartus@de.adit-jv.com> (raw)
The general idea of this patch is to be able to open the device without
defined bindings. As a result, it allows starting the audio clock of
underlying device without blocking a channel.
This might be useful for creating a dummy dsnoop pcm for hardware that
requires running clock early at system start. This clock is then present
even without application streaming audio data.
Patch n.1 is intended to check for null pointer of pcm callbacks,
it is not intended to alter any current functionality, properly defined
plugins should not suffer from this change
Patch n.2 is not intended to alter any current functionality, only
extend it
V2 of the patch, changes from V1:
- instead of creating new "pcm_unsupported.c" with ops and fast_ops
callbacks returning -ENOSYS, callback == NULL is checked directly
in core implementation and error is returned when pcm has no
callback defined
Adam Miartus (2):
alsa: pcm: return -ENOSYS when ops or fast_ops callback is NULL
alsa: dshare: allow missing bindings
src/pcm/pcm.c | 134 +++++++++++++++++++++++++++++++++++++++++----------
src/pcm/pcm_dshare.c | 29 ++++++-----
src/pcm/pcm_local.h | 20 ++++++++
src/pcm/pcm_mmap.c | 15 ++++--
src/pcm/pcm_params.c | 10 +++-
5 files changed, 166 insertions(+), 42 deletions(-)
--
2.7.4
next reply other threads:[~2019-07-24 10:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 10:12 Adam Miartus [this message]
2019-07-24 10:12 ` [PATCH 1/2] alsa: pcm: return -ENOSYS when ops or fast_ops callback is NULL Adam Miartus
2019-07-24 10:13 ` [PATCH 2/2] alsa: dshare: allow missing bindings Adam Miartus
2019-07-24 13:20 ` [ALSA patch] [PATCH 0/2 v2] Open Alsa dshare without channel binding 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=1563963180-416-1-git-send-email-amiartus@de.adit-jv.com \
--to=amiartus@de.adit-jv.com \
--cc=alsa-devel@alsa-project.org \
--cc=patch@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