From: Tobin Davis <tdavis@dsl-only.net>
To: Robert Jarzmik <rjarzmik@free.fr>
Cc: alsa-devel@alsa-project.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
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 14:32:42 -0700 [thread overview]
Message-ID: <1209159162.32245.63.camel@razman> (raw)
In-Reply-To: <87fxt9k5ge.fsf@free.fr>
The snd_hda_intel driver does this internally to mute the speakers when
headphones are plugged in. Ditto for front mic. But you are right, we
need a standard way of tracking this. I am exploring the HAL interface
now to see what I can learn from it. And most sound chips have an
insert detection mechanism. Usually they are wired to specific jacks,
but sometimes they just register a change in plug state, and read the
jack's impedance levels to know which jack is used. It is documented in
the Sigmatel/IDT, Realtek, and Analog Devices codec PRMs.
Tobin
On Fri, 2008-04-25 at 23:08 +0200, Robert Jarzmik 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);
>
> --
> Robert
>
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
--
Tobin Davis
All of the true things I am about to tell you are shameless lies.
-- The Book of Bokonon / Kurt Vonnegut Jr.
next prev parent reply other threads:[~2008-04-25 21:32 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 [this message]
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=1209159162.32245.63.camel@razman \
--to=tdavis@dsl-only.net \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox