All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Cc: Takashi Iwai <tiwai@suse.de>,
	alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>,
	lgirdwood@gmail.com
Subject: Re: [RFC] ALSA: add new alsa control byte extended
Date: Fri, 29 Nov 2013 18:58:25 +0530	[thread overview]
Message-ID: <20131129132825.GI8834@intel.com> (raw)
In-Reply-To: <20131129131153.GF10013@opensource.wolfsonmicro.com>

On Fri, Nov 29, 2013 at 01:11:53PM +0000, Charles Keepax 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.
> 
> It does feel a little odd to have this data set through a
> different interface to other existing control data, but I guess
> anything we do does have to be very careful around upsetting
> existing user-space code.
Am thinking users and driver shouldn't feel that it is different. The approach i
am leaning now is adding three ioctls, for enumerating, reading and then
writing. The tinyalsa and alsa-lib should also enumerate these new ones.  But we
don't impact ABI so old users/apps won't change.  Similarly on kernel side we
still treat these as kcontrols and drivers use existing infrastructure to manage
these...

-- 
~Vinod

  reply	other threads:[~2013-11-29 14:25 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
2013-11-29 13:11               ` Charles Keepax
2013-11-29 13:28                 ` Vinod Koul [this message]
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=20131129132825.GI8834@intel.com \
    --to=vinod.koul@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=ckeepax@opensource.wolfsonmicro.com \
    --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.