From: <twischer@de.adit-jv.com>
To: tiwai@suse.de
Cc: alsa-devel@alsa-project.org
Subject: [PATCH - IOPLUG DRAIN 0/2]
Date: Thu, 22 Mar 2018 14:48:55 +0100 [thread overview]
Message-ID: <1521726537-7651-1-git-send-email-twischer@de.adit-jv.com> (raw)
Hi Takashi,
> Why not poll()?
> IOW, why ioplug must be handled specially regarding the non-blocking
>operation? The normal kernel driver behaves like that (returning
> -EAGAIN, and let apps to sync with poll()).
What do you think about the following solution?
(I thought the whole time that you have to use snd_pcm_wait() to wait for drain
in nonblocking mode but you have to use the poll_descriptors directly.)
Know I am expecting that the user is calling poll()
if snd_pcm_drain() returns -EAGAIN and
the user has to call snd_pcm_drain() again after poll returns
to check if drain is done.
Thanks for your help so far.
Best regards
Timo
next reply other threads:[~2018-03-22 13:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-22 13:48 twischer [this message]
2018-03-22 13:48 ` [PATCH - IOPLUG DRAIN 1/1] ioplug: drain: Wait with pollwhen EAGAIN in blocking mode twischer
2018-03-22 13:48 ` [PATCH - IOPLUG DRAIN 1/1] jack: Support snd_pcm_drain() twischer
2018-03-22 14:28 ` [PATCH - IOPLUG DRAIN 0/2] Takashi Iwai
2018-03-22 14:50 ` Wischer, Timo (ADITG/ESB)
2018-03-22 14:55 ` Takashi Iwai
2018-03-22 15:17 ` Wischer, Timo (ADITG/ESB)
2018-03-22 16:22 ` Takashi Iwai
2018-03-23 7:23 ` Wischer, Timo (ADITG/ESB)
2018-03-23 7:28 ` Takashi Iwai
2018-03-23 7:43 ` Wischer, Timo (ADITG/ESB)
2018-03-23 8:01 ` Takashi Iwai
2018-03-23 8:08 ` Takashi Iwai
2018-03-23 9:03 ` Takashi Iwai
2018-03-28 8:42 ` Wischer, Timo (ADITG/ESB)
2018-03-28 16:09 ` Takashi Iwai
2018-03-29 6:39 ` Wischer, Timo (ADITG/ESB)
2018-03-29 7:25 ` Takashi Iwai
2018-03-29 7:38 ` Wischer, Timo (ADITG/ESB)
2018-03-23 8:21 ` Wischer, Timo (ADITG/ESB)
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=1521726537-7651-1-git-send-email-twischer@de.adit-jv.com \
--to=twischer@de.adit-jv.com \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
/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).