From: Mark Brown <broonie@kernel.org>
To: Banajit Goswami <bgoswami@codeaurora.org>
Cc: noman pouigt <variksla@gmail.com>,
vinod.koul@linux.intel.com, alsa-devel@alsa-project.org,
plai@codeaurora.org, pierre-louis.bossart@linux.intel.com
Subject: Re: compress: adding support for hardware dependent params
Date: Sun, 16 Mar 2014 20:00:16 +0000 [thread overview]
Message-ID: <20140316200016.GQ366@sirena.org.uk> (raw)
In-Reply-To: <77e1ff531b0670bae0c47d32a76bb6f4.squirrel@www.codeaurora.org>
[-- Attachment #1.1: Type: text/plain, Size: 679 bytes --]
On Sun, Mar 16, 2014 at 05:55:37AM -0000, Banajit Goswami wrote:
> audio. The parameters we are looking to set is not specific to gapless
> audio, but rather a few hardware/board specific parameters (for passing
> to our driver)
Why not just use ALSA controls for this - that's the normal way of doing
things like this, if the parameters aren't part of the stream data it's
not obvious to me why they're being set on the stream. I'm also a bit
concerned about the idea that applications would need to support another
custom API for passing opaque blobs to drivers, we already have bytes
controls. Can you give any examples of the sort of thing that would be
configured here?
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2014-03-16 20:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-03 9:01 compress: adding support for hardware dependent params noman pouigt
2014-02-07 5:35 ` Vinod Koul
2014-03-16 5:55 ` Banajit Goswami
2014-03-16 20:00 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-02-02 2:50 Banajit Goswami
2014-02-03 14:25 ` Pierre-Louis Bossart
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=20140316200016.GQ366@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bgoswami@codeaurora.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=plai@codeaurora.org \
--cc=variksla@gmail.com \
--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