From: Vinod Koul <vinod.koul@intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org, lgirdwood@gmail.com
Subject: Re: [RFC] ALSA: add new alsa control byte extended
Date: Fri, 29 Nov 2013 18:49:10 +0530 [thread overview]
Message-ID: <20131129131910.GH8834@intel.com> (raw)
In-Reply-To: <20131129114603.GS27568@sirena.org.uk>
[-- Attachment #1.1: Type: text/plain, Size: 966 bytes --]
On Fri, Nov 29, 2013 at 11:46:03AM +0000, Mark Brown wrote:
> On Fri, Nov 29, 2013 at 03:59:37PM +0530, Vinod Koul wrote:
> > I am leading more towards adding new ioctl for this along with new ones for
> > enumerating controls. Then additional support for alsa-lib and tinyalsa.
> > That way existing tinymix, amxier can see these as controls while not disturbing
> > existing apps. I dont think we need save and restor, then alsactl need not be
> > modified.
>
> I doubt you need it specifically for alsactl since that's a bit basic
> for most of the users but it would be good to have the ability to write
> tools that allow people to tune interactively and then save the results
> in a format that's useful for whatever use case management is in use.
I agree alsactl may not be required here and if its felt we can always add that!
managing parameters is different problem and yes needs to be dealt sperately
with tooling as well
--
~Vinod
[-- 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:[~2013-11-29 14:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-29 4:29 [RFC] ALSA: add new alsa control byte extended Vinod Koul
2013-11-29 7:27 ` Jarkko Nikula
2013-11-29 7:18 ` Vinod Koul
2013-11-29 7:46 ` Takashi Iwai
2013-11-29 7:44 ` Vinod Koul
2013-11-29 9:08 ` Takashi Iwai
2013-11-29 8:34 ` Vinod Koul
2013-11-29 9:40 ` Jaroslav Kysela
2013-11-29 9:48 ` Takashi Iwai
2013-11-29 10:10 ` Jaroslav Kysela
2013-11-29 11:25 ` Mark Brown
2013-11-29 11:31 ` Takashi Iwai
2013-11-29 12:27 ` Mark Brown
2013-11-29 11:05 ` Mark Brown
2013-11-29 10:29 ` Vinod Koul
2013-11-29 11:46 ` Mark Brown
2013-11-29 13:19 ` Vinod Koul [this message]
2013-11-29 13:11 ` Charles Keepax
2013-11-29 13:28 ` Vinod Koul
2013-11-29 14:17 ` 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=20131129131910.GH8834@intel.com \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.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.