From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Richard Fitzgerald <rf@opensource.wolfsonmicro.com>
Cc: vinod.koul@intel.com, ckeepax@opensource.wolfsonmicro.com,
alsa-devel@alsa-project.org, elaurent@google.com
Subject: Re: [TINYCOMPRESS][PATCH 1/1] compress: no need to set metadata before calling next_track
Date: Mon, 03 Mar 2014 08:57:10 -0600 [thread overview]
Message-ID: <53149846.3040104@linux.intel.com> (raw)
In-Reply-To: <20140303132547.GA20710@opensource.wolfsonmicro.com>
> Any format, or any use-case, where we don't need to send metadata. I said "other formats do not
> _necessarily_ require any additional metadata". I'm not saying that _no_ other format needs metadata,
> just that it's not something that's always going to be mandatory. Also you shouldn't think only in
> terms of gapless play, you can chain track together for other reasons than gapless (for example to
> make best use of the DSP buffering and allow maximum host sleep time across multiple tracs) and still
> want to be able to do partial drains to know when the DSP starts decoding the next track.
My point was that it's way simpler to use regular playback if you don't
need the gapless functionality. I don't buy the argument on power
savings either, if the transition lasts 500ms with 3mn tracks, we are
talking about optimizing a state that represents 0.27% of the AP activity.
> Also there's no reason why the kernel should be enforcing this restriction - the core ALSA state
> machine doesn't need the metadata so it should be left to the DSP driver and/or firmware to decide
> whether metadata is mandatory in the current situation.
The problem is that you removed checks at the kernel and tinycompress
levels, essentially moving error management to the HAL and firmware. I
would agree to the change at the kernel level but it makes sense to have
a common approach in tinycompress to make the integration work lighter.
If you truly want to be generic we should provide information at the
codec level on whether gapless is supported and if there is a need for
metadata - e.g. reclaim a reserved field from snd_codec_desc in
compress_params.h, and do the check only if needed.
next prev parent reply other threads:[~2014-03-03 14:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 14:29 [TINYCOMPRESS][PATCH 1/1] compress: no need to set metadata before calling next_track Richard Fitzgerald
2014-02-27 16:07 ` Pierre-Louis Bossart
2014-03-03 13:25 ` Richard Fitzgerald
2014-03-03 14:57 ` Pierre-Louis Bossart [this message]
2014-03-03 16:36 ` Richard Fitzgerald
2014-03-03 19:40 ` Pierre-Louis Bossart
2014-03-06 10:32 ` Richard Fitzgerald
2014-03-07 14:32 ` Richard Fitzgerald
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=53149846.3040104@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=elaurent@google.com \
--cc=rf@opensource.wolfsonmicro.com \
--cc=vinod.koul@intel.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