All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Jaroslav Kysela <perex@perex.cz>
Cc: alsa-devel@alsa-project.org, Lennart Poettering <mznyfn@0pointer.de>
Subject: Re: RFC: Jack-detection control elements on HD-audio
Date: Fri, 19 Jun 2009 11:02:27 +0200	[thread overview]
Message-ID: <s5hd490egv0.wl%tiwai@suse.de> (raw)
In-Reply-To: <alpine.LNX.2.00.0906191048150.3983@eeebox2.perex-int.cz>

At Fri, 19 Jun 2009 10:54:00 +0200 (CEST),
Jaroslav Kysela wrote:
> 
> On Fri, 19 Jun 2009, Takashi Iwai 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.
> 
> Before definining such extension, I would really see to define standard 
> control names in Documentation/ControlNames.txt file. It seems to me that 
> most new drivers does not follow suggested naming. The document should be 
> reviewed, of course.

That's true.  We definitely need a standard naming.

But note that these controls are no mixers but provided as IFACE_CARD,
so they won't pollute the mixer abstraction.  So, it's rather the
question of the user of these controls.


Takashi

  reply	other threads:[~2009-06-19  9:02 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 [this message]
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
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=s5hd490egv0.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=mznyfn@0pointer.de \
    --cc=perex@perex.cz \
    /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.