From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Matthias Grimm <joker@cymes.de>,
PPC-Dev Mailingliste <linuxppc-dev@lists.linuxppc.org>
Subject: Re: muteing speakers if headphones were plugged in?
Date: Tue, 16 Apr 2002 18:30:26 +0100 [thread overview]
Message-ID: <20020416173026.16606@smtp.wanadoo.fr> (raw)
In-Reply-To: <3CBC59C0.7000505@cymes.de>
>
>Hi,
>
>I was asked to built a new feature into pbbuttons: To mute the speakers
>if headphones are plugged in.
It's already implemented at the driver level for some chipsets.
>I don't know where to get the information if headphones are plugged in
>or not, so I had a look into the recent kernel and I saw some code (for
>eg. headphone_intr() ) that seems to do what I am asked for. On the
>other hand the code seems very experimental and not really complete as I
>could see at some comments.
>
>What is the status? Should this feature (muting the speakers ...) be
>part of the kernel or was it only a fast shot to get it work?
It works with recent drivers though only if your chipset is Tumbler afaik.
>I saw the most headphone code within the Tumbler section so I assume
>that it would only work on new TiBooks and iBooks?
Yes.
>Nevertheless is there a method to get the information of the line-in
>jack status from user space?
Not that I know of, but I don't know the OSS API that well, it may
be possible to add this information to what is returned from the driver.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-04-16 17:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-16 17:05 muteing speakers if headphones were plugged in? Matthias Grimm
2002-04-16 17:30 ` Benjamin Herrenschmidt [this message]
2002-04-17 15:23 ` Matthias Grimm
2002-04-17 18:56 ` benh
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=20020416173026.16606@smtp.wanadoo.fr \
--to=benh@kernel.crashing.org \
--cc=joker@cymes.de \
--cc=linuxppc-dev@lists.linuxppc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).