From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: David Henningsson <david.henningsson@canonical.com>
Cc: Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH 2/2] ALSA: Integrate control based jack reporting with core jack reporting
Date: Wed, 8 Feb 2012 13:57:20 +0000 [thread overview]
Message-ID: <20120208135719.GD5943@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4F327A21.8030805@canonical.com>
[-- Attachment #1.1: Type: text/plain, Size: 847 bytes --]
On Wed, Feb 08, 2012 at 02:35:29PM +0100, David Henningsson wrote:
> On 02/08/2012 12:46 PM, Mark Brown wrote:
> >Except for Mic where I don't mind either way I'd rather bring the HDA
> >names into (but note that the idea is to remove the HDA specific jack
> >controls - I think these names are used in other places though?).
> I'll let Takashi have the final say about the names. But note that
> for HDA these names will not be enough, e g, we might have one
> "Front Mic" and one "Rear Mic" and need to know which one is which.
Remember that once these are merged properly we'll be adding the jack
name on the front so the bare names will only exist for one or two
commits - doing so sensibly would mean changing the kctl API and doing
a refactor on that when the immediate goal is to make it private seems
like more trouble than it's worth.
[-- 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-02-08 13:57 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
2012-02-22 15:02 ` [PATCH 1/2] ALSA: Use a define for the number of jack switch types Mark Brown
2012-02-22 16:28 ` Takashi Iwai
2012-02-22 16:34 ` Mark Brown
2012-02-22 16:41 ` Takashi Iwai
2012-02-27 16:37 ` Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
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
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=20120208135719.GD5943@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=david.henningsson@canonical.com \
--cc=patches@opensource.wolfsonmicro.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).