From: Richard Fitzgerald <rf-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
To: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
myungjoo.ham-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org,
cw00.choi-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org,
ckeepax-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org,
patches-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-gpio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 7/8] ASoC: wm8998: Initial WM8998 codec driver
Date: Thu, 23 Apr 2015 15:28:23 +0100 [thread overview]
Message-ID: <20150423142823.GB17323@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20150422110030.GQ22845-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
On Wed, Apr 22, 2015 at 12:00:30PM +0100, Mark Brown wrote:
> On Tue, Apr 21, 2015 at 01:33:55PM +0100, Richard Fitzgerald wrote:
>
> > +static int wm8998_in1mux_ev(struct snd_soc_dapm_widget *w,
> > + struct snd_kcontrol *kcontrol,
> > + int event)
> > +{
> > + struct snd_soc_codec *codec = snd_soc_dapm_to_codec(w->dapm);
> > + struct arizona *arizona = dev_get_drvdata(codec->dev->parent);
> > + unsigned int left_mux, right_mux, in1mode, old;
> > +
> > + switch (event) {
> > + case SND_SOC_DAPM_PRE_PMU:
> > + /* Validate the mux configuration */
> > + left_mux = snd_soc_read(codec, ARIZONA_ADC_DIGITAL_VOLUME_1L) &
> > + ARIZONA_IN1L_SRC_MASK;
> > + right_mux = snd_soc_read(codec, ARIZONA_ADC_DIGITAL_VOLUME_1R) &
> > + ARIZONA_IN1R_SRC_MASK;
> > +
> > + /* Only IN1A can be digital, IN1B is always analogue */
> > + in1mode = (arizona->pdata.inmode[0] & 2)
> > + << (ARIZONA_IN1_MODE_SHIFT - 1);
> > +
> > + if (in1mode != 0) {
> > + /* if IN1A is digital, the only valid mux configs
> > + * are both channels A or both channels B.
> > + */
> > + if (left_mux != right_mux) {
> > + dev_err(arizona->dev,
> > + "IN1=DMIC and IN1L Mux != IN1R Mux");
> > + return -EINVAL;
> > + }
>
> This (or at least some of it) seems like something we should be doing by
> registering different widgets and routing at device probe time.
I'm not sure this is really a routing or widget problem. Problem is that
if the muxed inputs are analogue we need to provide separate ALSA controls
for the left and right mux because it is allowed to use them as two
independant mono channels with separate muxing. But if they are
configured as digital the mux controls are ganged so must be set the
same. I don't feel good about registering a single mux control if its
digital and two if its analogue because that means the codec's control
list depends on a pdata option. I could implement the control pair
so that if the input is digital changing one control always changes
the other so they will always be forced to the same setting. Any
better options?
>
> > + old = snd_soc_read(codec, ARIZONA_IN1L_CONTROL) &
> > + ARIZONA_IN1_MODE_MASK;
>
> > + if (old != in1mode)
> > + snd_soc_update_bits(codec, ARIZONA_IN1L_CONTROL,
> > + ARIZONA_IN1_MODE_MASK, in1mode);
>
> Why bother with the read into old here? Suppressing redundant updates
> is part of the point of snd_soc_update_bits().
Agreed, probably a legacy of an earlier implementation that's now redundant.
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-04-23 14:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 12:33 [PATCH 0/8] Add support for Wolfson WM8998 and WM1814 codecs Richard Fitzgerald
2015-04-21 12:33 ` [PATCH 1/8] mfd: arizona: Split INx_MODE into two fields Richard Fitzgerald
2015-04-21 12:33 ` [PATCH 2/8] ASoC: arizona: add defines for single-input gain control Richard Fitzgerald
2015-04-22 11:05 ` Mark Brown
2015-04-21 12:33 ` [PATCH 3/8] mfd: arizona: Add support for WM8998 and WM1814 Richard Fitzgerald
[not found] ` <1429619636-25478-4-git-send-email-rf-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2015-04-22 11:08 ` Mark Brown
2015-04-27 12:40 ` Richard Fitzgerald
2015-04-21 12:33 ` [PATCH 4/8] gpio: arizona: add " Richard Fitzgerald
2015-04-28 12:59 ` Linus Walleij
2015-04-21 12:33 ` [PATCH 5/8] regulator: " Richard Fitzgerald
2015-04-22 11:04 ` Mark Brown
2015-04-21 12:33 ` [PATCH 6/8] extcon: arizona: Add " Richard Fitzgerald
2015-04-22 5:53 ` Chanwoo Choi
2015-04-22 9:19 ` Richard Fitzgerald
2015-04-22 10:20 ` Chanwoo Choi
2015-04-23 14:15 ` Richard Fitzgerald
2015-04-24 0:59 ` [alsa-devel] " Chanwoo Choi
2015-04-21 12:33 ` [PATCH 7/8] ASoC: wm8998: Initial WM8998 codec driver Richard Fitzgerald
2015-04-22 11:00 ` Mark Brown
[not found] ` <20150422110030.GQ22845-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2015-04-23 14:28 ` Richard Fitzgerald [this message]
2015-04-23 17:54 ` Mark Brown
2015-04-22 19:46 ` Paul Bolle
2015-04-21 12:33 ` [PATCH 8/8] Documentation: Add WM8998/WM1814 device tree bindings Richard Fitzgerald
2015-04-23 2:05 ` Austin, Brian
2015-04-23 14:46 ` [alsa-devel] " Richard Fitzgerald
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=20150423142823.GB17323@opensource.wolfsonmicro.com \
--to=rf-yzvpicuk2aatku/dhu1wvuem+bqzidxxqq4iyu8u01e@public.gmane.org \
--cc=alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=ckeepax-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org \
--cc=cw00.choi-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-gpio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=myungjoo.ham-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
--cc=patches-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.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 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).