All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lennart Poettering <mznyfn@0pointer.de>
To: alsa-devel@alsa-project.org
Subject: Re: RFC: Jack-detection control elements on HD-audio
Date: Fri, 19 Jun 2009 14:21:26 +0200	[thread overview]
Message-ID: <20090619122126.GA5785@tango.0pointer.de> (raw)
In-Reply-To: <s5hk538ejj4.wl%tiwai@suse.de>

On Fri, 19.06.09 10:04, Takashi Iwai (tiwai@suse.de) wrote:

> Hi,
> 
> yet another thing I've worked recently on is a bit more generalized
> framework for jack-sense reporting for HD-audio.  This supersedes the
> existing jack-sense reporting via the input layer.  In addition, it
> gives the corresponding control elements.
> 
> For example, you'll have "Jack HP-Out" (or a bit more verbose like
> "Jack HP-Out at Ext Rear") control via control API as well as other
> mixer controls.  This can notify when a jack is plugged/unplugged.
> But, another big win is that you can read the current pin sense just
> by reading this element.
> 
> I think this is a sort of feature Lennart wanted for PA.
> Lennart, does it make sense?

Yes. I think it would. Also, if we can use the name of a control to
find the jack sensing control for it this would be great. I.e. if we
have a control "Headphone" and the Jack sensing control for it would
then be called "Headphone Jack" or so, this would be great! 

Right now the only way to identify the purpose of a mixer element is
by knowing it and going by the name. Would be good if that would be
made easy for jack sensing controls.

This also relieves us a bit from the little ugliness of having to
manage permissions for those input devices differently from other
input devices.

Lennart

-- 
Lennart Poettering                        Red Hat, Inc.
lennart [at] poettering [dot] net
http://0pointer.net/lennart/           GnuPG 0x1A015CC4

  parent reply	other threads:[~2009-06-19 12:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-19  8:04 RFC: Jack-detection control elements on HD-audio Takashi Iwai
2009-06-19  8:54 ` Jaroslav Kysela
2009-06-19  9:02   ` Takashi Iwai
2009-06-19 12:34   ` Lennart Poettering
2009-06-19  9:53 ` Mark Brown
2009-06-19 10:08   ` Takashi Iwai
2009-06-19 16:37     ` Mark Brown
2009-07-02 22:27     ` pl bossart
2009-07-03  5:32       ` Takashi Iwai
2009-06-19 12:21 ` Lennart Poettering [this message]
2009-06-19 12:31   ` Takashi Iwai

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=20090619122126.GA5785@tango.0pointer.de \
    --to=mznyfn@0pointer.de \
    --cc=alsa-devel@alsa-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.