From: Mark Brown <broonie@kernel.org>
To: Richard Fitzgerald <rf@opensource.wolfsonmicro.com>
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 12:48:49 +0100 [thread overview]
Message-ID: <20150506114849.GM22845@sirena.org.uk> (raw)
In-Reply-To: <20150506092405.GA17710@opensource.wolfsonmicro.com>
[-- Attachment #1: Type: text/plain, Size: 1273 bytes --]
On Wed, May 06, 2015 at 10:24:05AM +0100, Richard Fitzgerald wrote:
> 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
Providing that people remember that this is what's going on here and
that they remember that for this mux this shortened name is used rather
than the full one. We're relatively consistent in doing this for most
drivers, it's helpful that "I want to connect X to Y" usually translates
directly into one of "amixer cset X Y" or "amixer cset 'X Y' on".
> 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
Right, but as I said on the initial version in the case where you care
the user probably shouldn't have the ability to set them independently
in the first place.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-05-06 11:49 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
2015-05-06 11:48 ` Mark Brown [this message]
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=20150506114849.GM22845@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.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 \
--cc=rf@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
all inboxes | Powered by JetHome®