From: Vinod Koul <vkoul@kernel.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: 'Pierre-Louis Bossart' <pierre-louis.bossart@linux.intel.com>,
alsa-devel@alsa-project.org, khw0178.kim@samsung.com,
kimty@samsung.com, lgirdwood@gmail.com, tiwai@suse.com,
hmseo@samsung.com, tkjung@samsung.com,
Gyeongtaek Lee <gt82.lee@samsung.com>,
pilsun.jang@samsung.com, s47.kang@samsung.com
Subject: Re: [PATCH v2] ALSA: compress: allow pause and resume during draining
Date: Wed, 25 Nov 2020 16:19:06 +0530 [thread overview]
Message-ID: <20201125104906.GE8403@vkoul-mobl> (raw)
In-Reply-To: <s5h4kldq0om.wl-tiwai@suse.de>
On 25-11-20, 09:51, Takashi Iwai wrote:
> On Thu, 19 Nov 2020 03:51:19 +0100,
> Gyeongtaek Lee wrote:
> >
> > On Fri, 06 Nov 2020 09:58:24 +0100, Takashi Iwai wrote:
> > >On Tue, 27 Oct 2020 02:57:25 +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
> > >
> > >I personally find the approach is fine, but let's see what others
> > >think.
> > >
> > >One remaining concern to me is about the setup of
> > >use_pause_in_draining flag. This is done by an explicit function call
> > >after the snd_compr object initialization. It's a bit uncommon style,
> > >but OTOH I understand it from the current initialization code of
> > >compress-offload API.
> > Thanks for your kind review.
> >
> > It's been almost 2 weeks.
> > So, I think that there is no further comment for this patch.
>
> I guess it's just overlooked. Vinod?
Sorry indeed this seems to have slipped, this mostly looks okay to me
(saw some code style nits will reply on those)
I have todo in my list to fix use of PCM_STATE in compress, i will send
that later
--
~Vinod
next prev parent reply other threads:[~2020-11-25 10:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20201027015726epcas2p1af97e3b6d4a54948a0e29fced35a1cd6@epcas2p1.samsung.com>
2020-10-27 1:57 ` [PATCH v2] ALSA: compress: allow pause and resume during draining Gyeongtaek Lee
2020-11-06 8:58 ` Takashi Iwai
2020-11-19 2:51 ` Gyeongtaek Lee
2020-11-25 8:51 ` Takashi Iwai
2020-11-25 10:49 ` Vinod Koul [this message]
2020-11-25 10:58 ` Vinod Koul
[not found] <CGME20201030002721epcas2p1bffd10681a95aef2946482bf536240ae@epcas2p1.samsung.com>
2020-10-30 0:27 ` Gyeongtaek Lee
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=20201125104906.GE8403@vkoul-mobl \
--to=vkoul@kernel.org \
--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=tiwai@suse.de \
--cc=tkjung@samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox