From: dannym@scratchpost.org (Danny Milosavljevic)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-sunxi] Re: [PATCH v8 2/2] ASoc: sun4i-codec: Add FM, Line and Mic inputs
Date: Sat, 19 Mar 2016 17:51:24 +0100 [thread overview]
Message-ID: <20160319175124.6bfe3617@scratchpost.org> (raw)
In-Reply-To: <20160314104939.GL8418@lukather>
Hi Maxime,
> IIRC, in order to have shared controls, you just needed to share the
> controls structure.
Yeah. I did this and it actually works in a way, but in doesn't do all that I want.
There are two different kinds of sharing I mean:
The one kind with the controls structure causes the control to rename itself
to not state its mixer but there's still just one slider in the end.
So instead of "Left Mixer Left XXX" it will just say "Left XXX" if you put it
inside Left Mixer and Right Mixer and share the entry - for this hardware,
that's of doubtful use.
But what I would like to have is that the same Mic Playback Volume (the very
same bits) be used for different sliders
(1) Mic1 Left Channel Playback Volume
(2) Mic1 Right Channel Playback Volume
(3) Mic2 Left Channel Playback Volume (!!)
(4) Mic2 Right Channel Playback Volume
Additionally, Mic1 Playback and Mic2 Playback have two mutes each in the
hardware (all separately switchable).
Now if we could make the alsamixer selems look like the following,
that would be nice:
Mic1_Playback Mic2_Playback
MM MM
ii ii
cc cc
PP PP
ll ll
aa aa
yy yy
bb bb
aa aa
cc cc
kk kk
VV VV
oo oo
ll ll
uu uu
mm mm
ee ee
[Mm] [Nn]
^ ^^-- so are those, separately
+-- this one is a different muter :-)
Where the text is the same, it's supposed to signify the same bits
in the hardware.
Right now in v8 it's (and that's going to take a lot of horizontal space,
sorry - I know E-Mails like this aren't so nice to read):
Mic_Playback_Volume Left_Mic1_Playback_Switch Right_Mic1_Playback_Switch Left_Mic2_Playback_Switch Right_Mic2_Playback_Switch
MM
ii
cc
PP
ll
aa
yy
bb
aa
cc
kk
VV
oo
ll
uu
mm
ee
[MM] [NN] [OO] [PP]
^- WTF ^- WTF ^- WTF ^- WTF
(Actually, it's worse - believe it or not, that's how the simplified explanation looks)
> Unfortunately, that is exposed to the user-space. Once it's in, you
> cannot change it / fix it anymore.
Hmm. Right. Let's get it to work nicely then.
next prev parent reply other threads:[~2016-03-19 16:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-21 11:31 [PATCH v8 0/2] ASoc: sun4i-codec: Add FM, Line and Mic inputs 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
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 ` Danny Milosavljevic [this message]
2016-03-21 18:06 ` [linux-sunxi] " Maxime Ripard
2016-03-21 18:19 ` Mark Brown
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=20160319175124.6bfe3617@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=linux-arm-kernel@lists.infradead.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).