Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Banajit Goswami" <bgoswami@codeaurora.org>
To: vinod.koul@linux.intel.com, pierre-louis.bossart@linux.intel.com
Cc: alsa-devel@alsa-project.org, plai@codeaurora.org
Subject: compress: adding support for hardware dependent params
Date: Sun, 2 Feb 2014 02:50:36 -0000	[thread overview]
Message-ID: <655481c83253b83c0c7b902829eabfa6.squirrel@www.codeaurora.org> (raw)

Hi,

 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.
 Below are few of the proposed solutions that we could think of at this
point for getting this done-


1. Adding new IOCTL call: Add a new ioctl control in compress-offload.c
file to handle hardware specific parameters setting. This new ioctl
control will call into soc-compress.c and eventually call into platform
driver ioctl to set those hardware specific parameters. In this case, we
will add a new structure, let's say "snd_compr_hw_ctrl_params", with the
same fields as "snd_compr_metadata" struct.


2. Adding a function hw_dependant_hw_params(), which will be called after
hw_params() and before prepare() function. The new function will
eventually call into the platform driver to get the hardware specific
parameters set. Once implemented, this would look something like-
  hw_params();
  hw_dependant_hw_params();
  prepare();


3. Add a function "hw_dependant_hw_params()", as _part_ of the hw_params()
function. This new function will be called after the (existing) generic
parameters are set. So once implemented, the proposed function calls would
look like-
  hw_params() {
	generic_hw_params();
	hw_dependant_hw_params();
  }
  prepare();


We would like to get feedback on these proposed solutions and get a
discussion going to see how best these requirements can be fitted in the
current Compressed ALSA framework (for mainlining).

Thanks and Regards,
Banajit Goswami

The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation

             reply	other threads:[~2014-02-02  2:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-02  2:50 Banajit Goswami [this message]
2014-02-03 14:25 ` compress: adding support for hardware dependent params Pierre-Louis Bossart
  -- 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=655481c83253b83c0c7b902829eabfa6.squirrel@www.codeaurora.org \
    --to=bgoswami@codeaurora.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=pierre-louis.bossart@linux.intel.com \
    --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