alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Chris Winter <elwintro@gmail.com>
To: Liam Girdwood <lrg@slimlogic.co.uk>
Cc: Takashi Iwai <tiwai@suse.de>,
	alsa-devel@alsa-project.org,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Stefan Schmidt <stefan@slimlogic.co.uk>,
	Justin Xu <justinx@slimlogic.co.uk>
Subject: Re: [PATCH 1/3] ucm: header - ALSA Use Case Manager
Date: Tue, 24 Aug 2010 14:09:45 -0500	[thread overview]
Message-ID: <AANLkTimRsGPX6ZL8_iMe+TieozVr_fNx7aDYckBXHbZW@mail.gmail.com> (raw)
In-Reply-To: <1282580239-10549-2-git-send-email-lrg@slimlogic.co.uk>

Hi Liam,

On Mon, Aug 23, 2010 at 11:17 AM, Liam Girdwood <lrg@slimlogic.co.uk> wrote:
> This patch adds the API header for alsa-lib Use Case Management support.
>
> This file defines the public interface exported by UCM to client
> applications.
>
> UCM development has been kindly sponsored by Texas Instruments Inc,
> Wolfson Microelectronics PLC and Slimlogic Ltd.
>
> CC: Mark Brown <broonie@opensource.wolfsonmicro.com>
> Signed-off-by: Stefan Schmidt <stefan@slimlogic.co.uk>
> Signed-off-by: Jaroslav Kysela <perex@perex.cz>
> Signed-off-by: Justin Xu <justinx@slimlogic.co.uk>
> Signed-off-by: Liam Girdwood <lrg@slimlogic.co.uk>
> ---
>  include/use-case.h |  427 ++++++++++++++++++++++++++++++++++++++++++++++++++++
>  1 files changed, 427 insertions(+), 0 deletions(-)
>  create mode 100644 include/use-case.h

[...]

> +/**
> + * \brief Get ALSA volume/mute control names depending on use case device.
> + * \param uc_mgr Use case manager
> + * \param type The control type we are looking for
> + * \param device The device we are interested in.
> + * \return name if success, otherwise NULL
> + *
> + * Get the control name for common volume and mute controls that are aliased
> + * in the current use case verb.
> + */
> +const char *snd_use_case_get_device_ctl_elem_id(snd_use_case_mgr_t *uc_mgr,
> +               enum snd_use_case_control_alias type, const char *device);
> +
> +/**
> + * \brief Get ALSA volume/mute control names depending on use case modifier.
> + * \param uc_mgr Use case manager
> + * \param type The control type we are looking for
> + * \param modifier The modifier we are interested in.
> + * \return name if success, otherwise NULL
> + *
> + * Get the control name for common volume and mute controls that are aliased
> + * in the current use case modifier.
> + */
> +const char *snd_use_case_get_modifier_ctl_elem_id(snd_use_case_mgr_t *uc_mgr,
> +               enum snd_use_case_control_alias type, const char *modifier);


It would appear that the implementations of the above two functions
are named differently in src/use-case.c:

const char *snd_use_case_get_device_ctl_elem_name(...)
const char *snd_use_case_get_modifier_ctl_elem_name(...)

Regards,

Chris

  reply	other threads:[~2010-08-24 19:10 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-23 16:17 [PATCH 0/3] alsa-lib: UCM - Use Case Manager Liam Girdwood
2010-08-23 16:17 ` [PATCH 1/3] ucm: header - ALSA " Liam Girdwood
2010-08-24 19:09   ` Chris Winter [this message]
2010-08-24 20:34     ` Liam Girdwood
2010-08-23 16:17 ` [PATCH 3/3] ucm: build - add build support for " Liam Girdwood
2010-08-23 17:47 ` [PATCH 0/3] alsa-lib: UCM - " Jaroslav Kysela
2010-08-23 17:50   ` Mark Brown
2010-08-23 17:51     ` Mark Brown
2010-08-24  9:09   ` Liam Girdwood
2010-08-25  8:28     ` Jaroslav Kysela
2010-08-25  9:26       ` Liam Girdwood
2010-08-25  9:35         ` Jaroslav Kysela
2010-08-25 10:43           ` Liam Girdwood
2010-08-25 16:34             ` Jaroslav Kysela
     [not found]               ` <1283864698.3048.26.camel@odin>
2010-09-07 14:42                 ` Jaroslav Kysela
2010-09-07 15:53                   ` Mark Brown
2010-09-07 18:17                     ` Jaroslav Kysela
2010-09-07 18:53                       ` Mark Brown
2010-09-08  7:54                         ` Jaroslav Kysela
2010-09-08  9:47                           ` Mark Brown
2010-09-08  8:19                         ` Jaroslav Kysela
2010-09-09 12:16                           ` Mark Brown
2010-09-07 20:02                       ` Liam Girdwood
2010-09-07 22:43                         ` Mark Brown
2010-09-20 16:26                   ` Colin Guthrie
2010-09-21 17:13                     ` Chris Winter
2010-09-21 17:40                       ` Mark Brown
2010-09-21 18:11                       ` Jaroslav Kysela
2010-09-22 11:47                         ` Colin Guthrie
2010-09-22 13:20                         ` Mark Brown
2010-09-22 14:06                           ` Jaroslav Kysela
2010-09-22 15:14                             ` Mark Brown
2010-09-22 18:05                               ` Jaroslav Kysela
2010-09-22 18:48                                 ` Mark Brown
2010-09-23  7:18                                   ` Niels Mayer
2010-09-23 10:06                                     ` Mark Brown
2010-09-25 13:07                                     ` Colin Guthrie
2010-09-22 15:20                             ` Liam Girdwood
2010-08-24  1:23 ` Raymond Yau
2010-08-24  9:41   ` 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=AANLkTimRsGPX6ZL8_iMe+TieozVr_fNx7aDYckBXHbZW@mail.gmail.com \
    --to=elwintro@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=justinx@slimlogic.co.uk \
    --cc=lrg@slimlogic.co.uk \
    --cc=stefan@slimlogic.co.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).