From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org,
David Henningsson <david.henningsson@canonical.com>
Subject: Re: [PATCH 2/2] ALSA: Integrate control based jack reporting with core jack reporting
Date: Fri, 2 Mar 2012 11:45:30 +0000 [thread overview]
Message-ID: <20120302114530.GD3230@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <s5hobsfsc9j.wl%tiwai@suse.de>
[-- Attachment #1.1: Type: text/plain, Size: 818 bytes --]
On Fri, Mar 02, 2012 at 08:16:56AM +0100, Takashi Iwai wrote:
> David Henningsson wrote:
> > Also, in the sound/soc there seem to be plenty of hits for 'Line Output'
> > which could be changed to 'Line Out', mostly for consistency. Something
> > for Mark?
> I think we should standardize "Line Out" mixer control name at first,
> e.g. updating the outdated ControlNames.txt document.
> Anyway I'll leave ASoC part as is for now.
There's also a lot of LINEOUTn and so on. I've no intention of worrying
about this stuff too much for ASoC, the name based routing is mostly
nonsensical there anyway and it's very common for the thing connected to
the line output to actually be another thing such as a speaker so acting
on the fact that it's a line output might be actively wrong at the user
level.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2012-03-02 11:45 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 17:48 [PATCH 2/2] ALSA: Integrate control based jack reporting with core jack reporting Takashi Iwai
2012-03-02 6:26 ` David Henningsson
2012-03-02 7:16 ` Takashi Iwai
2012-03-02 11:45 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-02-07 19:48 [PATCH 1/2] ALSA: Use a define for the number of jack switch types Mark Brown
2012-02-07 19:48 ` [PATCH 2/2] ALSA: Integrate control based jack reporting with core jack reporting Mark Brown
2012-02-08 8:36 ` David Henningsson
2012-02-08 11:46 ` Mark Brown
2012-02-08 13:35 ` David Henningsson
2012-02-08 13:57 ` Mark Brown
2012-02-10 10:55 ` Takashi Iwai
2012-02-10 11:36 ` Mark Brown
2012-02-10 12:16 ` Takashi Iwai
2012-02-10 13:08 ` David Henningsson
2012-02-10 15:50 ` Mark Brown
2012-02-10 16:09 ` David Henningsson
2012-02-10 16:39 ` Mark Brown
2012-02-13 13:56 ` Takashi Iwai
2012-02-13 15:44 ` Mark Brown
2012-02-13 17:40 ` Takashi Iwai
2012-02-13 19:23 ` Mark Brown
2012-02-14 7:20 ` David Henningsson
2012-02-15 2:04 ` Mark Brown
2012-02-22 16:52 ` Takashi Iwai
2012-02-22 17:18 ` Mark Brown
2012-02-22 17:34 ` Takashi Iwai
2012-02-22 18:54 ` Mark Brown
2012-02-22 20:35 ` Takashi Iwai
2012-02-22 20:55 ` Mark Brown
2012-02-23 8:10 ` Takashi Iwai
2012-02-23 7:25 ` David Henningsson
2012-02-14 1:29 ` Raymond Yau
2012-02-16 19:59 ` 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=20120302114530.GD3230@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=david.henningsson@canonical.com \
--cc=tiwai@suse.de \
/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).