From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: David Henningsson <david.henningsson@canonical.com>
Cc: alsa-devel@alsa-project.org,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
James Cameron <quozl@laptop.org>
Subject: Re: Splitting out controls
Date: Wed, 14 Oct 2015 19:20:32 +0100 [thread overview]
Message-ID: <1444846832.2606.53.camel@loki> (raw)
In-Reply-To: <561D2997.1090401@canonical.com>
On Tue, 2015-10-13 at 17:56 +0200, David Henningsson wrote:
>
> On 2015-10-13 16:55, Pierre-Louis Bossart wrote:
> > On 10/13/15 2:07 AM, David Henningsson wrote:
> >>
> >>
> >> On 2015-10-12 22:59, James Cameron wrote:
> >>> On Mon, Oct 12, 2015 at 02:49:46PM +0100, Liam Girdwood wrote:
> >>>> I've written up the minutes here below
> >>>
> >>> Thanks!
> >>>
> >>>> Splitting out controls: Takashi
> >>>> ===============================
> >>>>
> >>>> - Restricted access. Consensus to restrict access to some controls
>
> Note: There is NOT consensus.
Sorry, this should be "control values" instead of "controls". I guess my
typing speed was not fast enough to keep up :(
My understanding at the time was we could use the existing clamp API to
clamp kcontrol values (in machine drivers) to reasonable/safe values.
I did hear many objections to setting some kcontrols as RO for certain
users and RW for other users.
Liam
next prev parent reply other threads:[~2015-10-14 18:20 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 13:49 [Minutes] ELCE Audio mini conf Liam Girdwood
2015-10-12 15:30 ` Jaroslav Kysela
2015-10-12 20:59 ` Splitting out controls James Cameron
2015-10-13 7:07 ` David Henningsson
2015-10-13 8:27 ` Keyon
2015-10-13 14:55 ` Pierre-Louis Bossart
2015-10-13 15:56 ` David Henningsson
2015-10-13 16:08 ` Pierre-Louis Bossart
2015-10-16 6:41 ` David Henningsson
2015-10-16 14:49 ` Pierre-Louis Bossart
2015-10-16 15:24 ` Richard Fitzgerald
2015-10-30 2:48 ` Mark Brown
2015-10-16 15:28 ` Takashi Iwai
2015-10-14 18:20 ` Liam Girdwood [this message]
2015-10-16 15:35 ` Richard Fitzgerald
2015-10-16 16:00 ` Takashi Iwai
2015-10-16 16:31 ` Richard Fitzgerald
2015-10-16 17:00 ` Takashi Iwai
2015-10-17 15:54 ` Pierre-Louis Bossart
2015-10-17 16:02 ` Takashi Iwai
2015-10-18 6:41 ` Ricard Wanderlof
2015-10-30 2:57 ` Mark Brown
2015-10-17 16:25 ` Alexander E. Patrakov
2015-10-30 2:50 ` Mark Brown
2015-10-30 2:36 ` Mark Brown
2015-10-30 8:36 ` David Henningsson
2015-10-30 8:53 ` James Cameron
2015-10-30 9:04 ` David Henningsson
2015-11-01 2:45 ` Mark Brown
2015-10-13 14:09 ` 'BATCH flag for USB' and 'ALSA Core Challenges' Takashi Sakamoto
2015-10-13 14:44 ` Alexander E. Patrakov
2015-10-18 3:22 ` Takashi Sakamoto
2015-10-13 16:01 ` Pierre-Louis Bossart
2015-10-14 12:27 ` Liam Girdwood
2015-10-22 17:10 ` [Minutes] ELCE Audio mini conf Mark Brown
2015-10-22 17:14 ` DP hotplug on USB C 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=1444846832.2606.53.camel@loki \
--to=liam.r.girdwood@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=david.henningsson@canonical.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=quozl@laptop.org \
/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.