linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Fitzgerald <rf@opensource.wolfsonmicro.com>
To: Mark Brown <broonie@kernel.org>
Cc: lee.jones@linaro.org, linus.walleij@linaro.org, gnurou@gmail.com,
	cw00.choi@samsung.com, myungjoo.ham@samsung.com,
	devicetree@vger.kernel.org, alsa-devel@alsa-project.org,
	patches@opensource.wolfsonmicro.com,
	linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
	ckeepax@opensource.wolfsonmicro.com
Subject: Re: [PATCH v3 7/8] ASoC: wm8998: Initial WM8998 codec driver
Date: Wed, 6 May 2015 10:24:05 +0100	[thread overview]
Message-ID: <20150506092405.GA17710@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20150505215934.GH15510@sirena.org.uk>

On Tue, May 05, 2015 at 10:59:34PM +0100, Mark Brown wrote:
> On Tue, May 05, 2015 at 02:31:29PM +0100, Richard Fitzgerald wrote:
> 
> > 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.
> 
> So you're saying that you've got a mux on a single physical input which
> has two inputs?  Are you sure that this is actually a mux and not some
> sort of mode setting that should be in platform data or DT - what do
> these settinngs actually correspond to?  The routes in the driver look
> like there's two physical pins for each one of IN1L/R which the device
> can switch between for some reason which does correspond to a mux but
> that'd more normally be named IN1AL or similar.
> 

No, I'm just saying I don't see how calling the mux positions "IN1AL"
is any clearer than calling them "A" and "B". The "IN1AL" names of the
DAPM widgets is purely an internal detail that you wouldn't see through
the ALSA interface anyway so they don't relate any more closely to what
Joe user is seeing in the control list. The IN1L mux is for IN1L
so including that information in the mux position is redundant. For me
the real benefit of the "A"/"B" naming is that if you're reading through
a configuration script and saw something like

    'IN1L Mux' = 'B'
    'IN1R Mux' = 'B'

It's much more readably obvious that both channels are set the same
rather than

    'IN1L Mux' = 'IN1BL'
    'IN1R Mux' = 'IN1BR'

The second version doesn't tell you any more information than the first
but makes it harder to scan so you have to read more carefully to check
the settings


> Though if the left and right side need to be set to the same thing
> (which IIRC a previous version had code to check for and you did mention
> in your mail) all the time then why are there two separate muxes anyway?

They only need to be set the same if the "A" input is set to digital mic
mode because that uses pins from both the left and right channel to
run the single digital interface. If the A input is analogue the two
channels are independant so the left/right muxes can be set to A or B
inputs independantly.


  reply	other threads:[~2015-05-06  9:24 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-01 15:15 [PATCH v3 0/8] Add support for Wolfson WM8998 and WM1814 codecs Richard Fitzgerald
2015-05-01 15:15 ` [PATCH v3 1/8] mfd: arizona: Split INx_MODE into two fields Richard Fitzgerald
2015-05-13 12:28   ` Lee Jones
2015-05-01 15:15 ` [PATCH v3 2/8] ASoC: arizona: add defines for single-input gain control Richard Fitzgerald
2015-05-01 15:15 ` [PATCH v3 3/8] mfd: arizona: Add support for WM8998 and WM1814 Richard Fitzgerald
2015-05-02  9:58   ` Paul Bolle
2015-05-04  9:11     ` Richard Fitzgerald
2015-05-04 10:44       ` Paul Bolle
2015-05-07  8:52   ` Lee Jones
2015-05-08  9:11     ` Richard Fitzgerald
2015-05-01 15:15 ` [PATCH v3 4/8] gpio: arizona: add " Richard Fitzgerald
2015-05-01 15:15 ` [PATCH v3 5/8] regulator: " Richard Fitzgerald
2015-05-01 15:15 ` [PATCH v3 6/8] extcon: arizona: Add " Richard Fitzgerald
2015-05-01 15:15 ` [PATCH v3 7/8] ASoC: wm8998: Initial WM8998 codec driver Richard Fitzgerald
2015-05-04 11:39   ` Mark Brown
2015-05-05  9:24     ` Richard Fitzgerald
2015-05-05 10:53       ` Mark Brown
2015-05-05 13:31         ` Richard Fitzgerald
2015-05-05 21:59           ` Mark Brown
2015-05-06  9:24             ` Richard Fitzgerald [this message]
2015-05-06 11:48               ` Mark Brown
2015-05-06 12:21                 ` Richard Fitzgerald
2015-05-06 12:34                   ` Mark Brown
2015-05-01 15:15 ` [PATCH v3 8/8] Documentation: Add WM8998/WM1814 device tree bindings Richard Fitzgerald
2015-05-13 12:29   ` Lee Jones

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=20150506092405.GA17710@opensource.wolfsonmicro.com \
    --to=rf@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=ckeepax@opensource.wolfsonmicro.com \
    --cc=cw00.choi@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=gnurou@gmail.com \
    --cc=lee.jones@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=myungjoo.ham@samsung.com \
    --cc=patches@opensource.wolfsonmicro.com \
    /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).