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, 12 Mar 2016 08:52:22 +0100 [thread overview]
Message-ID: <20160312085222.226d89bf@scratchpost.org> (raw)
In-Reply-To: <20160109164832.515d69b0@dayas>
Hi,
does anyone know the answer to the questions below?
> The other direction (making two controls which both do the same and update
> each other's value) doesn't seem to be easily available.
> Should I write a _put handler that does it manually?
> (Or should that be handled by alsa-lib mixer modules instead?)
> Is it possible to merge the "Left Mixer" control and respective
> "Right Mixer" control into one selem in alsamixer?
>
> Because alsamixer actually has support for one-sided muting.
If that's unknown, I can post v9 without doing the grouping-together of mixer controls and we can use it like that - I don't want the patch to stall indefinitely on mere usability issues...
Regards,
Danny
next prev parent reply other threads:[~2016-03-12 7:52 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 [this message]
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
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=20160312085222.226d89bf@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).