From: Lennart Poettering <mznyfn@0pointer.de>
To: alsa-devel@alsa-project.org
Subject: Re: How can you tell if the speaker jack on your sound card has anything plugged into it???
Date: Fri, 25 Apr 2008 23:28:40 +0200 [thread overview]
Message-ID: <20080425212839.GA20087@tango.0pointer.de> (raw)
In-Reply-To: <87fxt9k5ge.fsf@free.fr>
On Fri, 25.04.08 23:08, Robert Jarzmik (rjarzmik@free.fr) wrote:
>
> Mark Brown <broonie@opensource.wolfsonmicro.com> writes:
>
> > There's currently no standard way of getting this information from user
> > space even where the hardware provides it.
> Isn't the event api switch "SW_HEADPHONE_INSERT" standard ?
> I thought it was designed for such use.
>
> If I'm not mistaken, the Neo teams handles it that way, as I do for the mio :
> -> input_report_switch(mioa701_evdev, SW_HEADPHONE_INSERT, val);
AFAIK HDA generally supports Jack Sensing. However
it's not wired up properly on all hardware. And there's no driver support
in the Linux HDA driver to generate an input device for jack
sensing.
But I might be mistaken. Takashi and Jaroslav know the current state
of Jack Sensing on Linux much better.
Lennart
--
Lennart Poettering Red Hat, Inc.
lennart [at] poettering [dot] net ICQ# 11060553
http://0pointer.net/lennart/ GnuPG 0x1A015CC4
next prev parent reply other threads:[~2008-04-25 21:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-25 19:29 How can you tell if the speaker jack on your sound card has anything plugged into it??? Sean Thayne
2008-04-25 19:49 ` Mark Brown
2008-04-25 20:53 ` Sean Thayne
2008-04-25 20:56 ` Timur Tabi
2008-04-25 21:02 ` Sean Thayne
2008-04-25 21:04 ` Timur Tabi
2008-04-25 22:02 ` Mark Brown
2008-04-25 21:08 ` Robert Jarzmik
2008-04-25 21:28 ` Lennart Poettering [this message]
2008-04-25 21:32 ` Tobin Davis
2008-04-25 21:55 ` Mark Brown
2008-04-25 21:40 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2008-04-25 19:29 Sean Thayne
2008-04-25 19:28 Sean Thayne
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=20080425212839.GA20087@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.