Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lu Guanqun <guanqun.lu@intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Rajeev Kumar <rajeev-dlh.kumar@st.com>,
	"lrg@slimlogic.co.uk" <lrg@slimlogic.co.uk>
Subject: Re: [PATCH V3 1/5] sound: asoc: Adding support for STA529 Audio Codec
Date: Thu, 14 Apr 2011 22:19:36 +0800	[thread overview]
Message-ID: <20110414141936.GD31985@qtel.sh.intel.com> (raw)
In-Reply-To: <s5h62qhma4c.wl%tiwai@suse.de>

On Thu, Apr 14, 2011 at 05:54:11PM +0800, Takashi Iwai wrote:
> At Mon, 11 Apr 2011 07:56:22 -0700,
> Mark Brown wrote:
> > 
> > > +static const struct snd_kcontrol_new sta529_new_snd_controls[] = {
> > > +	SOC_ENUM("pwm select", pwm_src_enum),
> > > +	SOC_ENUM("mode select", mode_src_enum),
> > > +};
> > 
> > ALSA control names are idiomatically things like "PWM Select" with
> > capitalisation.
> 
> Actually, the capital words are no mandatory requirement (although
> it's conventionally so).  It's just alsa-mixer grouping rule that
> requires the capital words "Play", "Capture", "Volume", "Switch",
> etc.

Hi Takashi,

Where can I find these alsa-mixer grouping rule?
So that I can obey these rules and make them appear in the right view in
alsamixer.

> 
> You don't have to obey Capitalism :)
> 
> 
> Takashi
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

-- 
guanqun

  parent reply	other threads:[~2011-04-14 14:21 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-11  5:29 [PATCH V3 0/5] Adding ASoC drivers for SPEAr13XX platform Rajeev Kumar
2011-04-11  5:30 ` [PATCH V3 1/5] sound: asoc: Adding support for STA529 Audio Codec Rajeev Kumar
2011-04-11  5:30   ` [PATCH V3 2/5] sound: asoc: Adding support for SPEAr13XX ASoC platform driver Rajeev Kumar
2011-04-11  5:30     ` [PATCH V3 3/5] sound: asoc: Adding support for SPEAr13XX ASoC machine driver Rajeev Kumar
2011-04-11  5:30       ` [PATCH V3 4/5] sound: asoc: Adding Kconfig and Makefile to support SPEAr13XX ASoC driver Rajeev Kumar
2011-04-11  5:30         ` [PATCH V3 5/5] sound: asoc: Adding support for SPEAr13XX in soc Rajeev Kumar
2011-04-11 13:00     ` [PATCH V3 2/5] sound: asoc: Adding support for SPEAr13XX ASoC platform driver Lu Guanqun
2011-04-18  5:00       ` rajeev
2011-04-11 12:53   ` [PATCH V3 1/5] sound: asoc: Adding support for STA529 Audio Codec Lu Guanqun
2011-04-11 13:35     ` Mark Brown
2011-04-11 15:09       ` Lu Guanqun
2011-04-11 23:54         ` Mark Brown
2011-04-12  0:06           ` Lu Guanqun
2011-04-11 14:56   ` Mark Brown
2011-04-14  9:54     ` Takashi Iwai
2011-04-14 12:18       ` Mark Brown
2011-04-14 12:25         ` Takashi Iwai
2011-04-14 14:19       ` Lu Guanqun [this message]
2011-04-14 14:28         ` Lu Guanqun
2011-04-15  9:27           ` Takashi Iwai
2011-04-15 14:10             ` Lu Guanqun
2011-04-15  9:23         ` Takashi Iwai
2011-04-20  4:24     ` rajeev
2011-04-20 10:56       ` Mark Brown
2011-04-20 11:41         ` rajeev
2011-04-20 11:42         ` rajeev
2011-04-11 15:45   ` Lu Guanqun

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=20110414141936.GD31985@qtel.sh.intel.com \
    --to=guanqun.lu@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=lrg@slimlogic.co.uk \
    --cc=rajeev-dlh.kumar@st.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox