From: Takashi Iwai <tiwai@suse.de>
To: "S.j. Wang" <shengjiu.wang@nxp.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: [PATCH] aplay: support no period wakeup option in argument
Date: Tue, 01 Jan 2019 10:13:00 +0100 [thread overview]
Message-ID: <s5hlg44ivvn.wl-tiwai@suse.de> (raw)
In-Reply-To: <AM0PR0402MB3379A907F2E41F7DC17A1E5AE3B60@AM0PR0402MB3379.eurprd04.prod.outlook.com>
On Thu, 27 Dec 2018 07:46:57 +0100,
S.j. Wang wrote:
>
> I still have two questions:
> 1. It seems the no-period-wakeup feature should be dropped for it isn't recommended
> By alsa, right? I still found some driver in kernel support it, what's the reason?
>
> 2. Shall we add this option in aplay for it is feature that alsa support, even it is optional?
As Sakamoto-san already mentioned, no-period-wakeup is nothing but an
optional feature for very specific applications and setup, and it's
still valid and useful.
The condition to use this option is:
- If a hardware may perform DMA continuously on a ring buffer (a la
free-wheel mode), and
- Application doesn't need the wakeup from kernel at each PCM period,
but it manages the stream transfer timing by itself.
aplay doesn't satisfies the latter, hence adding such a command line
option makes no sense. But, it doesn't mean that no-period-wakeup is
useless. It can work well for specific applications like PulseAudio.
Takashi
prev parent reply other threads:[~2019-01-01 9:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-26 11:28 [PATCH] aplay: support no period wakeup option in argument S.j. Wang
2018-12-26 13:35 ` Takashi Sakamoto
2018-12-27 2:13 ` S.j. Wang
2018-12-27 4:28 ` Takashi Sakamoto
2018-12-27 6:46 ` S.j. Wang
2018-12-27 11:58 ` Takashi Sakamoto
2019-01-01 9:13 ` Takashi Iwai [this message]
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=s5hlg44ivvn.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=shengjiu.wang@nxp.com \
/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.