linux-kernel - Re: [PATCH v3 7/8] ASoC: wm8998: Initial WM8998 codec driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 5 May 2015 14:31:29 +0100
From:	Richard Fitzgerald <rf@...nsource.wolfsonmicro.com>
To:	Mark Brown <broonie@...nel.org>
Cc:	lee.jones@...aro.org, linus.walleij@...aro.org, gnurou@...il.com,
	cw00.choi@...sung.com, myungjoo.ham@...sung.com,
	devicetree@...r.kernel.org, alsa-devel@...a-project.org,
	patches@...nsource.wolfsonmicro.com, linux-kernel@...r.kernel.org,
	linux-gpio@...r.kernel.org, ckeepax@...nsource.wolfsonmicro.com
Subject: Re: [PATCH v3 7/8] ASoC: wm8998: Initial WM8998 codec driver

> 
> > > > +static const char * const wm8998_inmux_texts[] = {
> > > > +	"A",
> > > > +	"B",
> 
> > > Those are some fun input names...
> 
> > ... that's what the mux positions are called and it seems nice to have consistent
> > naming for all similar muxes across channels and across future codecs. Like for
> > example to switch both muxes of a stereo input you set them both to the same
> > position name (both "A" or both "B") is clearer, and quicker to spot in a dump
> > of ALSA control settings, than having the two muxes set to different enumeration
> > strings that actually mean the same mux position.
> 
> Equally when setting the muxes settings called A and B that's not really
> telling people what they do.

We can't really tell people what the selection does because that depends on
the external hardware. The A setting might be a headset mic, or a line in,
or a builtin mic...

All we can do is say what the selection is called generically by the codec.
So take the IN1L signal, on the codec it has two inputs "A" and "B". The
IN1L Mux control has two settings "A" and "B". That seems clear.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/