From: Mark Brown <broonie@kernel.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: Maxime Ripard <maxime.ripard@free-electrons.com>,
Chen-Yu Tsai <wens@csie.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
alsa-devel@alsa-project.org, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-sunxi@googlegroups.com
Subject: Re: [linux-sunxi] Re: [PATCH v8 2/2] ASoc: sun4i-codec: Add FM, Line and Mic inputs
Date: Thu, 31 Dec 2015 22:19:35 +0000 [thread overview]
Message-ID: <20151231221935.GG16023@sirena.org.uk> (raw)
In-Reply-To: <20151228040649.475a742f@dayas>
[-- Attachment #1: Type: text/plain, Size: 1569 bytes --]
On Mon, Dec 28, 2015 at 04:06:49AM +0100, Danny Milosavljevic wrote:
> Maxime Ripard <maxime.ripard@free-electrons.com> wrote:
> > > +static SOC_ENUM_SINGLE_DECL(sun4i_codec_enum_capture_source,
> > > + SUN4I_CODEC_ADC_ACTL,
> > > + SUN4I_CODEC_ADC_ACTL_ADCIS,
> > > + sun4i_codec_capture_source);
> > Isn't it possible to expose this as two (shared) muxes with different
> > names to make it clear what will go to the left ADC and what will go
> > to the right?
> I don't know how to do that. I'll try to find out.
> Can two muxes use the same bit in the hardware without problems?
IIRC we fixed things so that if you've got two controls that share the
same register we do the right thing. There are other devices with this
issue but it was years ago that I last looked at them, we do have
handling.
> > Those are not volume it's gain,
> We tried to call the things ..." Gain" before and it was difficult to do,
> with some breakage along the way, see below.
> Also, Mark said they should be named ..." Volume" (see
> <https://www.mail-archive.com/linux-sunxi@googlegroups.com/msg15126.html>).
>
> >and it should probably be two different shared controls for mic1 and mic2.
Yes, this is part of the ABI and honestly from an end user point of view
there is no meaningful difference between the two words (there would be
more if it were gain and attenuation since one is amplification and the
other isn't so there are different considerations when applying them to
signals but that's not the case here).
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-12-31 22:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-21 11:31 [PATCH v8 0/2] " Danny Milosavljevic
2015-12-21 11:33 ` [linux-sunxi] [PATCH v8 1/2] " Danny Milosavljevic
2015-12-27 17:34 ` Maxime Ripard
2015-12-21 11:34 ` [PATCH v8 2/2] " Danny Milosavljevic
2015-12-27 18:21 ` Maxime Ripard
2015-12-28 3:06 ` [linux-sunxi] " Danny Milosavljevic
2015-12-31 22:19 ` Mark Brown [this message]
2016-01-06 22:09 ` Maxime Ripard
2016-01-09 15:48 ` Danny Milosavljevic
2016-03-12 7:52 ` Danny Milosavljevic
2016-03-12 8:31 ` Code Kipper
2016-03-14 10:49 ` Maxime Ripard
2016-03-15 10:58 ` Mark Brown
2016-03-19 16:13 ` Danny Milosavljevic
2016-03-21 14:24 ` Mark Brown
2016-03-21 17:54 ` Maxime Ripard
2016-04-21 8:55 ` Danny Milosavljevic
2016-03-19 16:51 ` [linux-sunxi] " Danny Milosavljevic
2016-03-21 18:06 ` Maxime Ripard
2016-03-21 18:19 ` Mark Brown
2016-03-22 12:20 ` Stefan Monnier
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=20151231221935.GG16023@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=dannym@scratchpost.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=maxime.ripard@free-electrons.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=wens@csie.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
all inboxes | Powered by JetHome®