From: Takashi Iwai <tiwai@suse.de> To: "Gyeongtaek Lee" <gt82.lee@samsung.com> Cc: alsa-devel@alsa-project.org, pilsun.jang@samsung.com, khw0178.kim@samsung.com, lgirdwood@gmail.com, kimty@samsung.com, tiwai@suse.com, 'Pierre-Louis Bossart' <pierre-louis.bossart@linux.intel.com>, 'Vinod Koul' <vkoul@kernel.org>, hmseo@samsung.com, s47.kang@samsung.com, tkjung@samsung.com Subject: Re: [PATCH] ALSA: compress: allow pause and resume during draining Date: Mon, 26 Oct 2020 18:01:33 +0100 Message-ID: <s5h5z6w53bm.wl-tiwai@suse.de> (raw) In-Reply-To: <001801d6ab78$fcfe0760$f6fa1620$@samsung.com> On Mon, 26 Oct 2020 10:18:38 +0100, Gyeongtaek Lee wrote: > > With a stream with low bitrate, user can't pause or resume the stream > near the end of the stream because current ALSA doesn't allow it. > If the stream has very low bitrate enough to store whole stream into > the buffer, user can't do anything except stop the stream and then > restart it from the first because most of applications call draining > after sending last frame to the kernel. > If pause, resume are allowed during draining, user experience can be > enhanced. > To prevent malfunction in HW drivers which don't support pause > during draining, pause during draining will only work if HW driver > enable this feature explicitly by calling > snd_compr_use_pause_in_draining(). > > Signed-off-by: Gyeongtaek Lee <gt82.lee@samsung.com> > Cc: stable@vger.kernel.org Could you restart the new thread? It's been hanging too deeply and hard to read through. Since it's the revised patch, please give the revision number (v2 or such) and show what's different from the previous patches. About the changes: > +/** > + * snd_compr_use_pause_in_draining - Allow pause and resume in draining state > + * @substream: compress substream to set > + * > + * Allow pause and resume in draining state. > + * Only HW driver supports this transition can call this API. > + */ > +static inline void snd_compr_use_pause_in_draining( > + struct snd_compr_stream *substream) > +{ > + substream->device->use_pause_in_draining = true; > +} How to set the flag is an open question. A natural way would be to set it somehow at creating the component object, but currently there seems no way to pass any flags. thanks, Takashi
next prev parent reply index Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <CGME20200929084051epcas2p35fb2228ed1bdfce6a7ddf5b37c944823@epcas2p3.samsung.com> 2020-09-29 8:40 ` Gyeongtaek Lee 2020-09-29 8:54 ` Takashi Iwai 2020-09-29 9:17 ` Gyeongtaek Lee 2020-09-29 14:00 ` Pierre-Louis Bossart 2020-10-01 10:29 ` Vinod Koul 2020-10-01 15:28 ` Pierre-Louis Bossart 2020-10-06 6:21 ` Vinod Koul 2020-10-06 14:57 ` Pierre-Louis Bossart 2020-10-08 9:49 ` Gyeongtaek Lee 2020-10-09 15:13 ` Takashi Iwai 2020-10-09 17:43 ` Jaroslav Kysela 2020-10-10 9:08 ` Takashi Iwai 2020-10-12 5:25 ` Vinod Koul 2020-10-12 7:01 ` Takashi Iwai 2020-10-12 12:24 ` Vinod Koul 2020-10-12 13:29 ` Jaroslav Kysela 2020-10-12 13:55 ` Vinod Koul 2020-10-12 14:10 ` Jaroslav Kysela 2020-10-12 14:21 ` Takashi Iwai 2020-10-12 14:46 ` Jaroslav Kysela 2020-10-12 14:59 ` Takashi Iwai 2020-10-15 10:47 ` Gyeongtaek Lee 2020-10-20 5:23 ` Gyeongtaek Lee 2020-10-26 9:18 ` Gyeongtaek Lee 2020-10-26 17:01 ` Takashi Iwai [this message] 2020-10-27 1:56 ` Gyeongtaek Lee [not found] <CGME20200928105009epcas2p4a65d50d9d09800281395a490d1844ef3@epcas2p4.samsung.com> 2020-09-28 10:50 ` Gyeongtaek Lee 2020-09-28 11:13 ` Jaroslav Kysela 2020-09-28 14:34 ` Pierre-Louis Bossart 2020-09-29 1:51 ` Gyeongtaek Lee 2020-09-29 7:12 ` Takashi Iwai 2020-09-29 17:27 ` Jaroslav Kysela 2020-09-30 9:35 ` Takashi Iwai 2020-09-30 9:57 ` Jaroslav Kysela 2020-09-30 10:33 ` Takashi Iwai 2020-09-30 11:23 ` Jaroslav Kysela 2020-10-01 10:35 ` Vinod Koul
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=s5h5z6w53bm.wl-tiwai@suse.de \ --to=tiwai@suse.de \ --cc=alsa-devel@alsa-project.org \ --cc=gt82.lee@samsung.com \ --cc=hmseo@samsung.com \ --cc=khw0178.kim@samsung.com \ --cc=kimty@samsung.com \ --cc=lgirdwood@gmail.com \ --cc=pierre-louis.bossart@linux.intel.com \ --cc=pilsun.jang@samsung.com \ --cc=s47.kang@samsung.com \ --cc=tiwai@suse.com \ --cc=tkjung@samsung.com \ --cc=vkoul@kernel.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
Alsa-Devel Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/alsa-devel/0 alsa-devel/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 alsa-devel alsa-devel/ https://lore.kernel.org/alsa-devel \ alsa-devel@alsa-project.org public-inbox-index alsa-devel Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.alsa-project.alsa-devel AGPL code for this site: git clone https://public-inbox.org/public-inbox.git