From: Vinod Koul <vinod.koul@intel.com>
To: Tim Sheridan <Tim.Sheridan@imgtec.com>
Cc: Takashi Iwai <tiwai@suse.de>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
'Pierre-Louis Bossart' <pierre-louis.bossart@linux.intel.com>,
Neil Jones <neil.jones@imgtec.com>
Subject: Re: [PATCH] ALSA: compress: Add DSP private metadata interface
Date: Tue, 23 Feb 2016 21:37:54 +0530 [thread overview]
Message-ID: <20160223160754.GL17690@localhost> (raw)
In-Reply-To: <98E3058E5505294895CA69F176CAD6626A6D90F7@LEMAIL01.le.imgtec.org>
On Tue, Feb 23, 2016 at 03:40:29PM +0000, Tim Sheridan wrote:
> Hi Pierre-Louis,
>
> > I am not too sure I understand what you refer to as synchronization or multi-
> > device synchronization mechanisms. Since you mentioned you only need an
> > initial time, I wonder if this is conceptually related to the
> > start_at() functionality discussed last year for PCM?
>
> Yup, it is related to the start_at() functionality. Before start_at() playback can happen, the AXD DSP must be switched into the start_at mode.
>
> > If you have a set of implementation-defined mechanisms related to
> > algorithms, why not use an ALSA binary control where you define you own
> > syntax and content and use the alsa control layer as a 'dumb' pipe between
> > user and kernel. That's what everyone does for DSP control.
>
> Ah, thanks very much for that advice. This looks like a good option (looking how it's being done for filter parameters in sound/soc/intel/atom).
Also please note that we can now avoid hard coding these in kernel. You can
define a topology graph for DSP and use alsa topology to create a topology
binary which is loaded by driver and passed to ASoC topology core which
creates these elements as well as DAPM graph
This way you can change graphs and customize them very easily!
Thanks
--
~Vinod
prev parent reply other threads:[~2016-02-23 16:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 17:54 [PATCH] ALSA: compress: Add DSP private metadata interface Tim Sheridan
2016-02-23 9:31 ` Takashi Iwai
2016-02-23 9:42 ` Vinod Koul
2016-02-23 12:47 ` Tim Sheridan
2016-02-23 14:39 ` Pierre-Louis Bossart
2016-02-23 15:40 ` Tim Sheridan
2016-02-23 16:07 ` Vinod Koul [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=20160223160754.GL17690@localhost \
--to=vinod.koul@intel.com \
--cc=Tim.Sheridan@imgtec.com \
--cc=alsa-devel@alsa-project.org \
--cc=neil.jones@imgtec.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tiwai@suse.de \
/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.