[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200622053441.GE2324254@vkoul-mobl>
Date: Mon, 22 Jun 2020 11:04:41 +0530
From: Vinod Koul <vkoul@...nel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>
Cc: Takashi Iwai <tiwai@...e.com>, Jaroslav Kysela <perex@...ex.cz>,
Charles Keepax <ckeepax@...nsource.cirrus.com>,
alsa-devel@...a-project.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/3] ALSA: compress: document the compress gapless audio
state machine
On 19-06-20, 09:27, Pierre-Louis Bossart wrote:
>
> > +For Gapless, we move from running state to partial drain and back, along
> > +with setting of meta_data and signalling for next track ::
> > +
> > +
> > + +----------+
> > + compr_drain_notify() | |
> > + +------------------------>| RUNNING |
> > + | | |
> > + | +----------+
> > + | |
> > + | |
> > + | | compr_next_track()
> > + | |
> > + | V
> > + | +----------+
> > + | | |
> > + | |NEXT_TRACK|
> > + | | |
> > + | +----------+
> > + | |
> > + | |
> > + | | compr_partial_drain()
> > + | |
> > + | V
> > + | +----------+
> > + | | |
> > + +------------------------ | PARTIAL_ |
> > + | DRAIN |
> > + +----------+
>
> May I suggest having a single state machine, not a big one and an additional
> partial one. It would help explain why in one case compr_drain_notify()
> triggers a transition to RUNNING while in the other one it goes to SETUP.
>
> I realize it's more complicated to edit but it'd be easier on
> reviewers/users.
Ell adding stop and transitions would really make it complicated and
gapless is a bit different handling and it looks cleaner this way IMO,
so lets stick to this. Feel free to create one if you are up for it.
--
~Vinod
Powered by blists - more mailing lists