Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Tim Sheridan <Tim.Sheridan@imgtec.com>,
	'Vinod Koul' <vinod.koul@intel.com>, Takashi Iwai <tiwai@suse.de>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	Neil Jones <neil.jones@imgtec.com>
Subject: Re: [PATCH] ALSA: compress: Add DSP private metadata interface
Date: Tue, 23 Feb 2016 08:39:31 -0600	[thread overview]
Message-ID: <56CC6F23.6090705@linux.intel.com> (raw)
In-Reply-To: <98E3058E5505294895CA69F176CAD6626A6D8BE1@LEMAIL01.le.imgtec.org>


> AXD's got various features which require mode setting (e.g. for
> selecting between multi-device synchronization mechanisms that it
> supports). This would need an enum control, but I guess that this
> could be fudged with mutually exclusive switch controls for each of
> the enum values. AXD's also got numeric configuration parameters
> which it needs to be able to receive (e.g. parameters for stream
> synchronization heuristics, audio filter coefficients, etc.). Maybe a
> volume control with a domain wide enough could be used for this kind
> of configuration parameter. It's rather horrible, but might be fine
> for while the AXD driver is out of tree and there aren't more
> appropriate ALSA control types (e.g. enum and non-volume integer).
> :-/

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?

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.

  reply	other threads:[~2016-02-23 14:39 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 [this message]
2016-02-23 15:40         ` Tim Sheridan
2016-02-23 16:07           ` 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=56CC6F23.6090705@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --cc=Tim.Sheridan@imgtec.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=neil.jones@imgtec.com \
    --cc=tiwai@suse.de \
    --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