From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Robert Jarzmik <rjarzmik@free.fr>
Cc: alsa-devel@alsa-project.org,
Sean Thayne <sthayne@summitmediagroupllc.com>
Subject: Re: How can you tell if the speaker jack on your sound card has anything plugged into it???
Date: Fri, 25 Apr 2008 22:40:26 +0100 [thread overview]
Message-ID: <20080425214026.GB25041@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <87fxt9k5ge.fsf@free.fr>
On Fri, Apr 25, 2008 at 11:08:49PM +0200, Robert Jarzmik wrote:
> Isn't the event api switch "SW_HEADPHONE_INSERT" standard ?
> I thought it was designed for such use.
Yes. It'll also need extending to cover things that can detect jack
insertions other than headphones (espcailly usefully for devices that
can identify what is plugged into the jack).
> 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);
Indeed, and hopefully it'll get more widely adopted, at least for
embedded stuff. Unfortunately adoption is currently rather limited -
the only in-tree users are the Zaurus machines.
I'm currently working on some helpers for ALSA for this.
next prev parent reply other threads:[~2008-04-25 21:40 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
2008-04-25 21:32 ` Tobin Davis
2008-04-25 21:55 ` Mark Brown
2008-04-25 21:40 ` Mark Brown [this message]
-- 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=20080425214026.GB25041@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=rjarzmik@free.fr \
--cc=sthayne@summitmediagroupllc.com \
/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.