From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Banajit Goswami <bgoswami@codeaurora.org>, vinod.koul@linux.intel.com
Cc: alsa-devel@alsa-project.org, plai@codeaurora.org
Subject: Re: compress: adding support for hardware dependent params
Date: Mon, 03 Feb 2014 08:25:31 -0600 [thread overview]
Message-ID: <52EFA6DB.4030905@linux.intel.com> (raw)
In-Reply-To: <655481c83253b83c0c7b902829eabfa6.squirrel@www.codeaurora.org>
>
> We have a requirement, where we need to set a number of hardware specific
> parameters for compressed offload use-cases, before starting a stream. As
> these parameters need to be set once for the entire session, we would
> like to explore the best way to set these additional parameters somewhere
> before calling trigger() function.
I think you need to provide more context here. The compressed API
provides a fair amount of information on the parameters needed to handle
the stream - maybe too much in most cases -, I don't really get the
rationale for hardware-specific parameters needed specifically for
compressed data that you wouldn't need for PCM.
I am also not clear on how we are going to agree on new hw_params that
are hardware specific. Shouldn't this sort of requirement be handled
through a control interface?
next prev parent reply other threads:[~2014-02-03 14:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-02 2:50 compress: adding support for hardware dependent params Banajit Goswami
2014-02-03 14:25 ` Pierre-Louis Bossart [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-02-03 9:01 noman pouigt
2014-02-07 5:35 ` Vinod Koul
2014-03-16 5:55 ` Banajit Goswami
2014-03-16 20:00 ` Mark Brown
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=52EFA6DB.4030905@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=bgoswami@codeaurora.org \
--cc=plai@codeaurora.org \
--cc=vinod.koul@linux.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