alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
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] ALSA: hda/jack - Also add jack kctls for Conexant codecs
Date: Thu, 22 Dec 2011 14:29:45 +0000	[thread overview]
Message-ID: <20111222142944.GA4546@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <s5hy5u4bseb.wl%tiwai@suse.de>

On Thu, Dec 22, 2011 at 03:19:40PM +0100, Takashi Iwai wrote:
> Mark Brown wrote:

> > Once we've got a userspace interface we're pretty much stuck with it...

> Yes, but this is no new interface.  It uses the existing control API.

In terms of system calls it's not new but once you start saying "jacks
will appear as controls called X with type Y" or whatever that's also an
interface built on top of the raw interface which applications can start
relying on.  I'd call the entire ALSA control naming standard an
interface for example.

> > Supporting multiple objects on a single jack is a very basic requirement
> > in order to support headsets (which exist on PCs as well, the MacBooks
> > for example) - we can usually distinguish between at least headset and
> > headphone.

> Interesting.  This can be a single jack connected to multiple pins, so
> the codec sees two individual detection points.  So, if we want to
> expose pins, it'd become different from the jack representation.
> Hmm...

At the hardware level this is often a single detection point with
multiple values - a common technique for distinguishing a headphone is
that it's a microphone that's had the button shorted ever since it was
plugged in.  With all the different techniques for this stuff you end up
with a N:M mapping between jacks and detection methods and the same
again for things reported.

      reply	other threads:[~2011-12-22 14:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-20 14:23 [PATCH] ALSA: hda/jack - Also add jack kctls for Conexant codecs David Henningsson
2011-12-20 14:32 ` Takashi Iwai
2011-12-20 14:44   ` Takashi Iwai
2011-12-20 23:58   ` Mark Brown
2011-12-21 14:42     ` Takashi Iwai
2011-12-22  1:08       ` Mark Brown
2011-12-22 12:21       ` Mark Brown
2011-12-22 13:55         ` Takashi Iwai
2011-12-22 14:12           ` Mark Brown
2011-12-22 14:19             ` Takashi Iwai
2011-12-22 14:29               ` Mark Brown [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=20111222142944.GA4546@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).