From: Stefan Monnier <monnier@iro.umontreal.ca>
To: linux-kernel@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
alsa-devel@alsa-project.org, linux-sunxi@googlegroups.com
Subject: Re: [linux-sunxi] Re: [PATCH v8 2/2] ASoc: sun4i-codec: Add FM, Line and Mic inputs
Date: Tue, 22 Mar 2016 08:20:27 -0400 [thread overview]
Message-ID: <jwvio0eu2pr.fsf-monnier+gmane.comp.hardware.netbook.arm.sunxi@gnu.org> (raw)
In-Reply-To: <20160321181900.GZ2566@sirena.org.uk>
>> I don't think you should focus too much on alsamixer, there's other
>> tools to modify the configuration.
> The expectation is that most users will use something like UCM and only
> system integrators will see the full control set in normal operation.
This presumes the "system integrator" (which could very well be the end
user in many cases) somehow knows what all the controls do/mean.
Anyway, it seems this is an ALSA problem rather than a sunxi problem.
Stefan "who wishes ALSA could describe the meaning of all those
controls, maybe as a graphical diagram, or as some kind
of (hopefully simple) program"
prev parent reply other threads:[~2016-03-22 12:21 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
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 [this message]
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=jwvio0eu2pr.fsf-monnier+gmane.comp.hardware.netbook.arm.sunxi@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=alsa-devel@alsa-project.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.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®